From owner-freebsd-xen@FreeBSD.ORG Mon Aug 1 03:45:17 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F1CA106566C for ; Mon, 1 Aug 2011 03:45:17 +0000 (UTC) (envelope-from armondbc@gmail.com) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 162768FC0C for ; Mon, 1 Aug 2011 03:45:16 +0000 (UTC) Received: by qwc9 with SMTP id 9so3626258qwc.13 for ; Sun, 31 Jul 2011 20:45:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=8jyLjZNK72qA8/ZLXeIo9NNu7P9fyO4Ssn71t8sMsP4=; b=vTv9bKhhuntjRqMc95czSc2DXt/A2XgeTBmM1r7EzkEvnkGaQB1f92nOIoLu4Kwshw w7rOlZhU52Ev6AcU/Q5R1j8BmDWQZ51iI2qJF2KB5Y4XX0tMNttQYw1vp7Uw9tlGMcxG xtJhxYxdyKbWYo4YyftXHjwYX8P3VV+XPqlHQ= MIME-Version: 1.0 Received: by 10.229.14.158 with SMTP id g30mr2384240qca.34.1312168932325; Sun, 31 Jul 2011 20:22:12 -0700 (PDT) Received: by 10.229.187.18 with HTTP; Sun, 31 Jul 2011 20:22:12 -0700 (PDT) Date: Sun, 31 Jul 2011 22:22:12 -0500 Message-ID: From: "Ben C." To: freebsd-xen@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Networking issues with FreeBSD HVM + SMP X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Aug 2011 03:45:17 -0000 Hello all, Thanks for taking time to read this post. It's a fairly long winded tale of confusion, but here goes: * I originally installed FreeBSD 8.2-RELEASE fine working under 100% HVM. Using the GENERIC kernel with xen's qemu * I trashed the box (kind of willingly, it's been a while since I've had the pleasure of FreeBSD and think of it as my first pancake) * Reinstalled. Networking failed. I had no idea why. Several weeks past, I finally got networking back working after about 20-30 install attempts. * Setup the box properly. * Did some changes throughout the dom0/domu's - I had originally had the vcpu's pinned to physical cpu's and all this mojo. I found that my load averages on the dom0 were significantly lower when the vcpu's were bound to 'any physical' -- but that's beside the point. The point is, FreeBSD changed vcpu's from 1 to 2 - and networking stopped. * I honestly thought it surely was something else. I triple-checked and confirmed, when vcpu=1, networking worked as expected. When vcpu was >1, networking failed with a vauge .. em0 (or re0, see below) .. watchdog timeout spewing all over. If you take a look at my configuration below, I originally had model=e1000 in the vif, which I *thought* was what made it work originally. I was apprently wrong. vcpu pinning doesn't matter. Essentially, if it has more than 1 (v)cpu's, networking fails. The dom0 is running NetBSD -CURRENT [current there is just like current here], on an Intel i7. I could try the -current branch or using the xenhvm kernel/drivers. I'm fairly sure the latter may help the situation, but honestly I'm just a bit bothered by the strangeness of this "bug". Does anyone else have any suggestions on what I should try next? Thanks for your time, Ben name ="a5freebsd" memory = 2048 kernel = "/usr/pkg/lib/xen/boot/hvmloader" builder='hvm' device_model = '/usr/pkg/libexec/qemu-dm' disk = [ 'phy:/dev/mapper/rxenpool-a5freebsd_root,ioemu:hda,w', 'file:/home/xen/iso/FreeBSD-8.2-RELEASE-amd64-disc1.iso,ioemu:hdc:cdrom,r' ] boot = 'cd' vcpus=2 #cpus=['2'] #vif=[ 'type=ioemu,bridge=bridge0,model=e1000,mac=00:16:3e:4f:bb:78' ] vif=[ 'type=ioemu,bridge=bridge0,mac=00:16:3e:4f:bb:78' ] vnc = 1 vncdisplay = 2 vnclisten = "1.2.3.4" vncpasswd = "removed" on_reboot = 'restart' on_crash = 'restart' usbdevice = 'tablet' From owner-freebsd-xen@FreeBSD.ORG Mon Aug 1 11:07:22 2011 Return-Path: Delivered-To: freebsd-xen@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9264106568D for ; Mon, 1 Aug 2011 11:07:22 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AE5AE8FC17 for ; Mon, 1 Aug 2011 11:07:22 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p71B7Mf3014775 for ; Mon, 1 Aug 2011 11:07:22 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p71B7MbB014773 for freebsd-xen@FreeBSD.org; Mon, 1 Aug 2011 11:07:22 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 1 Aug 2011 11:07:22 GMT Message-Id: <201108011107.p71B7MbB014773@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-xen@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-xen@FreeBSD.org X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Aug 2011 11:07:22 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/155468 xen [xen] Xen PV i386 multi-kernel CPU system is not worki o kern/155353 xen [xen] [patch] put "nudging TOD" message under boot_ver o kern/154833 xen [xen]: xen 4.0 - DomU freebsd8.2RC3 i386, XEN kernel. o kern/154473 xen [xen] xen 4.0 - DomU freebsd8.1 i386, XEN kernel. Not o kern/154472 xen [xen] xen 4.0 - DomU freebsd8.1 i386 xen kernel reboot o kern/154428 xen [xen] xn0 network interface and PF - Massive performan o kern/154302 xen [xen] [panic] [patch] xn0: Error 2 parsing device/vif/ o kern/153789 xen [xen] [regression] FreeBSD 8.2-RC1 crashes under Solar o kern/153674 xen [xen] i386/XEN idle thread shows wrong percentages o kern/153672 xen [xen] [panic] i386/XEN panics under heavy fork load o kern/153620 xen [xen] Xen guest system clock drifts in AWS EC2 (FreeBS o kern/153477 xen [xen] XEN pmap code abuses vm page queue lock o kern/153150 xen [xen] xen/ec2: disable checksum offloading on interfac o kern/152228 xen [xen] [panic] Xen/PV panic with machdep.idle_mwait=1 o kern/144629 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143398 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor o kern/143340 xen [xen] FreeBSD 8-RELEASE XEN pvm networking doesn't wor f kern/143069 xen [xen] [panic] Xen Kernel Panic - Memory modified after f kern/135667 xen ufs filesystem corruption on XEN DomU system f kern/135421 xen [xen] FreeBSD Xen PVM DomU network failure - netfronc. f kern/135178 xen [xen] Xen domU outgoing data transfer stall when TSO i p kern/135069 xen [xen] FreeBSD-current/Xen SMP doesn't function at all f i386/124516 xen [xen] FreeBSD-CURRENT Xen Kernel Segfaults when config o kern/118734 xen [xen] FreeBSD 6.3-RC1 and FreeBSD 7.0-BETA 4 fail to b 24 problems total. From owner-freebsd-xen@FreeBSD.ORG Mon Aug 1 16:32:49 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E6461065781 for ; Mon, 1 Aug 2011 16:32:49 +0000 (UTC) (envelope-from seanbru@yahoo-inc.com) Received: from mrout1-b.corp.re1.yahoo.com (mrout1-b.corp.re1.yahoo.com [69.147.107.20]) by mx1.freebsd.org (Postfix) with ESMTP id DDF7C8FC19 for ; Mon, 1 Aug 2011 16:32:48 +0000 (UTC) Received: from [127.0.0.1] (cheese.corp.yahoo.com [216.145.50.99]) by mrout1-b.corp.re1.yahoo.com (8.14.4/8.14.4/y.out) with ESMTP id p71GWVfp028582; Mon, 1 Aug 2011 09:32:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=yahoo-inc.com; s=cobra; t=1312216352; bh=ODeqgBllQMhNMOHhVEA2/I9Z81ydNWXxM+mfqf+YyOA=; h=Subject:From:To:Cc:In-Reply-To:References:Content-Type:Date: Message-ID:Mime-Version:Content-Transfer-Encoding; b=GX332ljT73t86mLx3w0qOP7jBocls37d3+N2zJvU4sM+eESCO1ZFFgk6qteUwzkd/ 8XvxMlgE7obk41UrStrvLHXYDHvBQ/xLTlEikFZ+4OYamPE3BQFHonK5n1xptswaXx S3AU3KNphI1fIuGDmc2qid5+fRDkANyrgOB60ZUI= From: Sean Bruno To: "Ben C." In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Date: Mon, 01 Aug 2011 09:32:31 -0700 Message-ID: <1312216351.2872.4.camel@hitfishpass-lx.corp.yahoo.com> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 (2.32.2-1.fc14) Content-Transfer-Encoding: 7bit Cc: "freebsd-xen@freebsd.org" Subject: Re: Networking issues with FreeBSD HVM + SMP X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 01 Aug 2011 16:32:49 -0000 On Sun, 2011-07-31 at 20:22 -0700, Ben C. wrote: > Hello all, > > Thanks for taking time to read this post. It's a fairly long winded > tale of confusion, but here goes: > > * I originally installed FreeBSD 8.2-RELEASE fine working under 100% > HVM. Using the GENERIC kernel with xen's qemu > * I trashed the box (kind of willingly, it's been a while since I've > had the pleasure of FreeBSD and think of it as my first pancake) > * Reinstalled. Networking failed. I had no idea why. Several weeks > past, I finally got networking back working after about 20-30 install > attempts. > * Setup the box properly. > * Did some changes throughout the dom0/domu's - I had originally had > the vcpu's pinned to physical cpu's and all this mojo. I found that > my load averages on the dom0 were significantly lower when the vcpu's > were bound to 'any physical' -- but that's beside the point. The > point is, FreeBSD changed vcpu's from 1 to 2 - and networking stopped. > * I honestly thought it surely was something else. I triple-checked > and confirmed, when vcpu=1, networking worked as expected. When vcpu > was >1, networking failed with a vauge .. em0 (or re0, see below) .. > watchdog timeout spewing all over. > > If you take a look at my configuration below, I originally had > model=e1000 in the vif, which I *thought* was what made it work > originally. I was apprently wrong. vcpu pinning doesn't matter. > Essentially, if it has more than 1 (v)cpu's, networking fails. > > The dom0 is running NetBSD -CURRENT [current there is just like > current here], on an Intel i7. I could try the -current branch or > using the xenhvm kernel/drivers. I'm fairly sure the latter may help > the situation, but honestly I'm just a bit bothered by the strangeness > of this "bug". Does anyone else have any suggestions on what I > should try next? > > Thanks for your time, Ben > > > name ="a5freebsd" > memory = 2048 > > kernel = "/usr/pkg/lib/xen/boot/hvmloader" > builder='hvm' > device_model = '/usr/pkg/libexec/qemu-dm' > > disk = [ > 'phy:/dev/mapper/rxenpool-a5freebsd_root,ioemu:hda,w', > 'file:/home/xen/iso/FreeBSD-8.2-RELEASE-amd64-disc1.iso,ioemu:hdc:cdrom,r' > ] > boot = 'cd' > > vcpus=2 > #cpus=['2'] > > > #vif=[ 'type=ioemu,bridge=bridge0,model=e1000,mac=00:16:3e:4f:bb:78' ] > vif=[ 'type=ioemu,bridge=bridge0,mac=00:16:3e:4f:bb:78' ] > > vnc = 1 > vncdisplay = 2 > vnclisten = "1.2.3.4" > vncpasswd = "removed" > > on_reboot = 'restart' > on_crash = 'restart' > > usbdevice = 'tablet' I haven't tried the e1000 emulation on the refernce build Xen images in the cluster yet, but when I use the stock Generic kernel I seem to be using re(4). Not that this really matters, but its a reference point. Also, I kind of gave up on the NetBSD dom0 a while ago so I could get stuff working in the cluster. Currently I'm utilizing a CentOS 5.6 Dom0 with Xen 3.4.3 from http://www.gitco.de/repo/ Here's the config I'm using for ref8-xen64.freebsd.org that seems to be the most likely thing to work: #============================================================================ # Python configuration setup for 'xm create'. # This script sets the parameters used when a domain is created using 'xm create'. # You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #============================================================================ #---------------------------------------------------------------------------- # Kernel image file. kernel = "/usr/lib/xen/boot/hvmloader" #---------------------------------------------------------------------------- # device model to use: only qemu-dm available for now device_model = '/usr/lib64/xen/bin/qemu-dm' builder='hvm' # Initial memory allocation (in megabytes) for the new domain. memory = 1024 # number of CPUS vcpus = 2 # A name for your domain. All domains must have different names. name = "ref8-xen64" arch = "x86_64" #Network interface. By default emules a realtek 8139. For a NetBSD guest you # have to disable re(4) and let rtk attach to use it. # ne2k_pci emulates a pci ne2000 clone; this his cpu-hungry in dom0 # pcnet emulates a AMD PCnet-PCI controller; but it corrupts packets with # pcn(4) under NetBSD. vif = [ 'mac=00:16:3e:00:00:02, bridge=xenbr0, type=ioemu' ] #vif = [ 'mac=00:16:3e:00:00:02, bridge=xenbr0, type=vbd' ] # Define the disk devices you want the domain to have access to, and # what you want them accessible as. # Each disk entry is of the form phy:UNAME,DEV,MODE # where UNAME is the device, DEV is the device name the domain will see, # and MODE is r for read-only, w for read-write. # For hvm domains you can only use hda to hdd. You can set extra types # (e.g. cdrom) disk = [ 'file:/var/virt/FreeBSD-8.2-RELEASE-amd64-disc1.iso,hdc:cdrom,r', 'file:/var/virt/ref8-xen64.bin,hda,w' ] # floppy images; this doesn't seem to work currently. Use a iso image instead. #fda = '/home/domains/boot1.fs' # boot device: a = floppy, c= hard drive, d= cdrom (with the disk entry # before) # # boot CDROM image #boot='d' # boot from DISK file boot='c' # By default, 'xm create' will try to open an X window on the current display # for the virtal framebuffer. You can have the virtal framebuffer in vnc # instead, and connect using a vnc client (using localhost:$vncdisplay) # If vncunused is set to 1 (this is the default value), vncdisplay # will be set to the first unused port; so it's recommended to vnc = 1 vncdisplay = 2 vncunused = 1 vncpasswd='' #Xen emulates a PS/2 mouse, but the pointer in the guest has difficulties # tracking the absolute position. Xen can emulate a USB tablet in addition # to the mouse which will report the absolute position of the pointer, # and make the mouse much easier to use. # usb=1 usbdevice='tablet' #usbdevice='mouse' serial='pty' on_reboot='restart' #============================================================================ From owner-freebsd-xen@FreeBSD.ORG Thu Aug 4 18:44:59 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDFA1106564A for ; Thu, 4 Aug 2011 18:44:59 +0000 (UTC) (envelope-from hugo@barafranca.com) Received: from mail.barafranca.com (mail.barafranca.com [67.213.67.47]) by mx1.freebsd.org (Postfix) with ESMTP id C05E38FC13 for ; Thu, 4 Aug 2011 18:44:59 +0000 (UTC) Received: from localhost (unknown [172.16.100.24]) by mail.barafranca.com (Postfix) with ESMTP id 7F9498F9 for ; Thu, 4 Aug 2011 18:31:54 +0000 (UTC) X-Virus-Scanned: amavisd-new at barafranca.com Received: from mail.barafranca.com ([172.16.100.24]) by localhost (mail.barafranca.com [172.16.100.24]) (amavisd-new, port 10024) with ESMTP id lpWjfUuZxYap for ; Thu, 4 Aug 2011 18:31:15 +0000 (UTC) Received: from [192.168.1.1] (a89-152-172-232.cpe.netcabo.pt [89.152.172.232]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.barafranca.com (Postfix) with ESMTPSA id C04128F6 for ; Thu, 4 Aug 2011 18:31:14 +0000 (UTC) Message-ID: <4E3AE57D.3050600@barafranca.com> Date: Thu, 04 Aug 2011 19:31:25 +0100 From: Hugo Silva User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: "freebsd-xen@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: 9.0-BETA1: PV network still won't work with NetBSD dom0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Aug 2011 18:45:00 -0000 I'm giving 9.0 a spin here. So far so good! With the exception of this one thing; With a NetBSD dom0, the FreeBSD HVM+PV domU (7.x, 8.x, 9.0-BETA1) behaves strangely in the network; trying to ssh to it from my laptop yeilds: Bad packet length 3737169374. Disconnecting: Packet corrupt Disabling TSO, RXCSUM and TXCSUM on xn0 results in: )$ ssh %domU_ip load: 0.53 cmd: ssh 3101 [select] 0.48r 0.01u 0.01s 0% 4248k load: 0.53 cmd: ssh 3101 [select] 0.66r 0.01u 0.01s 0% 4248k load: 0.53 cmd: ssh 3101 [select] 0.83r 0.01u 0.01s 0% 4248k And on the console of the domU: xn_txeof: WARNING: response is -1! NetBSD (5.x, -current), Linux and OpenIndiana PV domUs work as expected. What could be the cause? Keep up the good work on the OS! Best regards, Hugo From owner-freebsd-xen@FreeBSD.ORG Sat Aug 6 14:17:54 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1973106564A for ; Sat, 6 Aug 2011 14:17:54 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id BC4388FC08 for ; Sat, 6 Aug 2011 14:17:54 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 4BCC746B06; Sat, 6 Aug 2011 10:17:54 -0400 (EDT) Date: Sat, 6 Aug 2011 15:17:54 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Sean Bruno In-Reply-To: <1311986628.2531.15.camel@hitfishpass-lx.corp.yahoo.com> Message-ID: References: <1311986628.2531.15.camel@hitfishpass-lx.corp.yahoo.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: "freebsd-xen@freebsd.org" Subject: Re: BETA-1 NFS not working, Xen PV i386 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Aug 2011 14:17:55 -0000 On Fri, 29 Jul 2011, Sean Bruno wrote: > Doesn't make a lot of sense here, but building with the i386 XEN kernel > config yields the following boot up in PV mode. > > Odd ... it looks like i386/XEN needs: > > options NFSCL # New Network Filesystem Client Yes -- in general, I consider the existence of a XEN configuration that isn't derived from "include GENERIC" to be a mistake. However, there's a somewhat tricky balance in terms of enumerating device drivers, etc. Someone(tm) needs to sync the XEN kernel to GENERIC before we ship to make sure it's generally in line, but in the long term it will remain a maintenance problem. Robert > > Sean > > Using config file "./ref9-xen32". > Started domain ref9-xen32 (id=38) > WARNING: loader(8) metadata is missing! > GDB: no debug ports present > KDB: debugger backends: ddb > KDB: current backend: ddb > Copyright (c) 1992-2011 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights > reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 9.0-BETA1 #0 r224482M: Fri Jul 29 13:34:25 PDT 2011 > > root@ref9-xen32.freebsd.org:/usr/obj/dumpster/scratch/sbruno-scratch/head/sys/XEN i386 > WARNING: WITNESS option enabled, expect reduced performance. > Xen reported: 2493.756 MHz processor. > Timecounter "ixen" frequency 1953125 Hz quality 0 > CPU: Intel(R) Xeon(R) CPU L5420 @ 2.50GHz (2493.76-MHz > 686-class CPU) > Origin = "GenuineIntel" Id = 0x10676 Family = 6 Model = 17 > Stepping = 6 > > Features=0xbfe3fbff > > Features2=0xce3bd > AMD Features=0x20100000 > AMD Features2=0x1 > real memory = 805306368 (768 MB) > avail memory = 777121792 (741 MB) > [XEN] IPI cpu=0 irq=128 vector=RESCHEDULE_VECTOR (0) > [XEN] IPI cpu=0 irq=129 vector=CALL_FUNCTION_VECTOR (1) > [XEN] xen_rtc_probe: probing Hypervisor RTC clock > rtc0: on motherboard > [XEN] xen_rtc_attach: attaching Hypervisor RTC clock > xenstore0: on motherboard > xc0: on motherboard > Event timer "ixen" quality 600 > Timecounters tick every 10.000 msec > xenbusb_front0: on xenstore0 > [XEN] hypervisor wallclock nudged; nudging TOD. > xn0: at device/vif/0 on xenbusb_front0 > xn0: Ethernet address: 00:16:3e:00:00:03 > xenbusb_back0: on xenstore0 > xctrl0: on xenstore0 > xbd0: 497MB at device/vbd/5632 on xenbusb_front0 > xbd0: attaching as ad2 > xbd1: 10240MB at device/vbd/768 on xenbusb_front0 > xbd1: attaching as ad0 > Timecounter "TSC" frequency 2493756000 Hz quality 800 > WARNING: WITNESS option enabled, expect reduced performance. > Trying to mount root from ufs:/dev/ad0p2 []... > WARNING: / was not properly dismounted > rtc0: [XEN] xen_rtc_gettime > rtc0: [XEN] xen_rtc_gettime: wallclock 1311892419 sec; 132269700 nsec > rtc0: [XEN] xen_rtc_gettime: uptime 94008 sec; 379306109 nsec > rtc0: [XEN] xen_rtc_gettime: TOD 1311986427 sec; 511575809 nsec > Setting hostuuid: 1c127834-ab5a-c2e4-7b24-5ea29d364d9d. > Setting hostid: 0xdea9fbfd. > Entropy harvesting: interrupts ethernet point_to_point kickstart. > Starting file system checks: > ** SU+J Recovering /dev/ad0p2 > ** Reading 33554432 byte journal from inode 4. > ** Building recovery table. > ** Resolving unreferenced inode list. > ** Processing journal entries. > > ***** FILE SYSTEM MARKED CLEAN ***** > Mounting local file systems:. > Setting hostname: ref9-xen32.freebsd.org. > xn0: link state changed to DOWN > xn0: link state changed to UP > Starting Network: lo0 xn0. > lo0: flags=8049 metric 0 mtu 16384 > options=3 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 > inet 127.0.0.1 netmask 0xff000000 > nd6 options=21 > xn0: flags=8843 metric 0 mtu > 1500 > options=503 > ether 00:16:3e:00:00:03 > nd6 options=29 > media: Ethernet manual > status: active > Starting devd. > DHCPREQUEST on xn0 to 255.255.255.255 port 67 > DHCPACK from 69.147.83.62 > bound to 69.147.83.99 -- renewal in 900 seconds. > add net ::ffff:0.0.0.0: gateway ::1 > add net ::0.0.0.0: gateway ::1 > add net fe80::: gateway ::1 > add net ff02::: gateway ::1 > kldload: can't load nfscl: File exists > /etc/rc: WARNING: Unable to load kernel module nfscl > ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib > a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout > Creating and/or trimming log files. > Starting syslogd. > No core dumps found. > Setting date via ntp. > rtc0: [XEN] xen_rtc_settime > 29 Jul 17:40:33 ntpdate[585]: step time server 69.147.83.54 offset > -25202.462526 sec > kldload: can't load nfscl: File exists > /etc/rc: WARNING: Unable to load kernel module nfscl > Setting NIS domain: freebsd. > Starting rpcbind. > Starting ypbind. > Clearing /tmp (X related). > Updating motd:. > Mounting late file systems:mount_nfs: nfscl is not available > mount_nfs: nfscl is not available > mount_nfs: nfscl is not available > . > Mounting /etc/fstab filesystems failed, startup aborted > ERROR: ABORTING BOOT (sending SIGTERM to parent)! > Jul 29 17:40:34 ref9-xen32 init: /bin/sh on /etc/rc terminated > abnormally, going to single user mode > Enter full pathname of shell or RETURN for /bin/sh: > > > _______________________________________________ > freebsd-xen@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-xen > To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" > From owner-freebsd-xen@FreeBSD.ORG Sat Aug 6 15:15:38 2011 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id E377C1065670 for ; Sat, 6 Aug 2011 15:15:38 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from xps.daemonology.net (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx2.freebsd.org (Postfix) with SMTP id D0C3A151F9F for ; Sat, 6 Aug 2011 15:15:24 +0000 (UTC) Received: (qmail 63173 invoked from network); 6 Aug 2011 15:15:23 -0000 Received: from unknown (HELO xps.daemonology.net) (127.0.0.1) by localhost with SMTP; 6 Aug 2011 15:15:23 -0000 Message-ID: <4E3D5A8A.4070104@freebsd.org> Date: Sat, 06 Aug 2011 08:15:22 -0700 From: Colin Percival User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20101220 Thunderbird/3.0.11 MIME-Version: 1.0 To: Robert Watson References: <1311986628.2531.15.camel@hitfishpass-lx.corp.yahoo.com> In-Reply-To: X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-xen@freebsd.org" , Sean Bruno Subject: Re: BETA-1 NFS not working, Xen PV i386 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Aug 2011 15:15:39 -0000 On 08/06/11 07:17, Robert Watson wrote: > On Fri, 29 Jul 2011, Sean Bruno wrote: >> Doesn't make a lot of sense here, but building with the i386 XEN >> kernel config yields the following boot up in PV mode. >> >> Odd ... it looks like i386/XEN needs: >> >> options NFSCL # New Network Filesystem Client > > Yes -- in general, I consider the existence of a XEN configuration that > isn't derived from "include GENERIC" to be a mistake. However, there's > a somewhat tricky balance in terms of enumerating device drivers, etc. > Someone(tm) needs to sync the XEN kernel to GENERIC before we ship to > make sure it's generally in line, but in the long term it will remain a > maintenance problem. I don't think XEN should be derived from GENERIC as it currently exists; there is an awful lot of stuff in GENERIC which doesn't make any sense to have in a PV environment. Maybe if GENERIC was split into separate "physical" and "logical" sets of options (so that XEN could suck in stuff like nfs without having drivers for hardware it will never see) the problems would be less? -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid