From justin.conover at gmail.com Wed Mar 1 14:35:20 2006 From: justin.conover at gmail.com (Justin Conover) Date: Wed, 1 Mar 2006 08:35:20 -0600 Subject: [Fedora-xen] Request for comments: Xen on centrino thinkpads In-Reply-To: References: Message-ID: On 2/28/06, Kevin Verma wrote: > > Hello, > > Some times ago, some where I had read that Xen does not work on > centrino based thinkpads, is that still true ? > > I had tried to run xen on my thinkpad r50e having a centrino processor > over FC4 but xen-hypervisor never booted succesfuly. > > I will be very much thankful for any of yours inputs to my questions > above. > > Thanks for reading, > Kevin > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen I have ran it off/on on a Dell Latitude D600 with Rawhide. I would like to use it all the time, however I do need vmware for w2k(work) so I get stuck since the vmware modules wont build into the xen kernel. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Axel.Thimm at ATrpms.net Wed Mar 1 15:45:45 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Wed, 1 Mar 2006 16:45:45 +0100 Subject: [Fedora-xen] Re: initscripts, xen and bonding In-Reply-To: <20060224232820.GD5644@devserv.devel.redhat.com> References: <20060224231311.GP21359@neu.nirvana> <20060224232820.GD5644@devserv.devel.redhat.com> Message-ID: <20060301154545.GA24276@neu.nirvana> On Fri, Feb 24, 2006 at 06:28:20PM -0500, Bill Nottingham wrote: > Axel Thimm (Axel.Thimm at ATrpms.net) said: > > I'm having a hard time getting bonding to work on FC5t3. > > Not surprising. The way Xen does its bridging breaks bonding > fairly badly. > > It's possible it could be fixed in the xen scripts, but I don't > think it's been looked at. I now jumped into the xen networking concepts. These make sense, but there are two issues: a) bonding should be performed onto the "physical" bonding interface, which xen renames to pbond0. Still the initscripts only work with MASTER=pbond0 if called *after* completion of the boot process. b) even if a) is fixed and requires MASTER=pbond0 setting, the switching from a xen kernel to a non-xen kernel the configuration in the initscripts would be bogus (pointing to a nonexisting pbond0), and the bonding device would be w/o slaves. I don't understand why a) happens, seems to be dependent on the order of the steps performed. Maybe the bonding/enslaving (at boot time) happens before xen renames the bond0 device and later on the enslaving is wrong. Reruning the ifup scripts sees the renamed devices and performs properly. That's a theory at least. I'm not sure how to solve b). Ideally one would like to not have xen specific actions in initscripts, but otherwise one risks cutting of the system of the net completely when upgrading kernels and booting into the wron one. Probably not something one wants when setting up bonding to ensure network availability. ;) Should I file a bugzilla? xen or initscripts? -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 191 bytes Desc: not available URL: From notting at redhat.com Wed Mar 1 16:43:44 2006 From: notting at redhat.com (Bill Nottingham) Date: Wed, 1 Mar 2006 11:43:44 -0500 Subject: [Fedora-xen] Re: initscripts, xen and bonding In-Reply-To: <20060301154545.GA24276@neu.nirvana> References: <20060224231311.GP21359@neu.nirvana> <20060224232820.GD5644@devserv.devel.redhat.com> <20060301154545.GA24276@neu.nirvana> Message-ID: <20060301164344.GA28603@devserv.devel.redhat.com> Axel Thimm (Axel.Thimm at ATrpms.net) said: > I don't understand why a) happens, seems to be dependent on the order > of the steps performed. Maybe the bonding/enslaving (at boot time) > happens before xen renames the bond0 device and later on the enslaving > is wrong. Correct. > I'm not sure how to solve b). Ideally one would like to not have xen > specific actions in initscripts, but otherwise one risks cutting of > the system of the net completely when upgrading kernels and booting > into the wron one. Probably not something one wants when setting up > bonding to ensure network availability. ;) > > Should I file a bugzilla? xen or initscripts? Ideally, xen shouldn't be mucking with networking that much. It does it because of some supposed race. Bill > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list From fedora at adslpipe.co.uk Thu Mar 2 17:35:17 2006 From: fedora at adslpipe.co.uk (Andy Burns) Date: Thu, 02 Mar 2006 17:35:17 +0000 Subject: [Fedora-xen] minor Xorg screen corruption on radeon under xen dom0 In-Reply-To: <44023237.9060900@adslpipe.co.uk> References: <44023237.9060900@adslpipe.co.uk> Message-ID: <44072CD5.8000900@adslpipe.co.uk> Andy Burns wrote: > also if the machien was left for half a day or > so it wouldn't wake ut of screen saver and needed CTRL-ALT-BKSP to > kill/restart xorg. Though I'm still seeing (and have reported) the red line glitches, I'm pleased to say the X locking up hasn't happened on a machine that's been up for 2 whole days (which is relatively speaking a long up time while keeping updated with rawhide) From Danny_Trinh at Dell.com Fri Mar 3 15:51:32 2006 From: Danny_Trinh at Dell.com (Danny_Trinh at Dell.com) Date: Fri, 3 Mar 2006 09:51:32 -0600 Subject: [Fedora-xen] Xen and VNCviewer Message-ID: Hello group, I try to login to guest OS through vncviewer by doing the following steps: - install guest OS - do "xm create -c /etc/xen/fc5t3-i386-guest1" - login to guest OS through console; setup vncpasswd, vncserver; edit /etc/sysconfig/vncserver; make sure tcp 5901, 5801 ports are open; and "chkconfig vncserver on". - shutdown guest OS, and restart guest OS back by "xm create /etc/xen/fc5t3-i386-guest1" - I go to another machine and use vncviewer to connect to the guest OS, but I can't. - However, I can use ssh to connect to the guest OS. Am I missing some thing? Why didn't guest OS let me connect by using vncviewer? Is that the limitation? Thanks, Danny Trinh CNE, MCSE, RHCE, LPIC1, A+ Engineer Tech/Senior Analyst Linux OS Development Dell Computer Corporation From katzj at redhat.com Fri Mar 3 16:05:09 2006 From: katzj at redhat.com (Jeremy Katz) Date: Fri, 03 Mar 2006 11:05:09 -0500 Subject: [Fedora-xen] Xen and VNCviewer In-Reply-To: References: Message-ID: <1141401909.16502.13.camel@bree.local.net> On Fri, 2006-03-03 at 09:51 -0600, Danny_Trinh at Dell.com wrote: > Am I missing some thing? Why didn't guest OS let me connect by using > vncviewer? Is that the limitation? Check your firewall settings Jeremy From datto at charter.net Fri Mar 3 16:50:09 2006 From: datto at charter.net (Datto) Date: Fri, 3 Mar 2006 8:50:09 -0800 Subject: Fwd: RE: [Fedora-xen] Xen and VNCviewer Message-ID: <12753303.1141404609542.JavaMail.root@fepweb02> >> /etc/sysconfig/vncserver; This filename is actually /etc/sysconfig/vncservers Datto From Danny_Trinh at Dell.com Fri Mar 3 20:17:15 2006 From: Danny_Trinh at Dell.com (Danny_Trinh at Dell.com) Date: Fri, 3 Mar 2006 14:17:15 -0600 Subject: [Fedora-xen] xenguest-install.py + ks.cfg Message-ID: Hi group, First, I say thank to Jeremy for "Xen and VNCviewer" problem. Yes, it's firewall problem. Second, does anyone try using xenguest-install.py + ks.cfg? Please give me some hint/instruction/url. I got tired of sitting to finish guest OS installation(s). Thanks, Danny Trinh CNE, MCSE, RHCE, LPIC1, A+ Engineer Tech/Senior Analyst Linux OS Development Dell Computer Corporation From katzj at redhat.com Fri Mar 3 20:48:31 2006 From: katzj at redhat.com (Jeremy Katz) Date: Fri, 03 Mar 2006 15:48:31 -0500 Subject: [Fedora-xen] xenguest-install.py + ks.cfg In-Reply-To: References: Message-ID: <1141418911.16502.21.camel@bree.local.net> On Fri, 2006-03-03 at 14:17 -0600, Danny_Trinh at Dell.com wrote: > Second, does anyone try using xenguest-install.py + ks.cfg? Please give > me some hint/instruction/url. Add '-x ks=http://my.server/ks.cfg' to the exec of xenguest-install.py just like you'd add ks= on the kernel command line (you can add other command line options as well) Jeremy From justin.conover at gmail.com Sun Mar 5 04:41:58 2006 From: justin.conover at gmail.com (Justin Conover) Date: Sat, 4 Mar 2006 22:41:58 -0600 Subject: [Fedora-xen] Re: can't boot xen kernel In-Reply-To: References: <1140452048.3357.18.camel@orbit.scot.redhat.com> <1140648108.24084.27.camel@orbit.scot.redhat.com> Message-ID: On 2/22/06, Justin Conover wrote: > > > > On 2/22/06, Stephen C. Tweedie wrote: > > > > Hi, > > > > On Mon, 2006-02-20 at 17:00 -0600, Justin Conover wrote: > > > > > Adding init=1 to the xen/kernel line only allows it to go so far > > > before it just reboots it self, not far enough for me to even hit I or > > > > > do anything else. > > > > > > If I comment out the raid5 /dev/md2 /home in /etc/fstab the xen kernel > > > boots > > > > It's probably down to an SSE oops in the raid5 module. I'm not seeing > > it on x86_64 but it seems still there on i386. > > > > > Should I report a bug on this? > > > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177644 > > > > Cheers, > > Stephen > > > > > > > Thank you, > Looks like the 2009 kernel is now working on xen/smp/i386 uname -rmv 2.6.15-1.2009.4.2_FC5hypervisor #1 SMP Thu Mar 2 18:45:34 EST 2006 i686 df -h /dev/md2 Filesystem Size Used Avail Use% Mounted on /dev/md2 688G 490G 163G 76% /home /sbin/lsmod | grep raid raid5 27713 1 xor 18505 1 raid5 raid1 24769 2 I didn't try to test the last few kernels -------------- next part -------------- An HTML attachment was scrubbed... URL: From justin.conover at gmail.com Sun Mar 5 16:05:38 2006 From: justin.conover at gmail.com (Justin Conover) Date: Sun, 5 Mar 2006 10:05:38 -0600 Subject: [Fedora-xen] xen creation error Message-ID: /usr/sbin/xenguest-install.py What is the name of your virtual machine? fc5-xen1 How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /xen What is the install location? http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/ Starting install... Using config file "/etc/xen/fc5-xen1". Error: Device 51712 (vbd) could not be connected. Backend device not found. If your install has exited, you can restart your guest by running 'xm create -c fc5-xen1'. Otherwise, you can reconnect to the console by running 'xm console fc5-xen1' xm create -c fc5-xen1 Using config file "/etc/xen/fc5-xen1". Traceback (most recent call last): File "/usr/bin/pygrub", line 256, in ? cf = get_config(file, isconfig) File "/usr/bin/pygrub", line 110, in get_config if is_disk_image(fn): File "/usr/bin/pygrub", line 78, in is_disk_image buf = os.read(fd, 512) OSError: [Errno 21] Is a directory Error: Boot loader didn't return any data! -------------- next part -------------- An HTML attachment was scrubbed... URL: From winston at stdout.org Sun Mar 5 18:19:47 2006 From: winston at stdout.org (Winston Chang) Date: Sun, 5 Mar 2006 13:19:47 -0500 Subject: [Fedora-xen] PCI problems with Xen kernel on SiS motherboard Message-ID: <2583EE60-A067-4D56-8C80-90C9E4D27D32@stdout.org> I just installed FC5-T3 on my computer. With the normal kernel, everthing works fine, but when I boot into the xen-hypervisor kernel, kudzu crashes and eth0 won't come up -- it says no such device. USB ports don't work either, under the xen kernel. I think the problem has something to do with PCI under the xen kernel. Running lspci under the xen kernel returns absolutely nothing, and there is nothing in /proc/pci either. This happens with both the stock 1955 kernel and the updated 2009 kernel. It also happened with the FC4 xen kernel, which I why I went to a FC5 test distribution in the first place... It's a desktop system, but it has a mobile Athlon XP 2800+ on a cheap PC Chips motherboard, with a SiS 760 GX northbridge and a SiS 964 southbridge. Has anyone else seen this or know of a possible fix? --Winston =============================================== This is the output when I run on the non-xen kernel (the xen kernel simply returns nothing for lspci): [root at localhost ~]# uname -a Linux localhost.localdomain 2.6.15-1.2009.4.2_FC5 #1 Thu Mar 2 18:10:16 EST 2006 i686 athlon i386 GNU/Linux [root at localhost ~]# lspci 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 741/741GX/M741 Host (rev 03) 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge) 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] (rev 36) 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev 01) 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound Controller (rev a0) 00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) 00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller 00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91) 01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600/GeForce 6600 GT] (rev a2) From yongkang.you at intel.com Mon Mar 6 10:43:33 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Mon, 6 Mar 2006 18:43:33 +0800 Subject: [Fedora-xen] Latest FC5 Xen (2009) issue Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575031C9541@pdsmsx402.ccr.corp.intel.com> Hi all, I have downloaded and installed latest Xen, Xen0(hypervisor), Guest (2.6.15-1.2009.4.2_FC5). None Xen packages are still FC5-test3 packages. When I try to create VMX domain, it reports "Error:.. Connection refused. Is xend running?" But I have start xend. I use ps -A to check process. I found xenstored and xenconsoled were not running. Attachment is the xen log. Would you please share some successful experience, if you have? Best Regards, Yongkang (Kangkang) ?? -------------- next part -------------- A non-text attachment was scrubbed... Name: xend.log Type: application/octet-stream Size: 1781 bytes Desc: xend.log URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: xend-debug.log Type: application/octet-stream Size: 53 bytes Desc: xend-debug.log URL: From fedora at leemhuis.info Mon Mar 6 10:56:40 2006 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Mon, 06 Mar 2006 11:56:40 +0100 Subject: [Fedora-xen] Latest FC5 Xen (2009) issue In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD30575031C9541@pdsmsx402.ccr.corp.intel.com> References: <16A54BF5D6E14E4D916CE26C9AD30575031C9541@pdsmsx402.ccr.corp.intel.com> Message-ID: <1141642600.2390.29.camel@thl.ct.heise.de> Am Montag, den 06.03.2006, 18:43 +0800 schrieb You, Yongkang: > I have downloaded and installed latest Xen, Xen0(hypervisor), Guest > (2.6.15-1.2009.4.2_FC5). None Xen packages are still FC5-test3 > packages. > > When I try to create VMX domain, it reports "Error:.. Connection > refused. Is xend running?" But I have start xend. https://www.redhat.com/archives/fedora-test-list/2006-March/msg00290.html Quote: --- Temporary problem. As root run the following: service xend stop cd /dev ; MAKEDEV /dev/kmem service xend start will allow xenstored to restart and then xend to work again. --- Did the trick for me. HTH Cu thl From yongkang.you at intel.com Mon Mar 6 11:13:09 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Mon, 6 Mar 2006 19:13:09 +0800 Subject: [Fedora-xen] Latest FC5 Xen (2009) issue Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575031C9543@pdsmsx402.ccr.corp.intel.com> >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Thorsten Leemhuis >Sent: 2006?3?6? 18:57 >To: fedora-xen at redhat.com >Subject: Re: [Fedora-xen] Latest FC5 Xen (2009) issue > >Am Montag, den 06.03.2006, 18:43 +0800 schrieb You, Yongkang: > >> I have downloaded and installed latest Xen, Xen0(hypervisor), Guest >> (2.6.15-1.2009.4.2_FC5). None Xen packages are still FC5-test3 >> packages. >> >> When I try to create VMX domain, it reports "Error:.. Connection >> refused. Is xend running?" But I have start xend. > >https://www.redhat.com/archives/fedora-test-list/2006-March/msg00290.html > >Quote: >--- >Temporary problem. > As root run the following: > > service xend stop > cd /dev ; MAKEDEV /dev/kmem > service xend start > >will allow xenstored to restart and then xend to work again. Great to hear that! It works! And VMX is created with above steps. Thanks a lot! Well, it is still a bug. :) I will do more testing on this version about VMX and XenU. >--- > >Did the trick for me. > >HTH >Cu >thl > Best Regards, Yongkang (Kangkang) ?? From fedora at leemhuis.info Mon Mar 6 13:55:34 2006 From: fedora at leemhuis.info (Thorsten Leemhuis) Date: Mon, 06 Mar 2006 14:55:34 +0100 Subject: "xenconsole: Could not read tty from store: No such file or directory" (was RE: [Fedora-xen] Latest FC5 Xen (2009) issue) In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD30575031C9543@pdsmsx402.ccr.corp.intel.com> References: <16A54BF5D6E14E4D916CE26C9AD30575031C9543@pdsmsx402.ccr.corp.intel.com> Message-ID: <1141653334.7601.3.camel@thl.ct.heise.de> Am Montag, den 06.03.2006, 19:13 +0800 schrieb You, Yongkang: > >-----Original Message----- > >From: fedora-xen-bounces at redhat.com > >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Thorsten Leemhuis > >Sent: 2006?3?6? 18:57 > >To: fedora-xen at redhat.com > >Subject: Re: [Fedora-xen] Latest FC5 Xen (2009) issue > >Am Montag, den 06.03.2006, 18:43 +0800 schrieb You, Yongkang: > >> I have downloaded and installed latest Xen, Xen0(hypervisor), Guest > >> (2.6.15-1.2009.4.2_FC5). None Xen packages are still FC5-test3 > >> packages. > >> > >> When I try to create VMX domain, it reports "Error:.. Connection > >> refused. Is xend running?" But I have start xend. > > > >https://www.redhat.com/archives/fedora-test-list/2006-March/msg00290.html >[...] > Great to hear that! It works! I had not so much luck -- I could create and start a VMX, but trying to create/start a HVM always resulted in xenconsole: Could not read tty from store: No such file or directory :-| CU thl From sct at redhat.com Mon Mar 6 17:45:03 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Mon, 06 Mar 2006 12:45:03 -0500 Subject: [Fedora-xen] xen creation error In-Reply-To: References: Message-ID: <1141667104.4086.5.camel@orbit.scot.redhat.com> Hi, On Sun, 2006-03-05 at 10:05 -0600, Justin Conover wrote: > /usr/sbin/xenguest-install.py > What is the name of your virtual machine? fc5-xen1 > How much RAM should be allocated (in megabytes)? 256 > What would you like to use as the disk (path)? /xen > What is the install location? > http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/ > > > Starting install... > Using config file "/etc/xen/fc5-xen1". > Error: Device 51712 (vbd) could not be connected. Backend device not > found. Which xen / kernel? --Stephen From sct at redhat.com Mon Mar 6 17:48:23 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Mon, 06 Mar 2006 12:48:23 -0500 Subject: [Fedora-xen] PCI problems with Xen kernel on SiS motherboard In-Reply-To: <2583EE60-A067-4D56-8C80-90C9E4D27D32@stdout.org> References: <2583EE60-A067-4D56-8C80-90C9E4D27D32@stdout.org> Message-ID: <1141667303.4086.9.camel@orbit.scot.redhat.com> Hi, On Sun, 2006-03-05 at 13:19 -0500, Winston Chang wrote: > I just installed FC5-T3 on my computer. With the normal kernel, > everthing works fine, but when I boot into the xen-hypervisor kernel, > kudzu crashes Known, and we're working on it: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=179013 > and eth0 won't come up -- it says no such device. It would be really helpful if you could try the 1.2009.4.2 kernel from rawhide (you'll need to update the xen rpm too.) > I think the problem has something to do with PCI under the xen > kernel. Running lspci under the xen kernel returns absolutely > nothing, and there is nothing in /proc/pci either. This happens with > both the stock 1955 kernel and the updated 2009 kernel. Plain 1.2009 or 1.2009.4.2? > It's a desktop system, but it has a mobile Athlon XP 2800+ on a cheap > PC Chips motherboard, with a SiS 760 GX northbridge and a SiS 964 > southbridge. > > Has anyone else seen this or know of a possible fix? I haven't heard it reported before; please open a bugzilla, as we'll need to collect proper kernel log info to dig into this. Thanks, Stephen From sct at redhat.com Mon Mar 6 17:50:31 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Mon, 06 Mar 2006 12:50:31 -0500 Subject: [Fedora-xen] Latest FC5 Xen (2009) issue In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD30575031C9543@pdsmsx402.ccr.corp.intel.com> References: <16A54BF5D6E14E4D916CE26C9AD30575031C9543@pdsmsx402.ccr.corp.intel.com> Message-ID: <1141667431.4086.11.camel@orbit.scot.redhat.com> Hi, On Mon, 2006-03-06 at 19:13 +0800, You, Yongkang wrote: > > service xend stop > > cd /dev ; MAKEDEV /dev/kmem > > service xend start > > > >will allow xenstored to restart and then xend to work again. > > Great to hear that! It works! And VMX is created with above steps. Thanks a lot! > Well, it is still a bug. :) Right; upstream xen just fixed things on Friday so that xen no longer needs /dev/kmem to find the xenstore page; we'll be picking up that fix today. Cheers, Stephen From justin.conover at gmail.com Mon Mar 6 19:01:53 2006 From: justin.conover at gmail.com (Justin Conover) Date: Mon, 6 Mar 2006 13:01:53 -0600 Subject: [Fedora-xen] xen creation error In-Reply-To: <1141667104.4086.5.camel@orbit.scot.redhat.com> References: <1141667104.4086.5.camel@orbit.scot.redhat.com> Message-ID: On 3/6/06, Stephen C. Tweedie wrote: > > Hi, > > On Sun, 2006-03-05 at 10:05 -0600, Justin Conover wrote: > > /usr/sbin/xenguest-install.py > > What is the name of your virtual machine? fc5-xen1 > > How much RAM should be allocated (in megabytes)? 256 > > What would you like to use as the disk (path)? /xen > > What is the install location? > > > http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/ > > > > > > Starting install... > > Using config file "/etc/xen/fc5-xen1". > > Error: Device 51712 (vbd) could not be connected. Backend device not > > found. > > Which xen / kernel? > > --Stephen > > > 2009 (everything is current to rawhide) -------------- next part -------------- An HTML attachment was scrubbed... URL: From justin.conover at gmail.com Mon Mar 6 19:02:50 2006 From: justin.conover at gmail.com (Justin Conover) Date: Mon, 6 Mar 2006 13:02:50 -0600 Subject: [Fedora-xen] xen creation error In-Reply-To: References: <1141667104.4086.5.camel@orbit.scot.redhat.com> Message-ID: On 3/6/06, Justin Conover wrote: > > > > On 3/6/06, Stephen C. Tweedie wrote: > > > > Hi, > > > > On Sun, 2006-03-05 at 10:05 -0600, Justin Conover wrote: > > > /usr/sbin/xenguest-install.py > > > What is the name of your virtual machine? fc5-xen1 > > > How much RAM should be allocated (in megabytes)? 256 > > > What would you like to use as the disk (path)? /xen > > > What is the install location? > > > http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/ > > > > > > > > > > > Starting install... > > > Using config file "/etc/xen/fc5-xen1". > > > Error: Device 51712 (vbd) could not be connected. Backend device not > > > found. > > > > Which xen / kernel? > > > > --Stephen > > > > > > 2009 (everything is current to rawhide) > I did do this before hand too. service xend stop cd /dev ; MAKEDEV /dev/kmem service xend start -------------- next part -------------- An HTML attachment was scrubbed... URL: From winston at stdout.org Mon Mar 6 22:01:24 2006 From: winston at stdout.org (Winston Chang) Date: Mon, 6 Mar 2006 17:01:24 -0500 Subject: [Fedora-xen] PCI problems with Xen kernel on SiS motherboard In-Reply-To: <1141667303.4086.9.camel@orbit.scot.redhat.com> References: <2583EE60-A067-4D56-8C80-90C9E4D27D32@stdout.org> <1141667303.4086.9.camel@orbit.scot.redhat.com> Message-ID: >> I think the problem has something to do with PCI under the xen >> kernel. Running lspci under the xen kernel returns absolutely >> nothing, and there is nothing in /proc/pci either. This happens with >> both the stock 1955 kernel and the updated 2009 kernel. > > Plain 1.2009 or 1.2009.4.2? I'll check this tonight and post it... > >> It's a desktop system, but it has a mobile Athlon XP 2800+ on a cheap >> PC Chips motherboard, with a SiS 760 GX northbridge and a SiS 964 >> southbridge. >> >> Has anyone else seen this or know of a possible fix? > > I haven't heard it reported before; please open a bugzilla, as we'll > need to collect proper kernel log info to dig into this. I opened a bugzilla with xensource on this issue -- in their forums I saw that two other people had the same problem with SiS chipsets. Should I open one with Fedora as well? Is there log info I should collect besides /var/log/messages and dmesg? Thanks, -Winston From sct at redhat.com Mon Mar 6 23:39:43 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Mon, 06 Mar 2006 18:39:43 -0500 Subject: [Fedora-xen] xen creation error In-Reply-To: References: <1141667104.4086.5.camel@orbit.scot.redhat.com> Message-ID: <1141688383.4086.40.camel@orbit.scot.redhat.com> Hi, On Mon, 2006-03-06 at 13:01 -0600, Justin Conover wrote: > > Starting install... > > Using config file "/etc/xen/fc5-xen1". > > Error: Device 51712 (vbd) could not be connected. Backend > device not > > found. > 2009 (everything is current to rawhide) Is it reproducible? I did an install earlier today with 1.2009.4.2 and had no problems. It would be really useful if you could bugzilla this so we don't lose it. Thanks, Stephen From justin.conover at gmail.com Tue Mar 7 03:57:41 2006 From: justin.conover at gmail.com (Justin Conover) Date: Mon, 6 Mar 2006 21:57:41 -0600 Subject: [Fedora-xen] xen creation error In-Reply-To: <1141688383.4086.40.camel@orbit.scot.redhat.com> References: <1141667104.4086.5.camel@orbit.scot.redhat.com> <1141688383.4086.40.camel@orbit.scot.redhat.com> Message-ID: On 3/6/06, Stephen C. Tweedie wrote: > > Hi, > > On Mon, 2006-03-06 at 13:01 -0600, Justin Conover wrote: > > > > Starting install... > > > Using config file "/etc/xen/fc5-xen1". > > > Error: Device 51712 (vbd) could not be connected. Backend > > device not > > > found. > > > 2009 (everything is current to rawhide) > > Is it reproducible? I did an install earlier today with 1.2009.4.2 and > had no problems. It would be really useful if you could bugzilla this > so we don't lose it. > > Thanks, > Stephen > > > Bugzilla Bug 184194 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=184194 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sct at redhat.com Tue Mar 7 19:54:27 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Tue, 07 Mar 2006 14:54:27 -0500 Subject: [Fedora-xen] PCI problems with Xen kernel on SiS motherboard In-Reply-To: References: <2583EE60-A067-4D56-8C80-90C9E4D27D32@stdout.org> <1141667303.4086.9.camel@orbit.scot.redhat.com> Message-ID: <1141761268.3231.45.camel@orbit.scot.redhat.com> Hi, On Mon, 2006-03-06 at 17:01 -0500, Winston Chang wrote: > I opened a bugzilla with xensource on this issue -- in their forums I > saw that two other people had the same problem with SiS chipsets. > Should I open one with Fedora as well? You can, if you like, certainly. Generally, platform problems like that are usually easiest hunted down upstream, but an FC bugzilla will still help to track it. > Is there log info I should collect besides /var/log/messages and dmesg? Not really, that's the first thing definitely. --Stephen From yongkang.you at intel.com Wed Mar 8 10:49:39 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Wed, 8 Mar 2006 18:49:39 +0800 Subject: [Fedora-xen] Latest Xen RPMS testing in FC5. Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575031C955A@pdsmsx402.ccr.corp.intel.com> Hi all, We have done a fuller testing for latest Xen updates on FC5. Brief results: In IA32 platform VMX/XenU/Xen run well without any problem. But in x86_64 platform destroy VMX domain will hang Xen0. The serial port output is put in attachment. (I will report a Bug to bugzilla) The detailed testing results: -------- IA32 -------- Xend start pass Xm destroy pass 2.4 vmx domain creating with 128M memory pass 2.6 vmx domain creating with 256M memory pass 2.4 vmx domain creating with 512M memory pass xenU domain creating pass VMX and xenU coexit pass 2 VMXs and 2 XenUs coexist pass 4 VMXs coexist pass VMX Xwindows testing pass Boot up a Windows domain pass ------- X86_64 -------- Xend start ok Create VMX ok Destroy VMX Fail. Hang Xen0. Create and destroy XenU pass ================================ Environments: The base FC5 environment is FC5-test3. -------------------- The Xen RPMs are: IA32: kernel-xen0-2.6.15-1.2025_FC5.i686.rpm kernel-xenU-2.6.15-1.2025_FC5.i686.rpm xen-3.0.1-2.i386.rpm kernel-xen0-2.6.15-1.2032_FC5.i686.rpm kernel-xenU-2.6.15-1.2032_FC5.i686.rpm xen-3.0.1-3.i386.rpm x86_64: kernel-xen0-2.6.15-1.2025_FC5.x86_64.rpm kernel-xenU-2.6.15-1.2025_FC5.x86_64.rpm xen-3.0.1-2.x86_64.rpm kernel-xen0-2.6.15-1.2032_FC5.x86_64.rpm kernel-xenU-2.6.15-1.2032_FC5.x86_64.rpm xen-3.0.1-3.x86_64.rpm ================================= Other issue: Sometime when Xen0 boot, udev will be failed to start up. It will report time out and kernel bugs. Best Regards, Yongkang (Kangkang) ?? -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ia32e hang.txt URL: From justin.conover at gmail.com Wed Mar 8 12:10:18 2006 From: justin.conover at gmail.com (Justin Conover) Date: Wed, 8 Mar 2006 06:10:18 -0600 Subject: [Fedora-xen] Re: memory usage? In-Reply-To: References: Message-ID: On 3/8/06, Justin Conover wrote: > > # /usr/sbin/xenguest-install.py > What is the name of your virtual machine? fc5-t1 > How much RAM should be allocated (in megabytes)? 256 > What would you like to use as the disk (path)? /xen > What is the install location? > http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/ > > > Starting install... > Using config file "/etc/xen/fc5-t1". > Error: Error creating domain: I need 257 MiB, but dom0_min_mem is 256 and > shrinking to 256 MiB would leave only 746 MiB free. > If your install has exited, you can restart your guest by running > 'xm create -c fc5-t1'. Otherwise, you can reconnect to the console > by running 'xm console fc5-t1' > > # /usr/sbin/xenguest-install.py What is the name of your virtual machine? fc5-t2 How much RAM should be allocated (in megabytes)? 260 What would you like to use as the disk (path)? /xen What is the install location? http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/ Starting install... Using config file "/etc/xen/fc5-t2". Error: Error creating domain: I need 261 MiB, but dom0_min_mem is 256 and shrinking to 256 MiB would leave only 746 MiB free. If your install has exited, you can restart your guest by running 'xm create -c fc5-t2'. Otherwise, you can reconnect to the console by running 'xm console fc5-t2' -------------- next part -------------- An HTML attachment was scrubbed... URL: From justin.conover at gmail.com Wed Mar 8 12:06:24 2006 From: justin.conover at gmail.com (Justin Conover) Date: Wed, 8 Mar 2006 06:06:24 -0600 Subject: [Fedora-xen] memory usage? Message-ID: # /usr/sbin/xenguest-install.py What is the name of your virtual machine? fc5-t1 How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /xen What is the install location? http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/ Starting install... Using config file "/etc/xen/fc5-t1". Error: Error creating domain: I need 257 MiB, but dom0_min_mem is 256 and shrinking to 256 MiB would leave only 746 MiB free. If your install has exited, you can restart your guest by running 'xm create -c fc5-t1'. Otherwise, you can reconnect to the console by running 'xm console fc5-t1' -------------- next part -------------- An HTML attachment was scrubbed... URL: From justin.conover at gmail.com Wed Mar 8 14:50:55 2006 From: justin.conover at gmail.com (Justin Conover) Date: Wed, 8 Mar 2006 08:50:55 -0600 Subject: [Fedora-xen] Re: memory usage? In-Reply-To: References: Message-ID: On 3/8/06, Justin Conover wrote: > > > > On 3/8/06, Justin Conover wrote: > > > > # /usr/sbin/xenguest-install.py > > What is the name of your virtual machine? fc5-t1 > > How much RAM should be allocated (in megabytes)? 256 > > What would you like to use as the disk (path)? /xen > > What is the install location? http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/ > > > > > > > > Starting install... > > Using config file "/etc/xen/fc5-t1". > > Error: Error creating domain: I need 257 MiB, but dom0_min_mem is 256 > > and shrinking to 256 MiB would leave only 746 MiB free. > > If your install has exited, you can restart your guest by running > > 'xm create -c fc5-t1'. Otherwise, you can reconnect to the console > > by running 'xm console fc5-t1' > > > > # /usr/sbin/xenguest-install.py > What is the name of your virtual machine? fc5-t2 > How much RAM should be allocated (in megabytes)? 260 > > What would you like to use as the disk (path)? /xen > What is the install location? > http://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/ > > > Starting install... > Using config file "/etc/xen/fc5-t2". > Error: Error creating domain: I need 261 MiB, but dom0_min_mem is 256 and > shrinking to 256 MiB would leave only 746 MiB free. > > If your install has exited, you can restart your guest by running > 'xm create -c fc5-t2'. Otherwise, you can reconnect to the console > by running 'xm console fc5-t2' > > Bugzilla Bug 184393? dom0_min_mem error -------------- next part -------------- An HTML attachment was scrubbed... URL: From justin.conover at gmail.com Wed Mar 8 17:55:42 2006 From: justin.conover at gmail.com (Justin Conover) Date: Wed, 8 Mar 2006 11:55:42 -0600 Subject: [Fedora-xen] kernel naming Message-ID: Apparently I missed this tidbit about kernel/name changes, back to the old style, any reason why yum didn't update them? Guess it doesn't really matter for final since the installs will use the "new/old-style" name changes. uname -r 2.6.15-1.2009.4.2_FC5hypervisor rpm -qa kernel\* kernel-xen-hypervisor-2.6.15-1.2009.4.2_FC5 kernel-xen-guest-devel-2.6.15-1.2009.4.2_FC5 kernel-smp-2.6.15-1.2009.4.2_FC5 kernel-xen-hypervisor-devel-2.6.15-1.2009.4.2_FC5 kernel-smp-2.6.15-1.2032_FC5 kernel-xen-guest-2.6.15-1.2009.4.2_FC5 yum update kernel\* No Packages marked for Update/Obsoletion yum list *\xen\* kernel-xen-guest.i686 2.6.15-1.2009.4.2_FC5 installed kernel-xen-guest-devel.i686 2.6.15-1.2009.4.2_FC5 installed kernel-xen-hypervisor.i686 2.6.15-1.2009.4.2_FC5 installed kernel-xen-hypervisor-devel.i686 2.6.15-1.2009.4.2_FC5 installed xen.i386 3.0.1-3 installed xen-debuginfo.i386 3.0.1-3 installed Available Packages kernel-xen0.i686 2.6.15-1.2032_FC5 development kernel-xen0-devel.i686 2.6.15-1.2032_FC5 development kernel-xenU.i686 2.6.15-1.2032_FC5 development kernel-xenU-devel.i686 2.6.15-1.2032_FC5 development kernel-2.6.15-1.2025_FC5 ------------------------ * Mon Mar 06 2006 Dave Jones - Disable DRI on Radeon R300 and above, due to instability. (#174646,#182196) - Don't do voluntary preempt until after bootup * Mon Mar 06 2006 Stephen Tweedie - Merge xen rebase with 1.2016 kernel - Rename kernel-xen-(hypervisor|guest) to kernel-xen(0|U) for consistency with upstream and to make kernel subtype suffixes match the subpackage names. (From Jeremy Katz.) - Export mmap-able kva interface for xen to find the xenstore page (xen-unstable cset 9130) - Remove stale linux-2.6-xen-module-fault .patch file - Add workaround for non-xen ia64 builds: temporarily back-out the ia64- specific portions of linux-2.6-xen.patch. -------------- next part -------------- An HTML attachment was scrubbed... URL: From katzj at redhat.com Wed Mar 8 18:38:31 2006 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 08 Mar 2006 13:38:31 -0500 Subject: [Fwd: Re: [Fedora-xen] kernel naming] Message-ID: <1141843111.21278.28.camel@orodruin.boston.redhat.com> -------- Forwarded Message -------- From: Jeremy Katz To: Justin Conover Subject: Re: [Fedora-xen] kernel naming Date: Wed, 08 Mar 2006 13:38:14 -0500 On Wed, 2006-03-08 at 11:55 -0600, Justin Conover wrote: > Apparently I missed this tidbit about kernel/name changes, back to the > old style, any reason why yum didn't update them? Guess it doesn't > really matter for final since the installs will use the > "new/old-style" name changes. We didn't add the obsoletes given that the names were only ever used in test releases/rawhide and updates between that and final aren't guaranteed. And the reason you missed the tidbit is that I forgot to send mail. We were having issues just getting rebased kernels working for a while and then I forgot to send once the change actually went in. We've gone back to kernel-xen0 and kernel-xenU as that is needed to make it possible to build extra kernel modules against these packages as defined by the Fedora Extras Kernel Module Package Policy Jeremy From sct at redhat.com Thu Mar 9 03:08:00 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Wed, 08 Mar 2006 22:08:00 -0500 Subject: [Fedora-xen] Latest Xen RPMS testing in FC5. In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD30575031C955A@pdsmsx402.ccr.corp.intel.com> References: <16A54BF5D6E14E4D916CE26C9AD30575031C955A@pdsmsx402.ccr.corp.intel.com> Message-ID: <1141873680.24300.15.camel@orbit.scot.redhat.com> Hi, On Wed, 2006-03-08 at 18:49 +0800, You, Yongkang wrote: > We have done a fuller testing for latest Xen updates on FC5. Thanks! > Sometime when Xen0 boot, udev will be failed to start up. It will report time out and kernel bugs. Do you have any more details? What is the kernel bug output? Thanks, Stephen From yongkang.you at intel.com Thu Mar 9 06:32:32 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Thu, 9 Mar 2006 14:32:32 +0800 Subject: [Fedora-xen] Latest Xen RPMS testing in FC5. Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575031C956E@pdsmsx402.ccr.corp.intel.com> Hi Stephen, I couldn't reproduce the failed udev problem in either IA32 or x86_64 again. But I met it once on both IA32 and x86_64 platforms yesterday. If I catch it next time, I will record the detail and send to you. For the x86_64 problem of hang xen0 if destroying HVM(VMX), our developer shared a information maybe usefully. From the failed info of serial out, it seemed debug=y was opened when making Xen. And VMX will meet some problem if debug option is opened. Could you have a double check? And let the debug=n? :) For enabling serial console in Xen and Xen0, we still meet the bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180126 . We have to disable acpi to enable serial console operation and output, or Xen0 couldn't boot up. Do you have some updates? Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Stephen C. Tweedie >Sent: 2006?3?9? 11:08 >To: You, Yongkang >Cc: fedora-xen at redhat.com >Subject: Re: [Fedora-xen] Latest Xen RPMS testing in FC5. > >Hi, > >On Wed, 2006-03-08 at 18:49 +0800, You, Yongkang wrote: > >> We have done a fuller testing for latest Xen updates on FC5. > >Thanks! > >> Sometime when Xen0 boot, udev will be failed to start up. It will report time out >and kernel bugs. > >Do you have any more details? What is the kernel bug output? > >Thanks, > Stephen > > >-- >Fedora-xen mailing list >Fedora-xen at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen From sct at redhat.com Thu Mar 9 17:12:56 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Thu, 09 Mar 2006 12:12:56 -0500 Subject: [Fedora-xen] Latest Xen RPMS testing in FC5. In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD30575031C956E@pdsmsx402.ccr.corp.intel.com> References: <16A54BF5D6E14E4D916CE26C9AD30575031C956E@pdsmsx402.ccr.corp.intel.com> Message-ID: <1141924377.3393.14.camel@orbit.scot.redhat.com> Hi, On Thu, 2006-03-09 at 14:32 +0800, You, Yongkang wrote: > I couldn't reproduce the failed udev problem in either IA32 or x86_64 > again. But I met it once on both IA32 and x86_64 platforms yesterday. > If I catch it next time, I will record the detail and send to you. Thanks. It may be related to a driver problem that we saw sporadically before and have also been unable to reproduce in 1.2032 --- it's possible that this was related to one of the other fixes that went into the underlying kernel when we moved from git8 to git9. > For the x86_64 problem of hang xen0 if destroying HVM(VMX), our > developer shared a information maybe usefully. From the failed info of > serial out, it seemed debug=y was opened when making Xen. And VMX will > meet some problem if debug option is opened. Could you have a double > check? And let the debug=n? :) What's the problem? I'd rather fix it than disable debug, and we're really close to the scheduled FC5 release date now so I don't want to be making significant changes at this point. > For enabling serial console in Xen and Xen0, we still meet the bug > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180126 . We have > to disable acpi to enable serial console operation and output, or Xen0 > couldn't boot up. Do you have some updates? No -- it always works for me. But I did notice something from the bugzilla that might be important, and I just added: kernel /boot/xen.gz-2.6.15-1.29_FC5 com1=115200,8n1 module /boot/vmlinuz-2.6.15-1.29_FC5hypervisor ro root=/dev/sda1 console=tty0 console=ttyS0 sync_console This is wrong, the "sync_console" needs to be on the "kernel" hypervisor option list, not the xen0 "module" list. Can you reproduce with that change? Cheers, Stephen From yongkang.you at intel.com Fri Mar 10 01:31:40 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Fri, 10 Mar 2006 09:31:40 +0800 Subject: [Fedora-xen] Latest Xen RPMS testing in FC5. Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575031C957A@pdsmsx402.ccr.corp.intel.com> >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Stephen C. Tweedie >Sent: 2006?3?10? 1:13 >To: You, Yongkang >Cc: fedora-xen at redhat.com >Subject: RE: [Fedora-xen] Latest Xen RPMS testing in FC5. > >Hi, > >On Thu, 2006-03-09 at 14:32 +0800, You, Yongkang wrote: > > >> For the x86_64 problem of hang xen0 if destroying HVM(VMX), our >> developer shared a information maybe usefully. From the failed info of >> serial out, it seemed debug=y was opened when making Xen. And VMX will >> meet some problem if debug option is opened. Could you have a double >> check? And let the debug=n? :) > >What's the problem? I'd rather fix it than disable debug, and we're >really close to the scheduled FC5 release date now so I don't want to be >making significant changes at this point. Emm~, our developers are trying to fix this issue and will send out the patch to Xen. After the patch come out, I will notify here to integrate it. Is it Okay? > >> For enabling serial console in Xen and Xen0, we still meet the bug >> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180126 . We have >> to disable acpi to enable serial console operation and output, or Xen0 >> couldn't boot up. Do you have some updates? > >No -- it always works for me. But I did notice something from the >bugzilla that might be important, and I just added: > > kernel /boot/xen.gz-2.6.15-1.29_FC5 com1=115200,8n1 > module /boot/vmlinuz-2.6.15-1.29_FC5hypervisor ro >root=/dev/sda1 > console=tty0 console=ttyS0 sync_console > > This is wrong, the "sync_console" needs to be on the "kernel" >hypervisor option > list, not the xen0 "module" list. Can you reproduce with that change? I have tried with your guide. It also worked for me. I think it is a little strange, that we didn't use "sync_console" in Xen befero. :) Maybe this specail config item should be added into something like readme in Fedora Xen, because Xen manual didn't mention it, user may meet the same trouble like me. > >Cheers, > Stephen > Best Regards, Yongkang (Kangkang) ?? From yongkang.you at intel.com Fri Mar 10 09:56:31 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Fri, 10 Mar 2006 17:56:31 +0800 Subject: [Fedora-xen] Latest Xen RPMS testing in FC5. Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575031C958A@pdsmsx402.ccr.corp.intel.com> >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of You, Yongkang >Sent: 2006?3?10? 9:32 >To: Stephen C. Tweedie >Cc: fedora-xen at redhat.com >Subject: RE: [Fedora-xen] Latest Xen RPMS testing in FC5. > >>No -- it always works for me. But I did notice something from the >>bugzilla that might be important, and I just added: >> >> kernel /boot/xen.gz-2.6.15-1.29_FC5 com1=115200,8n1 >> module /boot/vmlinuz-2.6.15-1.29_FC5hypervisor ro >>root=/dev/sda1 >> console=tty0 console=ttyS0 sync_console >> >> This is wrong, the "sync_console" needs to be on the "kernel" >>hypervisor option >> list, not the xen0 "module" list. Can you reproduce with that change? > >I have tried with your guide. It also worked for me. > >I think it is a little strange, that we didn't use "sync_console" in Xen befero. :) >Maybe this specail config item should be added into something like readme in >Fedora Xen, because Xen manual didn't mention it, user may meet the same >trouble like me. > With this config, I can get Xen0 start and serial output information. But I can not input any commands from serial console after Xen begin to boot. I have given the correct setting in Xen0 inittab. Can you input anything in serial console to control Xen? Is there any other configuration? Best Regards, Yongkang (Kangkang) ?? From jmorris at redhat.com Fri Mar 10 16:23:23 2006 From: jmorris at redhat.com (James Morris) Date: Fri, 10 Mar 2006 11:23:23 -0500 (EST) Subject: [Fedora-xen] Latest Xen RPMS testing in FC5. In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD30575031C958A@pdsmsx402.ccr.corp.intel.com> Message-ID: On Fri, 10 Mar 2006, You, Yongkang wrote: > With this config, I can get Xen0 start and serial output information. But I can not input any commands from serial console after Xen begin to boot. I have given the correct setting in Xen0 inittab. Can you input anything in serial console to control Xen? Is there any other configuration? This is a known problem. - James -- James Morris From sct at redhat.com Fri Mar 10 17:27:35 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Fri, 10 Mar 2006 12:27:35 -0500 Subject: [Fedora-xen] Latest Xen RPMS testing in FC5. In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD30575031C957A@pdsmsx402.ccr.corp.intel.com> References: <16A54BF5D6E14E4D916CE26C9AD30575031C957A@pdsmsx402.ccr.corp.intel.com> Message-ID: <1142011656.6192.7.camel@orbit.scot.redhat.com> Hi, On Fri, 2006-03-10 at 09:31 +0800, You, Yongkang wrote: > Emm~, our developers are trying to fix this issue and will send out > the patch to Xen. After the patch come out, I will notify here to > integrate it. Is it Okay? Perfect, thanks! Cheers, Stephen From muralid.india at gmail.com Sun Mar 12 04:03:33 2006 From: muralid.india at gmail.com (Murali D) Date: Sun, 12 Mar 2006 09:33:33 +0530 Subject: [Fedora-xen] =?windows-1252?q?Fwd=3A_Bugzilla_Bug_185081_=96_sof?= =?windows-1252?q?t_lockup_detected_on_CPU=230!?= In-Reply-To: <1142011373.6192.6.camel@orbit.scot.redhat.com> References: <4028a9ca0603100610j1b7b9d08jd709a8ab9288b21c@mail.gmail.com> <1142011373.6192.6.camel@orbit.scot.redhat.com> Message-ID: <4028a9ca0603112003s1afd913do9d6f835a6fa43ff0@mail.gmail.com> ---------- Forwarded message ---------- From: Stephen C. Tweedie Date: Mar 10, 2006 10:52 PM Subject: Re: Bugzilla Bug 185081 ? soft lockup detected on CPU#0! To: Murali D Cc: Stephen Tweedie Hi, On Fri, 2006-03-10 at 19:40 +0530, Murali D wrote: > I have filed a bug... Is this cpu intensive error.... the guest OS is > getting hang.. > Any solutions... Somebody else is working on this problem --- which is precisely why it's better to be asking on the list, not just always directing the questions to one person! Thanks, Stephen -------------- next part -------------- An HTML attachment was scrubbed... URL: From muralid.india at gmail.com Sun Mar 12 04:05:26 2006 From: muralid.india at gmail.com (Murali D) Date: Sun, 12 Mar 2006 09:35:26 +0530 Subject: [Fedora-xen] =?windows-1252?q?Bugzilla_Bug_185081_=96_soft_locku?= =?windows-1252?q?p_detected_on_CPU=230!?= Message-ID: <4028a9ca0603112005m91e86eeg3b2e07dd7a8b856e@mail.gmail.com> Dear All, I have filed a bug... Is this cpu intensive error.... the guest OS is getting hang.. Any solutions... Regards, Murali -------------- next part -------------- An HTML attachment was scrubbed... URL: From fedora at adslpipe.co.uk Sun Mar 12 10:51:51 2006 From: fedora at adslpipe.co.uk (Andy Burns) Date: Sun, 12 Mar 2006 10:51:51 +0000 Subject: [Fedora-xen] crash booting rawhide xen0 Message-ID: <4413FD47.90504@adslpipe.co.uk> Hi there, I've not been updating my xen kernels to *every* recent rawhide release, but did so today, to 2.6.15-1.2041_FC5xen0, my first two attempts to boot this xen0 crashed and stackdumped :-( Having seen it fail twice, I attached a serial console and was preparing to capture that with console=ttyS0,115200, but on the next two boots the crash didn't happen, however my console output still went to the vgaconsole, does xen have a different way to use the serial console? I'll gladly log a bug if I can make it happen again ... Also I've just tidied up my grub.conf, /boot/ and /lib/modules/ to get rid of heaps of old kernels that the switch from guest/hypervisor to xen0/xenU had left around, is there anywhere I can get back a few slightly older kernels to try and find out what version caused this breakage? I think my last known good version was kernel 2032 From yongkang.you at intel.com Sun Mar 12 11:34:20 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Sun, 12 Mar 2006 19:34:20 +0800 Subject: [Fedora-xen] crash booting rawhide xen0 Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575031C9594@pdsmsx402.ccr.corp.intel.com> >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Andy Burns >Sent: 2006?3?12? 18:52 >To: fedora-xen at redhat.com >Subject: [Fedora-xen] crash booting rawhide xen0 > > >Having seen it fail twice, I attached a serial console and was preparing >to capture that with console=ttyS0,115200, but on the next two boots the >crash didn't happen, however my console output still went to the >vgaconsole, does xen have a different way to use the serial console? If want to get serial output in Xen, you can give the grub.conf like: kernel /boot/xen.gz com1=115200,8n1 sync_console module /boot/vmlinuz-hypervisor ro root=/dev/sda1 console=tty0 console=ttyS0 module /boot/initrd.img... BTW, did the broken happen in booting XWin? I also catch a strange broken in 2032. Best Regards, Yongkang (Kangkang) ?? From fedora at adslpipe.co.uk Sun Mar 12 14:02:16 2006 From: fedora at adslpipe.co.uk (Andy Burns) Date: Sun, 12 Mar 2006 14:02:16 +0000 Subject: [Fedora-xen] crash booting rawhide xen0 In-Reply-To: <4413FD47.90504@adslpipe.co.uk> References: <4413FD47.90504@adslpipe.co.uk> Message-ID: <441429E8.4010306@adslpipe.co.uk> Andy Burns wrote: > 2.6.15-1.2041_FC5xen0, my first two attempts to > boot this xen0 crashed and stackdumped :-( OK, with Yongkang's info I've captured this happening https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185235 Full serial log attached there, but the offending bit seems to be Kernel BUG at arch/x86_64/mm/fault-xen.c:292 invalid opcode: 0000 [1] SMP CPU 0 Modules linked in: snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc hw_random i2c_i801 i2c_core dm_snapshot dm_zero dm_mirror dm_mod ext3 jbd ahci libata sd_mod scsi_mod Pid: 615, comm: udevd Not tainted 2.6.15-1.2041_FC5xen0 #1 RIP: e030:[] {do_page_fault+1690} RSP: e02b:ffffffff80418978 EFLAGS: 00010287 RAX: ffff800000000000 RBX: ffff880000ed7000 RCX: 00003ffffffff000 RDX: 0000000000050204 RSI: 000000000003ac4e RDI: 0000000000000c00 RBP: ffffffff80101c20 R08: 000000000003ac4e R09: ffff880000ae8070 R10: ffff880000ae9000 R11: ffff880000ae9000 R12: ffffc2000000e008 R13: ffffffff80418a58 R14: ffff880038d8f100 R15: 0000000000000000 FS: 00002b07a11e66d0(0000) GS:ffffffff80499000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 Process udevd (pid: 615, threadinfo ffff880038cc4000, task ffff880038d8f100) Stack: 0000000000000001 0000000000030001 ffffffff804189c8 ffffffff801f2163 ffff880000636048 ffff88000230e800 ffff880000636048 ffff880000636048 ffff880000636240 ffffffff801e727d Call Trace: {cfq_dispatch_requests+326} {elv_next_request+321} {kobject_get+18} {:scsi_mod:scsi_request_fn+843} {error_exit+0} {:ahci:ahci_interrupt+33} {handle_IRQ_event+78} {__do_IRQ+156} {do_IRQ+65} {evtchn_do_upcall+132} {do_hypervisor_callback+37} {hypercall_page+554} {hypercall_page+554} {mntput_no_expire+25} {force_evtchn_callback+10} {do_page_fault+196} {sys_mknodat+371} {error_exit+0} From bench at silentmedia.com Sun Mar 12 17:38:30 2006 From: bench at silentmedia.com (Ben) Date: Sun, 12 Mar 2006 09:38:30 -0800 Subject: [Fedora-xen] more advanced xenguest-install.py usage Message-ID: I'd like to install a Xen domU that uses a separate partition for its swap space, and also only sees a specific NIC in my dom0. Is that possible with xenguest-install? Looking at the questions it asks, I don't see how, but I've been known to miss obvious things before.... From tournesol33 at gmail.com Tue Mar 14 06:41:38 2006 From: tournesol33 at gmail.com (tournesol) Date: Tue, 14 Mar 2006 15:41:38 +0900 Subject: [Fedora-xen] xen with kickstart Message-ID: <441665A2.2000708@gmail.com> Hi all Does anyone tried install xen GuestOS with kickstart (or PXE )? Any advice please. tournesol From rmo at sunnmore.net Tue Mar 14 12:47:26 2006 From: rmo at sunnmore.net (Roy-Magne Mo) Date: Tue, 14 Mar 2006 13:47:26 +0100 Subject: [Fedora-xen] xen with kickstart In-Reply-To: <441665A2.2000708@gmail.com> References: <441665A2.2000708@gmail.com> Message-ID: <1142340446.29000.1.camel@host-81-191-138-133.bluecom.no> ty den 14.03.2006 klokka 15:41 (+0900) skreiv tournesol: > Hi all > > Does anyone tried install xen GuestOS with kickstart (or PXE )? > Any advice please. yes, I've done this semi-daily under rawhide for the last months, works like a charm :) -- Roy-Magne Mo From yongkang.you at intel.com Tue Mar 14 14:31:56 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Tue, 14 Mar 2006 22:31:56 +0800 Subject: [Fedora-xen] crash booting rawhide xen0 Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575031C95B3@pdsmsx402.ccr.corp.intel.com> Hi Andy, I suggested that you can do "yum update" to update other RPMs and retry too. I didn't meet this problem in x86_64, after I do yum update to catch up latest development tree. :) Best Regards, Yongkang (Kangkang) ?? >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Andy Burns >Sent: 2006?3?12? 22:02 >To: fedora-xen at redhat.com >Subject: Re: [Fedora-xen] crash booting rawhide xen0 > >Andy Burns wrote: > >> 2.6.15-1.2041_FC5xen0, my first two attempts to >> boot this xen0 crashed and stackdumped :-( > >OK, with Yongkang's info I've captured this happening > >https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185235 >Full serial log attached there, but the offending bit seems to be > >Kernel BUG at arch/x86_64/mm/fault-xen.c:292 >invalid opcode: 0000 [1] SMP >CPU 0 >Modules linked in: snd_mixer_oss snd_pcm snd_timer snd soundcore >snd_page_alloc hw_random i2c_i801 i2c_core dm_snapshot dm_zero >dm_mirror >dm_mod ext3 jbd ahci libata sd_mod scsi_mod >Pid: 615, comm: udevd Not tainted 2.6.15-1.2041_FC5xen0 #1 >RIP: e030:[] {do_page_fault+1690} >RSP: e02b:ffffffff80418978 EFLAGS: 00010287 >RAX: ffff800000000000 RBX: ffff880000ed7000 RCX: 00003ffffffff000 >RDX: 0000000000050204 RSI: 000000000003ac4e RDI: 0000000000000c00 >RBP: ffffffff80101c20 R08: 000000000003ac4e R09: ffff880000ae8070 >R10: ffff880000ae9000 R11: ffff880000ae9000 R12: ffffc2000000e008 >R13: ffffffff80418a58 R14: ffff880038d8f100 R15: 0000000000000000 >FS: 00002b07a11e66d0(0000) GS:ffffffff80499000(0000) >knlGS:0000000000000000 >CS: e033 DS: 0000 ES: 0000 >Process udevd (pid: 615, threadinfo ffff880038cc4000, task ffff880038d8f100) >Stack: 0000000000000001 0000000000030001 ffffffff804189c8 ffffffff801f2163 > ffff880000636048 ffff88000230e800 ffff880000636048 >ffff880000636048 > ffff880000636240 ffffffff801e727d >Call Trace: {cfq_dispatch_requests+326} > {elv_next_request+321} >{kobject_get+18} > {:scsi_mod:scsi_request_fn+843} >{error_exit+0} > {:ahci:ahci_interrupt+33} >{handle_IRQ_event+78} > {__do_IRQ+156} {do_IRQ+65} > {evtchn_do_upcall+132} >{do_hypervisor_callback+37} > {hypercall_page+554} >{hypercall_page+554} > {mntput_no_expire+25} >{force_evtchn_callback+10} > {do_page_fault+196} >{sys_mknodat+371} > {error_exit+0} > > >-- >Fedora-xen mailing list >Fedora-xen at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen From sct at redhat.com Tue Mar 14 17:43:01 2006 From: sct at redhat.com (Stephen Tweedie) Date: Tue, 14 Mar 2006 12:43:01 -0500 Subject: [Fedora-xen] Bugzilla Bug 185081 =?windows-1251?Q?=96?= soft lockup detected on CPU#0! In-Reply-To: <4028a9ca0603112005m91e86eeg3b2e07dd7a8b856e@mail.gmail.com> References: <4028a9ca0603112005m91e86eeg3b2e07dd7a8b856e@mail.gmail.com> Message-ID: <1142358181.4520.2.camel@localhost.localdomain> Hi, On Sun, 2006-03-12 at 09:35 +0530, Murali D wrote: > I have filed a bug... Is this cpu intensive error.... the guest OS is > getting hang.. > Any solutions... It's the Xen hypervisor scheduler; see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=181856 For now you can tweak the scheduler parameters with xm sched-sedf 0 0 0 0 1 1 and we'll make this the default at some point. --Stephen From fedora at adslpipe.co.uk Tue Mar 14 21:13:29 2006 From: fedora at adslpipe.co.uk (Andy Burns) Date: Tue, 14 Mar 2006 21:13:29 +0000 Subject: [Fedora-xen] crash booting rawhide xen0 In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD30575031C95B3@pdsmsx402.ccr.corp.intel.com> References: <16A54BF5D6E14E4D916CE26C9AD30575031C95B3@pdsmsx402.ccr.corp.intel.com> Message-ID: <441731F9.5050608@adslpipe.co.uk> You, Yongkang wrote: > I suggested that you can do "yum update" to update other RPMs and retry too. > I didn't meet this problem in x86_64, after I do yum update to catch up latest development tree. :) At the time I got the error I was completely up to date, obviously a few packages have changed since ... xen0 seems stable if it manages to boot up ok, 3 days uptime with frequent usage now. From aleksander.adamowski.redhat at altkom.com.pl Wed Mar 15 08:59:15 2006 From: aleksander.adamowski.redhat at altkom.com.pl (Aleksander Adamowski) Date: Wed, 15 Mar 2006 09:59:15 +0100 Subject: [Fedora-xen] crash booting rawhide xen0 In-Reply-To: <441429E8.4010306@adslpipe.co.uk> References: <4413FD47.90504@adslpipe.co.uk> <441429E8.4010306@adslpipe.co.uk> Message-ID: <4417D763.3070204@altkom.com.pl> Andy Burns wrote: > Andy Burns wrote: > >> 2.6.15-1.2041_FC5xen0, my first two attempts to boot this xen0 >> crashed and stackdumped :-( > > > OK, with Yongkang's info I've captured this happening > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=185235 > Full serial log attached there, but the offending bit seems to be > > Kernel BUG at arch/x86_64/mm/fault-xen.c:292 > invalid opcode: 0000 [1] SMP > CPU 0 > Modules linked in: snd_mixer_oss snd_pcm snd_timer snd soundcore > snd_page_alloc hw_random i2c_i801 i2c_core dm_snapshot dm_zero > dm_mirror dm_mod ext3 jbd ahci libata sd_mod scsi_mod > Pid: 615, comm: udevd Not tainted 2.6.15-1.2041_FC5xen0 #1 > RIP: e030:[] {do_page_fault+1690} > RSP: e02b:ffffffff80418978 EFLAGS: 00010287 > RAX: ffff800000000000 RBX: ffff880000ed7000 RCX: 00003ffffffff000 > RDX: 0000000000050204 RSI: 000000000003ac4e RDI: 0000000000000c00 > RBP: ffffffff80101c20 R08: 000000000003ac4e R09: ffff880000ae8070 > R10: ffff880000ae9000 R11: ffff880000ae9000 R12: ffffc2000000e008 > R13: ffffffff80418a58 R14: ffff880038d8f100 R15: 0000000000000000 > FS: 00002b07a11e66d0(0000) GS:ffffffff80499000(0000) > knlGS:0000000000000000 > CS: e033 DS: 0000 ES: 0000 > Process udevd (pid: 615, threadinfo ffff880038cc4000, task > ffff880038d8f100) > Stack: 0000000000000001 0000000000030001 ffffffff804189c8 > ffffffff801f2163 > ffff880000636048 ffff88000230e800 ffff880000636048 > ffff880000636048 > ffff880000636240 ffffffff801e727d > Call Trace: {cfq_dispatch_requests+326} > {elv_next_request+321} > {kobject_get+18} > {:scsi_mod:scsi_request_fn+843} > {error_exit+0} > {:ahci:ahci_interrupt+33} > {handle_IRQ_event+78} > {__do_IRQ+156} {do_IRQ+65} > {evtchn_do_upcall+132} > {do_hypervisor_callback+37} > {hypercall_page+554} > {hypercall_page+554} > {mntput_no_expire+25} > {force_evtchn_callback+10} > {do_page_fault+196} > {sys_mknodat+371} > {error_exit+0} I've reported this bug that I had with 2.6.15-1.2025_FC5xen0 to Bugzilla: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=184378 The error is the same, the stacktrace is different. Please add your error to that bug and CC yourself in the Bugzilla. -- Best Regards, Aleksander Adamowski GG#: 274614 ICQ UIN: 19780575 http://olo.ab.altkom.pl From bench at silentmedia.com Thu Mar 16 02:09:24 2006 From: bench at silentmedia.com (Ben) Date: Wed, 15 Mar 2006 18:09:24 -0800 Subject: [Fedora-xen] Unable to reboot a domU Message-ID: <3B988053-6CCC-44FD-8DA0-17450EED5897@silentmedia.com> I installed a domU on x86_64 today, and was very happy. I even logged into it and saw that things seemed to be working, and all was well. I tried to reboot it, and now the domU kernel panics every time I try to boot. :( The bug is 185603, and the console end with: no fstab.sys, mounting internal defaults Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys Kernel panic - not syncing: Attempted to kill init! Call Trace: {panic+134} {__up_read +19} {__fput+354} {_spin_unlock_irq+9} {__down_read+52} {_spin_lock_irqsave+38} {__up_read+19} {do_exit+140} {sys_exit_group+0} {system_call+134} {system_call+0} Any thoughts? From yongkang.you at intel.com Thu Mar 16 02:19:03 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Thu, 16 Mar 2006 10:19:03 +0800 Subject: [Fedora-xen] Unable to reboot a domU Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575031C95D4@pdsmsx402.ccr.corp.intel.com> >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Ben >Sent: 2006?3?16? 10:09 >To: fedora-xen at redhat.com >Subject: [Fedora-xen] Unable to reboot a domU > >I installed a domU on x86_64 today, and was very happy. I even logged >into it and saw that things seemed to be working, and all was well. I >tried to reboot it, and now the domU kernel panics every time I try >to boot. :( So at present you couldn't create XenU with that image again? I think maybe your XenU image is broken. Maybe you can do a manually mount that image file and check if /etc/fstab is there. mount -oloop xenU_image_file /mnt > >The bug is 185603, and the console end with: > >no fstab.sys, mounting internal defaults >Switching to new root and running init. >unmounting old /dev >unmounting old /proc >unmounting old /sys >Kernel panic - not syncing: Attempted to kill init! > > Best Regards, Yongkang (Kangkang) ?? From bench at silentmedia.com Thu Mar 16 02:53:17 2006 From: bench at silentmedia.com (Ben) Date: Wed, 15 Mar 2006 18:53:17 -0800 Subject: [Fedora-xen] Unable to reboot a domU In-Reply-To: <16A54BF5D6E14E4D916CE26C9AD30575031C95D4@pdsmsx402.ccr.corp.intel.com> References: <16A54BF5D6E14E4D916CE26C9AD30575031C95D4@pdsmsx402.ccr.corp.intel.com> Message-ID: Well, I used a DRBD block device, so the -oloop mount option won't work to mount my image. Oddly, I can't seem to mount the block device either. Perhaps that's my real problem? (Though why it worked the first time....?) Anyway, my xen config file looks like this: # Automatically generated xen config file name = "mail" memory = "512" disk = [ 'phy:/dev/drbd2,xvda,w', 'phy:/dev/VolGroup00/ mailSwap,xvdb,w' ] vif = [ 'mac=00:16:3e:75:d2:20' ] bootloader="/usr/bin/pygrub" on_reboot = 'restart' on_crash = 'restart' ... where /dev/drbd2 is the DRBD block device holding both /boot/ and /. If I use fdisk to get a listing on /dev/drbd2, I see: Disk /dev/drbd2: 31.4 GB, 31474057216 bytes 255 heads, 63 sectors/track, 3826 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/drbd2p1 * 1 13 104391 83 Linux /dev/drbd2p2 14 3826 30627922+ 8e Linux LVM So it *seems* like I should be able to mount /dev/drbd2p1 or /dev/ drbd2p2. Alas: # mount /dev/drbd2p1 /mnt mount: special device /dev/drbd2p1 does not exist # mount /dev/drbd2p2 /mnt mount: special device /dev/drbd2p2 does not exist I'd be happy to blame this on DRBD, but this did work for both install and after the first reboot.... On Mar 15, 2006, at 6:19 PM, You, Yongkang wrote: >> -----Original Message----- >> From: fedora-xen-bounces at redhat.com >> [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Ben >> Sent: 2006?3?16? 10:09 >> To: fedora-xen at redhat.com >> Subject: [Fedora-xen] Unable to reboot a domU >> >> I installed a domU on x86_64 today, and was very happy. I even logged >> into it and saw that things seemed to be working, and all was well. I >> tried to reboot it, and now the domU kernel panics every time I try >> to boot. :( > > So at present you couldn't create XenU with that image again? I > think maybe your XenU image is broken. > > Maybe you can do a manually mount that image file and check if /etc/ > fstab is there. > mount -oloop xenU_image_file /mnt > >> >> The bug is 185603, and the console end with: >> >> no fstab.sys, mounting internal defaults >> Switching to new root and running init. >> unmounting old /dev >> unmounting old /proc >> unmounting old /sys >> Kernel panic - not syncing: Attempted to kill init! >> >> > > > Best Regards, > Yongkang (Kangkang) ?? From bench at silentmedia.com Thu Mar 16 07:02:39 2006 From: bench at silentmedia.com (Ben) Date: Wed, 15 Mar 2006 23:02:39 -0800 Subject: [Fedora-xen] Re: Unable to reboot a domU In-Reply-To: <3B988053-6CCC-44FD-8DA0-17450EED5897@silentmedia.com> References: <3B988053-6CCC-44FD-8DA0-17450EED5897@silentmedia.com> Message-ID: OK, so it turns out I am a tard. Or SELinux is too picky. Or some combination of those two. In trying to disable SELinux, I accidently changed SELINUXTYPE=targeted to SELINUXTYPE=disabled. So the config effectively said: SELINUX=enforcing SELINUXTYPE=disabled That probably shouldn't cause a kernel panic, but then again, that's probably not what I should change it to, either. Bug updated. On Mar 15, 2006, at 6:09 PM, Ben wrote: > I installed a domU on x86_64 today, and was very happy. I even > logged into it and saw that things seemed to be working, and all > was well. I tried to reboot it, and now the domU kernel panics > every time I try to boot. :( > > The bug is 185603, and the console end with: > > no fstab.sys, mounting internal defaults > Switching to new root and running init. > unmounting old /dev > unmounting old /proc > unmounting old /sys > Kernel panic - not syncing: Attempted to kill init! > > Call Trace: {panic+134} > {__up_read+19} > {__fput+354} > {_spin_unlock_irq+9} > {__down_read+52} > {_spin_lock_irqsave+38} > {__up_read+19} {do_exit > +140} > {sys_exit_group+0} > {system_call+134} > {system_call+0} > > > > Any thoughts? From markryde at gmail.com Thu Mar 16 10:15:22 2006 From: markryde at gmail.com (Mark Ryden) Date: Thu, 16 Mar 2006 12:15:22 +0200 Subject: [Fedora-xen] setting IP address for domU in a config file Message-ID: Hello, I had followed the instructions in http://www.fedoraproject.org/wiki/FedoraXenQuickstart an I am succeeding in creating domain U. The thing is that I want domU to start with some static IP address. How can I do it ? I had tried adding , in the config file for domU, vif = [ 'ip=192.168.0.193', 'bridge=xenbr0' ] netmask="255.255.255.0" and run "xm create -c domUconfig" Dom U started , ifconfig -a showed eth0, but without the IP address. Any ideas ? Mark From jmenon at spikesource.com Thu Mar 16 10:25:22 2006 From: jmenon at spikesource.com (Jairaj Menon) Date: Thu, 16 Mar 2006 15:55:22 +0530 Subject: [Fedora-xen] setting IP address for domU in a config file In-Reply-To: References: Message-ID: <1142504722.2848.87.camel@cyborg> Mount the image file on your /mnt as explained in the quickstart guide and create the following files /etc/sysconfig/network-scripts/ifcfg-eth0 file DEVICE=eth0 BOOTPROTO=static HWADDR=00:14:22:B1:20:1E IPADDR=10.1.1.21 NETMASK=255.255.255.0 ONBOOT=yes TYPE=Ethernet /etc/sysconfig/network NETWORKING=yes HOSTNAME=(your hostname here) GATEWAY=10.1.1.1 Change the values as required. Thanks. - J a i On Thu, 2006-03-16 at 12:15 +0200, Mark Ryden wrote: > Hello, > I had followed the instructions in > http://www.fedoraproject.org/wiki/FedoraXenQuickstart > an I am succeeding in creating domain U. > The thing is that I want domU to start with some static IP address. > How can I do it ? > > I had tried adding , in the config file for domU, > vif = [ 'ip=192.168.0.193', 'bridge=xenbr0' ] > netmask="255.255.255.0" > > and run "xm create -c domUconfig" > Dom U started , ifconfig -a showed eth0, but without the IP address. > > Any ideas ? > > Mark > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From bench at silentmedia.com Fri Mar 17 18:05:54 2006 From: bench at silentmedia.com (Ben) Date: Fri, 17 Mar 2006 10:05:54 -0800 Subject: [Fedora-xen] Re: kudzu not seeing my new NIC In-Reply-To: References: Message-ID: <60826863-C5AB-42F1-9D44-5820DBFB8FC8@silentmedia.com> Actually, I take back that part about using the interfaces just fine. While I can *see* the manually configured interfaces just fine, it seems the xen dom0 scripting glue plays with the arp broadcasts in such a way as that an arp request for any interface always resolves to just of of them. On Mar 17, 2006, at 9:19 AM, Ben wrote: > I'm running a current set of rawhide RPMs on x86_64. I just tried > to add a new network card (a dual-port eepro100), and while I can > manually configure the NICs and use them just fine, kudzu didn't > see them. Is this expected behavior? > > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe:https://www.redhat.com/mailman/listinfo/fedora-test- > list From aleksander.adamowski.redhat at altkom.com.pl Fri Mar 17 18:46:54 2006 From: aleksander.adamowski.redhat at altkom.com.pl (Aleksander Adamowski) Date: Fri, 17 Mar 2006 19:46:54 +0100 Subject: [Fedora-xen] 2.6.15-1.2054_FC5xen0 - no network for guest domains Message-ID: <441B041E.6060204@altkom.com.pl> Hi! I'm using xenguest-install.py to install a guest domain on x86_64. The anaconda installer start up fine, but when I configure the network for the guest domain (be it DHCP or static IP), after trying to contact installation FTP server, I discover that the guest domain has no network connectivity at all - it cannot resolve the FTP server's hostname, or connect to it directly by its IP address; I cannot ping from other hosts or from dom0 to the guest domain. The physical network controller is a Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet using the tg3 driver. The virtual network devices are created by Xen on domain 0: # ifconfig eth0 Link encap:Ethernet HWaddr 00:15:60:0B:ED:88 inet addr:192.168.254.208 Bcast:192.168.254.255 Mask:255.255.255.0 inet6 addr: fe80::215:60ff:fe0b:ed88/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:475078 errors:0 dropped:0 overruns:0 frame:0 TX packets:601247 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:99094177 (94.5 MiB) TX bytes:322269097 (307.3 MiB) Interrupt:17 eth0:0 Link encap:Ethernet HWaddr 00:15:60:0B:ED:88 inet addr:192.168.254.4 Bcast:192.168.254.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:17 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:80137 errors:0 dropped:0 overruns:0 frame:0 TX packets:80137 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:288852189 (275.4 MiB) TX bytes:288852189 (275.4 MiB) vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:99 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:6 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4158 (4.0 KiB) TX bytes:0 (0.0 b) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:99 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2772 (2.7 KiB) TX bytes:468 (468.0 b) I suspect that this may have something to do with x86_64 architecture and the tg3 driver. Any ideas? -- Best Regards, Aleksander Adamowski GG#: 274614 ICQ UIN: 19780575 http://olo.ab.altkom.pl From bench at silentmedia.com Sun Mar 19 19:38:46 2006 From: bench at silentmedia.com (Ben) Date: Sun, 19 Mar 2006 11:38:46 -0800 Subject: [Fedora-xen] "enhanced" xenguest-install.py Message-ID: <1182BFFD-67E1-4DC2-A77F-6BF7B18E2A65@silentmedia.com> I just finished testing my enhancements to xenguest-install.py that let me specify multiple volumes and multiple NICs to export to the new domU. Seems to work ok for me, though I'm only testing it on the paravirtualized server. In case anybody else would find such a thing useful, I've attached it here. (Note that I gave up on the default bridging script. It just didn't make sense to me when I wanted more than a single NIC. Instead, I used the logic on http://wiki.xensource.com/xenwiki/XenNetworkingSuse? highlight=%28XenNetworking%29 pretty much verbatim.) -------------- next part -------------- A non-text attachment was scrubbed... Name: xenguest-install.py Type: text/x-python-script Size: 13607 bytes Desc: not available URL: -------------- next part -------------- From katzj at redhat.com Sun Mar 19 22:39:08 2006 From: katzj at redhat.com (Jeremy Katz) Date: Sun, 19 Mar 2006 17:39:08 -0500 Subject: [Fedora-xen] "enhanced" xenguest-install.py In-Reply-To: <1182BFFD-67E1-4DC2-A77F-6BF7B18E2A65@silentmedia.com> References: <1182BFFD-67E1-4DC2-A77F-6BF7B18E2A65@silentmedia.com> Message-ID: <1142807948.9638.43.camel@aglarond.local> On Sun, 2006-03-19 at 11:38 -0800, Ben wrote: > I just finished testing my enhancements to xenguest-install.py that > let me specify multiple volumes and multiple NICs to export to the > new domU. Seems to work ok for me, though I'm only testing it on the > paravirtualized server. In case anybody else would find such a thing > useful, I've attached it here. For the multi-disk case at least, it's definitely useful and the patch in bugzilla would do wonders for getting it in the package ;-) > (Note that I gave up on the default bridging script. It just didn't > make sense to me when I wanted more than a single NIC. Instead, I > used the logic on http://wiki.xensource.com/xenwiki/XenNetworkingSuse? > highlight=%28XenNetworking%29 pretty much verbatim.) Yeah, I'm not entirely happy with the default bridging setup, but am not sure exactly what makes more sense. I think we're pretty open to suggestions and seeing what works for people. Personally, my own preference is leaning more towards some form of NAT setup. This introduces complications with migration, though. Jeremy From bench at silentmedia.com Sun Mar 19 23:21:57 2006 From: bench at silentmedia.com (Ben) Date: Sun, 19 Mar 2006 15:21:57 -0800 Subject: [Fedora-xen] "enhanced" xenguest-install.py In-Reply-To: <1142807948.9638.43.camel@aglarond.local> References: <1182BFFD-67E1-4DC2-A77F-6BF7B18E2A65@silentmedia.com> <1142807948.9638.43.camel@aglarond.local> Message-ID: <5418E359-A90E-4D31-BF49-80256E6FD913@silentmedia.com> On Mar 19, 2006, at 2:39 PM, Jeremy Katz wrote: > > For the multi-disk case at least, it's definitely useful and the patch > in bugzilla would do wonders for getting it in the package ;-) Filed. Though, perhaps I sent this out too soon.... even though this script makes valid xen config files, as soon as my install reaches the point where it's about to start formatting my exported drives, anaconda aborts. I doubt it's directly the fault of these modifications, given that anaconda has already configured the drives and has downloaded a lot of data before it goes bad.... but that doesn't leave me with a workable system. How do I figure out what anaconda is unhappy about? > Yeah, I'm not entirely happy with the default bridging setup, but > am not > sure exactly what makes more sense. I think we're pretty open to > suggestions and seeing what works for people. I don't mind the bridging. And I don't suppose I'd mind NAT, either. All I need is a way to specify that domU A only sees dom0's eth1, and that domU B only sees dom0's eth2. From sct at redhat.com Mon Mar 20 21:15:17 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Mon, 20 Mar 2006 16:15:17 -0500 Subject: [Fedora-xen] 2.6.15-1.2054_FC5xen0 - no network for guest domains In-Reply-To: <441B041E.6060204@altkom.com.pl> References: <441B041E.6060204@altkom.com.pl> Message-ID: <1142889317.21593.41.camel@orbit.scot.redhat.com> Hi, On Fri, 2006-03-17 at 19:46 +0100, Aleksander Adamowski wrote: > I'm using xenguest-install.py to install a guest domain on x86_64. > > The anaconda installer start up fine, but when I configure the network > for the guest domain (be it DHCP or static IP), after trying to contact > installation FTP server, I discover that the guest domain has no network > connectivity at all - it cannot resolve the FTP server's hostname, or > connect to it directly by its IP address; I cannot ping from other hosts > or from dom0 to the guest domain. Works fine for me on x86_64, so it's not arch-specific. Hmm --- do you have a strong firewall enabled on the dom0 that might be getting in the way? > The physical network controller is a Broadcom Corporation NetXtreme > BCM5704 Gigabit Ethernet using the tg3 driver. > > The virtual network devices are created by Xen on domain 0: This does not look at *all* like a normal xen networking config: > # ifconfig > eth0 Link encap:Ethernet HWaddr 00:15:60:0B:ED:88 > Interrupt:17 this implies that eth0 is a physical device; > eth0:0 Link encap:Ethernet HWaddr 00:15:60:0B:ED:88 > inet addr:192.168.254.4 Bcast:192.168.254.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > Interrupt:17 with an alias; > vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF and then there's a vif1.0, which I assume is the one belonging to the domU guest's back-end driver in dom0. And finally you've got > xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF the bridge to bind them all together. With xen, normally you have no physical eth0: eth0 is a virtual loopback net device, the other end of which is bound to vif0.0; the original physical eth0 is renamed to peth0; and vif0.0 and peth0 are bridged together on xenbr0. So once I start a domU guest in such an environment, bridging shows: # brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no peth0 vif0.0 vif1.0 Your environment has no virtual eth0, no renamed physical peth0 and no loopback vif0.0; it doesn't look like any of the dom0 bits that xen tries to set up have been initialised. What sort of network config did you have set up before starting xend? What does "brctl show" show? --Stephen From esmithmail at gmail.com Sat Mar 25 05:03:35 2006 From: esmithmail at gmail.com (Eric Smith) Date: Fri, 24 Mar 2006 23:03:35 -0600 Subject: [Fedora-xen] xend hangs at start Message-ID: <820bc1260603242103p2acad1aen44603a271157bfa5@mail.gmail.com> Hi, Running FC5 now on Pentium 4 and want to try xen (for the first time). [root at gum ~]# xm list Error: Error connecting to xend: Connection refused. Is xend running? [root at gum ~]# ps -ef | grep xend root 2343 1 0 22:33 ? 00:00:00 python /usr/sbin/xend start root 2344 2343 0 22:33 ? 00:00:00 python /usr/sbin/xend start [root at gum ~]# uname -a Linux gum 2.6.15-1.1955_FC5hypervisor #1 SMP Wed Feb 15 16:21:02 EST 2006 i686 i686 i386 GNU/Linux The "start" never completes. Disabled SElinux and rebooted, same results. Any ideas? Thanks, Eric ps Installed FC5 test 3 and then ran yum update to move to FC5 when released. Updated again just today: [root at gum ~]# cat /etc/fedora-release Fedora Core release 5 (Bordeaux) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Axel.Thimm at ATrpms.net Sat Mar 25 09:49:56 2006 From: Axel.Thimm at ATrpms.net (Axel Thimm) Date: Sat, 25 Mar 2006 10:49:56 +0100 Subject: [Fedora-xen] Re: xend hangs at start In-Reply-To: <820bc1260603242103p2acad1aen44603a271157bfa5@mail.gmail.com> References: <820bc1260603242103p2acad1aen44603a271157bfa5@mail.gmail.com> Message-ID: <20060325094956.GB8534@neu.nirvana> On Fri, Mar 24, 2006 at 11:03:35PM -0600, Eric Smith wrote: > Running FC5 now on Pentium 4 and want to try xen (for the first time). > [root at gum ~]# uname -a > Linux gum 2.6.15-1.1955_FC5hypervisor #1 SMP Wed Feb 15 16:21:02 EST 2006 > i686 i686 i386 GNU/Linux > ps Installed FC5 test 3 and then ran yum update to move to FC5 when > released. Updated again just today: But you are still running a development kernel. I'd suggest to install FC5 from scratch to make sure you don't use any old rawhide bist anywhere, and retry with the latest kernel in updates-testing. -- Axel.Thimm at ATrpms.net -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 191 bytes Desc: not available URL: From veillard at redhat.com Sat Mar 25 11:03:35 2006 From: veillard at redhat.com (Daniel Veillard) Date: Sat, 25 Mar 2006 06:03:35 -0500 Subject: [Fedora-xen] Re: xend hangs at start In-Reply-To: <20060325094956.GB8534@neu.nirvana> References: <820bc1260603242103p2acad1aen44603a271157bfa5@mail.gmail.com> <20060325094956.GB8534@neu.nirvana> Message-ID: <20060325110335.GR16978@redhat.com> On Sat, Mar 25, 2006 at 10:49:56AM +0100, Axel Thimm wrote: > On Fri, Mar 24, 2006 at 11:03:35PM -0600, Eric Smith wrote: > > ps Installed FC5 test 3 and then ran yum update to move to FC5 when > > released. Updated again just today: > > But you are still running a development kernel. I'd suggest to > install FC5 from scratch to make sure you don't use any old rawhide > bist anywhere, and retry with the latest kernel in updates-testing. right the low level interfaces have changed and the new Xen Store daemon won't start on an old kernel, leading to this pending Xend Daemon in startup phase trying to connect a non-existent Xen Store. As suggested the simplest it to fully install to make sure you don't have older bits laying around. Daniel -- Daniel Veillard | Red Hat http://redhat.com/ veillard at redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From thomas.trepper at microbyte.at Sat Mar 25 15:56:36 2006 From: thomas.trepper at microbyte.at (Thomas Trepper) Date: Sat, 25 Mar 2006 16:56:36 +0100 Subject: [Fedora-xen] DeprecationWarning: Non-ASCII character '\xeb' .... Message-ID: <44256834.9010008@microbyte.at> Hi all, i have a fresh install of FC5 and the xen-kernel enabled. Yesterday i created two quest-systems also based on FC5, one in graphical mode with vnc and the other one in text-mode and all systems were running yesterday. Today when i will start up the systems i get the following error: [root at gondor ttrepper]# /usr/sbin/xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1878 1 r----- 33.3 [root at gondor ttrepper]# /usr/sbin/xm create -c /share/test Using config file "/share/test". /usr/lib64/python2.4/site-packages/xen/xm/opts.py:452: DeprecationWarning: Non-ASCII character '\xeb' in file /share/test on line 1, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details execfile(defconfig, globs, locs) Error: invalid syntax (test, line 1) Does anybody have an idea? Thanks a lot and kind regards, Thomas From kwan at digitalhermit.com Sun Mar 26 02:39:00 2006 From: kwan at digitalhermit.com (Kwan Lowe) Date: Sat, 25 Mar 2006 21:39:00 -0500 (EST) Subject: [Fedora-xen] Impressive! Message-ID: <1627.192.168.8.8.1143340740.squirrel@digitalhermit.com> I'm at this moment running "xm top" watching four domains bounce along happily in a 1G Athlon 1800 test box. Two have full X environments available via VNC, two are web server installations. There was some initial difficulty in the configuration until I had the bright idea of following the instructions in the Quickstart wiki and then everything worked beautifully. The domainU's are using both file and LVM backed disks. I'm about to build out a second domain0 machine to test the migration option. If I understand it correctly, if a domain is migrated from one physical host to another, it does so transparently to end users. I'm curious how to go about setting this up. The user guide shows the option but not much on how to actually configure it. Do I need to configure identical domains on both physical hosts? I'm assuming that the disk device would need to be available to both hosts via SAN. Or is there some synchronization that occurs between the domainUs? -- * The Digital Hermit http://www.digitalhermit.com * Unix and Linux Solutions kwan at digitalhermit.com From thomas.trepper at microbyte.at Sun Mar 26 07:33:27 2006 From: thomas.trepper at microbyte.at (Thomas Trepper) Date: Sun, 26 Mar 2006 09:33:27 +0200 Subject: [Fwd: [Fedora-xen] DeprecationWarning: Non-ASCII character '\xeb' ....] Message-ID: <442643C7.3030303@microbyte.at> Hi all, just to inform you, i have already modified the opt.py file as it is advised in the article, which i have read following the link in the error-statement. I added the following first two lines: #!/usr/bin/python # -*- coding: iso-8859-15 -*- But the error is the same. Do i still miss something? Does anybody has an idea? The base-system is FC5 on AMD-64 with 2GB memory. Thank you very much and best regards, Thomas -------- Original Message -------- Subject: [Fedora-xen] DeprecationWarning: Non-ASCII character '\xeb' .... Date: Sat, 25 Mar 2006 16:56:36 +0100 From: Thomas Trepper To: fedora-xen at redhat.com Hi all, i have a fresh install of FC5 and the xen-kernel enabled. Yesterday i created two quest-systems also based on FC5, one in graphical mode with vnc and the other one in text-mode and all systems were running yesterday. Today when i will start up the systems i get the following error: [root at gondor ttrepper]# /usr/sbin/xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1878 1 r----- 33.3 [root at gondor ttrepper]# /usr/sbin/xm create -c /share/test Using config file "/share/test". /usr/lib64/python2.4/site-packages/xen/xm/opts.py:452: DeprecationWarning: Non-ASCII character '\xeb' in file /share/test on line 1, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details execfile(defconfig, globs, locs) Error: invalid syntax (test, line 1) Does anybody have an idea? Thanks a lot and kind regards, Thomas -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From fedora at adslpipe.co.uk Sun Mar 26 12:19:50 2006 From: fedora at adslpipe.co.uk (Andy Burns) Date: Sun, 26 Mar 2006 13:19:50 +0100 Subject: [Fedora-xen] Impressive! In-Reply-To: <1627.192.168.8.8.1143340740.squirrel@digitalhermit.com> References: <1627.192.168.8.8.1143340740.squirrel@digitalhermit.com> Message-ID: <442686E6.3010303@adslpipe.co.uk> Kwan Lowe wrote: > I'm assuming that the > disk device would need to be available to both hosts via SAN. Fibre Channel, shared SCSI bus, NFS, DRBD, iSCSI ... From scott.hankin at gmail.com Wed Mar 15 17:13:52 2006 From: scott.hankin at gmail.com (Scott D Hankin) Date: Wed, 15 Mar 2006 12:13:52 -0500 Subject: [Fedora-xen] Problem installing FC5 guest in Xen on FC5 using xenguest-install.py Message-ID: Howdy - I'm attempting to install a FC5 guest in Xen on FC5, 2041 xen0 kernel. I've gotten to the point where anaconda runs and starts presenting me with menus. Unfortunately, the 3rd menu it presents is stopping me, the one which sets the IP address. If I select DHCP and networking is set up for NAT, it thinks for a bit and then returns to the same page. If I try to manually specify an IP address, it thinks for a bit, and then segfaults. If networking is bridged, it segfaults in either case. The command I'm running is: xenguest-intall.py -n vm2 -f /root/fedora.img -s 6 -r 256 -p -l ftp://mymachine I've tried this with the networking setup as bridged or NAT, but the result is always the same. Any thoughts? -- Scott (Originally posted, probably in error, to fedora-test.) ----------------------------- In the beginning, there was nothing, then God said, "Let there be light." And there was light. There was still nothing, but you could see it a lot better. -------------- next part -------------- An HTML attachment was scrubbed... URL: From toddf at technetiuminc.com Thu Mar 16 16:21:38 2006 From: toddf at technetiuminc.com (Todd Foster) Date: Thu, 16 Mar 2006 08:21:38 -0800 Subject: [Fedora-xen] setting IP address for domU in a config file Message-ID: <573107F1B90C61449D48757CED75765110BFEC@drwebdc.hal.corp> Start the domain and create a /etc/sysconfig/networking/devices/ifcfg-eth0 file with the following in it. (works for me!) This is on FC4 Zen 3.01 DEVICE=eth0 BROADCAST=192.168.1.255 HWADDR=aa:bb:00:00:00:12 IPADDR=192.168.1.110 NETMASK=255.255.255.0 NETWORK=192.168.1.0 ONBOOT=yes TYPE=Ethernet GATEWAY=192.168.1.1 BOOTPROTO=none USERCTL=no PEERDNS=yes IPV6INIT=no Todd H Foster, CEO Technetium, Inc. The Technical Element. One Ten Pine Avenue Suite 1080 Long Beach, CA 90802 ---------------------------- Phone: (310) 508-6476 Fax: (562) 427-4707 Email: toddf at technetiuminc.com Web: www.technetiuminc.com -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Mark Ryden Sent: Thursday, March 16, 2006 2:15 AM To: fedora-xen at redhat.com Subject: [Fedora-xen] setting IP address for domU in a config file Hello, I had followed the instructions in http://www.fedoraproject.org/wiki/FedoraXenQuickstart an I am succeeding in creating domain U. The thing is that I want domU to start with some static IP address. How can I do it ? I had tried adding , in the config file for domU, vif = [ 'ip=192.168.0.193', 'bridge=xenbr0' ] netmask="255.255.255.0" and run "xm create -c domUconfig" Dom U started , ifconfig -a showed eth0, but without the IP address. Any ideas ? Mark -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From kwan at digitalhermit.com Mon Mar 27 12:54:08 2006 From: kwan at digitalhermit.com (Kwan Lowe) Date: Mon, 27 Mar 2006 07:54:08 -0500 (EST) Subject: [Fedora-xen] Page space questions Message-ID: <47676.192.168.8.28.1143464048.squirrel@digitalhermit.com> Hello All: I've been successfully running several domains a test box under various workloads for about 48 hours now. Domains include an httpd server, mysql database, DNS, and development domain. My question is about memory sizing and page space. On a physical box one would allocate an appropriate page space on the local disks. In the DomainU's, however, would there be any advantage to maybe disabling page space entirely and allocating a larger base memory from the host? Will the Domain0 be able to allocate more physical memory than is available by using page space? E.g. The physical box (1G RAM) currently has four 128-192M domains with 128-256M page space defined in each DomainU. DomainU's are backed by LVM devices on a single 200G physical disk. I would like to have four domains of 256M apiece. This is greater than the available physical RAM, but at any one point the total memory in use by the DomainUs is much less. I'd probably have to tweak the individual overcommit settings in each DomainU. Anyhoo, the rationale is that the Domain0 may be better able to deal with disk I/O rather than each DomainU hitting the disk... If this is fatally flawed reasoning, another thought would be to have a monitor process on each DomainU report back to the Domain0. It would send memory commit information which the Domain0 could use to mem-set the DomainU's lower or higher. I'm thinking of a dynamic memory allocation scheme that could better utilize available physical memory. Thoughts? Suggestions? Derision? (BTW, xen just rocks. It compares very favorably with the VMWare and AIX micropartitions I use at my day job :D ). -- * The Digital Hermit http://www.digitalhermit.com * Unix and Linux Solutions kwan at digitalhermit.com From drhodus at machdep.com Mon Mar 27 15:11:38 2006 From: drhodus at machdep.com (David Rhodus) Date: Mon, 27 Mar 2006 10:11:38 -0500 Subject: [Fedora-xen] xen domain creation problem Message-ID: Hello. I am having problems getting xen setup and working on a FC5 install. I have been following the instructions from http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 [root at client ~]# xenguest-install.py What is the name of your virtual machine? vmxen How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /home/vmxen How large would you like the disk to be (in gigabytes)? 4 What is the install location? http://download.fedora.redhat.com/pub/fedora/linux/core/5/i386/os/ Starting install... Using config file "/etc/xen/vmxen". Error: Error creating domain: The privileged domain did not balloon! If your install has exited, you can restart your guest by running 'xm create -c vmxen'. Otherwise, you can reconnect to the console by running 'xm console vmxen' [root at client ~]# xm create -c vmxen Using config file "/etc/xen/vmxen". Traceback (most recent call last): File "/usr/bin/pygrub", line 256, in ? cf = get_config(file, isconfig) File "/usr/bin/pygrub", line 139, in get_config raise RuntimeError, "Unable to read filesystem" RuntimeError: Unable to read filesystem Error: Boot loader didn't return any data! [root at client ~]# ls -l /home/vmxen -rwxr-xr-x 1 root root 4294967297 Mar 27 09:22 /home/vmxen [root at client ~]# I have attached xend-debug.log and xend.log files. Any hints on what I should look at next ? -- David Rhodus -------------- next part -------------- A non-text attachment was scrubbed... Name: xend.log Type: text/x-log Size: 40656 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: xend-debug.log Type: text/x-log Size: 2940 bytes Desc: not available URL: From justin.conover at gmail.com Mon Mar 27 15:34:12 2006 From: justin.conover at gmail.com (Justin Conover) Date: Mon, 27 Mar 2006 09:34:12 -0600 Subject: [Fedora-xen] guests install problems Message-ID: I created a guest with the python script xenguest-install.py when I run # /usr/sbin/xm create -c webserver1 I get the following error Traceback (most recent call last): File "/usr/bin/pygrub", line 258, in ? curses.wrapper(run_main) File "/usr/lib/python2.4/curses/wrapper.py", line 44, in wrapper return func(stdscr, *args, **kwds) File "/usr/bin/pygrub", line 214, in run_main sel = main(cf) File "/usr/bin/pygrub", line 162, in main (stdscr, win) = draw_window() File "/usr/bin/pygrub", line 33, in draw_window curses.use_default_colors() _curses.error: use_default_colors() returned ERR Error: Boot loader didn't return any data! #xm log (3-27-06) [2006-03-27 09:30:26 xend] ERROR (XendBootloader:84) Boot loader didn't return any data! [2006-03-27 09:32:18 xend] INFO (SrvDaemon:192) Xend stopped due to signal 15. [2006-03-27 09:32:18 xend] INFO (SrvDaemon:285) Xend Daemon started [2006-03-27 09:32:18 xend] INFO (SrvDaemon:289) Xend changeset: unavailable . [2006-03-27 09:32:18 xend.XendDomainInfo] DEBUG (XendDomainInfo:199) XendDomainInfo.recreate({'paused': 0, 'cpu_time': 13021637090975L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 762984, 'maxmem_kb': -4, 'max_vcpu_id': 1, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 2, 'blocked': 0}) [2006-03-27 09:32:18 xend.XendDomainInfo] INFO (XendDomainInfo:211) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. [2006-03-27 09:32:18 xend] DEBUG (XendDomain:151) number of vcpus to use is 0 [2006-03-27 09:32:19 xend] INFO (SrvServer:114) unix path=/var/lib/xend/xend-socket [2006-03-27 09:32:22 xend] ERROR (XendBootloader:84) Boot loader didn't return any data! This file compared to the examples seems to be missing info, but that might be because the create -c didn't start/finish what it does. # cat /etc/xen/webserver1 # Automatically generated xen config file name = "webserver1" memory = "256" disk = [ 'file:/xen/webserver1,xvda,w' ] vif = [ 'mac=00:16:3e:14:83:a4' ] bootloader="/usr/bin/pygrub" on_reboot = 'restart' on_crash = 'restart' # xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 745 2 r----- 13017.5 -------------- next part -------------- An HTML attachment was scrubbed... URL: From winston at stdout.org Mon Mar 27 16:46:39 2006 From: winston at stdout.org (Winston Chang) Date: Mon, 27 Mar 2006 11:46:39 -0500 Subject: [Fedora-xen] xen domain creation problem In-Reply-To: References: Message-ID: <5EEB0CD9-8DDE-4CEC-B423-82EE19206FF1@stdout.org> I think the first error (about the ballooning) happens because there isn't enough RAM for your VM. Once you fix that, you should be able to run the installer properly. You may need to set your dom0 memory to your total memory minus 32MB (for xen) minus 256MB (for the fc5 installer). I have 512MB of RAM and it wouldn't work until I set the dom0 memory to 192MB. There's a line in my grub.conf that I modified to look like this: kernel /xen.gz-2.6.15-1.2054_FC5 dom0_mem=196608 As for the second problem, about the boot loader.... I'm trying to figure that out myself. --Winston On Mar 27, 2006, at 10:11 AM, David Rhodus wrote: > Hello. I am having problems getting xen setup and working on a FC5 > install. I have been following the instructions from > http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 > > [root at client ~]# xenguest-install.py > What is the name of your virtual machine? vmxen > How much RAM should be allocated (in megabytes)? 256 > What would you like to use as the disk (path)? /home/vmxen > How large would you like the disk to be (in gigabytes)? 4 > What is the install location? > http://download.fedora.redhat.com/pub/fedora/linux/core/5/i386/os/ > > > Starting install... > Using config file "/etc/xen/vmxen". > Error: Error creating domain: The privileged domain did not balloon! > If your install has exited, you can restart your guest by running > 'xm create -c vmxen'. Otherwise, you can reconnect to the console > by running 'xm console vmxen' > [root at client ~]# xm create -c vmxen > Using config file "/etc/xen/vmxen". > Traceback (most recent call last): > File "/usr/bin/pygrub", line 256, in ? > cf = get_config(file, isconfig) > File "/usr/bin/pygrub", line 139, in get_config > raise RuntimeError, "Unable to read filesystem" > RuntimeError: Unable to read filesystem > Error: Boot loader didn't return any data! > [root at client ~]# ls -l /home/vmxen > -rwxr-xr-x 1 root root 4294967297 Mar 27 09:22 /home/vmxen > [root at client ~]# > > I have attached xend-debug.log and xend.log files. > > Any hints on what I should look at next ? > > -- > David Rhodus > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From justin.conover at gmail.com Mon Mar 27 18:40:18 2006 From: justin.conover at gmail.com (Justin Conover) Date: Mon, 27 Mar 2006 12:40:18 -0600 Subject: [Fedora-xen] guests install problems In-Reply-To: <85531AA8-0883-4529-86EC-A8EAF1F62FE8@stdout.org> References: <85531AA8-0883-4529-86EC-A8EAF1F62FE8@stdout.org> Message-ID: On 3/27/06, Winston Chang wrote: > > I had the same problem and I just figured out a workaround. The > issue is that the curses screen-drawing library isn't happy -- it > can't print the nice grub-like kernel selection menu. On my > computer, this is because I sshed in from a Mac Terminal window. > When I connected via an xterm, it worked fine. > > Seems like a bug to me. > > --Winston That sounds like a good possiblity since I'm at work and sshd to it, I'll try running it on the box and see what happens. On Mar 27, 2006, at 10:34 AM, Justin Conover wrote: > > > I created a guest with the python script xenguest-install.py when I > > run > > > > # /usr/sbin/xm create -c webserver1 > > > > I get the following error > > > > > > Traceback (most recent call last): > > File "/usr/bin/pygrub", line 258, in ? > > curses.wrapper(run_main) > > File "/usr/lib/python2.4/curses/wrapper.py", line 44, in wrapper > > return func(stdscr, *args, **kwds) > > File "/usr/bin/pygrub", line 214, in run_main > > sel = main(cf) > > File "/usr/bin/pygrub", line 162, in main > > (stdscr, win) = draw_window() > > File "/usr/bin/pygrub", line 33, in draw_window > > curses.use_default_colors() > > _curses.error: use_default_colors() returned ERR > > Error: Boot loader didn't return any data! > > #xm log (3-27-06) > > > > [2006-03-27 09:30:26 xend] ERROR (XendBootloader:84) Boot loader > > didn't return any data! > > [2006-03-27 09:32:18 xend] INFO (SrvDaemon:192) Xend stopped due to > > signal 15. > > [2006-03-27 09:32:18 xend] INFO (SrvDaemon:285) Xend Daemon started > > [2006-03-27 09:32:18 xend] INFO (SrvDaemon:289) Xend changeset: > > unavailable . > > [2006-03-27 09:32:18 xend.XendDomainInfo] DEBUG (XendDomainInfo: > > 199) XendDomainInfo.recreate({'paused': 0, 'cpu_time': > > 13021637090975L, 'ssidref': 0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, > > 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying': 0, 'dom': > > 0, 'mem_kb': 762984, 'maxmem_kb': -4, 'max_vcpu_id': 1, 'crashed': > > 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 2, 'blocked': 0}) > > [2006-03-27 09:32:18 xend.XendDomainInfo] INFO (XendDomainInfo:211) > > Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. > > [2006-03-27 09:32:18 xend] DEBUG (XendDomain:151) number of vcpus > > to use is 0 > > [2006-03-27 09:32:19 xend] INFO (SrvServer:114) unix path=/var/lib/ > > xend/xend-socket > > [2006-03-27 09:32:22 xend] ERROR (XendBootloader:84) Boot loader > > didn't return any data! > > > > This file compared to the examples seems to be missing info, but > > that might be because the create -c didn't start/finish what it does. > > > > > > # cat /etc/xen/webserver1 > > > > # Automatically generated xen config file > > name = "webserver1" > > memory = "256" > > disk = [ 'file:/xen/webserver1,xvda,w' ] > > vif = [ 'mac=00:16:3e:14:83:a4' ] > > bootloader="/usr/bin/pygrub" > > > > on_reboot = 'restart' > > on_crash = 'restart' > > > > > > # xm list > > Name ID Mem(MiB) VCPUs State Time(s) > > Domain-0 0 745 2 r----- 13017.5 > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From tournesol33 at gmail.com Tue Mar 28 06:07:15 2006 From: tournesol33 at gmail.com (tournesol) Date: Tue, 28 Mar 2006 15:07:15 +0900 Subject: [Fedora-xen] Is guest-os only FC5 ? Message-ID: <4428D293.2070503@gmail.com> Hi all I am testing xen-3.0.1-4 on FC5 . when i tried install FC4 (not FC5 ) guest-os with xengust-install.py i got following error. ?xenguest-install.py ?What is the name of your virtual machine? FC4 How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /opt/fc4/fc4.img What is the install location? http://distro.ibiblio.org/pub/linux/distributions/fedora/linux/core/5/i386/os/ Invalid URL location given So the guest-os type that supported is only FC5 ? thanks tournesol From tournesol33 at gmail.com Tue Mar 28 06:43:09 2006 From: tournesol33 at gmail.com (tournesol) Date: Tue, 28 Mar 2006 15:43:09 +0900 Subject: [Fedora-xen] xen on fc5 Message-ID: <4428DAFD.8080008@gmail.com> Hi again I hava another guestions again. Q1: The xenguest-install.py was modified by FC5 team ? or xen team ? Can i run it on FC4 (or FC2,3) with xen-3.0.1-4 later? Q2: What is the difference between DomU kernel and Dom0 kernel ? Which should i run ? Q3: Where is the anaconda comes ? when i install the guest-os via VNC anaconda , the anaconda comes from host-os ? or from xen? thanks for your help. tournesol From tournesol33 at gmail.com Tue Mar 28 09:26:44 2006 From: tournesol33 at gmail.com (tournesol) Date: Tue, 28 Mar 2006 18:26:44 +0900 Subject: [Fedora-xen] Is guest-os only FC5 ? In-Reply-To: <4428F138.3050608@Bellsouth.net> References: <4428D293.2070503@gmail.com> <4428F138.3050608@Bellsouth.net> Message-ID: <44290154.3000706@gmail.com> Thanks for your advice. I tried intall guest-os(FC4) again #xenguest-install.py What is the name of your virtual machine? fc4 How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /opt/fc4 What is the install location? ftp://ftp.riken.jp/Linux/fedora/core/4/i386/os Invalid URL location given /*another ftp site*/ xenguest-install.py What is the name of your virtual machine? fc4 How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /opt/fc4 What is the install location? ftp://ftp.jaist.ac.jp/pub/Linux/Fedora/core/4/i386/os Invalid URL location given any ideas ? tournesol Otter wrote: >tournesol wrote: > > >>Hi all >> >>I am testing xen-3.0.1-4 on FC5 . when i tried install FC4 (not FC5 ) >>guest-os with xengust-install.py i got following error. >>?xenguest-install.py >>?What is the name of your virtual machine? FC4 >>How much RAM should be allocated (in megabytes)? 256 >>What would you like to use as the disk (path)? >>/opt/fc4/fc4.img >>What is the install location? >>http://distro.ibiblio.org/pub/linux/distributions/fedora/linux/core/5/i386/os/ >>Invalid URL location given >> >>So the guest-os type that supported is only FC5 ? >> >>thanks >>tournesol >> >>-- >>Fedora-xen mailing list >>Fedora-xen at redhat.com >>https://www.redhat.com/mailman/listinfo/fedora-xen >> >> >> >> >For the disk path, try using a directory >/opt/fc4/ > >the name you specify for the virtual machine is used as the name. > >So if you want fc4.img use: > >?What is the name of your virtual machine? fc4.img >How much RAM should be allocated (in megabytes)? 256 >What would you like to use as the disk (path)? >/opt/fc4/ >What is the install location? >http://distro.ibiblio.org/pub/linux/distributions/fedora/linux/core/5/i386/os/ > > > >For your 2nd question. I am not sure. I have only worked with the >installer on FC5. But the Fedora install script was actually in the Test >releases of FC4, so I imagine in works. > > > From filipe.miranda at gmail.com Tue Mar 28 19:46:32 2006 From: filipe.miranda at gmail.com (Filipe Miranda) Date: Tue, 28 Mar 2006 16:46:32 -0300 Subject: [Fedora-xen] Xen 3.0 on FC5 problems Message-ID: Hello there, I'm new to this xen technology and I'm trying it on FC5 but I'm having a hardtime trying to setup a guest xen machine. Here is what I did and all the error messages: The directory /nfs/fc5 has the following content: [root at fc5 fc5]# ls /nfs/fc5/ Fedora figs images isolinux repodata stylesheet-images I folllowed the steps described on http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 [root at fc5 fc5]# /usr/sbin/xenguest-install.py What is the name of your virtual machine? fc5 How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /xen/fc5 What is the install location? nfs:fc5:/nfs/fc5 Starting install... Using config file "/etc/xen/fc5". Error: Device 51712 (vbd) could not be connected. Backend device not found. If your install has exited, you can restart your guest by running 'xm create -c fc5'. Otherwise, you can reconnect to the console by running 'xm console fc5' Any suggestions? -- Att. --- Filipe T Miranda -------------- next part -------------- An HTML attachment was scrubbed... URL: From tournesol33 at gmail.com Wed Mar 29 01:26:27 2006 From: tournesol33 at gmail.com (tournesol) Date: Wed, 29 Mar 2006 10:26:27 +0900 Subject: [Fedora-xen] Is guest-os only FC5 ? In-Reply-To: <44292065.2040408@Bellsouth.net> References: <4428D293.2070503@gmail.com> <4428F138.3050608@Bellsouth.net> <44290154.3000706@gmail.com> <44292065.2040408@Bellsouth.net> Message-ID: <4429E243.4030108@gmail.com> Hi Otter As your advice i tired again # xenguest-install.py What is the name of your virtual machine? fc4 How much RAM should be allocated (in megabytes)? 260 What would you like to use as the disk (path)? /opt/fc4 What is the install location? ftp://ftp.riken.jp/Linux/fedora/core/4/i386/os/ Invalid URL location given #xenguest-install.py What is the name of your virtual machine? fc4 How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /opt/fc4 What is the install location? ftp://ftp.kddilabs.jp/Linux/packages/fedora/core/4/i386/os/ Invalid URL location given realy need backslash ? tournesol Otter wrote: >tournesol wrote: > > >>Thanks for your advice. >> >>I tried intall guest-os(FC4) again >> >>#xenguest-install.py >>What is the name of your virtual machine? fc4 >>How much RAM should be allocated (in megabytes)? 256 >>What would you like to use as the disk (path)? /opt/fc4 >>What is the install location? ftp://ftp.riken.jp/Linux/fedora/core/4/i386/os >>Invalid URL location given >> >>/*another ftp site*/ >> >>xenguest-install.py >>What is the name of your virtual machine? fc4 >>How much RAM should be allocated (in megabytes)? 256 >>What would you like to use as the disk (path)? /opt/fc4 >>What is the install location? >>ftp://ftp.jaist.ac.jp/pub/Linux/Fedora/core/4/i386/os >>Invalid URL location given >> >>any ideas ? >> >>tournesol >> >>Otter wrote: >> >> >> >> >>>tournesol wrote: >>> >>> >>> >>> >>> >>>>Hi all >>>> >>>>I am testing xen-3.0.1-4 on FC5 . when i tried install FC4 (not FC5 ) >>>>guest-os with xengust-install.py i got following error. >>>>?xenguest-install.py >>>>?What is the name of your virtual machine? FC4 >>>>How much RAM should be allocated (in megabytes)? 256 >>>>What would you like to use as the disk (path)? >>>>/opt/fc4/fc4.img >>>>What is the install location? >>>>http://distro.ibiblio.org/pub/linux/distributions/fedora/linux/core/5/i386/os/ >>>>Invalid URL location given >>>> >>>>So the guest-os type that supported is only FC5 ? >>>> >>>>thanks >>>>tournesol >>>> >>>>-- >>>>Fedora-xen mailing list >>>>Fedora-xen at redhat.com >>>>https://www.redhat.com/mailman/listinfo/fedora-xen >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>For the disk path, try using a directory >>>/opt/fc4/ >>> >>>the name you specify for the virtual machine is used as the name. >>> >>>So if you want fc4.img use: >>> >>>?What is the name of your virtual machine? fc4.img >>>How much RAM should be allocated (in megabytes)? 256 >>>What would you like to use as the disk (path)? >>>/opt/fc4/ >>>What is the install location? >>>http://distro.ibiblio.org/pub/linux/distributions/fedora/linux/core/5/i386/os/ >>> >>> >>> >>>For your 2nd question. I am not sure. I have only worked with the >>>installer on FC5. But the Fedora install script was actually in the Test >>>releases of FC4, so I imagine in works. >>> >>> >>> >>> >>> >>> >> >> >> >Anytime it ask for a disk path, or install path, use a backslash at the end, as its expecting a directory " / " > > >What would you like to use as the disk (path)? /opt/fc4/ >What is the install location? ftp://ftp.riken.jp/Linux/fedora/core/4/i386/os/ > >adding those slashes, you should get prompted " how much disk space " > > > > From riel at redhat.com Wed Mar 29 02:57:03 2006 From: riel at redhat.com (Rik van Riel) Date: Tue, 28 Mar 2006 21:57:03 -0500 (EST) Subject: [Fedora-xen] Page space questions In-Reply-To: <47676.192.168.8.28.1143464048.squirrel@digitalhermit.com> References: <47676.192.168.8.28.1143464048.squirrel@digitalhermit.com> Message-ID: On Mon, 27 Mar 2006, Kwan Lowe wrote: > If this is fatally flawed reasoning, another thought would be to have a > monitor process on each DomainU report back to the Domain0. It would > send memory commit information which the Domain0 could use to mem-set > the DomainU's lower or higher. I'm thinking of a dynamic memory > allocation scheme that could better utilize available physical memory. This idea would work, but the domU that shrinks may still need to move some data from its memory into its own swap area. The problem is measuring how much memory each domU really needs. I've got some ideas on that, which I'll be presenting at this year's Ottawa Linux Symposium. Once I've finished writing my paper I'll start making some info available... -- All Rights Reversed From riel at redhat.com Wed Mar 29 02:59:43 2006 From: riel at redhat.com (Rik van Riel) Date: Tue, 28 Mar 2006 21:59:43 -0500 (EST) Subject: [Fedora-xen] xen on fc5 In-Reply-To: <4428DAFD.8080008@gmail.com> References: <4428DAFD.8080008@gmail.com> Message-ID: On Tue, 28 Mar 2006, tournesol wrote: > Q1: The xenguest-install.py was modified by FC5 team ? or xen team ? It was written by one of the Fedora developers, Jeremy to be precise. > Can i run it on FC4 (or FC2,3) with xen-3.0.1-4 later? It might work, but then again it might not. You may be the first to try ;) > Q2: What is the difference between DomU kernel and Dom0 kernel ? > Which should i run ? The domU kernel: - has no drivers for real hardware, since it runs as a virtual machine - gets its /boot/grub/grub.conf entry suitable for booting inside a guest with pygrub > Q3: Where is the anaconda comes ? > when i install the guest-os via VNC anaconda , the anaconda comes from > host-os ? or from xen? At that point anaconda is running inside the guest OS. -- All Rights Reversed From tournesol33 at gmail.com Wed Mar 29 04:12:59 2006 From: tournesol33 at gmail.com (tournesol) Date: Wed, 29 Mar 2006 13:12:59 +0900 Subject: [Fedora-xen] Is guest-os only FC5 ? In-Reply-To: <4429F420.9030500@Bellsouth.net> References: <4428D293.2070503@gmail.com> <4428F138.3050608@Bellsouth.net> <44290154.3000706@gmail.com> <44292065.2040408@Bellsouth.net> <4429E243.4030108@gmail.com> <4429F420.9030500@Bellsouth.net> Message-ID: <442A094B.8070909@gmail.com> I think it is not slash problem let me show you detail # xenguest-install.py What is the name of your virtual machine? fc4 How much RAM should be allocated (in megabytes)? 260 What would you like to use as the disk (path)? /opt/fc4/ What is the install location? ftp://ftp.riken.jp/Linux/fedora/core/4/i386/os/ Invalid URL location given Otter wrote: >You are still missing the slash here: > >What would you like to use as the disk (path)? /opt/fc4 > >use >What would you like to use as the disk (path)? /opt/fc4/ > > > > From kwan at digitalhermit.com Wed Mar 29 04:20:40 2006 From: kwan at digitalhermit.com (Kwan Lowe) Date: Tue, 28 Mar 2006 23:20:40 -0500 (EST) Subject: [Fedora-xen] FC5 installation notes Message-ID: <44650.192.168.8.28.1143606040.squirrel@digitalhermit.com> Just posting my installation notes here in case someone finds them useful: Installation media setup: Setup FTP yum -y install vsftpd service vsftpd start Loopback mount the installation DVD to /var/ftp/pub mount -o loop /export/C-5-i386-DVD.iso /var/ftp/pub Create a VBD for the installation lvcreate -L 3G -n xm-fc5-001_lv rootvg Run the installation xenguest-install.py -n xm-fc5-001 \ -f /dev/rootvg/xm-fc5-001_lv \ -r 256 -l ftp://192.168.0.10/pub/ Caveats: Installer doesn't check if enough memory is available. Drop to run level 3 and/or mem-set other existing dom0s to lower memory (or shut them off). Installation path is to the root of the DVD, not the Yum repository package path. Copying an LVM (easy way to duplicate VBD) 1) Start with an installed DHCP enabled domU. 2) lvcreate -L 2G -n copyof_xm rootvg 3) cd /dev/mapper; dd if=rootvg-xm of=rootvg-copyof--xm bs=1M 4) cp /etc/xen/xm /etx/xen/copyof_xm 5) edit /etc/xen/copyof_xm; change the MAC, name 6) xm create copyof_xm -- * The Digital Hermit http://www.digitalhermit.com * Unix and Linux Solutions kwan at digitalhermit.com From kwan at digitalhermit.com Wed Mar 29 10:31:01 2006 From: kwan at digitalhermit.com (Kwan Lowe) Date: Wed, 29 Mar 2006 05:31:01 -0500 (EST) Subject: [Fedora-xen] Automated installations via kickstart Message-ID: <59387.192.168.8.28.1143628261.squirrel@digitalhermit.com> Whoohoo! Finally got xen/kickstart to do a complete hands-off installation. The goal is to be able to provision an OS for a customer (internal/external) with as little interaction as possible, giving me more time to drink my coffee :D. The kickstart piece makes it as easy/easier than AIX NIM installations... I used the anaconda_ks.cfg from a previously installed domU and made a few changes. To use it with xenguest-install.py you need to specify the kickstart file with the "-x" option: xenguest-install.py -n xm-fc4-004 \ -f /dev/rootvg/xm-fc4-004_lv \ -r 256 -l ftp://192.168.8.21/pub \ -x ks=ftp://192.168.8.21/xm-fc4-004_ks.cfg The kickstart file follows. Some notes: If you start with an anaconda generated file you need to add the keyboard directive. For some reason it does not save this information (bug??). The zerombr directive will also destroy the existing LVM volume so use with care. The rootpw directive needs to be changed in the example. You'd probably want to change the bootproto option also. I'm hand-editing the IP info because I already have DNS entries. # Kickstart file automatically generated by anaconda. install url --url ftp://192.168.8.21//pub lang en_US.UTF-8 keyboard us network --device eth0 --bootproto static --ip 192.168.8.64 --netmask 255.255.255.0 --gateway 192.168.8.1 --nameserver 192.168.8 rootpw --iscrypted $1$ma1gooDL$myPaSsw0rdhashwh000h000 firewall --enabled --port=22:tcp authconfig --enableshadow --enablemd5 selinux --disabled timezone America/New_York bootloader --location=mbr --driveorder=xvda reboot zerombr yes clearpart --all part /boot --fstype ext3 --size=100 part swap --size=256 part pv.00 --size=1 --grow --asprimary volgroup rootvg pv.00 logvol / --name root_lv --vgname=rootvg --size=400 logvol swap --name swap_lv --vgname=rootvg --size=256 logvol /usr --name usr_lv --vgname=rootvg --size=2000 logvol /tmp --name tmp_lv --vgname=rootvg --size=200 logvol /var --name var_lv --vgname=rootvg --size=200 logvol /home --name home_lv --vgname=rootvg --size=400 %packages @admin-tools @base @core @dns-server @editors @text-internet @web-server comps-extras cracklib-dicts gnome-mime-data rmt tzdata %post -- * The Digital Hermit http://www.digitalhermit.com * Unix and Linux Solutions kwan at digitalhermit.com From sxu1902 at 163.com Wed Mar 29 15:08:02 2006 From: sxu1902 at 163.com (sxu1902) Date: Wed, 29 Mar 2006 23:08:02 +0800 (CST) Subject: [Fedora-xen] VMX guest machine issue Message-ID: <442AA2D2.0000C7.19638@bj163app50.163.com> Hi, I am testing Xen3 on FC5. My FC5 is x86_64. My box is using Pentium D 920 on Asus P5LD2-VM motherboard with 2G RAM. After installation, "xm list" shows domain0 running ok. I use: dd if=/dev/zero of=/hdd_mnt/sda5/g_img/gl112/gl112.img bs=1M count=1 seek=10240 to create iamge file. And the paremeter file look like this: # Automatically generated xen config file name = "gl112" builder = "hvm" memory = "256" acpi = 0 apic = 0 cdrom = '/hdd_mnt/sda5/dvd/CentOS-4.3-i386-binDVD.iso' #cdrom = '/dev/cdrom' boot = 'd' disk = [ 'file:/hdd_mnt/sda5/g_img/gl112/gl112.img,ioemu:hda,w' ] vif = [ 'type=ioemu,bridge=xenbr0,mac=00:17:3e:59:78:30' ] on_reboot = 'restart' on_crash = 'restart' #on_poweroff = 'destroy' kernel = '/usr/lib/xen/boot/hvmloader' device_model = '/usr/lib64/xen/bin/qemu-dm' sdl = 1 # use SDL for graphics vnc = 0 # use VNC for graphics vncviewer = 0 # spawn vncviewer by default nographic = 0 # don't use graphics serial = 'pty' # enable serial console I tried different linux distributions as VMX guest. It appears to me the guest machine always reboot itself when loading the linux from CD images or CDs. Sometimes it even freezes domain0. Occasionally it boots into the installation CD (after reboot itself once) and tells me it can't find hard drive, so it can't proceed with the installation... Anybody tested VMX? Any similar problems? Any suggestions? Sam Xu -------------- next part -------------- An HTML attachment was scrubbed... URL: From rmo at sunnmore.net Wed Mar 29 15:16:47 2006 From: rmo at sunnmore.net (Roy-Magne Mo) Date: Wed, 29 Mar 2006 17:16:47 +0200 Subject: [Fedora-xen] Is guest-os only FC5 ? In-Reply-To: <442A094B.8070909@gmail.com> References: <4428D293.2070503@gmail.com> <4428F138.3050608@Bellsouth.net> <44290154.3000706@gmail.com> <44292065.2040408@Bellsouth.net> <4429E243.4030108@gmail.com> <4429F420.9030500@Bellsouth.net> <442A094B.8070909@gmail.com> Message-ID: <1143645407.28653.2.camel@localhost.localdomain> on den 29.03.2006 klokka 13:12 (+0900) skreiv tournesol: > I think it is not slash problem > > let me show you detail > > # xenguest-install.py > What is the name of your virtual machine? fc4 > How much RAM should be allocated (in megabytes)? 260 > What would you like to use as the disk (path)? /opt/fc4/ > What is the install location? > ftp://ftp.riken.jp/Linux/fedora/core/4/i386/os/ > Invalid URL location given You can only install distros which have a native XEN guest kernel, AFAIK this is only FC5 and rawhide at the moment. If you want other preinstalled distros, you might find this site interesting: http://jailtime.org/ -- Roy-Magne Mo From brads at redhat.com Wed Mar 29 16:34:58 2006 From: brads at redhat.com (Brad Smith) Date: Wed, 29 Mar 2006 11:34:58 -0500 Subject: [Fedora-xen] Problems with Xen + FC5 + Thinkpad Message-ID: <442AB732.1070208@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, I recently upgraded from FC4 to FC5 on my Thinkpad T30 laptop and am looking forward to playing with Xen. However, I've hit a few stumbling blocks along the way. Following the instructions at http://www.fedoraproject.org/wiki/FedoraXenQuickstartFC5 I installed the Xen0 kernel and booted my system with it. However it hangs, seemingly forever, at the "Starting xend" stage. The OS seems ok as keypresses are still printed to the screen, but because the daemon never completes its startup process the boot sequence never finishes. Upon rebooting I noticed an error that gets printed while the kernel is loading, which says that it could not bind IRQ2 to guest because it is in use by cascade. This happens consistently, so I wonder if it's a hardware problem? I booted the system into single user mode and chkconfig'd xend off, booted normally and attempted to start the daemon post-boot. It printed a message about starting the Bridged Firewall, which I had not seen during bootup, but still seemed to hang indefinitely. Oh, and SELinux is loaded but not enforcing. Should that be sufficient? Does anyone have suggestions for how I might further troubleshoot this? Thanks, - --Brad -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFEKrcaDvp49DvQ8kcRAv8yAJ0cHBQsP3KwEGb+x9GZTXga6e24/ACeIQG6 MCywwa529LxnXECf2YLo4SI= =Z3wj -----END PGP SIGNATURE----- From veillard at redhat.com Wed Mar 29 17:05:08 2006 From: veillard at redhat.com (Daniel Veillard) Date: Wed, 29 Mar 2006 12:05:08 -0500 Subject: [Fedora-xen] Problems with Xen + FC5 + Thinkpad In-Reply-To: <442AB732.1070208@redhat.com> References: <442AB732.1070208@redhat.com> Message-ID: <20060329170508.GF14102@redhat.com> On Wed, Mar 29, 2006 at 11:34:58AM -0500, Brad Smith wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hello all, > > I recently upgraded from FC4 to FC5 on my Thinkpad T30 laptop and am looking forward to playing with > Xen. However, I've hit a few stumbling blocks along the way. Following the instructions at Try to make a clean install to make sure you really have all FC5 bits. You can check /var/log/xend.log for hints on what's going wrong. Daniel -- Daniel Veillard | Red Hat http://redhat.com/ veillard at redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From rmo at sunnmore.net Wed Mar 29 19:28:55 2006 From: rmo at sunnmore.net (Roy-Magne Mo) Date: Wed, 29 Mar 2006 21:28:55 +0200 Subject: [Fedora-xen] Is guest-os only FC5 ? In-Reply-To: <20060329142659.3787d0de@aud.vb.futz.org> References: <4428D293.2070503@gmail.com> <4428F138.3050608@Bellsouth.net> <44290154.3000706@gmail.com> <44292065.2040408@Bellsouth.net> <4429E243.4030108@gmail.com> <4429F420.9030500@Bellsouth.net> <442A094B.8070909@gmail.com> <1143645407.28653.2.camel@localhost.localdomain> <20060329142659.3787d0de@aud.vb.futz.org> Message-ID: <1143660536.2464.3.camel@host-81-191-138-133.bluecom.no> on den 29.03.2006 klokka 14:26 (-0500) skreiv Robert Story: > On Wed, 29 Mar 2006 17:16:47 +0200 Roy-Magne wrote: > RMM> You can only install distros which have a native XEN guest kernel, AFAIK > RMM> this is only FC5 and rawhide at the moment. > > That may be a restriction imposed by the FC5 anaconda installer, but I don't > think it's true in general. > > Although I'm using the FC5 domU kernel, I've got 2 domUs running CentOS 4.3. A > little more work to install, but they are working fine. I don't mean that FC5 is the only distribution that could run under XEN in Fedora, but it's problably one of the few that can be installed unmodified. -- Roy-Magne Mo From rstory-l at 2006.revelstone.com Wed Mar 29 19:33:17 2006 From: rstory-l at 2006.revelstone.com (Robert Story) Date: Wed, 29 Mar 2006 14:33:17 -0500 Subject: [Fedora-xen] Problems with Xen + FC5 + Thinkpad In-Reply-To: <442AB732.1070208@redhat.com> References: <442AB732.1070208@redhat.com> Message-ID: <20060329143317.7efcd1bc@aud.vb.futz.org> On Wed, 29 Mar 2006 11:34:58 -0500 Brad wrote: BS> -----BEGIN PGP SIGNED MESSAGE----- BS> Hash: SHA1 BS> BS> Hello all, BS> BS> I recently upgraded from FC4 to FC5 on my Thinkpad T30 laptop and am BS> looking forward to playing with Xen. However, I've hit a few stumbling BS> blocks along the way. Following the instructions at BS> BS> http://www.fedoraproject.org/wiki/FedoraXenQuickstartFC5 BS> BS> I installed the Xen0 kernel and booted my system with it. However it BS> hangs, seemingly forever, at the "Starting xend" stage. Did you do the part about updating grub to include 'init 3' to disable X? If so, go back and delete the 'init' (you just need '3'). This fixed the dom0 kernel hang I had. I asked someone in the #fedora irc channel to fix this, but it's still there. If anyone can fix it, it also needs to be fixed on http://www.fedoraproject.org/wiki/FedoraXenQuickstart From yongkang.you at intel.com Thu Mar 30 01:34:15 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Thu, 30 Mar 2006 09:34:15 +0800 Subject: [Fedora-xen] VMX guest machine issue Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A20AC@pdsmsx402.ccr.corp.intel.com> Hi Sam, FC5 release has some known issue to play with VMX in x86_64, e.g. destroying IA32 VMX will hang Xen0 and creating x86_64 VMX will reboot Xen0. This bug will be fixed in the FC5 update. I am not sure if it is there now. Seemed not? A way is worthy to have a try, if you don?t want to wait for FC5 update to test. Get the Xen source RPM package from FC5 and only re-make xen (go into xen folder to do make, you don?t need to remake xen0 and xenU). After making finishes, copy xen.gz to /boot and replace the old hypervisor kernel. Reboot~. I didn?t find any error in your config file. But the error info ?it can't find hard drive? is very strange. Did you try the FC5 or FC4 ISO to install? Have a look at /var/log/xend.log to see if the disk option (hda) has been sent to qemu, such like: /usr/lib64/xen/bin/qemu-dm', '-d', '1?, '-m', '256', '-boot', 'c', '-serial', 'pty', '-vcpus', '1', '-domain-name', 'ExampleHVMDomain', '-hda', '/xxx/xxx.img', '-hdb', '/xxx/yyy.img', '-macaddr', '00:16:3e:00:00:11', '-bridge', 'xenbr0', '-nics', '1' BTW, you can find a lot of OS installed disk image in http://free.oszoo.org/ . Best Regards, Yongkang (Kangkang) ?? ________________________________ From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of sxu1902 Sent: 2006?3?29? 23:08 To: fedora-xen at redhat.com Subject: [Fedora-xen] VMX guest machine issue Hi, I am testing Xen3 on FC5. My FC5 is x86_64. My box is using Pentium D 920 on Asus P5LD2-VM motherboard with 2G RAM. After installation, "xm list" shows domain0 running ok. I use: dd if=/dev/zero of=/hdd_mnt/sda5/g_img/gl112/gl112.img bs=1M count=1 seek=10240 to create iamge file. And the paremeter file look like this: # Automatically generated xen config file name = "gl112" builder = "hvm" memory = "256" acpi = 0 apic = 0 cdrom = '/hdd_mnt/sda5/dvd/CentOS-4.3-i386-binDVD.iso' #cdrom = '/dev/cdrom' boot = 'd' disk = [ 'file:/hdd_mnt/sda5/g_img/gl112/gl112.img,ioemu:hda,w' ] vif = [ 'type=ioemu,bridge=xenbr0,mac=00:17:3e:59:78:30' ] on_reboot = 'restart' on_crash = 'restart' #on_poweroff = 'destroy' kernel = '/usr/lib/xen/boot/hvmloader' device_model = '/usr/lib64/xen/bin/qemu-dm' sdl = 1 # use SDL for graphics vnc = 0 # use VNC for graphics vncviewer = 0 # spawn vncviewer by default nographic = 0 # don't use graphics serial = 'pty' # enable serial console I tried different linux distributions as VMX guest. It appears to me the guest machine always reboot itself when loading the linux from CD images or CDs. Sometimes it even freezes domain0. Occasionally it boots into the installation CD (after reboot itself once) and tells me it can't find hard drive, so it can't proceed with the installation... Anybody tested VMX? Any similar problems? Any suggestions? Sam Xu ? ? ? 2006 ? ? ? ? ? ? ? ? ? ? ? ? ? 1.1 ? ? ? ? ? ? ? ? 2000 ? ? ? ? ? ? ? ? ? ? 280 ? ? ? ? ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From brads at redhat.com Thu Mar 30 12:14:44 2006 From: brads at redhat.com (Brad Smith) Date: Thu, 30 Mar 2006 07:14:44 -0500 Subject: [Fedora-xen] Disk problems on FC5 Message-ID: <442BCBB4.7090906@redhat.com> Hi folks, I set up Xen on a freshly-installed FC5 system, configured the guest using xenguest-install.py and then began an installation via VNC. However, as soon as I got to the partitioning phase I received an error that the partition table for my disk couldn't be read. I opted to ignore this as I've seen that error even on real systems and have proceeded without incident. However, the installer continued to produce errors about not being able to find the disk, being unable to read the partition table, etc and eventually just died. Looking at the disk file I told Xen to create (I gave it 4096 as the size) it appears to have a size of 0. Is that the way it should be? Any further advice for troubleshooting? Thanks, --Brad From aleksander.adamowski.redhat at altkom.com.pl Thu Mar 30 09:43:31 2006 From: aleksander.adamowski.redhat at altkom.com.pl (Aleksander Adamowski) Date: Thu, 30 Mar 2006 11:43:31 +0200 Subject: [Fedora-xen] 2.6.15-1.2054_FC5xen0 - no network for guest domains In-Reply-To: <1142889317.21593.41.camel@orbit.scot.redhat.com> References: <441B041E.6060204@altkom.com.pl> <1142889317.21593.41.camel@orbit.scot.redhat.com> Message-ID: <442BA843.9010700@altkom.com.pl> Stephen C. Tweedie wrote: >This does not look at *all* like a normal xen networking config: > > >># ifconfig >>eth0 Link encap:Ethernet HWaddr 00:15:60:0B:ED:88 >> Interrupt:17 >> >> >this implies that eth0 is a physical device; > > >>eth0:0 Link encap:Ethernet HWaddr 00:15:60:0B:ED:88 >> inet addr:192.168.254.4 Bcast:192.168.254.255 Mask:255.255.255.0 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> Interrupt:17 >> >> >with an alias; > > You were right, it seems that the eth0:0 alias had confused the network startup scripts and they didn't set up the bridging and virtual interfaces correctly. In my case "brctl show" has been showing a "Function not implemented" error in the interfaces column. I got rid of the unnecessary (not anymore) alias from ifcfg-eth0:0 and assigned it's IP address to ifcfg-eth0. Restarting the network afterwards using the /etc/init.d/network script didn't solve the problem, but rebooting the system did - all virtual inferfaces and bridging started working properly. Here's my current state: [root at domzero2 ~]# ifconfig eth0 Link encap:Ethernet HWaddr 00:15:60:0B:ED:88 inet addr:192.168.254.4 Bcast:192.168.254.255 Mask:255.255.255.0 inet6 addr: fe80::215:60ff:fe0b:ed88/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3953 errors:0 dropped:0 overruns:0 frame:0 TX packets:3482 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:470410 (459.3 KiB) TX bytes:446958 (436.4 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:209 errors:0 dropped:0 overruns:0 frame:0 TX packets:209 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:32078 (31.3 KiB) TX bytes:32078 (31.3 KiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:3989 errors:0 dropped:0 overruns:0 frame:0 TX packets:3485 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:488345 (476.8 KiB) TX bytes:463068 (452.2 KiB) Interrupt:17 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:3489 errors:0 dropped:0 overruns:0 frame:0 TX packets:3961 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:448316 (437.8 KiB) TX bytes:471006 (459.9 KiB) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:701 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:38658 (37.7 KiB) TX bytes:468 (468.0 b) [root at domzero2 ~]# brctl show bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no peth0 vif0.0 [root at domzero2 ~]# netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.254.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 192.168.254.1 0.0.0.0 UG 0 0 0 eth0 [root at domzero2 ~]# dmesg | egrep '(eth|vif|xenbr)' eth0: Tigon3 [partno(349321-001) rev 2100 PHY(5704)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:15:60:0b:ed:88 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] Split[0] WireSpeed[1] TSOcap[0] eth0: dma_rwctrl[769f4000] eth1: Tigon3 [partno(349321-001) rev 2100 PHY(5704)] (PCIX:133MHz:64-bit) 10/100/1000BaseT Ethernet 00:15:60:0b:ed:87 eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] Split[0] WireSpeed[1] TSOcap[1] eth1: dma_rwctrl[769f4000] tg3: eth0: Link is up at 100 Mbps, full duplex. tg3: eth0: Flow control is off for TX and off for RX. eth0: no IPv6 routers present device vif0.0 entered promiscuous mode xenbr0: port 1(vif0.0) entering learning state xenbr0: topology change detected, propagating xenbr0: port 1(vif0.0) entering forwarding state ADDRCONF(NETDEV_UP): peth0: link is not ready tg3: peth0: Link is up at 100 Mbps, full duplex. tg3: peth0: Flow control is off for TX and off for RX. ADDRCONF(NETDEV_CHANGE): peth0: link becomes ready device peth0 entered promiscuous mode xenbr0: port 2(peth0) entering learning state xenbr0: topology change detected, propagating xenbr0: port 2(peth0) entering forwarding state xenbr0: no IPv6 routers present vif0.0: no IPv6 routers present peth0: no IPv6 routers present eth0: no IPv6 routers present >With xen, normally you have no physical eth0: eth0 is a virtual loopback >net device, the other end of which is bound to vif0.0; the original >physical eth0 is renamed to peth0; and vif0.0 and peth0 are bridged >together on xenbr0. So once I start a domU guest in such an >environment, bridging shows: > ># brctl show >bridge name bridge id STP enabled interfaces >xenbr0 8000.feffffffffff no peth0 > vif0.0 > vif1.0 > >Your environment has no virtual eth0, no renamed physical peth0 and no >loopback vif0.0; it doesn't look like any of the dom0 bits that xen >tries to set up have been initialised. What sort of network config did >you have set up before starting xend? What does "brctl show" show? > > Thanks for the hint, it has directed me on the right tracks! BTW. Would it be possible to make the Xen network stuff support migrating to Xen from a setup with aliases on physical interfaces, like in my case? I predict that this scenario will be quite typical of migrations to Xen: imagine one has a server with multiple aliases on a physical interface (because there are several services that depend on specifiv IP addresses - as it was in my case). Such a setup is of course a typical candidate for migrating to a virtualized server setup with Xen - I think there will be more people with setups like mine, wanting to switch to Xen as flawlessly as possible. Not very nice that interface aliases currently aren't handled gracefully - it would be good to make it work for next RHEL... What's your opinion? -- Best Regards, Aleksander Adamowski GG#: 274614 ICQ UIN: 19780575 http://olo.ab.altkom.pl From aleksander.adamowski.redhat at altkom.com.pl Thu Mar 30 11:23:52 2006 From: aleksander.adamowski.redhat at altkom.com.pl (Aleksander Adamowski) Date: Thu, 30 Mar 2006 13:23:52 +0200 Subject: [Fedora-xen] "xm create" error: /usr/lib64/python2.4/site-packages/xen/xm/opts.py:452: DeprecationWarning: Non-ASCII character '\xeb' Message-ID: <442BBFC8.4060700@altkom.com.pl> Introduction: when one installs a Xen guest using xenguest-install.py, at the end of the installation the guest is shutdown and xenguest-install.py prints out instructions to start it up with "xm create -c GUEST_NAME". The instructions are wrong - the parameter to "-c" switch is a file name, so a full path is needed. So the instructions should read "xm create -c /etc/xen/GUEST_NAME" instead. If one proceeds according to the instructions, and the current working directory isn't /etc/xen, an unhelpful error will occur: --- SNIP ---- [root at domzero2 xen]# xm create -c svn Using config file "svn". /usr/lib64/python2.4/site-packages/xen/xm/opts.py:452: DeprecationWarning: Non-ASCII character '\xeb' in file svn on line 1, but no encoding declared; see http://www.python.org/peps/pep-0263.html for details execfile(defconfig, globs, locs) Error: invalid syntax (svn, line 1) [root at domzero2 xen]# hexdump -C /etc/xen/svn 00000000 23 20 41 75 74 6f 6d 61 74 69 63 61 6c 6c 79 20 |# Automatically | 00000010 67 65 6e 65 72 61 74 65 64 20 78 65 6e 20 63 6f |generated xen co| 00000020 6e 66 69 67 20 66 69 6c 65 0a 6e 61 6d 65 20 3d |nfig file.name =| 00000030 20 22 73 76 6e 22 0a 6d 65 6d 6f 72 79 20 3d 20 | "svn".memory = | 00000040 22 35 31 32 22 0a 64 69 73 6b 20 3d 20 5b 20 27 |"512".disk = [ '| 00000050 66 69 6c 65 3a 2f 76 61 72 2f 78 65 6e 2f 73 76 |file:/var/xen/sv| 00000060 6e 2c 78 76 64 61 2c 77 27 20 5d 0a 76 69 66 20 |n,xvda,w' ].vif | 00000070 3d 20 5b 20 27 6d 61 63 3d 30 30 3a 31 36 3a 33 |= [ 'mac=00:16:3| 00000080 65 3a 33 62 3a 38 65 3a 34 63 27 20 5d 0a 62 6f |e:3b:8e:4c' ].bo| 00000090 6f 74 6c 6f 61 64 65 72 3d 22 2f 75 73 72 2f 62 |otloader="/usr/b| 000000a0 69 6e 2f 70 79 67 72 75 62 22 0a 0a 6f 6e 5f 72 |in/pygrub"..on_r| 000000b0 65 62 6f 6f 74 20 20 20 3d 20 27 72 65 73 74 61 |eboot = 'resta| 000000c0 72 74 27 0a 6f 6e 5f 63 72 61 73 68 20 20 20 20 |rt'.on_crash | 000000d0 3d 20 27 72 65 73 74 61 72 74 27 0a |= 'restart'.| 000000dc --- SNIP ---- Of course, there's no "EB" byte in this guest config file, as can be seen on the hexdump! When starting the guest using a full path all is OK: --- SNIP ---- [root at domzero2 xen]# xm create -c /etc/xen/svn pyGRUB version 0.3 ????????????????????????? ? Fedora Core (2.6.15-1.2054_FC5xenU) ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?????????????????????????? Use the - and . keys to select which entry is highlighted. Press enter to boot the selected OS. 'e' to edit the commands before booting, 'a' to modify the kernel arguments before booting, or 'c' for a command line. Will boot selected entry in 1 seconds Going to boot Fedora Core (2.6.15-1.2054_FC5xenU) kernel: /boot/vmlinuz-2.6.15-1.2054_FC5xenU initrd: /boot/initrd-2.6.15-1.2054_FC5xenU.img Started domain svn Bootdata ok (command line is ro root=LABEL=/) Linux version 2.6.15-1.2054_FC5xenU (bhcompile at hs20-bc1-7.build.redhat.com) (gcc version 4.1.0 20060304 (Red Hat 4.1.0-3)) #1 SMP Tue Mar 14 16:18:03 EST 2006 Built 1 zonelists Kernel command line: ro root=LABEL=/ Initializing CPU#0 PID hash table entries: 4096 (order: 12, 131072 bytes) Xen reported: 1804.087 MHz processor. Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Software IO TLB disabled Memory: 507260k/532480k available (1891k kernel code, 24560k reserved, 720k data, 116k init) Calibrating delay using timer specific routine.. 4512.41 BogoMIPS (lpj=9024823) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) Brought up 1 CPUs 0 checking if image is initramfs... it is Freeing initrd memory: 1890k freed DMI not present or invalid. Grant table initialized ..... --- SNIP ---- -- Best Regards, Aleksander Adamowski GG#: 274614 ICQ UIN: 19780575 http://olo.ab.altkom.pl From aleksander.adamowski.redhat at altkom.com.pl Thu Mar 30 12:53:46 2006 From: aleksander.adamowski.redhat at altkom.com.pl (Aleksander Adamowski) Date: Thu, 30 Mar 2006 14:53:46 +0200 Subject: [Fedora-xen] Xen 3.0 on FC5 problems In-Reply-To: References: Message-ID: <442BD4DA.7040401@altkom.com.pl> Filipe Miranda wrote: > Hello there, > > I'm new to this xen technology and I'm trying it on FC5 but I'm having > a hardtime trying to setup a guest xen machine. > Here is what I did and all the error messages: > > The directory /nfs/fc5 has the following content: > [root at fc5 fc5]# ls /nfs/fc5/ > Fedora figs images isolinux repodata stylesheet-images > > I folllowed the steps described on > http://fedoraproject.org/wiki/FedoraXenQuickstartFC5 > > > [root at fc5 fc5]# /usr/sbin/xenguest-install.py > What is the name of your virtual machine? fc5 > How much RAM should be allocated (in megabytes)? 256 > What would you like to use as the disk (path)? /xen/fc5 > What is the install location? nfs:fc5:/nfs/fc5 > > Starting install... > Using config file "/etc/xen/fc5". > Error: Device 51712 (vbd) could not be connected. Backend device not > found. > If your install has exited, you can restart your guest by running > 'xm create -c fc5'. Otherwise, you can reconnect to the console > by running 'xm console fc5' > > Any suggestions? What are the contents of /etc/exports on fc5? Can the guest domain successfully resolve the name of the Dom0 domain in DNS? Try using fc5's IP address at first, then use its DNS name if it works OK using IP. -- Best Regards, Aleksander Adamowski GG#: 274614 ICQ UIN: 19780575 http://olo.ab.altkom.pl From ext-Taneli.Vahakangas at nokia.com Tue Mar 28 09:45:18 2006 From: ext-Taneli.Vahakangas at nokia.com (Taneli =?ISO-8859-1?Q?V=E4h=E4kangas?=) Date: Tue, 28 Mar 2006 12:45:18 +0300 Subject: [Fedora-xen] xen domain0 corrupted fs Message-ID: <1143539118.26015.14.camel@hed03956.research.nokia.com> Hi! Sorry for sketchiness in this report, but the xen domain0 kernel (I don't have any guests set-up yet) just shitted all over /etc directory and locked up the machine while trying to do shutdown. There was a backtrace or somesuch on the screen, but apparently that was not logged anywhere. On next boot, the xen kernel halted while trying to fsck, so I gave up and started the standard kernel and then fsck.ext3 corrected a few thousand errors (or so it seemed) on the / partition. The problems happened on the first and only boot to the xen kernel ever, about 20 minutes after installing FC5. The machine is a bog-standard dell optiplex gx620 (P4 HT), with 3G memory. Did I hit a known bug? I'm not on the list, so please keep me on cc ... Taneli From thomas.uhl at gmail.com Wed Mar 29 17:34:44 2006 From: thomas.uhl at gmail.com (Thomas Uhl) Date: Wed, 29 Mar 2006 19:34:44 +0200 Subject: [Fedora-xen] Problems with e1000 drivers with kernel 2.6.15... Message-ID: <2d90b1800603290934o7257a8aw1f8801d158def919@mail.gmail.com> Hi! I am testing xen on a preproduction Intel box. The standard kernel of FC5 (2.6.15-1.2054) does not detect the embedded e1000 NICs in my setup. So I tried kernel 2.6.16-1.2102 from rawhide. It worked. When will we see a "xenified" 2.6.16 kernel in rawhide? Yours Tom Here the dmesg output with kernel 2.6.16... Intel(R) PRO/1000 Network Driver - version 7.0.33-k2-NAPI Copyright (c) 1999-2005 Intel Corporation. ACPI: PCI Interrupt 0000:05:00.0[A] -> GSI 18 (level, low) -> IRQ 19 PCI: Setting latency timer of device 0000:05:00.0 to 64 e1000: 0000:05:00.0: e1000_probe: (PCI Express:2.5Gb/s:Width x4) From muratisik at bilgiguvenlik.com Thu Mar 30 22:22:50 2006 From: muratisik at bilgiguvenlik.com (Murat =?iso-8859-9?Q?I=FE=FDk?=) Date: Fri, 31 Mar 2006 01:22:50 +0300 (EEST) Subject: [Fedora-xen] Problem booting jailtime images Message-ID: <1690.195.174.105.65.1143757370.squirrel@webmail.bilcag.net> Hello, After installing a fresh fc5, I followed fedoraproject.org/wiki/FedoraXenQuickstartFC5 up until xenguest-install.py part. After that point for a quick try I downloaded both fc4 and debian prebuilt images from jailtime.org . However both images, as I boot them with xm create -c {related one}.cfg , crash with this error: VFS: Cannot open root device "sda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) I did extensive googling and mounted the images, cheking their fstab and so on. Everything looks fine. But the problem is unresolved. Does anybody have any experiences with jailtime images? any suggestions? BTW my host fc5 has LVM partitioning. Very unlikely but can this have an effect? Have a nice day. -- Murat Isik www.bilgiguvenlik.com From yongkang.you at intel.com Fri Mar 31 05:18:53 2006 From: yongkang.you at intel.com (You, Yongkang) Date: Fri, 31 Mar 2006 13:18:53 +0800 Subject: [Fedora-xen] Problem booting jailtime images Message-ID: <16A54BF5D6E14E4D916CE26C9AD30575044A20C1@pdsmsx402.ccr.corp.intel.com> >-----Original Message----- >From: fedora-xen-bounces at redhat.com >[mailto:fedora-xen-bounces at redhat.com] On Behalf Of Murat I??k >Sent: 2006?3?31? 6:23 >To: fedora-xen at redhat.com >Subject: [Fedora-xen] Problem booting jailtime images > >Hello, > >After installing a fresh fc5, I followed >fedoraproject.org/wiki/FedoraXenQuickstartFC5 up until xenguest-install.py >part. After that point for a quick try I downloaded both fc4 and debian >prebuilt images from jailtime.org . However both images, as I boot them >with xm create -c {related one}.cfg , crash with this error: > >VFS: Cannot open root device "sda1" or unknown-block(0,0) >Please append a correct "root=" boot option >Kernel panic - not syncing: VFS: Unable to mount root fs on >unknown-block(0,0) > >I did extensive googling and mounted the images, cheking their fstab and >so on. Everything looks fine. But the problem is unresolved. Did you use the '/dev/sda1' as the root boot option in xenU config? And the xenU fstab also used sda1? Change they to /dev/hda1 and have a try. > >Does anybody have any experiences with jailtime images? any suggestions? >BTW my host fc5 has LVM partitioning. Very unlikely but can this have an >effect? > >Have a nice day. > > >-- >Murat Isik >www.bilgiguvenlik.com > >-- Best Regards, Yongkang (Kangkang) ?? From vmm at datamarkets.com.ar Fri Mar 31 17:31:45 2006 From: vmm at datamarkets.com.ar (Victor Mihalik) Date: Fri, 31 Mar 2006 14:31:45 -0300 Subject: [Fedora-xen] Problems to hide pci appliance Message-ID: <442D6781.9060404@datamarkets.com.ar> Hi People, I've problems when I want to use a pci device within a guest machine. I try modify grub.conf and put physdev_dom0_hide and pciback.hide in the line of kernel and module but it does not happen anything. Somebody knows the way to make this? Thanks a lot Victor :-) From muratisik at bilgiguvenlik.com Fri Mar 31 20:04:26 2006 From: muratisik at bilgiguvenlik.com (Murat =?iso-8859-9?Q?I=FE=FDk?=) Date: Fri, 31 Mar 2006 23:04:26 +0300 (EEST) Subject: [Fedora-xen] Problem booting jailtime images In-Reply-To: <20060331170014.8DD027377A@hormel.redhat.com> References: <20060331170014.8DD027377A@hormel.redhat.com> Message-ID: <1138.195.174.105.65.1143835466.squirrel@webmail.bilcag.net> Hello, thanks for the reply. actually here is what I have/did: [root at muratisik ~]# cd /xen/fedora/ [root at muratisik fedora]# ls fedora.fc4.img fedora.fc4.xen.cfg fedora.swap [root at muratisik fedora]# cat fedora.fc4.xen.cfg kernel = "/boot/vmlinuz-2.6.16-1.2080_FC5xen0" memory = 128 name = "fedora.fc4" nics = 1 dhcp = "dhcp" disk = ['file:/xen/fedora/fedora.fc4.img,sda1,w', 'file:/xen/fedora/fedora.swap,sda2,w'] root = "/dev/sda1 ro" [root at muratisik fedora]# mount -o loop fedora.fc4.img /mnt/ [root at muratisik fedora]# cat /mnt/etc/fstab # This file is edited by fstab-sync - see 'man fstab-sync' for details /dev/sda1 / ext3 defaults 1 1 /dev/sda2 none swap sw 0 0 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 [root at muratisik fedora]# umount /mnt/ [root at muratisik fedora]# xm create fedora.fc4.xen.cfg -c and the error appears: ... md: ... autorun DONE. VFS: Cannot open root device "sda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [] panic+0x3c/0x190 [] mount_block_root+0x19c/0x1aa [] mount_root+0x49/0x4e [] prepare_namespace+0xc0/0xf1 [] init+0x23e/0x2fe [] init+0x0/0x2fe [] kernel_thread_helper+0x5/0xb Then I changed both image's fstab to hda1 and hda2 , also editted cfg to match hdas. and I get the same error. any ideas? is there any more information (log, config, debug vs.) I can supply? have a nice day. >> >>Hello, >> >>After installing a fresh fc5, I followed >>fedoraproject.org/wiki/FedoraXenQuickstartFC5 up until >> xenguest-install.py >>part. After that point for a quick try I downloaded both fc4 and debian >>prebuilt images from jailtime.org . However both images, as I boot them >>with xm create -c {related one}.cfg , crash with this error: >> >>VFS: Cannot open root device "sda1" or unknown-block(0,0) >>Please append a correct "root=" boot option >>Kernel panic - not syncing: VFS: Unable to mount root fs on >>unknown-block(0,0) >> >>I did extensive googling and mounted the images, cheking their fstab and >>so on. Everything looks fine. But the problem is unresolved. > > Did you use the '/dev/sda1' as the root boot option in xenU config? > And the xenU fstab also used sda1? > Change they to /dev/hda1 and have a try. > >> >>Does anybody have any experiences with jailtime images? any suggestions? >>BTW my host fc5 has LVM partitioning. Very unlikely but can this have an >>effect? >> >>Have a nice day. >> >> >>-- >>Murat Isik >>www.bilgiguvenlik.com >> >>-- > > > Best Regards, > Yongkang (Kangkang) ???? > From sct at redhat.com Fri Mar 31 21:00:09 2006 From: sct at redhat.com (Stephen C. Tweedie) Date: Fri, 31 Mar 2006 16:00:09 -0500 Subject: [Fedora-xen] 2.6.15-1.2054_FC5xen0 - no network for guest domains In-Reply-To: <442BA843.9010700@altkom.com.pl> References: <441B041E.6060204@altkom.com.pl> <1142889317.21593.41.camel@orbit.scot.redhat.com> <442BA843.9010700@altkom.com.pl> Message-ID: <1143838809.3477.24.camel@orbit.scot.redhat.com> Hi, On Thu, 2006-03-30 at 11:43 +0200, Aleksander Adamowski wrote: > You were right, it seems that the eth0:0 alias had confused the network > startup scripts and they didn't set up the bridging and virtual > interfaces correctly. OK, could you open a bugzilla for this please? We probably want to fix this at some point, even though you've been able to work around it for now. Thanks, Stephen