From ametzger at silkspeed.com Sat Dec 1 00:45:49 2007 From: ametzger at silkspeed.com (Aaron Metzger) Date: Fri, 30 Nov 2007 19:45:49 -0500 Subject: [Fedora-xen] Guest Image File Size Message-ID: <4750AEBD.906@silkspeed.com> virt-install has a checkbox which suggests that you can avoid preallocating the entire guest image size -- that the guest image file will grow on demand. Does this work for Xen or is it only supported for KVM and the QEMU COW files? My experience when creating Xen guests as regular files is that I end up with a file that is the full size even when I pick the option to not preallocate the entire image. -- Thanks, Aaron From dlbewley at lib.ucdavis.edu Sat Dec 1 01:02:14 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Fri, 30 Nov 2007 17:02:14 -0800 (PST) Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? In-Reply-To: Message-ID: <90145598.309921196470934409.JavaMail.root@zebra.lib.ucdavis.edu> I haven't done bonding, but you should be able to bond them and then compose a bridge on top of this bonded device I would think. -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From mnielsen at redhat.com Sat Dec 1 01:50:11 2007 From: mnielsen at redhat.com (Mark Nielsen) Date: Fri, 30 Nov 2007 20:50:11 -0500 Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? In-Reply-To: <90145598.309921196470934409.JavaMail.root@zebra.lib.ucdavis.edu> References: <90145598.309921196470934409.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: <4750BDD3.2040600@redhat.com> just FYI for the list, I have a how-to for a bonded and VLAN tagged network. http://www.certifried.com ODT and PDF formats available. It might not be the best way, but I've sent it out to my colleagues several times and have never received any negative feedback. Mark Dale Bewley wrote: > I haven't done bonding, but you should be able to bond them and then compose a bridge on top of this bonded device I would think. > > -- > Dale Bewley - Unix Administrator - Shields Library - UC Davis > GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From fedora.lists at burns.me.uk Sat Dec 1 12:43:24 2007 From: fedora.lists at burns.me.uk (Andy Burns) Date: Sat, 1 Dec 2007 12:43:24 +0000 Subject: [Fedora-xen] FYI: The plan for Xen kernels in Fedora 9 In-Reply-To: References: <20071130185909.GA32711@redhat.com> Message-ID: On 30/11/2007, Paul Wouters wrote: > Though having the lwm.net site, which at least semi > documents API changes, makes the work a bit easier. I'm sure Living Word Ministries are glad for the link ;-) From sputhenp at redhat.com Sat Dec 1 15:31:14 2007 From: sputhenp at redhat.com (Sadique Puthen) Date: Sat, 01 Dec 2007 21:01:14 +0530 Subject: [Fedora-xen] Guest Image File Size In-Reply-To: <4750AEBD.906@silkspeed.com> References: <4750AEBD.906@silkspeed.com> Message-ID: <47517E42.2050801@redhat.com> Aaron Metzger wrote: > virt-install has a checkbox which suggests that you can avoid > preallocating the entire guest image size -- that the guest image file > will grow on demand. > > Does this work for Xen or is it only supported for KVM and the QEMU > COW files? yes, this works fine on xen. > > My experience when creating Xen guests as regular files is that I end > up with a file that is the full size even when I pick the option to > not preallocate the entire image. Basically it if you don't pre-allocate the entire image, virt-manager creates a sparse file to store the guest data which only occupies disk blocks while you write contents to that sparse file . When checking the size of the pre-allocated and sparse images, you should use "du", not "ls -lh". --Sadique > > > -- > Thanks, > Aaron > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From ametzger at silkspeed.com Sat Dec 1 17:42:40 2007 From: ametzger at silkspeed.com (Aaron Metzger) Date: Sat, 01 Dec 2007 12:42:40 -0500 Subject: [Fedora-xen] Guest Image File Size In-Reply-To: <47517E42.2050801@redhat.com> References: <4750AEBD.906@silkspeed.com> <47517E42.2050801@redhat.com> Message-ID: <47519D10.9090301@silkspeed.com> Sadique Puthen wrote: > > Basically it if you don't pre-allocate the entire image, virt-manager > creates a sparse file to store the guest data which only occupies disk > blocks while you write contents to that sparse file . When checking the > size of the pre-allocated and sparse images, you should use "du", not > "ls -lh". > Thank you for your insight. You are correct. I have a guest image stored in a file called "subversion". "du" shows the actual size being used is smaller than what "ls" thinks. du -a subversion 2158768 subversion ls -ld subversion -rwxr-xr-x 1 root root 64424509441 2007-11-27 18:16 subversion I have a follow up question though. How do you cleanly backup and restore these files using the smaller amount of space? Any simplistic program that I try (e.g. "tar") also thinks my file is 60 Gig not 2 Gig and creates a real file that uses 60 Gig of actual disk space. Can anyone share the simple steps with "dd" or other programs that let you cleanly store a backup of the guest image which uses the smaller amount of space and also correctly restores from that backup in a way that preserves the orginal idea of a 60 Gig max guest disk size? I am sorry if these are just basic Xen or even just basic Unix questions that you all already know the answers to as opposed to "fedora-xen" questions but I'm sure I'm not the only one who will run into such things while trying to virtualize their existing infrastructure using Fedora and Xen. This low traffic list has been a wonderful asset in helping with my conversion to Fedora Virtualization. I appreciate all the help I have received. -- Thanks, Aaron From berrange at redhat.com Sat Dec 1 17:46:14 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Sat, 1 Dec 2007 17:46:14 +0000 Subject: [Fedora-xen] Guest Image File Size In-Reply-To: <47519D10.9090301@silkspeed.com> References: <4750AEBD.906@silkspeed.com> <47517E42.2050801@redhat.com> <47519D10.9090301@silkspeed.com> Message-ID: <20071201174614.GF14465@redhat.com> On Sat, Dec 01, 2007 at 12:42:40PM -0500, Aaron Metzger wrote: > Sadique Puthen wrote: > > > > >Basically it if you don't pre-allocate the entire image, virt-manager > >creates a sparse file to store the guest data which only occupies disk > >blocks while you write contents to that sparse file . When checking the > >size of the pre-allocated and sparse images, you should use "du", not > >"ls -lh". > > > > Thank you for your insight. You are correct. > > I have a guest image stored in a file called "subversion". > > "du" shows the actual size being used is smaller than what "ls" thinks. > > du -a subversion > 2158768 subversion > > ls -ld subversion > -rwxr-xr-x 1 root root 64424509441 2007-11-27 18:16 subversion You don't need to use 'du' - just use the '-s' flag to ls $ ls -lsh dan1.img 16K -rwxr-xr-x 1 root root 2.1G 2007-11-29 17:51 dan1.img Shows its physical size is 16k, while its logical size is 2.1 GB. > I have a follow up question though. How do you cleanly backup and > restore these files using the smaller amount of space? Any simplistic > program that I try (e.g. "tar") also thinks my file is 60 Gig not 2 Gig > and creates a real file that uses 60 Gig of actual disk space. Use the --sparse option with tar. -S, --sparse handle sparse files efficiently > Can anyone share the simple steps with "dd" or other programs that let > you cleanly store a backup of the guest image which uses the smaller > amount of space and also correctly restores from that backup in a way > that preserves the orginal idea of a 60 Gig max guest disk size? 'cp' will also try to detect sparse files & handle them properly, but if it gets it wrong you can also use '--sparse=always' Dan -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From mnielsen at redhat.com Sat Dec 1 19:03:06 2007 From: mnielsen at redhat.com (Mark Nielsen) Date: Sat, 01 Dec 2007 14:03:06 -0500 Subject: [Fedora-xen] Guest Image File Size In-Reply-To: <20071201174614.GF14465@redhat.com> References: <4750AEBD.906@silkspeed.com> <47517E42.2050801@redhat.com> <47519D10.9090301@silkspeed.com> <20071201174614.GF14465@redhat.com> Message-ID: <4751AFEA.7040509@redhat.com> I think you'll get the same sort of thing if you gzip the file. I've gzip'd some 20G xen images down to around 2G. Daniel P. Berrange wrote: > On Sat, Dec 01, 2007 at 12:42:40PM -0500, Aaron Metzger wrote: > >> Sadique Puthen wrote: >> >> >>> Basically it if you don't pre-allocate the entire image, virt-manager >>> creates a sparse file to store the guest data which only occupies disk >>> blocks while you write contents to that sparse file . When checking the >>> size of the pre-allocated and sparse images, you should use "du", not >>> "ls -lh". >>> >>> >> Thank you for your insight. You are correct. >> >> I have a guest image stored in a file called "subversion". >> >> "du" shows the actual size being used is smaller than what "ls" thinks. >> >> du -a subversion >> 2158768 subversion >> >> ls -ld subversion >> -rwxr-xr-x 1 root root 64424509441 2007-11-27 18:16 subversion >> > > You don't need to use 'du' - just use the '-s' flag to ls > > $ ls -lsh dan1.img > 16K -rwxr-xr-x 1 root root 2.1G 2007-11-29 17:51 dan1.img > > Shows its physical size is 16k, while its logical size is 2.1 GB. > > >> I have a follow up question though. How do you cleanly backup and >> restore these files using the smaller amount of space? Any simplistic >> program that I try (e.g. "tar") also thinks my file is 60 Gig not 2 Gig >> and creates a real file that uses 60 Gig of actual disk space. >> > > Use the --sparse option with tar. > > -S, --sparse > handle sparse files efficiently > > >> Can anyone share the simple steps with "dd" or other programs that let >> you cleanly store a backup of the guest image which uses the smaller >> amount of space and also correctly restores from that backup in a way >> that preserves the orginal idea of a 60 Gig max guest disk size? >> > > 'cp' will also try to detect sparse files & handle them properly, but > if it gets it wrong you can also use '--sparse=always' > > Dan > From berrange at redhat.com Sat Dec 1 19:11:50 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Sat, 1 Dec 2007 19:11:50 +0000 Subject: [Fedora-xen] Guest Image File Size In-Reply-To: <4751AFEA.7040509@redhat.com> References: <4750AEBD.906@silkspeed.com> <47517E42.2050801@redhat.com> <47519D10.9090301@silkspeed.com> <20071201174614.GF14465@redhat.com> <4751AFEA.7040509@redhat.com> Message-ID: <20071201191150.GA18257@redhat.com> On Sat, Dec 01, 2007 at 02:03:06PM -0500, Mark Nielsen wrote: > I think you'll get the same sort of thing if you gzip the file. I've > gzip'd some 20G xen images down to around 2G. AFAIR, this is just because sparse files appear as long sequences of zeros & thus compress wel - gzip isn't actually optimizing for sparseness. The trouble is that when you extract the file gunzip will fully allocate it filling with zeros. My original 1M file takes 4k # ls -lhs foo 4.0K -rw-r--r-- 1 root root 1.0M 2007-12-01 14:18 foo #gzip foo # ls -lhs foo.gz 8.0K -rw-r--r-- 1 root root 1.1K 2007-12-01 14:18 foo.gz Now when it uncompress it it takes up the full 1 MB :-( # gunzip foo.gz # ls -lhs foo 1.1M -rw-r--r-- 1 root root 1.0M 2007-12-01 14:18 foo You *always* want to use tar to preserve sparseness, and then gzip the tar file so you get optimal resource usage both on archiving & extracting. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From christian at matissenetworks.com Sat Dec 1 23:03:55 2007 From: christian at matissenetworks.com (Christian Lahti) Date: Sat, 1 Dec 2007 15:03:55 -0800 Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? Message-ID: Hi Dale: I work with David who posted the original question to the mailing list. I think we need to give a bit more background info on what we are trying to do. We are running a mixed environment of mostly CentOS 3, 4and 5, we do have a few windows servers and XP systems as well. We are looking to virtualize all these platforms. Normally we have a bonded pair of NICs for the physical hosts, we were able to get this running using CentOS 5 x86_64 with no problems, the guest machines use the bonded pair in bridged mode as expected after a bit of tweaking. The biggest issue we found with EL5 is that windows guest performace is dismal at best, hence our decision to have a look at Fedora Core 8 x86_64. I am happy to report that performance for all of our guest platforms is *very* good with FC8, but it seems that libvirt changed the way networking is setup for Xen. The default NAT configuration is pretty useless for production server environment. Thanks to the mailing list we are now able to bridge a single NIC on FC8 (like eth0 for example), but we cannot figure out how to get a bridge for bond0 (comprised of eth0 and eth1) defined and available to Xen. All the tweaks that worked find on EL5 have not worked so far on FC8. I am going to review your document tomorrow and give it a try, but any idea on whether your methodology will work on FC8 and libvirt? I am willing to blow a Sunday to get this worked out once and for all :) Basically we are after good performance on both para and fully virtualized guests using a bonded pair of GB NICs for speed and redundancy. If this can be achieved with enterprise linux then that would be preferable, but we will go FC8 if the bonding thing can be sorted out. By the way Xensource 4.x looks to be a respin of RHEL5 and has pretty good performance but their free version is limited to 32bit (and hence 4GB ram). Adding the clustering failover is the next step of course :) Thanks again for the help so far. /Christian >>>>>>>>>>> just FYI for the list, I have a how-to for a bonded and VLAN tagged network. http://www.certifried.com ODT and PDF formats available. It might not be the best way, but I've sent it out to my colleagues several times and have never received any negative feedback. Mark Dale Bewley wrote: I haven't done bonding, but you should be able to bond them and then compose a bridge on top of this bonded device I would think. -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 -- Fedora-xen mailing list Fedora-xen redhat com https://www.redhat.com/mailman/listinfo/fedora-xen **************************************************************************** Checked by MailWasher server (www.Firetrust.com) WARNING. No FirstAlert account found. To reduce spam further activate FirstAlert. This message can be removed by purchasing a FirstAlert Account. **************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From christian at matissenetworks.com Sat Dec 1 23:55:34 2007 From: christian at matissenetworks.com (Christian Lahti) Date: Sat, 1 Dec 2007 15:55:34 -0800 Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? References: <4751EBFE.6000100@redhat.com> Message-ID: Hi Mark: Thank you very much for your response, I did indeed read the original poster as Dale by mistake :) So what you are saying makes perfect sense to me and sounds like exactly what we are after, I will have 3 vlans to bridge myself ultimately. My next question is the relative merits of RHEL5.1 as compared to Fedora 8. Obviously I would prefer the stable enterprise release rather than bleeding edge Fedora, but has fully virtualized windows performance been fixed in this release? At any rate I am looking forward to getting this up and running tomorrow! /Christian ________________________________ From: Mark Nielsen [mailto:mnielsen at redhat.com] Sent: Sat 12/1/2007 3:19 PM To: Christian Lahti Subject: Re: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? hmm, did you mean "Hi Mark" ?? I have 8 Dell 2950s running RHEL 5.1 (new libvirt with that funky NAT they added). I have 4 NICs in each; 2 copper, 2 fiber. I bond the 2 copper (eth0 and eth1) and call it bond0. bond0 carries my "private" IP for cluster suite communications on the dom0 (physical) cluster. Then I bond eth2 and eth3 (fiber) in to bond1. I lay down the public network for the dom0 cluster on bond1.100 (for example, that would be VLAN 100). I also add many (up to 10 or so now) VLANs on bond1 (bond1.20, bond1.21, bond1.22, etc). Then I create xen bridges to each of these bond/VLAN devices. This allows me to put any particular VM on any particular (or combination up to 3) of these xen bridged bonded VLAN device. My document explains, in detail, how to do all of this :) The only added step is that I have to "undefine" (virsh net-undefine default) the default network that the new libvirt creates (virbr0). Even with this new NAT thing they added, I've been told (by our devs) that the preferred way to do static network configurations is with the method I lay out. NAT is more for dynamic networks (cable modems, dial-up, wifi, etc). I'm pretty sure there weren't any significant changes in Fedora 8 (we've dropped the word "core" now, btw) that don't exist in RHEL 5.1 with respects to the network. 5.0 -> 5.1 is when that NAT change came down the pipe. Mark p.s. I'm happy to answer any other questions you may have about my document. I'm quite certain that, if you follow it, you'll have what you're looking for. Christian Lahti wrote: > Hi Dale: > > I work with David who posted the original question to the mailing > list. I think we need to give a bit more background info on what we > are trying to do. We are running a mixed environment of mostly CentOS > 3, 4and 5, we do have a few windows servers and XP systems as well. > We are looking to virtualize all these platforms. Normally we have a > bonded pair of NICs for the physical hosts, we were able to get this > running using CentOS 5 x86_64 with no problems, the guest machines use > the bonded pair in bridged mode as expected after a bit of tweaking. > The biggest issue we found with EL5 is that windows guest performace > is dismal at best, hence our decision to have a look at Fedora Core 8 > x86_64. I am happy to report that performance for all of our guest > platforms is *very* good with FC8, but it seems that libvirt changed > the way networking is setup for Xen. The default NAT configuration is > pretty useless for production server environment. Thanks to the > mailing list we are now able to bridge a single NIC on FC8 (like eth0 > for example), but we cannot figure out how to get a bridge for bond0 > (comprised of eth0 and eth1) defined and available to Xen. All the > tweaks that worked find on EL5 have not worked so far on FC8. I am > going to review your document tomorrow and give it a try, but any idea > on whether your methodology will work on FC8 and libvirt? I am > willing to blow a Sunday to get this worked out once and for all :) > > Basically we are after good performance on both para and fully > virtualized guests using a bonded pair of GB NICs for speed and > redundancy. If this can be achieved with enterprise linux then that > would be preferable, but we will go FC8 if the bonding thing can be > sorted out. By the way Xensource 4.x looks to be a respin of RHEL5 > and has pretty good performance but their free version is limited to > 32bit (and hence 4GB ram). Adding the clustering failover is the next > step of course :) > > Thanks again for the help so far. > > /Christian > > > > >>>>>>>>>>> > just FYI for the list, I have a how-to for a bonded and VLAN tagged network. > > http://www.certifried.com > > ODT and PDF formats available. > > > It might not be the best way, but I've sent it out to my colleagues > several times and have never received any negative feedback. > Mark > > > > Dale Bewley wrote: > > > I haven't done bonding, but you should be able to bond them and then compose a bridge on top of this bonded device I would think. > > -- > Dale Bewley - Unix Administrator - Shields Library - UC Davis > GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 > > -- > Fedora-xen mailing list > Fedora-xen redhat com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > **************************************************************************** > Checked by MailWasher server (www.Firetrust.com) > WARNING. No FirstAlert account found. > To reduce spam further activate FirstAlert. > This message can be removed by purchasing a FirstAlert Account. > **************************************************************************** > > ------------------------------------------------------------------------ > > -- > 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 debian at herakles.homelinux.org Sun Dec 2 00:20:07 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Sun, 02 Dec 2007 09:20:07 +0900 Subject: [Fedora-xen] Guest Image File Size In-Reply-To: <4750AEBD.906@silkspeed.com> References: <4750AEBD.906@silkspeed.com> Message-ID: <4751FA37.2090709@herakles.homelinux.org> Aaron Metzger wrote: > virt-install has a checkbox which suggests that you can avoid > preallocating the entire guest image size -- that the guest image file > will grow on demand. > > Does this work for Xen or is it only supported for KVM and the QEMU COW > files? It's a filesystem property: [root at potoroo ~]# ls -shoog /var/lib/xen/images/* 1.1G -rwxr-xr-x 1 3.1G Nov 7 10:39 /var/lib/xen/images/ClarkConnect.img 2.9G -rwxr-xr-x 1 3.1G Nov 30 18:31 /var/lib/xen/images/DebianEtch.img 4.0G -rwxr-xr-x 1 4.0G Nov 28 17:49 /var/lib/xen/images/F8-1.img 16K -rwxr-xr-x 1 4.0G Nov 28 17:57 /var/lib/xen/images/F8-2.img 16K -rwxr-xr-x 1 4.0G Nov 28 17:38 /var/lib/xen/images/F8.img 16K -rwxr-xr-x 1 4.1G Nov 7 14:06 /var/lib/xen/images/Fedora7.img 16K -rwxr-xr-x 1 2.1G Nov 12 22:55 /var/lib/xen/images/FreeBSD_70.img 129M -rwxr-xr-x 1 4.0G Nov 18 15:51 /var/lib/xen/images/Gentoo.2.img 2.9G -rwxr-xr-x 1 3.1G Nov 18 17:00 /var/lib/xen/images/Gentoo.img 16K -rwxr-xr-x 1 3.1G Nov 5 08:45 /var/lib/xen/images/Kubuntu.img 16K -rwxr-xr-x 1 2.1G Nov 4 10:00 /var/lib/xen/images/NetBSD-31.img 16K -rwxr-xr-x 1 4.0G Nov 28 17:55 /var/lib/xen/images/f8.img 1.1G -rwxr-xr-x 1 2.1G Nov 7 07:52 /var/lib/xen/images/windows_c.img [root at potoroo ~]# > > My experience when creating Xen guests as regular files is that I end up > with a file that is the full size even when I pick the option to not > preallocate the entire image. To interpret my listing above, man ls -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From debian at herakles.homelinux.org Sun Dec 2 00:21:38 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Sun, 02 Dec 2007 09:21:38 +0900 Subject: [Fedora-xen] Guest Image File Size In-Reply-To: <20071201191150.GA18257@redhat.com> References: <4750AEBD.906@silkspeed.com> <47517E42.2050801@redhat.com> <47519D10.9090301@silkspeed.com> <20071201174614.GF14465@redhat.com> <4751AFEA.7040509@redhat.com> <20071201191150.GA18257@redhat.com> Message-ID: <4751FA92.2030906@herakles.homelinux.org> Daniel P. Berrange wrote: > On Sat, Dec 01, 2007 at 02:03:06PM -0500, Mark Nielsen wrote: >> I think you'll get the same sort of thing if you gzip the file. I've >> gzip'd some 20G xen images down to around 2G. > > AFAIR, this is just because sparse files appear as long sequences of > zeros & thus compress wel - gzip isn't actually optimizing for sparseness. > The trouble is that when you extract the file gunzip will fully allocate > it filling with zeros. undo that with "cp --sparse" -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From debian at herakles.homelinux.org Sun Dec 2 00:34:05 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Sun, 02 Dec 2007 09:34:05 +0900 Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? In-Reply-To: References: <4751EBFE.6000100@redhat.com> Message-ID: <4751FD7D.1020604@herakles.homelinux.org> Christian Lahti wrote: > Hi Mark: > > Thank you very much for your response, I did indeed read the original poster as Dale by mistake :) So what you are saying makes perfect sense to me and sounds like exactly what we are after, I will have 3 vlans to bridge myself ultimately. My next question is the relative merits of RHEL5.1 as compared to Fedora 8. Obviously I would prefer the stable enterprise release rather than bleeding edge Fedora, but has fully virtualized windows performance been fixed in this release? At any rate I am looking forward to getting this up and running tomorrow! > > /Christian > > > ________________________________ > > From: Mark Nielsen [mailto:mnielsen at redhat.com] > Sent: Sat 12/1/2007 3:19 PM > To: Christian Lahti > Subject: Re: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? > > > > hmm, did you mean "Hi Mark" ?? > > I have 8 Dell 2950s running RHEL 5.1 (new libvirt with that funky NAT > they added). I have 4 NICs in each; 2 copper, 2 fiber. I bond the 2 > copper (eth0 and eth1) and call it bond0. bond0 carries my "private" IP > for cluster suite communications on the dom0 (physical) cluster. > > Then I bond eth2 and eth3 (fiber) in to bond1. I lay down the public > network for the dom0 cluster on bond1.100 (for example, that would be > VLAN 100). I also add many (up to 10 or so now) VLANs on bond1 > (bond1.20, bond1.21, bond1.22, etc). Then I create xen bridges to each > of these bond/VLAN devices. This allows me to put any particular VM on > any particular (or combination up to 3) of these xen bridged bonded VLAN > device. > > My document explains, in detail, how to do all of this :) The only added > step is that I have to "undefine" (virsh net-undefine default) the > default network that the new libvirt creates (virbr0). Even with this > new NAT thing they added, I've been told (by our devs) that the > preferred way to do static network configurations is with the method I > lay out. NAT is more for dynamic networks (cable modems, dial-up, wifi, > etc). > > I'm pretty sure there weren't any significant changes in Fedora 8 (we've > dropped the word "core" now, btw) that don't exist in RHEL 5.1 with > respects to the network. 5.0 -> 5.1 is when that NAT change came down > the pipe. > > Mark > > p.s. I'm happy to answer any other questions you may have about my > document. I'm quite certain that, if you follow it, you'll have what > you're looking for. > > Christian Lahti wrote: >> Hi Dale: >> >> I work with David who posted the original question to the mailing >> list. I think we need to give a bit more background info on what we >> are trying to do. We are running a mixed environment of mostly CentOS >> 3, 4and 5, we do have a few windows servers and XP systems as well. >> We are looking to virtualize all these platforms. Normally we have a >> bonded pair of NICs for the physical hosts, we were able to get this >> running using CentOS 5 x86_64 with no problems, the guest machines use >> the bonded pair in bridged mode as expected after a bit of tweaking. >> The biggest issue we found with EL5 is that windows guest performace >> is dismal at best, hence our decision to have a look at Fedora Core 8 >> x86_64. I am happy to report that performance for all of our guest >> platforms is *very* good with FC8, but it seems that libvirt changed >> the way networking is setup for Xen. The default NAT configuration is >> pretty useless for production server environment. Thanks to the >> mailing list we are now able to bridge a single NIC on FC8 (like eth0 >> for example), but we cannot figure out how to get a bridge for bond0 >> (comprised of eth0 and eth1) defined and available to Xen. All the >> tweaks that worked find on EL5 have not worked so far on FC8. I am >> going to review your document tomorrow and give it a try, but any idea >> on whether your methodology will work on FC8 and libvirt? I am >> willing to blow a Sunday to get this worked out once and for all :) >> >> Basically we are after good performance on both para and fully >> virtualized guests using a bonded pair of GB NICs for speed and >> redundancy. If this can be achieved with enterprise linux then that >> would be preferable, but we will go FC8 if the bonding thing can be >> sorted out. By the way Xensource 4.x looks to be a respin of RHEL5 >> and has pretty good performance but their free version is limited to >> 32bit (and hence 4GB ram). Adding the clustering failover is the next >> step of course :) >> >> Thanks again for the help so far. In your position, I might consider another Sunday to see whether the f8 tools run on C5, and not, then what's needed. The -xen kernel's probably needed along with the most obvious *virt*. There might not be a lot of building to do, and the odds are good that a Fedora kernel will "just work," depending on whether you need extra drivers. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From deepc2005 at hotmail.com Sun Dec 2 00:54:10 2007 From: deepc2005 at hotmail.com (Maximilian Freisinger) Date: Sat, 1 Dec 2007 19:54:10 -0500 Subject: [Fedora-xen] lv as "partition"? Message-ID: Hello, im just trying to use a logical volume as a partition (for example sdc1) in my domU. As there seems to be no possibility to define such things on virt manager, i tried virsh with attach-disk and attach-device. But i always get: libvir: Xen Daemon Fehler: POST Operation schlug fehl. (Xend.err 'Device 2081 not connected') my xml for device: my definition for disk: virsh attach-disk /dev/master/part01 sdc1 my question is where is my error, or how can i achieve my aim? thx _________________________________________________________________ You keep typing, we keep giving. Download Messenger and join the i?m Initiative now. http://im.live.com/messenger/im/home/?source=TAGLM From armbru at redhat.com Mon Dec 3 09:48:59 2007 From: armbru at redhat.com (Markus Armbruster) Date: Mon, 03 Dec 2007 10:48:59 +0100 Subject: [Fedora-xen] Best practices questions In-Reply-To: (Denise Lopez's message of "Wed\, 28 Nov 2007 16\:31\:47 -0800") References: Message-ID: <87d4tow1kk.fsf@pike.pond.sub.org> "Lopez, Denise" writes: > Hi all, > > > > I am in the process of building a new Xen server from scratch and wanted > to ask a couple of questions about best practices. > > > > First, should the guest domains be image files or LVM's or just regular > ext3 partitions? What are the pros and/or cons of each? Image files are slow. Sparse image files lead to *nasty* domU data corruption when you run out of space in the filesystem containing the image file. LVM vs. regular partitions is the usual deal: LVM gives you more flexibility. You might find that you appreciate the flexibility even more when you run guests. > Second, since the Dom0 is supposed to be kept secure, and most of my > servers I don't install any X11 server on, is there any security risk > installing an X11 server on the Dom0 in order to take advantage of the > virt-manager GUI interface? X is network transparent. Why not use a remote display? You don't need an X server in dom0 for that. > Thank you in advance for any thoughts and or opinions. > > > > Denise Lopez From armbru at redhat.com Mon Dec 3 09:50:50 2007 From: armbru at redhat.com (Markus Armbruster) Date: Mon, 03 Dec 2007 10:50:50 +0100 Subject: [Fedora-xen] Xen : virsh error In-Reply-To: <97c69f7d0711282357n62a6b7d8p7dfabd1c1d3258d0@mail.gmail.com> (unixfoo@users.sourceforge.net's message of "Thu\, 29 Nov 2007 13\:27\:06 +0530") References: <97c69f7d0711282357n62a6b7d8p7dfabd1c1d3258d0@mail.gmail.com> Message-ID: <878x4cw1hh.fsf@pike.pond.sub.org> Quick sanity check: you are running the xen kernel, aren't you? From armbru at redhat.com Mon Dec 3 10:01:54 2007 From: armbru at redhat.com (Markus Armbruster) Date: Mon, 03 Dec 2007 11:01:54 +0100 Subject: [Fedora-xen] Guest Image File Size In-Reply-To: <47517E42.2050801@redhat.com> (Sadique Puthen's message of "Sat\, 01 Dec 2007 21\:01\:14 +0530") References: <4750AEBD.906@silkspeed.com> <47517E42.2050801@redhat.com> Message-ID: <874pf0w0z1.fsf@pike.pond.sub.org> Sadique Puthen writes: > Aaron Metzger wrote: >> virt-install has a checkbox which suggests that you can avoid >> preallocating the entire guest image size -- that the guest image >> file will grow on demand. >> >> Does this work for Xen or is it only supported for KVM and the QEMU >> COW files? > > yes, this works fine on xen. Until you run out of space in the filesystem containing the image file! Then the guest can't write any blocks that were previously left out of the image file, which leads to massive guest filesystem corruption and data loss. I use sparse image files all the time. But only for the throw-away domains I create for testing. [...] From berrange at redhat.com Mon Dec 3 12:51:15 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 3 Dec 2007 12:51:15 +0000 Subject: [Fedora-xen] Best practices questions In-Reply-To: <87d4tow1kk.fsf@pike.pond.sub.org> References: <87d4tow1kk.fsf@pike.pond.sub.org> Message-ID: <20071203125115.GA30043@redhat.com> On Mon, Dec 03, 2007 at 10:48:59AM +0100, Markus Armbruster wrote: > "Lopez, Denise" writes: > > > Hi all, > > > > > > > > I am in the process of building a new Xen server from scratch and wanted > > to ask a couple of questions about best practices. > > > > > > > > First, should the guest domains be image files or LVM's or just regular > > ext3 partitions? What are the pros and/or cons of each? > > Image files are slow. Sparse image files lead to *nasty* domU data > corruption when you run out of space in the filesystem containing the > image file. Actually that's not true. You will definitely get I/O errors in the DomU if Dom0 runs out of space. Journalling FS will save you though. If you kill the guest, add more Dom0 space, and start the guest again it should recover just fine. This is why I went to great lengths to fixing Xen 3.0.3 to make sure I/O errors are actually propagated to the guest, rather than being dropped on the floor in Dom0 pretending it was all OK like in the bad Xen 3.0.2 days. The issue with sparse files is that they have really bad performance characteristics whe nyou do writes, becaue each time Dom0 as to allocate an extra block behind the sparse file it hits the journal, and this basically serializes all I/O requests in the guest. Once the sparse file is fully-allocated, it should be good again. > LVM vs. regular partitions is the usual deal: LVM gives you more > flexibility. You might find that you appreciate the flexibility even > more when you run guests. LVM & partitions give best performance characteristics. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From ametzger at silkspeed.com Mon Dec 3 14:07:27 2007 From: ametzger at silkspeed.com (Aaron Metzger) Date: Mon, 03 Dec 2007 09:07:27 -0500 Subject: [Fedora-xen] Best practices questions In-Reply-To: <20071203125115.GA30043@redhat.com> References: <87d4tow1kk.fsf@pike.pond.sub.org> <20071203125115.GA30043@redhat.com> Message-ID: <47540D9F.2030100@silkspeed.com> Daniel P. Berrange wrote: > >> LVM vs. regular partitions is the usual deal: LVM gives you more >> flexibility. You might find that you appreciate the flexibility even >> more when you run guests. > > LVM & partitions give best performance characteristics. > > Regards, > Dan. Dan: Thanks for your insight. If, for example, a guest has separate /root, /boot, and swap do you recommend as best practice a separate logical volume for each or do you give just one logical volume to the guest for it to dice up into the various types of file systems? Is there a significant performance difference between these two solutions? For us newbies using virt-install or virt-manager, it prompts for at most one partitition (which can be a logical volume) so without editing of the config after the fact it naturally leads to the case of using just one logical volume for the entire guest with it dicing it up into /root, /boot, and swap or whatever. So, for the case of just one logical volume which has been "formatted" during the guest install, this led to the question of how do I generically backup and restore that one logical volume. Every piece of documentation that I find for creating an LVM snapshot and then creating a backup requires that the snapshot volume be mounted to perform the backup. This led me on an adventure with device mapper and kpartx etc during which I was able to eventually get to and backup the inner guts of my guest but it seemed like there had to be a better way. Is there a vanilla generic backup and restore procedure for a logical volume (a snapshot volume of the running guest logical volume) which does not require case-by-case knowledge of what type of file system(s) have been mapped to that logical volume? If so, is there then also a way to do that backup in a manner which only stores the small amount of space actually used by the guest instead of the entire space allocated to the logical volume? In other words, something that preserves the idea of sparseness? This is probably a generic LVM question but I could not find my answer in the LVM docs either. My lack of knowledge related to the above questions is why I am currently using image files but would love to switch to individual logical volumes for the performance benefits. -- Thanks, Aaron From Dustin.Henning at prd-inc.com Mon Dec 3 22:43:51 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Mon, 3 Dec 2007 17:43:51 -0500 Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? In-Reply-To: <4751FD7D.1020604@herakles.homelinux.org> References: <4751EBFE.6000100@redhat.com> <4751FD7D.1020604@herakles.homelinux.org> Message-ID: <003301c835fd$f9bd7440$ed385cc0$@Henning@prd-inc.com> Unfortunately, I took interest in this discussion and decided to mess around with it (primarily to see if there really were noticeable performance gains between xen's built-in bridge script and this manual method) even though I don't currently have a test box. I am running F7, and prior to trying to do this, I had xenbr0 working fine (perhaps from modifying xend-config.sxp, I don't remember exactly) alongside virbr0 (which I didn't want, but couldn't get rid of). I thought undonig changes would surely get me back to where I started, so I didn't bother with backups (though, admittedly, backups really equate to undoing changes, so I don't know what good additional copies of the files I might have backed up would have done). My experience went something like this: 1) I created the ifcfg-peth0 file as described in "xen-lke bridging" here: http://watzmann.net/blog/index.php/2007/04/27/networking_with_kvm_and_libvir t 2) I created a ifcfg-eth0 and an ifcfg-br0 in hopes of making an eth0 separate from the bridge as xen does. When that didn't work (by simply restarting the network) I got rid of the ifcfg-eth0 and used only the ifcfg-br0 (bridge=br0 was the setting in my peth0 all along), note that I had changed network-script to /bin/false and restarted xend as well by this point. 3) I added the iptables command as in the page from the link above 4) I went ahead and enabled forwarding in procfs via sysctl.conf thinking that xen was probably manually setting and unsetting this with its script 5) I rebooted and still had xenbr0 and virbr0, along with eth0 and br0 (both bridges) and peth0 (the real nic) 6) I started one of my HVM domains using bridge=br0, and it worked, as peth0 was bridged on br0 (the other three bridges weren't being used at all) 7) I ran "virsh net-autostart --disable default" thinking it might get rid of xenbr0 and virbr0, it didn't, they come back on subsequent reboots 8) I decided to change back so there would be less unnecessary bridges (shown as interfaces in ifconfig) since xenbr0 was still there, I thought that would be simple enough 9) I got rid of ifcfg-br0 and ifcfg-peth0 and rebuilt my original ifcfg-eth0 (though probably in a different order and without the presumably unnecessary ipv6 lines) 10) I changed network script back to network-bridge and rebooted 11) The system came up and still had all four bridges, brctl show now shows peth0 to be a member of bridge eth0, if I disable the network, all interfaces left up (ifconfig br0 down, etc), and all bridges ([brctl delif eth0 peth0] brctl delbr br0, etc), then when I start the network back up, eth0 is real eth0 (though it takes some time to start up), but when I start xend back up again, all of that mess comes back. 12) If I reboot into the standard kernel, eth0 is eth0 and all is well, but upon rebooting back into xen, I have the same mess (4 bridges with peth0 on the eth0 bridge), but I got my domUs working by setting bridge to eth0 in their config files (when that was set to xenbr0, I couldn't contact them from dom0 like I could before this fiasco, and I don't think they could get out to the network either, though I didn't test that exhaustively). While it is working and that is fine, I would like to get rid of the virbr0 (and at this point, also xenbr0 and br0 I guess), but I am not sure how to go about that. Brctl certainly isn't deleting them permanently, and virsh doesn't seem to have anything to do with them. I did stumble upon a gui bridge controller at one point while messing with all of this, but haven't found it again and don't know if it would have caused this stuff to stick. I may have caused all of this confusion when messing with system-config-network, as I thought a second device in there was a NIC I had removed, so I deleted it, and that may have been used by xen (as opposed to the NIC sitting in a drawer that may or may not have been installed and removed on this particular system), but the network-scripts folder in sysconfig is right (according to my inspection and the happy boot into non-xen f7). That said, can anyone tell me where settings might be hiding that would somehow be creating my br0 along with the other unnecessary (in my current situation) bridges? Thanks, Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of John Summerfield Sent: Saturday, December 01, 2007 19:34 To: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? Christian Lahti wrote: > Hi Mark: > > Thank you very much for your response, I did indeed read the original poster as Dale by mistake :) So what you are saying makes perfect sense to me and sounds like exactly what we are after, I will have 3 vlans to bridge myself ultimately. My next question is the relative merits of RHEL5.1 as compared to Fedora 8. Obviously I would prefer the stable enterprise release rather than bleeding edge Fedora, but has fully virtualized windows performance been fixed in this release? At any rate I am looking forward to getting this up and running tomorrow! > > /Christian > > > ________________________________ > > From: Mark Nielsen [mailto:mnielsen at redhat.com] > Sent: Sat 12/1/2007 3:19 PM > To: Christian Lahti > Subject: Re: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? > > > > hmm, did you mean "Hi Mark" ?? > > I have 8 Dell 2950s running RHEL 5.1 (new libvirt with that funky NAT > they added). I have 4 NICs in each; 2 copper, 2 fiber. I bond the 2 > copper (eth0 and eth1) and call it bond0. bond0 carries my "private" IP > for cluster suite communications on the dom0 (physical) cluster. > > Then I bond eth2 and eth3 (fiber) in to bond1. I lay down the public > network for the dom0 cluster on bond1.100 (for example, that would be > VLAN 100). I also add many (up to 10 or so now) VLANs on bond1 > (bond1.20, bond1.21, bond1.22, etc). Then I create xen bridges to each > of these bond/VLAN devices. This allows me to put any particular VM on > any particular (or combination up to 3) of these xen bridged bonded VLAN > device. > > My document explains, in detail, how to do all of this :) The only added > step is that I have to "undefine" (virsh net-undefine default) the > default network that the new libvirt creates (virbr0). Even with this > new NAT thing they added, I've been told (by our devs) that the > preferred way to do static network configurations is with the method I > lay out. NAT is more for dynamic networks (cable modems, dial-up, wifi, > etc). > > I'm pretty sure there weren't any significant changes in Fedora 8 (we've > dropped the word "core" now, btw) that don't exist in RHEL 5.1 with > respects to the network. 5.0 -> 5.1 is when that NAT change came down > the pipe. > > Mark > > p.s. I'm happy to answer any other questions you may have about my > document. I'm quite certain that, if you follow it, you'll have what > you're looking for. > > Christian Lahti wrote: >> Hi Dale: >> >> I work with David who posted the original question to the mailing >> list. I think we need to give a bit more background info on what we >> are trying to do. We are running a mixed environment of mostly CentOS >> 3, 4and 5, we do have a few windows servers and XP systems as well. >> We are looking to virtualize all these platforms. Normally we have a >> bonded pair of NICs for the physical hosts, we were able to get this >> running using CentOS 5 x86_64 with no problems, the guest machines use >> the bonded pair in bridged mode as expected after a bit of tweaking. >> The biggest issue we found with EL5 is that windows guest performace >> is dismal at best, hence our decision to have a look at Fedora Core 8 >> x86_64. I am happy to report that performance for all of our guest >> platforms is *very* good with FC8, but it seems that libvirt changed >> the way networking is setup for Xen. The default NAT configuration is >> pretty useless for production server environment. Thanks to the >> mailing list we are now able to bridge a single NIC on FC8 (like eth0 >> for example), but we cannot figure out how to get a bridge for bond0 >> (comprised of eth0 and eth1) defined and available to Xen. All the >> tweaks that worked find on EL5 have not worked so far on FC8. I am >> going to review your document tomorrow and give it a try, but any idea >> on whether your methodology will work on FC8 and libvirt? I am >> willing to blow a Sunday to get this worked out once and for all :) >> >> Basically we are after good performance on both para and fully >> virtualized guests using a bonded pair of GB NICs for speed and >> redundancy. If this can be achieved with enterprise linux then that >> would be preferable, but we will go FC8 if the bonding thing can be >> sorted out. By the way Xensource 4.x looks to be a respin of RHEL5 >> and has pretty good performance but their free version is limited to >> 32bit (and hence 4GB ram). Adding the clustering failover is the next >> step of course :) >> >> Thanks again for the help so far. In your position, I might consider another Sunday to see whether the f8 tools run on C5, and not, then what's needed. The -xen kernel's probably needed along with the most obvious *virt*. There might not be a lot of building to do, and the odds are good that a Fedora kernel will "just work," depending on whether you need extra drivers. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From unixfoo at users.sourceforge.net Tue Dec 4 03:31:25 2007 From: unixfoo at users.sourceforge.net (unixfoo) Date: Tue, 4 Dec 2007 09:01:25 +0530 Subject: [Fedora-xen] Xen : virsh error In-Reply-To: <878x4cw1hh.fsf@pike.pond.sub.org> References: <97c69f7d0711282357n62a6b7d8p7dfabd1c1d3258d0@mail.gmail.com> <878x4cw1hh.fsf@pike.pond.sub.org> Message-ID: <97c69f7d0712031931u4049420cv90eaccaaf7213a02@mail.gmail.com> Yeah Of course , Im running xen kernel :) . But I dont see a /etc/init.d/libvirtd and virsh doesnt work. [root at unixfoo1~]# rpm -qa | grep virt libvirt-0.1.8-15.el5.0.1 libvirt-python-0.1.8-15.el5.0.1 python-virtinst-0.99.0-2.el5 [root at unixfoo1 ~]# uname -a Linux unixfoo1 2.6.18-8.1.6.0.6.el5xen #1 SMP Mon Aug 6 18:55:57 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux [root at unixfoo1 ~]# xm info host : unixfoo1 release : 2.6.18-8.1.6.0.6.el5xen version : #1 SMP Mon Aug 6 18:55:57 EDT 2007 machine : x86_64 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 2 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 2327 hw_caps : bfebfbff:20100800:00000000:00000140:0004e3bd:00000000:00000001 total_memory : 16383 free_memory : 512 xen_major : 3 xen_minor : 0 xen_extra : -unstable xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.1 20070105 (Red Hat 4.1.1-52) cc_compile_by : mockbuild cc_compile_domain : (none) cc_compile_date : Mon Aug 6 18:53:29 EDT 2007 xend_config_format : 4 [root at unixfoo1 ~]# virsh virsh: error: failed to connect to the hypervisor [root at unixfoo1 ~]# On Dec 3, 2007 3:20 PM, Markus Armbruster wrote: > Quick sanity check: you are running the xen kernel, aren't you? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From debian at herakles.homelinux.org Tue Dec 4 09:08:01 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Tue, 04 Dec 2007 18:08:01 +0900 Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? In-Reply-To: <003301c835fd$f9bd7440$ed385cc0$@Henning@prd-inc.com> References: <4751EBFE.6000100@redhat.com> <4751FD7D.1020604@herakles.homelinux.org> <003301c835fd$f9bd7440$ed385cc0$@Henning@prd-inc.com> Message-ID: <475518F1.2030101@herakles.homelinux.org> Dustin Henning wrote: > Unfortunately, I took interest in this discussion and decided to > mess around with it (primarily to see if there really were noticeable > performance gains between xen's built-in bridge script and this manual > method) even though I don't currently have a test box. I am running F7, and > prior to trying to do this, I had xenbr0 working fine (perhaps from > modifying xend-config.sxp, I don't remember exactly) alongside virbr0 (which > I didn't want, but couldn't get rid of). I thought undonig changes would > surely get me back to where I started, so I didn't bother with backups > (though, admittedly, backups really equate to undoing changes, so I don't > know what good additional copies of the files I might have backed up would > have done). My experience went something like this: I don't feel like reading the rest when I can point you at a backup:-) cd rpm2cpio References: <4750AEBD.906@silkspeed.com> <47517E42.2050801@redhat.com> <874pf0w0z1.fsf@pike.pond.sub.org> Message-ID: <47551A7C.6090300@herakles.homelinux.org> Markus Armbruster wrote: > Sadique Puthen writes: > >> Aaron Metzger wrote: >>> virt-install has a checkbox which suggests that you can avoid >>> preallocating the entire guest image size -- that the guest image >>> file will grow on demand. >>> >>> Does this work for Xen or is it only supported for KVM and the QEMU >>> COW files? >> yes, this works fine on xen. > > Until you run out of space in the filesystem containing the image > file! Then the guest can't write any blocks that were previously left > out of the image file, which leads to massive guest filesystem > corruption and data loss. > > I use sparse image files all the time. But only for the throw-away > domains I create for testing. I thought I read that ext3 journals save the day. Whether they always save it, "man mke2fs" for journal options. Using a device that _is not_ sparse, it seems to me, must be safe. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From veillard at redhat.com Tue Dec 4 11:12:52 2007 From: veillard at redhat.com (Daniel Veillard) Date: Tue, 4 Dec 2007 06:12:52 -0500 Subject: [Fedora-xen] Xen : virsh error In-Reply-To: <97c69f7d0712031931u4049420cv90eaccaaf7213a02@mail.gmail.com> References: <97c69f7d0711282357n62a6b7d8p7dfabd1c1d3258d0@mail.gmail.com> <878x4cw1hh.fsf@pike.pond.sub.org> <97c69f7d0712031931u4049420cv90eaccaaf7213a02@mail.gmail.com> Message-ID: <20071204111252.GB2747@redhat.com> On Tue, Dec 04, 2007 at 09:01:25AM +0530, unixfoo wrote: > > Yeah Of course , Im running xen kernel :) . But I dont see a > /etc/init.d/libvirtd and virsh doesnt work. > [root at unixfoo1~]# rpm -qa | grep virt > libvirt-0.1.8-15.el5.0.1 > libvirt-python-0.1.8-15.el5.0.1 > python-virtinst-0.99.0-2.el5 You stated previously "I use Fedora 8" and now you have RHEL 5.0 bits there. It gets harder to help you if you don't tell us exactly what is going on. The daemon is definitely present in the most recent packages for RHEL, I suggest you update your installation if possible or at least make sure everything is pristine and correwctly installed, that will certainly help: [root at test2 ~]# rpm -qf /etc/init.d/libvirtd libvirt-0.2.3-9.el5 Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard at redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From rjones at redhat.com Tue Dec 4 13:10:56 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 04 Dec 2007 13:10:56 +0000 Subject: [Fedora-xen] Xen : virsh error In-Reply-To: <97c69f7d0712031931u4049420cv90eaccaaf7213a02@mail.gmail.com> References: <97c69f7d0711282357n62a6b7d8p7dfabd1c1d3258d0@mail.gmail.com> <878x4cw1hh.fsf@pike.pond.sub.org> <97c69f7d0712031931u4049420cv90eaccaaf7213a02@mail.gmail.com> Message-ID: <475551E0.1090605@redhat.com> unixfoo wrote: > Yeah Of course , Im running xen kernel :) . But I dont see a > /etc/init.d/libvirtd and virsh doesnt work. > > [root at unixfoo1~]# rpm -qa | grep virt > libvirt-0.1.8-15.el5.0.1 > libvirt-python-0.1.8-15.el5.0.1 You won't find libvirtd in this ancient (pre-remote) version of libvirt[1]. I think you need to check you're really running F8 as you said, and not RHEL 5, CentOS or similar. Rich. [1] http://libvirt.org/hvsupport.html -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From Dustin.Henning at prd-inc.com Tue Dec 4 13:20:01 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Tue, 4 Dec 2007 08:20:01 -0500 Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? In-Reply-To: <475518F1.2030101@herakles.homelinux.org> References: <4751EBFE.6000100@redhat.com> <4751FD7D.1020604@herakles.homelinux.org> <003301c835fd$f9bd7440$ed385cc0$@Henning@prd-inc.com> <475518F1.2030101@herakles.homelinux.org> Message-ID: <001201c83678$600c8db0$2025a910$@Henning@prd-inc.com> Fair enough; I certainly can't blame you for not wanting to read that big long thing. However, while I thank you for this useful piece of advice, the actual problem is that I don't know what files are causing my issue, but I am pretty sure they aren't files I modified by hand. I think maybe one of the GUI tools changed some file I am not familiar with (or F7 did on account of a change I made in a file I am familiar with). So I am hoping someone could point me toward such a file. I need to know what could cause my situation, which I believe is fully described starting at "11)". Everything prior to that is part of the cause and/or attempts to get rid of extra bridges. Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of John Summerfield Sent: Tuesday, December 04, 2007 04:08 To: Fedora Xen Subject: Re: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? Dustin Henning wrote: > Unfortunately, I took interest in this discussion and decided to > mess around with it (primarily to see if there really were noticeable > performance gains between xen's built-in bridge script and this manual > method) even though I don't currently have a test box. I am running F7, and > prior to trying to do this, I had xenbr0 working fine (perhaps from > modifying xend-config.sxp, I don't remember exactly) alongside virbr0 (which > I didn't want, but couldn't get rid of). I thought undonig changes would > surely get me back to where I started, so I didn't bother with backups > (though, admittedly, backups really equate to undoing changes, so I don't > know what good additional copies of the files I might have backed up would > have done). My experience went something like this: I don't feel like reading the rest when I can point you at a backup:-) cd rpm2cpio References: <4750AEBD.906@silkspeed.com> <47517E42.2050801@redhat.com> <47519D10.9090301@silkspeed.com> <20071201174614.GF14465@redhat.com> <4751AFEA.7040509@redhat.com> Message-ID: <1196789183.16969.31.camel@localhost.localdomain> On Sat, 2007-12-01 at 14:03 -0500, Mark Nielsen wrote: > I think you'll get the same sort of thing if you gzip the file. I've > gzip'd some 20G xen images down to around 2G. Another nice way to compress disk images is with 'qemu-img convert', outputting to a compressed qcow. David From debian at herakles.homelinux.org Tue Dec 4 23:24:20 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Wed, 05 Dec 2007 08:24:20 +0900 Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? In-Reply-To: <001201c83678$600c8db0$2025a910$@Henning@prd-inc.com> References: <4751EBFE.6000100@redhat.com> <4751FD7D.1020604@herakles.homelinux.org> <003301c835fd$f9bd7440$ed385cc0$@Henning@prd-inc.com> <475518F1.2030101@herakles.homelinux.org> <001201c83678$600c8db0$2025a910$@Henning@prd-inc.com> Message-ID: <4755E1A4.3060800@herakles.homelinux.org> Dustin Henning wrote: > Fair enough; I certainly can't blame you for not wanting to read > that big long thing. However, while I thank you for this useful piece of :-) > advice, the actual problem is that I don't know what files are causing my > issue, but I am pretty sure they aren't files I modified by hand. I think to see what you really changed, rpm -V Then you can use the other trick to get the original files, and hence their differences with, er, diff. > maybe one of the GUI tools changed some file I am not familiar with (or F7 > did on account of a change I made in a file I am familiar with). So I am > hoping someone could point me toward such a file. I need to know what could > cause my situation, which I believe is fully described starting at "11)". > Everything prior to that is part of the cause and/or attempts to get rid of > extra bridges. > Dustin > > -----Original Message----- > From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] > On Behalf Of John Summerfield > Sent: Tuesday, December 04, 2007 04:08 > To: Fedora Xen > Subject: Re: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? > > Dustin Henning wrote: >> Unfortunately, I took interest in this discussion and decided to >> mess around with it (primarily to see if there really were noticeable >> performance gains between xen's built-in bridge script and this manual >> method) even though I don't currently have a test box. I am running F7, > and >> prior to trying to do this, I had xenbr0 working fine (perhaps from >> modifying xend-config.sxp, I don't remember exactly) alongside virbr0 > (which >> I didn't want, but couldn't get rid of). I thought undonig changes would >> surely get me back to where I started, so I didn't bother with backups >> (though, admittedly, backups really equate to undoing changes, so I don't >> know what good additional copies of the files I might have backed up would >> have done). My experience went something like this: > > I don't feel like reading the rest when I can point you at a backup:-) > > cd > > rpm2cpio > Find and copy the files you want. > > > > -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From jayeola at gmail.com Wed Dec 5 01:21:04 2007 From: jayeola at gmail.com (John Maclean) Date: Wed, 05 Dec 2007 01:21:04 +0000 Subject: [Fedora-xen] virt-install hangs for fc6,7 Message-ID: <1196817664.13064.20.camel@x60s> Hey guys, First post and apologies if this has been up OT before. virt-install fails to create a domU for FC6/7. Distro of node is BLAG, an FC derivative. Just jump to the end to the end of the boot up message to see where the domU hangs. /var/log/xen/xend.log indicate no warnings or explanations why this domain has failed to be "born". Commands used:- /usr/sbin/virt-install --name fx6foo \ --paravirt \ --ram 256 \ --nographics \ --file-size 10 \ --file /dev/zulu_images/fx6foo \ --location http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ or [root at zulu ~]# virt-install --paravirt \ > --name fx7template \ > --ram 256 \ > --nographics \ > --file-size 10 \ > --file /dev/zulu_images/fx7template \ > --location http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ Typical output:- Starting install... libvir: Xen Daemon error : GET operation failed: Retrieving file Fedora... 434 kB 00:02 Retrieving file vmlinuz.. 100% |=========================| 2.1 MB 00:09 Retrieving file initrd.im 100% |=========================| 5.4 MB 00:26 libvir: Xen Daemon error : GET operation failed: Creating domain... 0 B 00:01 Linux version 2.6.20-2925.9.fc7xen (kojibuilder at xenbuilder4.fedora.phx.redhat.com) (gcc version 4.1.2 20070502 (Red H at 4.1.2-12)) #1 SMP Tue May 22 08:53:03 EDT 2007 BIOS-provided physical RAM map: sanitize start sanitize bail 0 copy_e820_map() start: 0000000000000000 size: 0000000010800000 end: 0000000010800000 type: 1 Xen: 0000000000000000 - 0000000010800000 (usable) 0MB HIGHMEM available. 264MB LOWMEM available. Using x86 segment limits to approximate NX protection Zone PFN ranges: DMA 0 -> 67584 Normal 67584 -> 67584 HighMem 67584 -> 67584 early_node_map[1] active PFN ranges 0: 0 -> 67584 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 67056 Kernel command line: method=http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c135f000 soft=c133f000 PID hash table entries: 2048 (order: 11, 8192 bytes) Xen reported: 2806.356 MHz processor. Console: colour dummy device 80x25 Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar ... MAX_LOCKDEP_SUBCLASSES: 8 ... MAX_LOCK_DEPTH: 30 ... MAX_LOCKDEP_KEYS: 2048 ... CLASSHASH_SIZE: 1024 ... MAX_LOCKDEP_ENTRIES: 8192 ... MAX_LOCKDEP_CHAINS: 16384 ... CHAINHASH_SIZE: 8192 memory used by lock dependency info: 1064 kB per task-struct memory footprint: 1200 bytes Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Software IO TLB disabled vmalloc area: d1000000-f4ffe000, maxmem 2d7fe000 Memory: 245120k/270336k available (2030k kernel code, 16724k reserved, 1079k data, 180k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xd1000000 - 0xf4ffe000 ( 575 MB) lowmem : 0xc0000000 - 0xd0800000 ( 264 MB) .init : 0xc130e000 - 0xc133b000 ( 180 kB) .data : 0xc11fb8b9 - 0xc1309714 (1079 kB) .text : 0xc1000000 - 0xc11fb8b9 (2030 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 7023.08 BogoMIPS (lpj=14046165) 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: 512 CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 1024K Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 11k freed Brought up 1 CPUs Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub Setting up standard PCI resources ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 7, 524288 bytes) TCP bind hash table entries: 8192 (order: 6, 262144 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 7264k freedIA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1196625149.792:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize input: Macintosh mouse button emulation as /class/input/input0 Xen virtual console successfully installed as xvc0 Event-channel device installed. usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 180k freed Write protecting the kernel read-only data: 762k # Everything seems to hang from here. Made a few cups of coffee/cigarettes to see if it was just the box being slow.... # detached and listed domains... # detaching from console... Domain installation still in progress. You can reconnect to the console to complete the installation process. [root at zulu ~]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1000 2 r----- 1072.2 cx5foo 256 1 24.7 cx5template 256 1 0.0 cxmon 256 1 24.7 fx6foo 256 1 0.0 fx7template 13 256 1 -b---- 1.7 fxfoo 256 1 0.0 zcx1dump 256 1 0.0 /var/log/xen/xend.log is not reporting any problems. Clues? Would be nice to be able diagnose this one. -- Regards, John Maclean Msc (DIC) + 44 7739 1717 531 From berrange at redhat.com Wed Dec 5 01:27:49 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 5 Dec 2007 01:27:49 +0000 Subject: [Fedora-xen] virt-install hangs for fc6,7 In-Reply-To: <1196817664.13064.20.camel@x60s> References: <1196817664.13064.20.camel@x60s> Message-ID: <20071205012749.GF22561@redhat.com> On Wed, Dec 05, 2007 at 01:21:04AM +0000, John Maclean wrote: > Hey guys, > > First post and apologies if this has been up OT before. virt-install > fails to create a domU for FC6/7. Distro of node is BLAG, an FC > derivative. Just jump to the end to the end of the boot up message to > see where the domU hangs. /var/log/xen/xend.log indicate no warnings or > explanations why this domain has failed to be "born". This is a bug in the F7 install kernel. When running in nographics mode it still sends boot output to the graphical console instead o the text console. Add '--append console=xvc0' to the virt-install args when doing a nographics install of Fedora 7. FC6/F8 get the text mode stuff right - only F7 is broken in this respect. > > Commands used:- > > /usr/sbin/virt-install --name fx6foo \ > --paravirt \ > --ram 256 \ > --nographics \ > --file-size 10 \ > --file /dev/zulu_images/fx6foo \ > --location > http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ Your VM name is FC6, but you're still pointing at a F7 repo here... > > or > > [root at zulu ~]# virt-install --paravirt \ > > --name fx7template \ > > --ram 256 \ > > --nographics \ > > --file-size 10 \ > > --file /dev/zulu_images/fx7template \ > > --location > http://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ > > Typical output:- Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From christian at matissenetworks.com Wed Dec 5 03:42:30 2007 From: christian at matissenetworks.com (Christian Lahti) Date: Tue, 4 Dec 2007 19:42:30 -0800 Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? In-Reply-To: References: <4751EBFE.6000100@redhat.com> Message-ID: Hi Mark: Well, I carefully went through your PDF document for setting up a bonded pair on RHEL 5.1 and at the end of the day this does not work for me. This is the procedure more or less I have tried: * Make sure eth0 and eth1 work as normal eth devices without LACP * Edit /etc/modprobe.conf to add the bonding kernel module * Edit /etc/sysconfig/network-scripts/ifcfg-eth0 and ifcfg-eth1 to be slave devices with the master as bond0 * Create /etc/sysconfig/network-scripts/ifcfg-bond0 with static IP info * Plug into LACP enabled ports on switch and reboot the box * At this point bond0 works fine, as expected, we have been doing this all day long on non-xen kernels for years * NOW...following your document * Remove the /etc/libvirt/qemu/networks/autostart/* so that the pointless 192.168.122.x NAT network does not get created * Grab the network-scripts-bridge-bond-vlan script from the link in the message and put into /etc/xen/scripts * Edit /etc/xen/xend-config.sxp and replace (network-script network-bridge) with (network-script network-bridge-bond-vlan) * Restart networking * At this point networking for the physical host in invariably completely hosed, and there is no xen networking at all * It is noteworthy to add that I did not make any modifications to the network-scripts-bridge-bond-vlan script as you suggest since I am on a single vlan (so far) and the default setup in the script seems sane for a single NON-VLAN bond0 configuration So in a nutshell the it seems that libvirt interface just does not seem to use the xen scripts...rather it's own (undocumented?) crap. After a week of head-banging on this we really have no choice but to abandon Redhat in favor of Suse 10.3, which incidentally works right out of the box with bridge, NAT, bond, you name it. I suggest RH staff install a copy of this to see how they did it, you don't even have to jump through hoops to configure a bond from the command line, you can do this with their stock GUI tools if you so choose. I am not knocking RedHat, but we need something that "just works" and so far for xen + bond + RH has been a non-starter for us after much effort. By the way, to get networking un-foobar'ed on the physical machine I have to run system-config-network and remove all Ethernet devices, then reboot, then redefine eth0 and eth1 as as normal DHCP devices. I can then go re-setup the bond0 device from the command line. If anyone has step-by-step directions on how to do this with RHEL 5.1 I am happy to try again at some future point. The goals are simple: * Step one: create a bond0 from eth0 and eth1 that can be used as a bridged device by xen on a single VLAN * Step two: create a bond0 (aliases?) that can be assigned multiple VLANs, AND have these VLAN devices available to be used by xen I would settle for item #1 really. /Christian ________________________________ From: Christian Lahti Sent: Saturday, December 01, 2007 3:56 PM To: mnielsen at redhat.com; fedora-xen at redhat.com Subject: RE: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? Hi Mark: Thank you very much for your response, I did indeed read the original poster as Dale by mistake :) So what you are saying makes perfect sense to me and sounds like exactly what we are after, I will have 3 vlans to bridge myself ultimately. My next question is the relative merits of RHEL5.1 as compared to Fedora 8. Obviously I would prefer the stable enterprise release rather than bleeding edge Fedora, but has fully virtualized windows performance been fixed in this release? At any rate I am looking forward to getting this up and running tomorrow! /Christian ________________________________ From: Mark Nielsen [mailto:mnielsen at redhat.com] Sent: Sat 12/1/2007 3:19 PM To: Christian Lahti Subject: Re: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? hmm, did you mean "Hi Mark" ?? I have 8 Dell 2950s running RHEL 5.1 (new libvirt with that funky NAT they added). I have 4 NICs in each; 2 copper, 2 fiber. I bond the 2 copper (eth0 and eth1) and call it bond0. bond0 carries my "private" IP for cluster suite communications on the dom0 (physical) cluster. Then I bond eth2 and eth3 (fiber) in to bond1. I lay down the public network for the dom0 cluster on bond1.100 (for example, that would be VLAN 100). I also add many (up to 10 or so now) VLANs on bond1 (bond1.20, bond1.21, bond1.22, etc). Then I create xen bridges to each of these bond/VLAN devices. This allows me to put any particular VM on any particular (or combination up to 3) of these xen bridged bonded VLAN device. My document explains, in detail, how to do all of this :) The only added step is that I have to "undefine" (virsh net-undefine default) the default network that the new libvirt creates (virbr0). Even with this new NAT thing they added, I've been told (by our devs) that the preferred way to do static network configurations is with the method I lay out. NAT is more for dynamic networks (cable modems, dial-up, wifi, etc). I'm pretty sure there weren't any significant changes in Fedora 8 (we've dropped the word "core" now, btw) that don't exist in RHEL 5.1 with respects to the network. 5.0 -> 5.1 is when that NAT change came down the pipe. Mark p.s. I'm happy to answer any other questions you may have about my document. I'm quite certain that, if you follow it, you'll have what you're looking for. Christian Lahti wrote: > Hi Dale: > > I work with David who posted the original question to the mailing > list. I think we need to give a bit more background info on what we > are trying to do. We are running a mixed environment of mostly CentOS > 3, 4and 5, we do have a few windows servers and XP systems as well. > We are looking to virtualize all these platforms. Normally we have a > bonded pair of NICs for the physical hosts, we were able to get this > running using CentOS 5 x86_64 with no problems, the guest machines use > the bonded pair in bridged mode as expected after a bit of tweaking. > The biggest issue we found with EL5 is that windows guest performace > is dismal at best, hence our decision to have a look at Fedora Core 8 > x86_64. I am happy to report that performance for all of our guest > platforms is *very* good with FC8, but it seems that libvirt changed > the way networking is setup for Xen. The default NAT configuration is > pretty useless for production server environment. Thanks to the > mailing list we are now able to bridge a single NIC on FC8 (like eth0 > for example), but we cannot figure out how to get a bridge for bond0 > (comprised of eth0 and eth1) defined and available to Xen. All the > tweaks that worked find on EL5 have not worked so far on FC8. I am > going to review your document tomorrow and give it a try, but any idea > on whether your methodology will work on FC8 and libvirt? I am > willing to blow a Sunday to get this worked out once and for all :) > > Basically we are after good performance on both para and fully > virtualized guests using a bonded pair of GB NICs for speed and > redundancy. If this can be achieved with enterprise linux then that > would be preferable, but we will go FC8 if the bonding thing can be > sorted out. By the way Xensource 4.x looks to be a respin of RHEL5 > and has pretty good performance but their free version is limited to > 32bit (and hence 4GB ram). Adding the clustering failover is the next > step of course :) > > Thanks again for the help so far. > > /Christian > > > > >>>>>>>>>>> > just FYI for the list, I have a how-to for a bonded and VLAN tagged network. > > http://www.certifried.com > > ODT and PDF formats available. > > > It might not be the best way, but I've sent it out to my colleagues > several times and have never received any negative feedback. > Mark > > > > Dale Bewley wrote: > > > I haven't done bonding, but you should be able to bond them and then compose a bridge on top of this bonded device I would think. > > -- > Dale Bewley - Unix Administrator - Shields Library - UC Davis > GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 > > -- > Fedora-xen mailing list > Fedora-xen redhat com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > ************************************************************************ **** > Checked by MailWasher server (www.Firetrust.com) > WARNING. No FirstAlert account found. > To reduce spam further activate FirstAlert. > This message can be removed by purchasing a FirstAlert Account. > ************************************************************************ **** > > ------------------------------------------------------------------------ > > -- > 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 nooroon at gmail.com Wed Dec 5 09:44:12 2007 From: nooroon at gmail.com (nooroon) Date: Wed, 5 Dec 2007 10:44:12 +0100 Subject: [Fedora-xen] recompile for using sdl and vnc In-Reply-To: <474C263E.7020705@redhat.com> References: <7675761b0711230222u329e63f2hd83b611511a80619@mail.gmail.com> <20071123164150.GD11721@redhat.com> <7675761b0711260618v6d3ba304m733926efc9e7dffb@mail.gmail.com> <474C263E.7020705@redhat.com> Message-ID: <7675761b0712050144n348749a1h81ada48ab1a9d485@mail.gmail.com> 2007/11/27, Richard W.M. Jones : > > mathieu rohon wrote: > > With sdl display, I don't any mouse and keyboard issues, that's not the > case > > in VNC. Tha fact that te VM dies when the X session dies is not a matter > for > > me. > > My aim is to have a Windows VM which works as if it was not in a VM. > Thanks > > to sdl display, the windows VM is more fluid. But I'd like to use VNC if > I > > can have the same result. > > Have you tried virt-viewer (it's in recent Fedora) instead of vncviewer > or the default virt-manager widget? > > Also I've found that setting up libvirt to use a USB graphics tablet > instead of the default PS/2 mouse improves mouse handling no end. Thanks to VNC USB tablet, the issue whith mouse synchronisation has disappeared. But the VNC display is still less fluid than sdl display. > In a second hand, I'd like to have a local AND remote display. With VNC, I > > can't have both at the same time. I though that I could have it thanks > to > > SDL (for local) and VNC (for remote). > > VNC should support screen sharing, if that's what you want. Or do you > mean two separate displays? Perhaps rdesktop would suit you. > > > Is there a way, with VNC, to configure two access (local and remote) to > the > > VM at the same time? > > vncviewer -Shared. Not sure if there is a virt-viewer option for this. I'm using a classical VNC client. But even if i use the -shared option, another client can't display the VM screen. I think that the server embedded in qemu-dm is not configured to shared the VM screen, and i can't find the way to configure this VNC server. For information, I've tried the FC 8. In this release, the qemu-dm should have been configured with sdl libs, and the sdl display is working for VM. Rich. > > -- > Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ > Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod > Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in > England and Wales under Company Registration No. 03798903 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nooroon at gmail.com Wed Dec 5 10:00:02 2007 From: nooroon at gmail.com (nooroon) Date: Wed, 5 Dec 2007 11:00:02 +0100 Subject: [Fedora-xen] fedora 8 : exit a windows VM Message-ID: <7675761b0712050200h485f521bu80c7f0d084350893@mail.gmail.com> Hi, I'm testing a fedora 8 and it was a good surprise for me : virtualization tools are more usable, and virtualization with xen seems more stable. I'm using xen to create a windows xp VM. the only issue that I have, is when i ask windows to stop the machine, with traditionnal windows tools : start>shutdown computer the windows OS is stopping but the VM doesn't stop. It hangs on a windows screen that says "you can now safely stop the computer". With xen and fedora 7, I didn't have this issue. Does anyone have an explanation? -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at pavlodarproductions.com Wed Dec 5 19:15:36 2007 From: lists at pavlodarproductions.com (Bob Jones) Date: Wed, 05 Dec 2007 13:15:36 -0600 Subject: [Fedora-xen] fedora 8 : exit a windows VM In-Reply-To: <7675761b0712050200h485f521bu80c7f0d084350893@mail.gmail.com> References: <7675761b0712050200h485f521bu80c7f0d084350893@mail.gmail.com> Message-ID: <4756F8D8.1010707@pavlodarproductions.com> Hi, I had the same problem initially with all 3 of the full-virt machines I've setup (XP Pro, 2000 server, and 2003 Small Business Server). I don't know if it was solved with Fedora updates or with Windows updates, but it now works like a native Windows machine. An aside to the rest of the list: I have to admit that I have been very pleased with the performance using a Xen VM over KVM/QEMU. It runs at almost what I would expect it to run at on the bare metal machine (AMD Athlon FX-62 w/4GB DDR2 800 memory, software raid5). This is a HUGE improvement over other virtualization products I have used in the past (WIn4Lin/Win4Lin Pro, VMWare workstation and server, Parallels, KVM/Qemu, and now Xen). Developers, please keep up the great work! Bob J. nooroon wrote: > Hi, > > I'm testing a fedora 8 and it was a good surprise for me : > virtualization tools are more usable, and virtualization with xen seems > more stable. > > I'm using xen to create a windows xp VM. > the only issue that I have, is when i ask windows to stop the machine, > with traditionnal windows tools : start>shutdown computer > the windows OS is stopping but the VM doesn't stop. It hangs on a > windows screen that says "you can now safely stop the computer". > > With xen and fedora 7, I didn't have this issue. Does anyone have an > explanation? > > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From mnielsen at redhat.com Wed Dec 5 19:59:22 2007 From: mnielsen at redhat.com (Mark Nielsen) Date: Wed, 05 Dec 2007 14:59:22 -0500 Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? In-Reply-To: References: <4751EBFE.6000100@redhat.com> Message-ID: <4757031A.6030004@redhat.com> Christian, Sorry to hear it didn't work out for you. It's not a straight-forward or simple configuration. The problem is that there are so many possible combinations of VLANs, bonds, networks that most of the configuration is left up to the ability and knowledge of the administrator. It sounds like you might've missed a few steps somewhere along the way. I admit that my document isn't 100% step-by-step, it takes a pretty good understanding of everything that's going on. Your problem could be in your step where you "Restart networking". This stuff all needs to happen in a particular order, and that might not have happened. Unfortunately it's nearly impossible to help troubleshoot that in e-mails. I can say that I have the configuration I describe (and it sounds like what you want) working perfectly, so I know it's possible. Mark Christian Lahti wrote: > Hi Mark: > > > > Well, > > > > I carefully went through your PDF document for setting up a bonded pair > on RHEL 5.1 and at the end of the day this does not work for me. This > is the procedure more or less I have tried: > > > > * Make sure eth0 and eth1 work as normal eth devices without LACP > * Edit /etc/modprobe.conf to add the bonding kernel module > * Edit /etc/sysconfig/network-scripts/ifcfg-eth0 and ifcfg-eth1 to > be slave devices with the master as bond0 > * Create /etc/sysconfig/network-scripts/ifcfg-bond0 with static IP > info > * Plug into LACP enabled ports on switch and reboot the box > * At this point bond0 works fine, as expected, we have been doing > this all day long on non-xen kernels for years > * NOW...following your document > * Remove the /etc/libvirt/qemu/networks/autostart/* so that the > pointless 192.168.122.x NAT network does not get created > * Grab the network-scripts-bridge-bond-vlan script from the link > in the message and put into /etc/xen/scripts > * Edit /etc/xen/xend-config.sxp and replace (network-script > network-bridge) with (network-script network-bridge-bond-vlan) > * Restart networking > * At this point networking for the physical host in invariably > completely hosed, and there is no xen networking at all > * It is noteworthy to add that I did not make any modifications to > the network-scripts-bridge-bond-vlan script as you suggest since I am on > a single vlan (so far) and the default setup in the script seems sane > for a single NON-VLAN bond0 configuration > > > > So in a nutshell the it seems that libvirt interface just does not seem > to use the xen scripts...rather it's own (undocumented?) crap. After a > week of head-banging on this we really have no choice but to abandon > Redhat in favor of Suse 10.3, which incidentally works right out of the > box with bridge, NAT, bond, you name it. I suggest RH staff install a > copy of this to see how they did it, you don't even have to jump through > hoops to configure a bond from the command line, you can do this with > their stock GUI tools if you so choose. I am not knocking RedHat, but > we need something that "just works" and so far for xen + bond + RH has > been a non-starter for us after much effort. By the way, to get > networking un-foobar'ed on the physical machine I have to run > system-config-network and remove all Ethernet devices, then reboot, then > redefine eth0 and eth1 as as normal DHCP devices. I can then go > re-setup the bond0 device from the command line. > > > > If anyone has step-by-step directions on how to do this with RHEL 5.1 I > am happy to try again at some future point. The goals are simple: > > > > * Step one: create a bond0 from eth0 and eth1 that can be used as > a bridged device by xen on a single VLAN > * Step two: create a bond0 (aliases?) that can be assigned > multiple VLANs, AND have these VLAN devices available to be used by xen > > > > I would settle for item #1 really. > > > > /Christian > > > > > > > > > > > > ________________________________ > > From: Christian Lahti > Sent: Saturday, December 01, 2007 3:56 PM > To: mnielsen at redhat.com; fedora-xen at redhat.com > Subject: RE: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? > > > > Hi Mark: > > > > Thank you very much for your response, I did indeed read the original > poster as Dale by mistake :) So what you are saying makes perfect sense > to me and sounds like exactly what we are after, I will have 3 vlans to > bridge myself ultimately. My next question is the relative merits of > RHEL5.1 as compared to Fedora 8. Obviously I would prefer the stable > enterprise release rather than bleeding edge Fedora, but has fully > virtualized windows performance been fixed in this release? At any rate > I am looking forward to getting this up and running tomorrow! > > > > /Christian > > > > > > ________________________________ > > From: Mark Nielsen [mailto:mnielsen at redhat.com] > Sent: Sat 12/1/2007 3:19 PM > To: Christian Lahti > Subject: Re: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? > > hmm, did you mean "Hi Mark" ?? > > I have 8 Dell 2950s running RHEL 5.1 (new libvirt with that funky NAT > they added). I have 4 NICs in each; 2 copper, 2 fiber. I bond the 2 > copper (eth0 and eth1) and call it bond0. bond0 carries my "private" IP > for cluster suite communications on the dom0 (physical) cluster. > > Then I bond eth2 and eth3 (fiber) in to bond1. I lay down the public > network for the dom0 cluster on bond1.100 (for example, that would be > VLAN 100). I also add many (up to 10 or so now) VLANs on bond1 > (bond1.20, bond1.21, bond1.22, etc). Then I create xen bridges to each > of these bond/VLAN devices. This allows me to put any particular VM on > any particular (or combination up to 3) of these xen bridged bonded VLAN > device. > > My document explains, in detail, how to do all of this :) The only added > step is that I have to "undefine" (virsh net-undefine default) the > default network that the new libvirt creates (virbr0). Even with this > new NAT thing they added, I've been told (by our devs) that the > preferred way to do static network configurations is with the method I > lay out. NAT is more for dynamic networks (cable modems, dial-up, wifi, > etc). > > I'm pretty sure there weren't any significant changes in Fedora 8 (we've > dropped the word "core" now, btw) that don't exist in RHEL 5.1 with > respects to the network. 5.0 -> 5.1 is when that NAT change came down > the pipe. > > Mark > > p.s. I'm happy to answer any other questions you may have about my > document. I'm quite certain that, if you follow it, you'll have what > you're looking for. > > Christian Lahti wrote: > >> Hi Dale: >> >> I work with David who posted the original question to the mailing >> list. I think we need to give a bit more background info on what we >> are trying to do. We are running a mixed environment of mostly CentOS >> 3, 4and 5, we do have a few windows servers and XP systems as well. >> We are looking to virtualize all these platforms. Normally we have a >> bonded pair of NICs for the physical hosts, we were able to get this >> running using CentOS 5 x86_64 with no problems, the guest machines use >> the bonded pair in bridged mode as expected after a bit of tweaking. >> The biggest issue we found with EL5 is that windows guest performace >> is dismal at best, hence our decision to have a look at Fedora Core 8 >> x86_64. I am happy to report that performance for all of our guest >> platforms is *very* good with FC8, but it seems that libvirt changed >> the way networking is setup for Xen. The default NAT configuration is >> pretty useless for production server environment. Thanks to the >> mailing list we are now able to bridge a single NIC on FC8 (like eth0 >> for example), but we cannot figure out how to get a bridge for bond0 >> (comprised of eth0 and eth1) defined and available to Xen. All the >> tweaks that worked find on EL5 have not worked so far on FC8. I am >> going to review your document tomorrow and give it a try, but any idea >> on whether your methodology will work on FC8 and libvirt? I am >> willing to blow a Sunday to get this worked out once and for all :) >> >> Basically we are after good performance on both para and fully >> virtualized guests using a bonded pair of GB NICs for speed and >> redundancy. If this can be achieved with enterprise linux then that >> would be preferable, but we will go FC8 if the bonding thing can be >> sorted out. By the way Xensource 4.x looks to be a respin of RHEL5 >> and has pretty good performance but their free version is limited to >> 32bit (and hence 4GB ram). Adding the clustering failover is the next >> step of course :) >> >> Thanks again for the help so far. >> >> /Christian >> >> >> >> >> just FYI for the list, I have a how-to for a bonded and VLAN tagged >> > network. > >> http://www.certifried.com >> >> ODT and PDF formats available. >> >> >> It might not be the best way, but I've sent it out to my colleagues >> several times and have never received any negative feedback. >> Mark >> >> >> >> Dale Bewley wrote: >> >> >> I haven't done bonding, but you should be able to bond them and >> > then compose a bridge on top of this bonded device I would think. > >> -- >> Dale Bewley - Unix Administrator - Shields Library - UC Davis >> GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 >> >> -- >> Fedora-xen mailing list >> Fedora-xen redhat com >> https://www.redhat.com/mailman/listinfo/fedora-xen >> >> >> >> > ************************************************************************ > **** > >> Checked by MailWasher server (www.Firetrust.com) >> WARNING. No FirstAlert account found. >> To reduce spam further activate FirstAlert. >> This message can be removed by purchasing a FirstAlert Account. >> >> > ************************************************************************ > **** > >> > ------------------------------------------------------------------------ > >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen >> >> > > From robin-lists at robinbowes.com Fri Dec 7 01:26:18 2007 From: robin-lists at robinbowes.com (Robin Bowes) Date: Fri, 07 Dec 2007 01:26:18 +0000 Subject: [Fedora-xen] Problem booting Fedora 8 guest on FC6 host Message-ID: Hi, I'm trying to get a Fedora 8 para-virtual guest to run on a FC6 host. I had problems with the install because of the bugs in the 0.200 release of virtinst. I fixed this by doing a source install of virtinst-0.300. The F8 install completed succesfully, but when the guest boots I get this msg: md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. VFS: Cannot open root device "vg_skeggles/lv_root" 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) Has anyone got any ideas about how to fix this? I am currently using kernel-xen-2.6.20-1.2952.fc6 and xen 3.0.3-9.fc6 (I've upgraded to kernel-xen-2.6.20-1.3002.fc6 and xen-3.0.3-13.fc6 but not rebooted yet). My xen config file (created automatically by virt-install) is as follows: name = "skeggles" uuid = "a8912edd-ea7c-f324-f1bb-fdbc0c1a4b65" maxmem = 512 memory = 512 vcpus = 1 bootloader = "/usr/bin/pygrub" on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" sdl = 0 vnc = 0 vncunused = 0 disk = [ "phy:/dev/vg_guests/lv_skeggles,xvda,w" ] vif = [ "mac=00:16:3e:4c:82:c7,bridge=xenbr0" ] Thanks, R. From berrange at redhat.com Fri Dec 7 01:41:42 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 7 Dec 2007 01:41:42 +0000 Subject: [Fedora-xen] Update to Xen 3.1.2 available for testing Message-ID: <20071207014142.GA13085@redhat.com> FYI, in both Fedora 7 & and Fedora 8, I have got new updates of the Xen userspace to be sync to the latest Xen 3.1.2 bugfix release available for testing. If you wish to test this, you can do yum --enablerepo=updates-testing update xen If there are no major problems reported I will push these to 'updates' in about a week. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From dan at danny.cz Fri Dec 7 09:55:22 2007 From: dan at danny.cz (Dan =?ISO-8859-1?Q?Hor=E1k?=) Date: Fri, 07 Dec 2007 10:55:22 +0100 Subject: [Fedora-xen] align fix for vmm-create.glade Message-ID: <1197021322.3277.9.camel@eagle.danny.cz> Hello, in the virt-manager's new VM wizard there is a small alignment inconsistency on the "Locating installation media" page for paravirtualized machine. The second and third label are right aligned, while the first (Install Media URL) is not. The included patch fixes this issue. With regards, Dan Horak -------------- next part -------------- A non-text attachment was scrubbed... Name: vmm-create.glade-align.patch Type: text/x-patch Size: 540 bytes Desc: not available URL: From dan at danny.cz Fri Dec 7 09:55:22 2007 From: dan at danny.cz (Dan =?ISO-8859-1?Q?Hor=E1k?=) Date: Fri, 07 Dec 2007 10:55:22 +0100 Subject: [Fedora-xen] align fix for vmm-create.glade Message-ID: <1197021322.3277.9.camel@eagle.danny.cz> Hello, in the virt-manager's new VM wizard there is a small alignment inconsistency on the "Locating installation media" page for paravirtualized machine. The second and third label are right aligned, while the first (Install Media URL) is not. The included patch fixes this issue. With regards, Dan Horak -------------- next part -------------- A non-text attachment was scrubbed... Name: vmm-create.glade-align.patch Type: text/x-patch Size: 540 bytes Desc: not available URL: From pasik at iki.fi Fri Dec 7 10:34:55 2007 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Fri, 7 Dec 2007 12:34:55 +0200 Subject: [Fedora-xen] Update to Xen 3.1.2 available for testing In-Reply-To: <20071207014142.GA13085@redhat.com> References: <20071207014142.GA13085@redhat.com> Message-ID: <20071207103455.GX17677@edu.joroinen.fi> On Fri, Dec 07, 2007 at 01:41:42AM +0000, Daniel P. Berrange wrote: > FYI, in both Fedora 7 & and Fedora 8, I have got new updates of the Xen > userspace to be sync to the latest Xen 3.1.2 bugfix release available for > testing. If you wish to test this, you can do > > yum --enablerepo=updates-testing update xen > > If there are no major problems reported I will push these to 'updates' in > about a week. > Hmm, this is only the userspace, so how about the xen itself? Is it going to be updaded to 3.1.2 .. It would mean new kernel packages? -- Pasi From nooroon at gmail.com Fri Dec 7 13:47:17 2007 From: nooroon at gmail.com (nooroon) Date: Fri, 7 Dec 2007 14:47:17 +0100 Subject: [Fedora-xen] fedora 8 : exit a windows VM In-Reply-To: <4756F8D8.1010707@pavlodarproductions.com> References: <7675761b0712050200h485f521bu80c7f0d084350893@mail.gmail.com> <4756F8D8.1010707@pavlodarproductions.com> Message-ID: <7675761b0712070547k1b4aabc9p3ff7fa2197d0803e@mail.gmail.com> I totally agree with you about the Xen performance on fed 8! Thanks to yum, I've updated my system, but it has no effect. Shutting down windows VM doesn't stop the virtuel machine. Does anyone knows what is the issue? 2007/12/5, Bob Jones : > > Hi, > > I had the same problem initially with all 3 of the full-virt machines > I've setup (XP Pro, 2000 server, and 2003 Small Business Server). I > don't know if it was solved with Fedora updates or with Windows updates, > but it now works like a native Windows machine. > > An aside to the rest of the list: > > I have to admit that I have been very pleased with the performance using > a Xen VM over KVM/QEMU. It runs at almost what I would expect it to run > at on the bare metal machine (AMD Athlon FX-62 w/4GB DDR2 800 memory, > software raid5). This is a HUGE improvement over other virtualization > products I have used in the past (WIn4Lin/Win4Lin Pro, VMWare > workstation and server, Parallels, KVM/Qemu, and now Xen). Developers, > please keep up the great work! > > Bob J. > > nooroon wrote: > > Hi, > > > > I'm testing a fedora 8 and it was a good surprise for me : > > virtualization tools are more usable, and virtualization with xen seems > > more stable. > > > > I'm using xen to create a windows xp VM. > > the only issue that I have, is when i ask windows to stop the machine, > > with traditionnal windows tools : start>shutdown computer > > the windows OS is stopping but the VM doesn't stop. It hangs on a > > windows screen that says "you can now safely stop the computer". > > > > With xen and fedora 7, I didn't have this issue. Does anyone have an > > explanation? > > > > > > ------------------------------------------------------------------------ > > > > -- > > 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 berrange at redhat.com Fri Dec 7 14:26:25 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 7 Dec 2007 14:26:25 +0000 Subject: [Fedora-xen] Update to Xen 3.1.2 available for testing In-Reply-To: <20071207103455.GX17677@edu.joroinen.fi> References: <20071207014142.GA13085@redhat.com> <20071207103455.GX17677@edu.joroinen.fi> Message-ID: <20071207142624.GB31006@redhat.com> On Fri, Dec 07, 2007 at 12:34:55PM +0200, Pasi K?rkk?inen wrote: > On Fri, Dec 07, 2007 at 01:41:42AM +0000, Daniel P. Berrange wrote: > > FYI, in both Fedora 7 & and Fedora 8, I have got new updates of the Xen > > userspace to be sync to the latest Xen 3.1.2 bugfix release available for > > testing. If you wish to test this, you can do > > > > yum --enablerepo=updates-testing update xen > > > > If there are no major problems reported I will push these to 'updates' in > > about a week. > > > > Hmm, this is only the userspace, so how about the xen itself? Is it going to > be updaded to 3.1.2 .. It would mean new kernel packages? Xen 3.1.x maintains hypervisor ABI compatability, so you can use any 3.1.x hypervisor with any 3.1.x userspace. We will update the hypervisor separately, when we do a kernel-xen update. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From jklein at saugus.k12.ca.us Fri Dec 7 21:16:45 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Fri, 7 Dec 2007 13:16:45 -0800 (PST) Subject: [Fedora-xen] Panic with 32bit RHEL4 on 64bit RHEL5 Message-ID: <29088781.9251197062205908.JavaMail.root@do8> Am experiencing a domU panic when running 32bit RHEL4 (2.6.9-67.ELxenU) on 64bit RHEL5 (2.6.18-53.el5xen) under high load conditions. Problem has not occurred (so far) when hosting the same domU on 32bit RHEL5, so I'm a little stumped. Any ideas or recommendations would be greatly appreciated. Thanks in advance! Unable to handle kernel NULL pointer dereference at virtual address 00000000 printing eip: c01496c9 2c84c000 -> *pde = 00000000:9a3e9027 1b3eb000 -> *pme = 00000000:bfd81067 1c064000 -> *pte = 00000000:00000000 Oops: 0000 [#1] SMP Modules linked in: md5 ipv6 autofs4 sunrpc dm_mirror xennet ext3 jbd dm_mod xenblk sd_mod scsi_mod CPU: 0 EIP: 0061:[] Not tainted VLI EFLAGS: 00010287 (2.6.9-67.ELxenU) EIP is at zap_pte_range+0x279/0x489 eax: 00046000 ebx: 00000000 ecx: f5392000 edx: 00000000 esi: 000b0b21 edi: c1f75bc0 ebp: 00000000 esp: e5aa3e04 ds: 007b es: 007b ss: 0068 Process amavisd (pid: 30894, threadinfo=e5aa3000 task=e54146c0) Stack: b0b21067 00000000 00000000 00000000 00000000 00000000 00046000 0a800000 c202d2a0 e548a2a8 0a846000 00000000 0a800000 c0149980 c202d2a0 e548a2a0 0a800000 00046000 00000000 0a7c6000 e5486008 0a846000 00000000 c01499e5 Call Trace: [] zap_pmd_range+0xa7/0xcb [] unmap_page_range+0x41/0x65 [] unmap_vmas+0xcd/0x1e8 [] exit_mmap+0x85/0x15b [] mmput+0x52/0x77 [] copy_mm+0x36c/0x396 [] copy_process+0x6b5/0xb0b [] do_fork+0x8a/0x16b [] sys_clone+0x24/0x28 [] syscall_call+0x7/0xb Code: 8b 4c 24 14 8b 41 04 85 c0 75 0a 83 39 00 0f 45 c1 89 44 24 14 c7 44 24 10 00 00 00 00 8b 44 24 18 39 44 24 10 0f 83 08 02 00 00 <8b> 55 00 8b 4d 04 85 d2 75 08 85 c9 0f 84 e6 01 00 00 88 d0 a8 -------------- next part -------------- An HTML attachment was scrubbed... URL: From clalance at redhat.com Fri Dec 7 21:34:01 2007 From: clalance at redhat.com (Chris Lalancette) Date: Fri, 07 Dec 2007 16:34:01 -0500 Subject: [Fedora-xen] Panic with 32bit RHEL4 on 64bit RHEL5 In-Reply-To: <29088781.9251197062205908.JavaMail.root@do8> References: <29088781.9251197062205908.JavaMail.root@do8> Message-ID: <4759BC49.6010306@redhat.com> Jim Klein wrote: > Am experiencing a domU panic when running 32bit RHEL4 (2.6.9-67.ELxenU) > on 64bit RHEL5 (2.6.18-53.el5xen) under high load conditions. Problem > has not occurred (so far) when hosting the same domU on 32bit RHEL5, so > I'm a little stumped. Any ideas or recommendations would be greatly > appreciated. Thanks in advance! 32 PV on 64 hypervisor is known to be unstable with RHEL-5.1 as the dom0. This should be addressed in an upcoming release. Chris Lalancette From Dustin.Henning at prd-inc.com Fri Dec 7 21:38:20 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Fri, 7 Dec 2007 16:38:20 -0500 Subject: [Fedora-xen] Xen Network Configuration Files? In-Reply-To: <4755E1A4.3060800@herakles.homelinux.org> References: <4751EBFE.6000100@redhat.com> <4751FD7D.1020604@herakles.homelinux.org> <003301c835fd$f9bd7440$ed385cc0$@Henning@prd-inc.com> <475518F1.2030101@herakles.homelinux.org> <001201c83678$600c8db0$2025a910$@Henning@prd-inc.com> <4755E1A4.3060800@herakles.homelinux.org> Message-ID: <006501c83919$7ca2f880$75e8e980$@Henning@prd-inc.com> When xend starts on my F7 box, it creates virbr0 and xenbr0 as expected, but it also creates br0, which is a bridge I had set up by creating an ifcfg-br0 in network-scripts, and that file is long since gone (the box has gone through two kernel updates and at least as many boots since then). I didn't use xend tools to create this stuff, so I have no idea why xend has taken to creating the bridge (which was never even used for a domU). Additionally, when I was messing around trying to get rid of it, xend stopped creating peth0. I created some network-scripts and added a line to rc.local to get the system working again and make all of this stuff to act on my terms, but I would like to find the config files responsible and get this set up properly. In the discussion labeled "Fedora Core 8 + Xenbr0 + network bridging?" John Summerfield suggested that I use rpm -V to find any changed files that might be responsible. I ran rpm- V for the following packages: kvm qemu kernel-xen xen xen-libs libvirt-python libvirt virt-manager python-virtinst The only files that aren't in original condition are xendomains and xen-config.sxp. A diff of extracted originals and my copies shows nothing different in either of these files that would cause my problem. I have done enough testing to determine that 'xend start' (in the appropriate bin folder, not even the init script [which notably runs 'xend start' causing the same end result]) creates br0 and no longer creates peth0 (these results did not appear in tandem). Can anyone point me toward any standard files that might (when using xen cli utils but f7 runlevel 5) somehow get automatically updated and effect how xend sets up the network (system boots normal in non-xen kernels or when xend is prevented from starting) that wouldn't be associated with any of the above rpms (pointers toward any other rpms I might need to check would be appreciated too). Thank you, Dustin From gcatalano at crypticstudios.com Fri Dec 7 22:45:05 2007 From: gcatalano at crypticstudios.com (Gary Catalano) Date: Fri, 7 Dec 2007 14:45:05 -0800 Subject: [Fedora-xen] (no subject) Message-ID: Greetings! I'm having a problem with fedora8 and Xen 3.1.0. I'm trying to get Windows to run under Xen (I've been using these instructions http://www.xensource.com/files/xen_install_windows.pdf) and I get all the way to the last steps but when I start my virtual machine I get an error saying it can't find a bootable drive: CDROM boot failure code : 0002 Boot from CD-Rom failed: could not read the boot disk FATAL: No bootable device. Here's the .hvm I'm using to launch my virtual machine: # -*- mode: python; -*- #============================================================================ # Python configuration setup for 'xm create'. # This script sets the parameters used when a domain is created using 'xm create'. # You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #============================================================================ import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' #---------------------------------------------------------------------------- # Kernel image file. kernel = "/usr/lib/xen/boot/hvmloader" # The domain build function. HVM domain uses 'hvm'. builder='hvm' # Initial memory allocation (in megabytes) for the new domain. # # WARNING: Creating a domain with insufficient memory may cause out of # memory errors. The domain needs enough memory to boot kernel # and modules. Allocating less than 32MBs is not recommended. memory = 1024 # Shadow pagetable memory for the domain, in MB. # Should be at least 2KB per MB of domain memory, plus a few MB per vcpu. # shadow_memory = 8 # A name for your domain. All domains must have different names. name = "win2k3-001" # 128-bit UUID for the domain. The default behavior is to generate a new UUID # on each call to 'xm create'. #uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9" #----------------------------------------------------------------------------- # The number of cpus guest platform has, default=1 #vcpus=1 # Enable/disable HVM guest PAE, default=1 (enabled) #pae=1 # Enable/disable HVM guest ACPI, default=1 (enabled) #acpi=1 # Enable/disable HVM APIC mode, default=1 (enabled) # Note that this option is ignored if vcpus > 1 #apic=1 # List of which CPUS this domain is allowed to use, default Xen picks #cpus = "" # leave to Xen to pick #cpus = "0" # all vcpus run on CPU0 #cpus = "0-3,5,^1" # run on cpus 0,2,3,5 # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci' ] # type=ioemu specify the NIC is an ioemu device not netfront vif = [ 'type=ioemu, mac=00:16:3e:00:00:94, bridge=xenbr0' ] #---------------------------------------------------------------------------- # Define the disk devices you want the domain to have access to, and # what you want them accessible as. # Each disk entry is of the form phy:UNAME,DEV,MODE # where UNAME is the device, DEV is the device name the domain will see, # and MODE is r for read-only, w for read-write. disk = [ 'phy:/dev/VGGuests/w2k3-001,ioemu:hda,w' ] #disk = [ 'file:/.img,hda,w', ',hdc:cdrom,r' ] #---------------------------------------------------------------------------- # Configure the behaviour when a domain exits. There are three 'reasons' # for a domain to stop: poweroff, reboot, and crash. For each of these you # may specify: # # "destroy", meaning that the domain is cleaned up as normal; # "restart", meaning that a new domain is started in place of the old # one; # "preserve", meaning that no clean-up is done until the domain is # manually destroyed (using xm destroy, for example); or # "rename-restart", meaning that the old domain is not cleaned up, but is # renamed and a new domain started in its place. # # The default is # # on_poweroff = 'destroy' # on_reboot = 'restart' # on_crash = 'restart' # # For backwards compatibility we also support the deprecated option restart # # restart = 'onreboot' means on_poweroff = 'destroy' # on_reboot = 'restart' # on_crash = 'destroy' # # restart = 'always' means on_poweroff = 'restart' # on_reboot = 'restart' # on_crash = 'restart' # # restart = 'never' means on_poweroff = 'destroy' # on_reboot = 'destroy' # on_crash = 'destroy' #on_poweroff = 'destroy' #on_reboot = 'restart' #on_crash = 'restart' #============================================================================ # New stuff device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm' #----------------------------------------------------------------------------- # Disk image for cdrom= "/tmp/win2k3srv.iso" #----------------------------------------------------------------------------- # boot on floppy (a), hard disk (c), Network (n) or CD-ROM (d) # default: hard disk, cd-rom, floppy boot="d" #----------------------------------------------------------------------------- # write to temporary files instead of disk image files #snapshot=1 #---------------------------------------------------------------------------- # enable SDL library for graphics, default = 0 sdl=1 #---------------------------------------------------------------------------- # enable VNC library for graphics, default = 1 vnc=0 #---------------------------------------------------------------------------- # address that should be listened on for the VNC server if vnc is set. # default is to use 'vnc-listen' setting from /etc/xen/xend-config.sxp #vnclisten="127.0.0.1" #---------------------------------------------------------------------------- # set VNC display number, default = domid #vncdisplay=1 #---------------------------------------------------------------------------- # try to find an unused port for the VNC server, default = 1 #vncunused=1 #---------------------------------------------------------------------------- # enable spawning vncviewer for domain's console # (only valid when vnc=1), default = 0 #vncconsole=0 #---------------------------------------------------------------------------- # set password for domain's VNC console # default is depents on vncpasswd in xend-config.sxp vncpasswd='' #---------------------------------------------------------------------------- # no graphics, use serial port #nographic=0 #---------------------------------------------------------------------------- # enable stdvga, default = 0 (use cirrus logic device model) #stdvga=0 #----------------------------------------------------------------------------- # serial port re-direct to pty deivce, /dev/pts/n # set password for domain's VNC console # default is depents on vncpasswd in xend-config.sxp vncpasswd='' #---------------------------------------------------------------------------- # no graphics, use serial port #nographic=0 #---------------------------------------------------------------------------- # enable stdvga, default = 0 (use cirrus logic device model) #stdvga=0 #----------------------------------------------------------------------------- # serial port re-direct to pty deivce, /dev/pts/n # then xm console or minicom can connect #serial='pty' #----------------------------------------------------------------------------- # Qemu Monitor, default is disable # Use ctrl-alt-2 to connect #monitor=1 #----------------------------------------------------------------------------- # enable sound card support, [sb16|es1370|all|..,..], default none #soundhw='sb16' #----------------------------------------------------------------------------- # set the real time clock to local time [default=0 i.e. set to utc] #localtime=1 #----------------------------------------------------------------------------- # set the real time clock offset in seconds [default=0 i.e. same as dom0] #rtc_timeoffset=3600 #----------------------------------------------------------------------------- # start in full screen #full-screen=1 #----------------------------------------------------------------------------- # Enable USB support (specific devices specified at runtime through the # monitor window) #usb=1 # Enable USB mouse support (only enable one of the following, `mouse' for # PS/2 protocol relative mouse, `tablet' for # absolute mouse) #usbdevice='mouse' #usbdevice='tablet' #----------------------------------------------------------------------------- # Set keyboard layout, default is en-us keyboard. #keymap='ja' Any help would be appreciated. Gary Catalano IT Manager Cryptic Studios (408) 399 -1969 x150 (office) (650) 776-2500 (cell) www.crypticstudios.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From erenoglu at gmail.com Sun Dec 9 02:32:08 2007 From: erenoglu at gmail.com (Emre Erenoglu) Date: Sun, 9 Dec 2007 03:32:08 +0100 Subject: [Fedora-xen] Fedora 8 - Linux HVM Guest - PV Drivers Message-ID: Hi, I'm trying to use a linux HVM guest (DomU) with Paravirtual drivers for network and disk access on my updated Fedora 8 setup. In order to achieve this, I've downloaded the source package of appropriate (same version) Xen Hypervisor from redhat website, then copied this source to my DomU and compiled the unmodified_drivers folder following the steps mentioned in the README file. Everything went fine and I got my xen-platform-pci, xen-baloon, xen-vnif and xen-vbd (.ko) drivers. They modprobe fine, however, after some time, the DomU freezes up. Specifically, system freezes quicker (usually) with only vbd, and takes more time to free with only xen-vnif loaded into memory. When I say only, xen-platform-pci always loaded, but only the mentioned driver is netfront or block-front, others are ioemu. xen-vnif also complains about a memory leak when it's rmmod 'ed. Shall I file a bug report? Thanks, Emre Erenoglu erenoglu at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jackson at eu.citrix.com Mon Dec 10 12:01:27 2007 From: Ian.Jackson at eu.citrix.com (Ian Jackson) Date: Mon, 10 Dec 2007 12:01:27 +0000 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages Message-ID: <18269.10903.495456.360011@mariner.uk.xensource.com> We hope to be releasing upstream Xen 3.2 soon. As you'll know, we've been in the habit of producing binary packages for our releases, including for Fedora. It seemed to me that the best approach would be, where possible, to use a distro's own packaging setup. That would be more likely to generate packages which integrate well with the distro and behave more like the distro's own Xen packaging arrangements. I haven't looked at the FC6 srpm in detail yet but what would you think about it if we were to generate our 3.2 binary rpms based on that ? Regards, Ian. From debian at herakles.homelinux.org Mon Dec 10 12:09:42 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Mon, 10 Dec 2007 21:09:42 +0900 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages In-Reply-To: <18269.10903.495456.360011@mariner.uk.xensource.com> References: <18269.10903.495456.360011@mariner.uk.xensource.com> Message-ID: <475D2C86.7050401@herakles.homelinux.org> Ian Jackson wrote: > We hope to be releasing upstream Xen 3.2 soon. As you'll know, we've > been in the habit of producing binary packages for our releases, > including for Fedora. > > It seemed to me that the best approach would be, where possible, to > use a distro's own packaging setup. That would be more likely to > generate packages which integrate well with the distro and behave more > like the distro's own Xen packaging arrangements. > > I haven't looked at the FC6 srpm in detail yet but what would you > think about it if we were to generate our 3.2 binary rpms based on > that ? I wouldn't be impressed:-) I believe FC6 has just been terminated (support for Fedora ends soon after the second successor). Is basing on Fedora 8 a problem? It's got about a year of life left in it. Note to Ian I assume that since you seem to have set reply to your own address that you want off-list replies. You cannot reply direct to me however. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From Ian.Jackson at eu.citrix.com Mon Dec 10 12:35:39 2007 From: Ian.Jackson at eu.citrix.com (Ian Jackson) Date: Mon, 10 Dec 2007 12:35:39 +0000 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages In-Reply-To: <475D2C86.7050401@herakles.homelinux.org> References: <18269.10903.495456.360011@mariner.uk.xensource.com> <475D2C86.7050401@herakles.homelinux.org> Message-ID: <18269.12955.151851.455070@mariner.uk.xensource.com> John Summerfield writes ("Re: [Fedora-xen] xen-unstable => 3.2, binary packages"): > I believe FC6 has just been terminated (support for Fedora ends soon > after the second successor). Maybe I'm confused about version numbers or looking at the wrong sites. I'm pretty new to the fedora world so I hope you'll forgive me needing a bit of handholding. The sources I found were at http://download.fedora.redhat.com/pub/fedora/linux/core/ http://download.fedora.redhat.com/pub/fedora/linux/core/test/ where the most recent are 6 and 6.93 (which I take to be a work-in-progress 7). I was somewhat puzzled by the .redhat.com domain but I wasn't able to find anywhere more recent. Did I miss the relevant documentation ? I found this: http://fedoraproject.org/wiki/PackageMaintainers/Join http://fedoraproject.org/wiki/PackageMaintainers but I seem still in the dark. > Is basing on Fedora 8 a problem? It's got about a year of life left in it. If that's released then yes. I see from the fedoraproject.org website that there's some marketing swooshing for it :-). > Note to Ian > I assume that since you seem to have set reply to your own address that > you want off-list replies. You cannot reply direct to me however. I'm not sure I follow. Evidently there is a convention here of how to deal with mailing lists and email headers, but I'm not aware of it. http://fedoraproject.org/wiki/Communicate/MailingListGuidelines didn't seem to help me. I'm subscribed to the list and will read replies sent there, if that's what you mean. And I think it's be rude to just post and expect responders to email you rather than replying to the list. OTOH I know most (more than half, but by no means all) people prefer to get a CC. I'll assume from what you say above that you would prefer me not to CC you. Ian. From veillard at redhat.com Mon Dec 10 12:47:21 2007 From: veillard at redhat.com (Daniel Veillard) Date: Mon, 10 Dec 2007 07:47:21 -0500 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages In-Reply-To: <18269.12955.151851.455070@mariner.uk.xensource.com> References: <18269.10903.495456.360011@mariner.uk.xensource.com> <475D2C86.7050401@herakles.homelinux.org> <18269.12955.151851.455070@mariner.uk.xensource.com> Message-ID: <20071210124721.GC15951@redhat.com> On Mon, Dec 10, 2007 at 12:35:39PM +0000, Ian Jackson wrote: > John Summerfield writes ("Re: [Fedora-xen] xen-unstable => 3.2, binary packages"): > > I believe FC6 has just been terminated (support for Fedora ends soon > > after the second successor). > > Maybe I'm confused about version numbers or looking at the wrong > sites. I'm pretty new to the fedora world so I hope you'll forgive me > needing a bit of handholding. > > The sources I found were at > http://download.fedora.redhat.com/pub/fedora/linux/core/ > http://download.fedora.redhat.com/pub/fedora/linux/core/test/ > where the most recent are 6 and 6.93 (which I take to be a > work-in-progress 7). 'Fedora Core' was renamed 'Fedora' between version 6 and 7, you will find the latests under the 'releases' subdir: http://download.fedora.redhat.com/pub/fedora/linux/releases/ Please rebase based on Fedora 8 if you a binary rebuild, thanks, but ... My own opinion about this is that since xen is packaged as part of Fedora, rebuilding a package on your side might be more of a problem than a solution (I mean for official release rather than for testing) since it's best to keep a coherency. If you have some problems with the packages as done in Fedora, it's better to get the issues (assuming any) solved, rather than putting a parallel set of packages, in the end avoiding users confusions helps everybody in my opinion. my 2 euros cents, Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard at redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From Ian.Jackson at eu.citrix.com Mon Dec 10 13:02:18 2007 From: Ian.Jackson at eu.citrix.com (Ian Jackson) Date: Mon, 10 Dec 2007 13:02:18 +0000 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages In-Reply-To: <20071210124721.GC15951@redhat.com> References: <18269.10903.495456.360011@mariner.uk.xensource.com> <475D2C86.7050401@herakles.homelinux.org> <18269.12955.151851.455070@mariner.uk.xensource.com> <20071210124721.GC15951@redhat.com> Message-ID: <18269.14554.836384.714726@mariner.uk.xensource.com> Daniel Veillard writes ("Re: [Fedora-xen] xen-unstable => 3.2, binary packages"): > 'Fedora Core' was renamed 'Fedora' between version 6 and 7, you > will find the latests under the 'releases' subdir: Ahh! Thanks. > My own opinion about this is that since xen is packaged as part of > Fedora, rebuilding a package on your side might be more of a problem > than a solution (I mean for official release rather than for testing) > since it's best to keep a coherency. If you have some problems with > the packages as done in Fedora, it's better to get the issues (assuming > any) solved, rather than putting a parallel set of packages, in the end > avoiding users confusions helps everybody in my opinion. Right, I can absolutely see where you're coming from and obviously I would prefer to let Fedora developers do the work too :-). The question is what users might be expected to do between the release of Xen 3.2 and the time that Fedora releases its Xen 3.2 packages. For most users of Xen it's a pretty critical and important package and some kind of backport of Xen 3.2 onto their running system is likely to be valuable to many. Xen users may often want to choose explicitly to upgrade their Xen version. I don't know what Fedora's policy is about including new upstream versions in updates, but I would think that most sensible policies would generally frown on pushing a new hypervisor into an already-released distribution. Ian. From debian at herakles.homelinux.org Mon Dec 10 13:34:48 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Mon, 10 Dec 2007 22:34:48 +0900 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages In-Reply-To: <18269.14554.836384.714726@mariner.uk.xensource.com> References: <18269.10903.495456.360011@mariner.uk.xensource.com> <475D2C86.7050401@herakles.homelinux.org> <18269.12955.151851.455070@mariner.uk.xensource.com> <20071210124721.GC15951@redhat.com> <18269.14554.836384.714726@mariner.uk.xensource.com> Message-ID: <475D4078.3030307@herakles.homelinux.org> Ian Jackson wrote: > Daniel Veillard writes ("Re: [Fedora-xen] xen-unstable => 3.2, binary packages"): >> 'Fedora Core' was renamed 'Fedora' between version 6 and 7, you >> will find the latests under the 'releases' subdir: > > Ahh! Thanks. > >> My own opinion about this is that since xen is packaged as part of >> Fedora, rebuilding a package on your side might be more of a problem >> than a solution (I mean for official release rather than for testing) >> since it's best to keep a coherency. If you have some problems with >> the packages as done in Fedora, it's better to get the issues (assuming >> any) solved, rather than putting a parallel set of packages, in the end >> avoiding users confusions helps everybody in my opinion. > > Right, I can absolutely see where you're coming from and obviously I > would prefer to let Fedora developers do the work too :-). > > The question is what users might be expected to do between the release > of Xen 3.2 and the time that Fedora releases its Xen 3.2 packages. > For most users of Xen it's a pretty critical and important package and > some kind of backport of Xen 3.2 onto their running system is likely > to be valuable to many. Xen users may often want to choose explicitly > to upgrade their Xen version. > > I don't know what Fedora's policy is about including new upstream > versions in updates, but I would think that most sensible policies > would generally frown on pushing a new hypervisor into an > already-released distribution. I'm not an official part of the fedora project. I suggest you get the latest from rawhide and work from that. Contact one or more of the most recent people mentioned in the changelog and offer to contribute the results, and by the way, can this go into Fedora 7 & 8 too? Rawhide is the bleeding edge of Fedora. people there expect to get cut:-) I wouldn't regard fedora as a stable distribution; if stability is important, CentOS is the place to go for cheapskates like me. Fedora regularly gets new kernels and other new stuff, I don't see why xen should be excluded. Best all round though if it can be built to cohabit with earlier xen, so people can have both at once, maybe (given its nature) choosing which at boot time. That though will depend in part on related packages. This user would quite like the latest in F8, but I'm not sure I want to run rawhide. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From Dustin.Henning at prd-inc.com Mon Dec 10 13:59:11 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Mon, 10 Dec 2007 08:59:11 -0500 Subject: [Fedora-xen] (no subject) - (Win HVM not booting) In-Reply-To: References: Message-ID: <002601c83b34$d7147740$853d65c0$@Henning@prd-inc.com> Gary, I suspect that one of two things is causing you problem, but I?m not sure which. First, if you have not yet installed windows and need to boot to a Windows CD, then you actually need a virtual CD-ROM drive, so the following line needs changed: disk = [ 'phy:/dev/VGGuests/w2k3-001,ioemu:hda,w' ] This might work if you were using a real CD and had /dev/cdrom: disk = [ 'phy:/dev/VGGuests/w2k3-001,ioemu:hda,w' , 'phy:/dev/cdrom,hdc:cdrom,r' ] This might work if you were using an winxp.iso in /ISO: disk = [ 'phy:/dev/VGGuests/w2k3-001,ioemu:hda,w' , 'file:/iso/winxp.iso,hdc:cdrom,r' ] I say might because I don't use ioemu and you might need more than one '/' after 'file:' Also, once finished, you might set it up as follows: disk = [ 'phy:/dev/VGGuests/w2k3-001,ioemu:hda,w' , ',hdc:cdrom,r' ] This would just be so the vm has an empty cdrom drive. Also (and now I'm totally guessing), since you are using ioemu, instead of hdc:cdrom, it might be ioemu:cdrom or something in all of the above cases. The other problem could be that you have Windows installed and want to boot, then you just forgot to delete this line: boot="d" or change it as follows: boot="cd" The default will boot to c first, but after trying c and d (HD and CD, like the above), but it will try network or floppy (don't remember which) third. You may have gotten a direct reply or figured this out already, but I thought it should be posted to the group since the question was. Dustin From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Gary Catalano Sent: Friday, December 07, 2007 17:45 To: fedora-xen at redhat.com Subject: [Fedora-xen] (no subject) Greetings! ? I?m having a problem with fedora8 and Xen 3.1.0.? I?m trying to get Windows to run under Xen (I?ve been using these instructions http://www.xensource.com/files/xen_install_windows.pdf) and I get all the way to the last steps but when I start my virtual machine I get an error saying it can?t find a bootable drive: ? CDROM boot failure code : 0002 Boot from CD-Rom failed: could not read the boot disk FATAL: No bootable device. ? ? Here?s the .hvm I?m using to launch my virtual machine: ? ? #? -*- mode: python; -*- #=========================================================================== = # Python configuration setup for 'xm create'. # This script sets the parameters used when a domain is created using 'xm create'. # You use a separate script for each domain you want to create, or # you can set the parameters for the domain on the xm command line. #=========================================================================== = ? import os, re arch = os.uname()[4] if re.search('64', arch): ??? arch_libdir = 'lib64' else: ??? arch_libdir = 'lib' ? #--------------------------------------------------------------------------- - # Kernel image file. kernel = "/usr/lib/xen/boot/hvmloader" ? # The domain build function. HVM domain uses 'hvm'. builder='hvm' ? # Initial memory allocation (in megabytes) for the new domain. # # WARNING: Creating a domain with insufficient memory may cause out of #????????? memory errors. The domain needs enough memory to boot kernel #????????? and modules. Allocating less than 32MBs is not recommended. memory = 1024 ? # Shadow pagetable memory for the domain, in MB. # Should be at least 2KB per MB of domain memory, plus a few MB per vcpu. # shadow_memory = 8 ? # A name for your domain. All domains must have different names. name = "win2k3-001" ? # 128-bit UUID for the domain.? The default behavior is to generate a new UUID # on each call to 'xm create'. #uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9" ? #--------------------------------------------------------------------------- -- # The number of cpus guest platform has, default=1 #vcpus=1 ? # Enable/disable HVM guest PAE, default=1 (enabled) #pae=1 ? # Enable/disable HVM guest ACPI, default=1 (enabled) #acpi=1 ? # Enable/disable HVM APIC mode, default=1 (enabled) # Note that this option is ignored if vcpus > 1 #apic=1 ? # List of which CPUS this domain is allowed to use, default Xen picks #cpus = ""???????? # leave to Xen to pick #cpus = "0"??????? # all vcpus run on CPU0 #cpus = "0-3,5,^1" # run on cpus 0,2,3,5 ? # Optionally define mac and/or bridge for the network interfaces. # Random MACs are assigned if not given. #vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0, model=ne2k_pci' ] # type=ioemu specify the NIC is an ioemu device not netfront vif = [ 'type=ioemu, mac=00:16:3e:00:00:94, bridge=xenbr0' ] ? #--------------------------------------------------------------------------- - # Define the disk devices you want the domain to have access to, and # what you want them accessible as. # Each disk entry is of the form phy:UNAME,DEV,MODE # where UNAME is the device, DEV is the device name the domain will see, # and MODE is r for read-only, w for read-write. ? disk = [ 'phy:/dev/VGGuests/w2k3-001,ioemu:hda,w' ] #disk = [ 'file:/.img,hda,w', ',hdc:cdrom,r' ] ? #--------------------------------------------------------------------------- - # Configure the behaviour when a domain exits.? There are three 'reasons' # for a domain to stop: poweroff, reboot, and crash.? For each of these you # may specify: # #?? "destroy",??????? meaning that the domain is cleaned up as normal; #?? "restart",??????? meaning that a new domain is started in place of the old #???????????????????? one; #?? "preserve",?????? meaning that no clean-up is done until the domain is #???????????????????? manually destroyed (using xm destroy, for example); or #?? "rename-restart", meaning that the old domain is not cleaned up, but is #???????????????????? renamed and a new domain started in its place. # # The default is # #?? on_poweroff = 'destroy' #?? on_reboot?? = 'restart' #?? on_crash??? = 'restart' # # For backwards compatibility we also support the deprecated option restart # # restart = 'onreboot' means on_poweroff = 'destroy' #??????????????????????????? on_reboot?? = 'restart' #??????????????????????????? on_crash??? = 'destroy' # # restart = 'always'?? means on_poweroff = 'restart' #??????????????????????????? on_reboot?? = 'restart' #??????????????????????????? on_crash??? = 'restart' # # restart = 'never'??? means on_poweroff = 'destroy' #??????????????????????????? on_reboot?? = 'destroy' #??????????????????????????? on_crash??? = 'destroy' ? #on_poweroff = 'destroy' #on_reboot?? = 'restart' #on_crash??? = 'restart' ? #=========================================================================== = # New stuff device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm' ? #--------------------------------------------------------------------------- -- # Disk image for cdrom= "/tmp/win2k3srv.iso" ? #--------------------------------------------------------------------------- -- # boot on floppy (a), hard disk (c), Network (n) or CD-ROM (d) # default: hard disk, cd-rom, floppy boot="d" ? #--------------------------------------------------------------------------- -- #? write to temporary files instead of disk image files #snapshot=1 ? #--------------------------------------------------------------------------- - # enable SDL library for graphics, default = 0 sdl=1 ? #--------------------------------------------------------------------------- - # enable VNC library for graphics, default = 1 vnc=0 ? #--------------------------------------------------------------------------- - # address that should be listened on for the VNC server if vnc is set. # default is to use 'vnc-listen' setting from /etc/xen/xend-config.sxp #vnclisten="127.0.0.1" ? #--------------------------------------------------------------------------- - # set VNC display number, default = domid #vncdisplay=1 ? #--------------------------------------------------------------------------- - # try to find an unused port for the VNC server, default = 1 #vncunused=1 ? #--------------------------------------------------------------------------- - # enable spawning vncviewer for domain's console # (only valid when vnc=1), default = 0 #vncconsole=0 ? #--------------------------------------------------------------------------- - # set password for domain's VNC console # default is depents on vncpasswd in xend-config.sxp vncpasswd='' ? #--------------------------------------------------------------------------- - # no graphics, use serial port #nographic=0 ? #--------------------------------------------------------------------------- - # enable stdvga, default = 0 (use cirrus logic device model) #stdvga=0 ? #--------------------------------------------------------------------------- -- #?? serial port re-direct to pty deivce, /dev/pts/n ? # set password for domain's VNC console # default is depents on vncpasswd in xend-config.sxp vncpasswd='' ? #--------------------------------------------------------------------------- - # no graphics, use serial port #nographic=0 ? #--------------------------------------------------------------------------- - # enable stdvga, default = 0 (use cirrus logic device model) #stdvga=0 ? #--------------------------------------------------------------------------- -- #?? serial port re-direct to pty deivce, /dev/pts/n #?? then xm console or minicom can connect #serial='pty' ? ? #--------------------------------------------------------------------------- -- #?? Qemu Monitor, default is disable #?? Use ctrl-alt-2 to connect #monitor=1 ? ? #--------------------------------------------------------------------------- -- #?? enable sound card support, [sb16|es1370|all|..,..], default none #soundhw='sb16' ? ? #--------------------------------------------------------------------------- -- #??? set the real time clock to local time [default=0 i.e. set to utc] #localtime=1 ? ? #--------------------------------------------------------------------------- -- #??? set the real time clock offset in seconds [default=0 i.e. same as dom0] #rtc_timeoffset=3600 ? #--------------------------------------------------------------------------- -- #??? start in full screen #full-screen=1 ? ? #--------------------------------------------------------------------------- -- #?? Enable USB support (specific devices specified at runtime through the #?????????????????????? monitor window) #usb=1 ? #?? Enable USB mouse support (only enable one of the following, `mouse' for #???????????????????????????? PS/2 protocol relative mouse, `tablet' for #???????????????????????????? absolute mouse) #usbdevice='mouse' #usbdevice='tablet' ? #--------------------------------------------------------------------------- -- #?? Set keyboard layout, default is en-us keyboard. #keymap='ja' ? ? Any help would be appreciated. ? ? Gary Catalano IT Manager Cryptic Studios (408) 399 -1969 x150 (office) (650) 776-2500 (cell) www.crypticstudios.com ? ? ? From robin-lists at robinbowes.com Mon Dec 10 13:59:27 2007 From: robin-lists at robinbowes.com (Robin Bowes) Date: Mon, 10 Dec 2007 13:59:27 +0000 Subject: [Fedora-xen] Re: xen-unstable => 3.2, binary packages In-Reply-To: <18269.14554.836384.714726@mariner.uk.xensource.com> References: <18269.10903.495456.360011@mariner.uk.xensource.com> <475D2C86.7050401@herakles.homelinux.org> <18269.12955.151851.455070@mariner.uk.xensource.com> <20071210124721.GC15951@redhat.com> <18269.14554.836384.714726@mariner.uk.xensource.com> Message-ID: You might also like to read Daniel Berrange's post from 30th November entitled "FYI: The plan for Xen kernels in Fedora 9" R. From Ian.Jackson at eu.citrix.com Mon Dec 10 14:28:32 2007 From: Ian.Jackson at eu.citrix.com (Ian Jackson) Date: Mon, 10 Dec 2007 14:28:32 +0000 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages In-Reply-To: <475D4078.3030307@herakles.homelinux.org> References: <18269.10903.495456.360011@mariner.uk.xensource.com> <475D2C86.7050401@herakles.homelinux.org> <18269.12955.151851.455070@mariner.uk.xensource.com> <20071210124721.GC15951@redhat.com> <18269.14554.836384.714726@mariner.uk.xensource.com> <475D4078.3030307@herakles.homelinux.org> Message-ID: <18269.19728.810412.330655@mariner.uk.xensource.com> John Summerfield writes ("Re: [Fedora-xen] xen-unstable => 3.2, binary packages"): > I'm not an official part of the fedora project. I suggest you get the > latest from rawhide and work from that. I see. Right. I'll take a look. > I wouldn't regard fedora as a stable distribution; if stability is > important, CentOS is the place to go for cheapskates like me. Fedora > regularly gets new kernels and other new stuff, I don't see why xen > should be excluded. Fedora 8 gets substantial new stuff ? OK, well in that case if that's likely to happen quickly then that's good. > Best all round though if it can be built to cohabit with earlier xen, so > people can have both at once, maybe (given its nature) choosing which at > boot time. That though will depend in part on related packages. Yes. The Debian packages have an arrangement for doing this but they achieve it with a very invasive (and time-consuming to maintain) set of changes to the upstream Makefiles. We're not going to get that feature upstream in in 3.2 now, although I'll definitely be pushing it later (although probably not based exactly on the Debian patchset). > This user would quite like the latest in F8, but I'm not sure I want to > run rawhide. Right. Regards, Ian. From berrange at redhat.com Mon Dec 10 14:36:29 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 10 Dec 2007 14:36:29 +0000 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages In-Reply-To: <18269.10903.495456.360011@mariner.uk.xensource.com> References: <18269.10903.495456.360011@mariner.uk.xensource.com> Message-ID: <20071210143629.GB12703@redhat.com> On Mon, Dec 10, 2007 at 12:01:27PM +0000, Ian Jackson wrote: > We hope to be releasing upstream Xen 3.2 soon. As you'll know, we've > been in the habit of producing binary packages for our releases, > including for Fedora. > > It seemed to me that the best approach would be, where possible, to > use a distro's own packaging setup. That would be more likely to > generate packages which integrate well with the distro and behave more > like the distro's own Xen packaging arrangements. Personally I don't see the point in XenSource generating RPMs for Fedora since we already generate them ourselves, and it creates confusion about which RPMs should be used on Fedora. We will be syncing Fedora 9 (aka rawhide) to Xen 3.2.0 release candidates this week, with the plan that F 9 will ship the 3.2.0 hypervisor and userspace. That said I guess you may wish to generate 3.2.0 packages for old Fedora 7 and 8 releases, since we intend to keep the official Fedora packages for those release on the 3.1.x tree. For kernel side of things it is more complex in F9 world.... http://fedoraproject.org/wiki/Features/XenPvops http://www.redhat.com/archives/fedora-xen/2007-November/msg00106.html > I haven't looked at the FC6 srpm in detail yet but what would you > think about it if we were to generate our 3.2 binary rpms based on > that ? FC6 is dead, so skip that. Each Fedora release evolves the packaging to some degree, so for each release you intend to build binary packages for you should look at the corresponding src.rpm. This will help ensure that your packages integrate cleanly with each particular release. Current live supported releases are F7 and F8, and latest dev tree is F9. CVS for the Xen userspace package is here: http://cvs.fedoraproject.org/viewcvs/devel/xen/ While the kernel + hypervisor live here: http://cvs.fedoraproject.org/viewcvs/devel/kernel-xen-2.6/ In F9 the kernel bit will be changing - the hypervisor will likely move out into its own package - possibly part of the the main 'xen' package - its undecided at this stage. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Mon Dec 10 14:38:26 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 10 Dec 2007 14:38:26 +0000 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages In-Reply-To: <18269.12955.151851.455070@mariner.uk.xensource.com> References: <18269.10903.495456.360011@mariner.uk.xensource.com> <475D2C86.7050401@herakles.homelinux.org> <18269.12955.151851.455070@mariner.uk.xensource.com> Message-ID: <20071210143826.GC12703@redhat.com> On Mon, Dec 10, 2007 at 12:35:39PM +0000, Ian Jackson wrote: > John Summerfield writes ("Re: [Fedora-xen] xen-unstable => 3.2, binary packages"): > > I believe FC6 has just been terminated (support for Fedora ends soon > > after the second successor). > > Maybe I'm confused about version numbers or looking at the wrong > sites. I'm pretty new to the fedora world so I hope you'll forgive me > needing a bit of handholding. > > The sources I found were at > http://download.fedora.redhat.com/pub/fedora/linux/core/ > http://download.fedora.redhat.com/pub/fedora/linux/core/test/ > where the most recent are 6 and 6.93 (which I take to be a > work-in-progress 7). Ignore the download sites - go straight to the CVS repo I posted in the other thread since that ensures you get current master sources > I was somewhat puzzled by the .redhat.com domain but I wasn't able to > find anywhere more recent. Did I miss the relevant documentation ? I > found this: Don't worry about the domain - download.fedora.redhat.com is just one of the mirrors for download.fedoraproject.org Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Mon Dec 10 14:41:11 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 10 Dec 2007 14:41:11 +0000 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages In-Reply-To: <18269.14554.836384.714726@mariner.uk.xensource.com> References: <18269.10903.495456.360011@mariner.uk.xensource.com> <475D2C86.7050401@herakles.homelinux.org> <18269.12955.151851.455070@mariner.uk.xensource.com> <20071210124721.GC15951@redhat.com> <18269.14554.836384.714726@mariner.uk.xensource.com> Message-ID: <20071210144111.GD12703@redhat.com> On Mon, Dec 10, 2007 at 01:02:18PM +0000, Ian Jackson wrote: > Daniel Veillard writes ("Re: [Fedora-xen] xen-unstable => 3.2, binary packages"): > > 'Fedora Core' was renamed 'Fedora' between version 6 and 7, you > > will find the latests under the 'releases' subdir: > > Ahh! Thanks. > > > My own opinion about this is that since xen is packaged as part of > > Fedora, rebuilding a package on your side might be more of a problem > > than a solution (I mean for official release rather than for testing) > > since it's best to keep a coherency. If you have some problems with > > the packages as done in Fedora, it's better to get the issues (assuming > > any) solved, rather than putting a parallel set of packages, in the end > > avoiding users confusions helps everybody in my opinion. > > Right, I can absolutely see where you're coming from and obviously I > would prefer to let Fedora developers do the work too :-). > > The question is what users might be expected to do between the release > of Xen 3.2 and the time that Fedora releases its Xen 3.2 packages. > For most users of Xen it's a pretty critical and important package and > some kind of backport of Xen 3.2 onto their running system is likely > to be valuable to many. Xen users may often want to choose explicitly > to upgrade their Xen version. > > I don't know what Fedora's policy is about including new upstream > versions in updates, but I would think that most sensible policies > would generally frown on pushing a new hypervisor into an > already-released distribution. Since the userspace and hypervisor have a pretty tight ABI requirement we cannot do major Xen upgrades during the life of any single Fedora release. So, during the rawhide development cycles we track to the latest Xen major release, and then Fedora releases we track the minor bug fix release of Xen. So, Fedora 7 and 8 were released on Xen 3.1.0 and are now updated to Xen 3.1.2. We will not update Fedora 7 or 8 to Xen 3.2.0 because the 3.2.0 hypervisor is ABI incompatible with the 3.1.x userspace and vica-verca Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From Ian.Jackson at eu.citrix.com Mon Dec 10 14:52:22 2007 From: Ian.Jackson at eu.citrix.com (Ian Jackson) Date: Mon, 10 Dec 2007 14:52:22 +0000 Subject: [Fedora-xen] Re: xen-unstable => 3.2, binary packages In-Reply-To: References: <18269.10903.495456.360011@mariner.uk.xensource.com> <475D2C86.7050401@herakles.homelinux.org> <18269.12955.151851.455070@mariner.uk.xensource.com> <20071210124721.GC15951@redhat.com> <18269.14554.836384.714726@mariner.uk.xensource.com> Message-ID: <18269.21158.457474.600095@mariner.uk.xensource.com> Robin Bowes writes ("[Fedora-xen] Re: xen-unstable => 3.2, binary packages"): > You might also like to read Daniel Berrange's post from 30th November > entitled "FYI: The plan for Xen kernels in Fedora 9" Thanks. That's definitely interesting, particularly for our post-3.2 plans. Ian. From Ian.Jackson at eu.citrix.com Mon Dec 10 14:58:14 2007 From: Ian.Jackson at eu.citrix.com (Ian Jackson) Date: Mon, 10 Dec 2007 14:58:14 +0000 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages In-Reply-To: <20071210144111.GD12703@redhat.com> References: <18269.10903.495456.360011@mariner.uk.xensource.com> <475D2C86.7050401@herakles.homelinux.org> <18269.12955.151851.455070@mariner.uk.xensource.com> <20071210124721.GC15951@redhat.com> <18269.14554.836384.714726@mariner.uk.xensource.com> <20071210144111.GD12703@redhat.com> Message-ID: <18269.21510.667537.645655@mariner.uk.xensource.com> Daniel P. Berrange writes ("Re: [Fedora-xen] xen-unstable => 3.2, binary packages"): > On Mon, Dec 10, 2007 at 01:02:18PM +0000, Ian Jackson wrote: > > I don't know what Fedora's policy is about including new upstream > > versions in updates, but I would think that most sensible policies > > would generally frown on pushing a new hypervisor into an > > already-released distribution. > > Since the userspace and hypervisor have a pretty tight ABI requirement we > cannot do major Xen upgrades during the life of any single Fedora release. I don't necessarily disagree with your conclusion but I'm not sure this reasoning makes sense. Certainly there's an ABI compatibility requirement but all that means is that you would want to upgrade both the hypervisor and the dom0 toolstack together. > So, during the rawhide development cycles we track to the latest Xen major > release, and then Fedora releases we track the minor bug fix release of > Xen. So, Fedora 7 and 8 were released on Xen 3.1.0 and are now updated to > Xen 3.1.2. We will not update Fedora 7 or 8 to Xen 3.2.0 because the > 3.2.0 hypervisor is ABI incompatible with the 3.1.x userspace and vica-verca So do you think it would be worthwhile for Xensource to make binary packages of Xen 3.2 (both hypervisor and dom0 tools) backported to Fedora 8 ? Ian. From clalance at redhat.com Mon Dec 10 15:05:43 2007 From: clalance at redhat.com (Chris Lalancette) Date: Mon, 10 Dec 2007 10:05:43 -0500 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages In-Reply-To: <18269.21510.667537.645655@mariner.uk.xensource.com> References: <18269.10903.495456.360011@mariner.uk.xensource.com> <475D2C86.7050401@herakles.homelinux.org> <18269.12955.151851.455070@mariner.uk.xensource.com> <20071210124721.GC15951@redhat.com> <18269.14554.836384.714726@mariner.uk.xensource.com> <20071210144111.GD12703@redhat.com> <18269.21510.667537.645655@mariner.uk.xensource.com> Message-ID: <475D55C7.6030209@redhat.com> Ian Jackson wrote: > Daniel P. Berrange writes ("Re: [Fedora-xen] xen-unstable => 3.2, binary packages"): >> On Mon, Dec 10, 2007 at 01:02:18PM +0000, Ian Jackson wrote: >>> I don't know what Fedora's policy is about including new upstream >>> versions in updates, but I would think that most sensible policies >>> would generally frown on pushing a new hypervisor into an >>> already-released distribution. >> Since the userspace and hypervisor have a pretty tight ABI requirement we >> cannot do major Xen upgrades during the life of any single Fedora release. > > I don't necessarily disagree with your conclusion but I'm not sure > this reasoning makes sense. Certainly there's an ABI compatibility > requirement but all that means is that you would want to upgrade both > the hypervisor and the dom0 toolstack together. In theory, yes. However, the problem ends up being that we can't force people to reboot to the new kernel, so what happens in practice is that people update their kernel + userspace API, don't reboot, and then wonder why things don't work anymore. Chris Lalancette From berrange at redhat.com Mon Dec 10 15:07:25 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 10 Dec 2007 15:07:25 +0000 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages In-Reply-To: <18269.21510.667537.645655@mariner.uk.xensource.com> References: <18269.10903.495456.360011@mariner.uk.xensource.com> <475D2C86.7050401@herakles.homelinux.org> <18269.12955.151851.455070@mariner.uk.xensource.com> <20071210124721.GC15951@redhat.com> <18269.14554.836384.714726@mariner.uk.xensource.com> <20071210144111.GD12703@redhat.com> <18269.21510.667537.645655@mariner.uk.xensource.com> Message-ID: <20071210150724.GE12703@redhat.com> On Mon, Dec 10, 2007 at 02:58:14PM +0000, Ian Jackson wrote: > Daniel P. Berrange writes ("Re: [Fedora-xen] xen-unstable => 3.2, binary packages"): > > On Mon, Dec 10, 2007 at 01:02:18PM +0000, Ian Jackson wrote: > > > I don't know what Fedora's policy is about including new upstream > > > versions in updates, but I would think that most sensible policies > > > would generally frown on pushing a new hypervisor into an > > > already-released distribution. > > > > Since the userspace and hypervisor have a pretty tight ABI requirement we > > cannot do major Xen upgrades during the life of any single Fedora release. > > I don't necessarily disagree with your conclusion but I'm not sure > this reasoning makes sense. Certainly there's an ABI compatibility > requirement but all that means is that you would want to upgrade both > the hypervisor and the dom0 toolstack together. The problem comes because when you upgrade the userspace that takes effect immediately, but the hypervisor only takes effect upon reboot. So you have a time of incompatbility. In addition if the new hypervisor doesn't work out and you want to reboot to old version, then you're now incompatible with the userspace you upgraded. So while we could provide updates of both hypervisor and userspace it generates more support problems & bug reports that it is worth. So we decide to only update along the bugfix release trees. The release cycle of Fedora is fast enough (6 months) that there isn't very long to wait before the next Fedora release to get the newer Xen so there's no serious pressure to do major updates within one release. > > So, during the rawhide development cycles we track to the latest Xen major > > release, and then Fedora releases we track the minor bug fix release of > > Xen. So, Fedora 7 and 8 were released on Xen 3.1.0 and are now updated to > > Xen 3.1.2. We will not update Fedora 7 or 8 to Xen 3.2.0 because the > > 3.2.0 hypervisor is ABI incompatible with the 3.1.x userspace and vica-verca > > So do you think it would be worthwhile for Xensource to make binary > packages of Xen 3.2 (both hypervisor and dom0 tools) backported to > Fedora 8 ? There may well be people interested in that. We won't be doing it as part of the official Fedora xen packages, so if you wish to provide those updates you won't be duplicating effort & some people may find it useful. For sanity testing I'd recommend verifying the ability to run 'virt-install' 'virt-manager' & 'virsh' against your updated pacakges, since those are the primary virtualizatioln administration tools used in Fedora. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From Ian.Jackson at eu.citrix.com Mon Dec 10 15:24:08 2007 From: Ian.Jackson at eu.citrix.com (Ian Jackson) Date: Mon, 10 Dec 2007 15:24:08 +0000 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages In-Reply-To: <475D55C7.6030209@redhat.com> References: <18269.10903.495456.360011@mariner.uk.xensource.com> <475D2C86.7050401@herakles.homelinux.org> <18269.12955.151851.455070@mariner.uk.xensource.com> <20071210124721.GC15951@redhat.com> <18269.14554.836384.714726@mariner.uk.xensource.com> <20071210144111.GD12703@redhat.com> <18269.21510.667537.645655@mariner.uk.xensource.com> <475D55C7.6030209@redhat.com> Message-ID: <18269.23064.954858.484370@mariner.uk.xensource.com> Chris Lalancette writes ("Re: [Fedora-xen] xen-unstable => 3.2, binary packages"): > Ian Jackson wrote: > > I don't necessarily disagree with your conclusion but I'm not sure > > this reasoning makes sense. Certainly there's an ABI compatibility > > requirement but all that means is that you would want to upgrade both > > the hypervisor and the dom0 toolstack together. > > In theory, yes. However, the problem ends up being that we can't > force people to reboot to the new kernel, so what happens in > practice is that people update their kernel + userspace API, don't > reboot, and then wonder why things don't work anymore. Right. Having separate 3.2 packages available from a different place would avoid that problem because a user would have to go out of their way to choose to get it, rather than just taking the updates in the usual way. So would it be best for Xensource to build and publish those packages based on Fedora 8 srpms or do you have somewhere at Fedora for this kind of thing (effectively a backport) ? Ian. From Ian.Jackson at eu.citrix.com Mon Dec 10 15:24:55 2007 From: Ian.Jackson at eu.citrix.com (Ian Jackson) Date: Mon, 10 Dec 2007 15:24:55 +0000 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages In-Reply-To: <20071210150724.GE12703@redhat.com> References: <18269.10903.495456.360011@mariner.uk.xensource.com> <475D2C86.7050401@herakles.homelinux.org> <18269.12955.151851.455070@mariner.uk.xensource.com> <20071210124721.GC15951@redhat.com> <18269.14554.836384.714726@mariner.uk.xensource.com> <20071210144111.GD12703@redhat.com> <18269.21510.667537.645655@mariner.uk.xensource.com> <20071210150724.GE12703@redhat.com> Message-ID: <18269.23111.280027.350052@mariner.uk.xensource.com> Daniel P. Berrange writes ("Re: [Fedora-xen] xen-unstable => 3.2, binary packages"): > On Mon, Dec 10, 2007 at 02:58:14PM +0000, Ian Jackson wrote: > > So do you think it would be worthwhile for Xensource to make binary > > packages of Xen 3.2 (both hypervisor and dom0 tools) backported to > > Fedora 8 ? > > There may well be people interested in that. We won't be doing it as part of > the official Fedora xen packages, so if you wish to provide those updates > you won't be duplicating effort & some people may find it useful. Right. > For sanity testing I'd recommend verifying the ability to run 'virt-install' > 'virt-manager' & 'virsh' against your updated pacakges, since those are the > primary virtualizatioln administration tools used in Fedora. I'll see what I can do. Ian. From berrange at redhat.com Mon Dec 10 15:27:46 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 10 Dec 2007 15:27:46 +0000 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages In-Reply-To: <18269.23064.954858.484370@mariner.uk.xensource.com> References: <18269.10903.495456.360011@mariner.uk.xensource.com> <475D2C86.7050401@herakles.homelinux.org> <18269.12955.151851.455070@mariner.uk.xensource.com> <20071210124721.GC15951@redhat.com> <18269.14554.836384.714726@mariner.uk.xensource.com> <20071210144111.GD12703@redhat.com> <18269.21510.667537.645655@mariner.uk.xensource.com> <475D55C7.6030209@redhat.com> <18269.23064.954858.484370@mariner.uk.xensource.com> Message-ID: <20071210152746.GG12703@redhat.com> On Mon, Dec 10, 2007 at 03:24:08PM +0000, Ian Jackson wrote: > Chris Lalancette writes ("Re: [Fedora-xen] xen-unstable => 3.2, binary packages"): > > Ian Jackson wrote: > > > I don't necessarily disagree with your conclusion but I'm not sure > > > this reasoning makes sense. Certainly there's an ABI compatibility > > > requirement but all that means is that you would want to upgrade both > > > the hypervisor and the dom0 toolstack together. > > > > In theory, yes. However, the problem ends up being that we can't > > force people to reboot to the new kernel, so what happens in > > practice is that people update their kernel + userspace API, don't > > reboot, and then wonder why things don't work anymore. > > Right. > > Having separate 3.2 packages available from a different place would > avoid that problem because a user would have to go out of their way to > choose to get it, rather than just taking the updates in the usual > way. > > So would it be best for Xensource to build and publish those packages > based on Fedora 8 srpms or do you have somewhere at Fedora for this > kind of thing (effectively a backport) ? No, we don't have any separate backports repository, so hosting it on xen.org would be the best bet. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From debian at herakles.homelinux.org Mon Dec 10 23:00:18 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Tue, 11 Dec 2007 08:00:18 +0900 Subject: [Fedora-xen] xen-unstable => 3.2, binary packages In-Reply-To: <20071210152746.GG12703@redhat.com> References: <18269.10903.495456.360011@mariner.uk.xensource.com> <475D2C86.7050401@herakles.homelinux.org> <18269.12955.151851.455070@mariner.uk.xensource.com> <20071210124721.GC15951@redhat.com> <18269.14554.836384.714726@mariner.uk.xensource.com> <20071210144111.GD12703@redhat.com> <18269.21510.667537.645655@mariner.uk.xensource.com> <475D55C7.6030209@redhat.com> <18269.23064.954858.484370@mariner.uk.xensource.com> <20071210152746.GG12703@redhat.com> Message-ID: <475DC502.4010305@herakles.homelinux.org> Daniel P. Berrange wrote: >> >> Having separate 3.2 packages available from a different place would >> avoid that problem because a user would have to go out of their way to >> choose to get it, rather than just taking the updates in the usual >> way. >> >> So would it be best for Xensource to build and publish those packages >> based on Fedora 8 srpms or do you have somewhere at Fedora for this >> kind of thing (effectively a backport) ? > > No, we don't have any separate backports repository, so hosting it on xen.org > would be the best bet. I think it would be worth talking to the rpmforge folk; they may find a space for you and I think that would be more visible. I think they also have rpms for other distros, and I suppose that might be of interest. If you think RHEL (and its clone) users might be interested, CentOS has an area for RHEL-compatible packages. Some CentOS users might be more adventurous than RHEL users; they don't have support arrangements to break. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From kadafax at gmail.com Mon Dec 10 23:33:25 2007 From: kadafax at gmail.com (kfx) Date: Tue, 11 Dec 2007 00:33:25 +0100 Subject: [Fedora-xen] Network Problem after update 3.0 -> 3.1: blkback Message-ID: <475DCCC5.7030704@gmail.com> Hello, I have a big problem: Dom0 is centos5.1, domU are centos5.1. My setup is really simple, the only thing is that I give 3 nics to the domU so I use a modified network script (which has worked since january... since fedora 6): " #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 "$dir/network-bridge" "$@" vifnum=1 "$dir/network-bridge" "$@" vifnum=2 " So I have updated my xen dom0 from 3.0.3-rc5-8.1.15.el5 to 3.1.0-53.1.4.el5 (and kernel-xen 2.6.18-8.1.15.el5xen to 2.6.18-53.1.4.el5xen) and now my domU cant access the network. The interfaces are good in the domU, all seems to be ok but there are no connectivity at all (no arp entries). This message shows up on the dom0 each time I launch a domU: blkback: ring-ref 9, event-channel 7, protocol 1 (x86_64-abi) Do someone know what is happening ? this is very embarrassing after a simple upgrade... Hopefully I have another identical server (Centos 5.0 with 5.1 domUs) which is still in 3.0 but I cant stay not updated. Thanks for any help. xm info: host : host.foo.com release : 2.6.18-53.1.4.el5xen version : #1 SMP Fri Nov 30 01:21:23 EST 2007 machine : x86_64 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 2 cores_per_socket : 1 threads_per_core : 2 cpu_mhz : 2992 hw_caps : bfebfbff:20100800:00000000:00000180:0000641d total_memory : 4095 free_memory : 3246 xen_major : 3 xen_minor : 1 xen_extra : .0-53.1.4.el5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20070626 (Red Hat 4.1.2-14) cc_compile_by : mockbuild cc_compile_domain : cc_compile_date : Fri Nov 30 00:37:12 EST 2007 xend_config_format : 2 From Dustin.Henning at prd-inc.com Tue Dec 11 13:01:13 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Tue, 11 Dec 2007 08:01:13 -0500 Subject: [Fedora-xen] Network Problem after update 3.0 -> 3.1: blkback In-Reply-To: <475DCCC5.7030704@gmail.com> References: <475DCCC5.7030704@gmail.com> Message-ID: <000c01c83bf5$e8f36270$bada2750$@Henning@prd-inc.com> Since you are running Xen, I assume you are booting to 2.6.18-53.1.4.el5xen and not 3.1.0-53.1.4.el5. That said, have you tried booting to 2.6.18-8.1.15.el5xen (presumably still on the machine) to see if your VMs work then? If they don't, then some other package upgraded alongside the 3.1 kernel might be to blame, and I have certainly had problems going from CentOS X.Y to CentOS X.Z in the past (not Xen problems, but still). Since you will presumably still want to go to the newer kernel eventually, hopefully someone with more Xen/Linux experience can help you troubleshoot the actual problem, but if booting to a previous kernel makes you functional in the meantime, that certainly can't hurt. Another thought, assuming paravirt, is that you might need to change the kernel in your config to the new version of the DomU kernel for compatibility or something, but I don't know how likely that is to help with the problem. Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of kfx Sent: Monday, December 10, 2007 18:33 To: xen-users at lists.xensource.com; fedora-xen at redhat.com Subject: [Fedora-xen] Network Problem after update 3.0 -> 3.1: blkback Hello, I have a big problem: Dom0 is centos5.1, domU are centos5.1. My setup is really simple, the only thing is that I give 3 nics to the domU so I use a modified network script (which has worked since january... since fedora 6): " #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 "$dir/network-bridge" "$@" vifnum=1 "$dir/network-bridge" "$@" vifnum=2 " So I have updated my xen dom0 from 3.0.3-rc5-8.1.15.el5 to 3.1.0-53.1.4.el5 (and kernel-xen 2.6.18-8.1.15.el5xen to 2.6.18-53.1.4.el5xen) and now my domU cant access the network. The interfaces are good in the domU, all seems to be ok but there are no connectivity at all (no arp entries). This message shows up on the dom0 each time I launch a domU: blkback: ring-ref 9, event-channel 7, protocol 1 (x86_64-abi) Do someone know what is happening ? this is very embarrassing after a simple upgrade... Hopefully I have another identical server (Centos 5.0 with 5.1 domUs) which is still in 3.0 but I cant stay not updated. Thanks for any help. xm info: host : host.foo.com release : 2.6.18-53.1.4.el5xen version : #1 SMP Fri Nov 30 01:21:23 EST 2007 machine : x86_64 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 2 cores_per_socket : 1 threads_per_core : 2 cpu_mhz : 2992 hw_caps : bfebfbff:20100800:00000000:00000180:0000641d total_memory : 4095 free_memory : 3246 xen_major : 3 xen_minor : 1 xen_extra : .0-53.1.4.el5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20070626 (Red Hat 4.1.2-14) cc_compile_by : mockbuild cc_compile_domain : cc_compile_date : Fri Nov 30 00:37:12 EST 2007 xend_config_format : 2 -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From mnielsen at redhat.com Tue Dec 11 13:12:28 2007 From: mnielsen at redhat.com (Mark Nielsen) Date: Tue, 11 Dec 2007 08:12:28 -0500 Subject: [Fedora-xen] Network Problem after update 3.0 -> 3.1: blkback In-Reply-To: <475DCCC5.7030704@gmail.com> References: <475DCCC5.7030704@gmail.com> Message-ID: <475E8CBC.5040002@redhat.com> there were some changes in how networking is done going from 5.0 to 5.1. You may need to revisit the documentation for CentOS 5.1 kfx wrote: > Hello, > > I have a big problem: > Dom0 is centos5.1, domU are centos5.1. My setup is really simple, the > only thing is that I give 3 nics to the domU so I use a modified > network script (which has worked since january... since fedora 6): > " > #!/bin/sh > dir=$(dirname "$0") > "$dir/network-bridge" "$@" vifnum=0 > "$dir/network-bridge" "$@" vifnum=1 > "$dir/network-bridge" "$@" vifnum=2 > " > > So I have updated my xen dom0 from 3.0.3-rc5-8.1.15.el5 to > 3.1.0-53.1.4.el5 (and kernel-xen 2.6.18-8.1.15.el5xen to > 2.6.18-53.1.4.el5xen) and now my domU cant access the network. The > interfaces are good in the domU, all seems to be ok but there are no > connectivity at all (no arp entries). This message shows up on the > dom0 each time I launch a domU: > > blkback: ring-ref 9, event-channel 7, protocol 1 (x86_64-abi) > > Do someone know what is happening ? this is very embarrassing after a > simple upgrade... Hopefully I have another identical server (Centos > 5.0 with 5.1 domUs) which is still in 3.0 but I cant stay not updated. > > Thanks for any help. > > xm info: > host : host.foo.com > release : 2.6.18-53.1.4.el5xen > version : #1 SMP Fri Nov 30 01:21:23 EST 2007 > machine : x86_64 > nr_cpus : 4 > nr_nodes : 1 > sockets_per_node : 2 > cores_per_socket : 1 > threads_per_core : 2 > cpu_mhz : 2992 > hw_caps : bfebfbff:20100800:00000000:00000180:0000641d > total_memory : 4095 > free_memory : 3246 > xen_major : 3 > xen_minor : 1 > xen_extra : .0-53.1.4.el5 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > cc_compiler : gcc version 4.1.2 20070626 (Red Hat 4.1.2-14) > cc_compile_by : mockbuild > cc_compile_domain : > cc_compile_date : Fri Nov 30 00:37:12 EST 2007 > xend_config_format : 2 > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- A non-text attachment was scrubbed... Name: mnielsen.vcf Type: text/x-vcard Size: 177 bytes Desc: not available URL: From kadafax at gmail.com Tue Dec 11 13:33:36 2007 From: kadafax at gmail.com (kadafax) Date: Tue, 11 Dec 2007 14:33:36 +0100 Subject: [Fedora-xen] [SOLVED] Network Problem after update 3.0 -> 3.1: blkback In-Reply-To: <000c01c83bf5$e8f36270$bada2750$@Henning@prd-inc.com> References: <475DCCC5.7030704@gmail.com> <000c01c83bf5$e8f36270$bada2750$@Henning@prd-inc.com> Message-ID: <475E91B0.5020201@gmail.com> Thanks for your answer and sorry for top-posting. I've solved the problem: Before in xen 3.0 this was okay: vif = [ 'mac=aa:dd:rr:ee:ss:11', 'mac=aa:dd:rr:ee:ss:22, bridge=xenbr1'] The first vif was implicitly attached to bridge 0 (xenbr0). BUT now in 3.1 this doesn't work anymore, you must explicitly give the "bridge=xenbr0" argument: vif = [ 'mac=aa:dd:rr:ee:ss:11, bridge=xenbr0', 'mac=aa:dd:rr:ee:ss:22, bridge=xenbr1'] Dustin Henning wrote: > Since you are running Xen, I assume you are booting to > 2.6.18-53.1.4.el5xen and not 3.1.0-53.1.4.el5. That said, have you tried > booting to 2.6.18-8.1.15.el5xen (presumably still on the machine) to see if > your VMs work then? If they don't, then some other package upgraded > alongside the 3.1 kernel might be to blame, and I have certainly had > problems going from CentOS X.Y to CentOS X.Z in the past (not Xen problems, > but still). Since you will presumably still want to go to the newer kernel > eventually, hopefully someone with more Xen/Linux experience can help you > troubleshoot the actual problem, but if booting to a previous kernel makes > you functional in the meantime, that certainly can't hurt. Another thought, > assuming paravirt, is that you might need to change the kernel in your > config to the new version of the DomU kernel for compatibility or something, > but I don't know how likely that is to help with the problem. > Dustin > > -----Original Message----- > From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] > On Behalf Of kfx > Sent: Monday, December 10, 2007 18:33 > To: xen-users at lists.xensource.com; fedora-xen at redhat.com > Subject: [Fedora-xen] Network Problem after update 3.0 -> 3.1: blkback > > Hello, > > I have a big problem: > Dom0 is centos5.1, domU are centos5.1. My setup is really simple, the > only thing is that I give 3 nics to the domU so I use a modified network > script (which has worked since january... since fedora 6): > " > #!/bin/sh > dir=$(dirname "$0") > "$dir/network-bridge" "$@" vifnum=0 > "$dir/network-bridge" "$@" vifnum=1 > "$dir/network-bridge" "$@" vifnum=2 > " > > So I have updated my xen dom0 from 3.0.3-rc5-8.1.15.el5 to > 3.1.0-53.1.4.el5 (and kernel-xen 2.6.18-8.1.15.el5xen to > 2.6.18-53.1.4.el5xen) and now my domU cant access the network. The > interfaces are good in the domU, all seems to be ok but there are no > connectivity at all (no arp entries). This message shows up on the dom0 > each time I launch a domU: > > blkback: ring-ref 9, event-channel 7, protocol 1 (x86_64-abi) > > Do someone know what is happening ? this is very embarrassing after a > simple upgrade... Hopefully I have another identical server (Centos 5.0 > with 5.1 domUs) which is still in 3.0 but I cant stay not updated. > > Thanks for any help. > > xm info: > host : host.foo.com > release : 2.6.18-53.1.4.el5xen > version : #1 SMP Fri Nov 30 01:21:23 EST 2007 > machine : x86_64 > nr_cpus : 4 > nr_nodes : 1 > sockets_per_node : 2 > cores_per_socket : 1 > threads_per_core : 2 > cpu_mhz : 2992 > hw_caps : bfebfbff:20100800:00000000:00000180:0000641d > total_memory : 4095 > free_memory : 3246 > xen_major : 3 > xen_minor : 1 > xen_extra : .0-53.1.4.el5 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > cc_compiler : gcc version 4.1.2 20070626 (Red Hat 4.1.2-14) > cc_compile_by : mockbuild > cc_compile_domain : > cc_compile_date : Fri Nov 30 00:37:12 EST 2007 > xend_config_format : 2 > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > From rjones at redhat.com Tue Dec 11 14:10:28 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 11 Dec 2007 14:10:28 +0000 Subject: [Fedora-xen] Fedora 8 - Linux HVM Guest - PV Drivers In-Reply-To: References: Message-ID: <475E9A54.5010307@redhat.com> Emre Erenoglu wrote: > Hi, > > I'm trying to use a linux HVM guest (DomU) with Paravirtual drivers for > network and disk access on my updated Fedora 8 setup. > > In order to achieve this, I've downloaded the source package of appropriate > (same version) Xen Hypervisor from redhat website, then copied this source > to my DomU and compiled the unmodified_drivers folder following the steps > mentioned in the README file. > > Everything went fine and I got my xen-platform-pci, xen-baloon, xen-vnif and > xen-vbd (.ko) drivers. > > They modprobe fine, however, after some time, the DomU freezes up. > > Specifically, system freezes quicker (usually) with only vbd, and takes more > time to free with only xen-vnif loaded into memory. When I say only, > xen-platform-pci always loaded, but only the mentioned driver is netfront or > block-front, others are ioemu. > > xen-vnif also complains about a memory leak when it's rmmod 'ed. > > Shall I file a bug report? This sounds to me like a bug in those paravirt drivers, ie. file a bug with Xen. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From berrange at redhat.com Tue Dec 11 15:19:53 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 11 Dec 2007 15:19:53 +0000 Subject: [Fedora-xen] align fix for vmm-create.glade In-Reply-To: <1197021322.3277.9.camel@eagle.danny.cz> References: <1197021322.3277.9.camel@eagle.danny.cz> Message-ID: <20071211151953.GE17368@redhat.com> On Fri, Dec 07, 2007 at 10:55:22AM +0100, Dan Hor?k wrote: > Hello, > > in the virt-manager's new VM wizard there is a small alignment > inconsistency on the "Locating installation media" page for > paravirtualized machine. The second and third label are right aligned, > while the first (Install Media URL) is not. The included patch fixes > this issue. Thanks - I've applied the patch to the latest upstream code http://hg.et.redhat.com/virt/applications/virt-manager--devel?cs=e1f8d926c4a9 Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From gcatalano at crypticstudios.com Wed Dec 12 00:59:07 2007 From: gcatalano at crypticstudios.com (Gary Catalano) Date: Tue, 11 Dec 2007 16:59:07 -0800 Subject: [Fedora-xen] (no subject) - (Win HVM not booting) - FIXED! Message-ID: Thanks to everyone who sent me responses on my original issue. I got it resolved and it's humming along! =) I've been doing some benchmarking on my Windows-on-Xen instance and the numbers are pretty low for certain kinds of tests. Is there a general assumption about the performance that one can expect from a Xen-instance (i.e. 70% of the speed of a real system, etc.)? I've got my virtual machine running with 1 virtual cpu and 2gb of RAM, running windows xp. Many thanks! Gary Catalano -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.hellings at harcourt.com Wed Dec 12 00:59:17 2007 From: greg.hellings at harcourt.com (Greg Hellings) Date: Tue, 11 Dec 2007 16:59:17 -0800 Subject: [Fedora-xen] Problem installing a para 32 bit FC5 guest on a 32 bit FC7 domU Message-ID: I'm trying to install a 32 bit FC5 paravirt guest on a 32 bit FC7 domU and I'm getting the following error: libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\\n')") Everything I read says this should work. The hypervisor will allow me to install a 32 bit FC7 guest fine. The following is a cut and paste the commands I'm actually putting in and their output; [root at localhost ~]# virt-install --os-variant=fedora5 --name=dddev --location=http://167.208.15.27/FC5/i386 -f /var/lib/xen/images/dddev.img -p -r 3072 --vnc --vcpus=4 Starting install... libvir: Xen Daemon error : GET operation failed: Retrieving file fedora.cs 100% |=========================| 2.3 kB 00:00 Retrieving file vmlinuz.. 100% |=========================| 1.2 MB 00:00 Retrieving file initrd.im 100% |=========================| 2.0 MB 00:00 libvir: Xen Daemon error : GET operation failed: libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating domain: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\\n')") virDomainCreateLinux() failed POST operation failed: (xend.err "Error creating domain: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\\n')") Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start dddev'; otherwise, please restart your installation. Mon, 10 Dec 2007 08:50:01 ERROR virDomainCreateLinux() failed POST operation failed: (xend.err "Error creating domain: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\\n')") Traceback (most recent call last): File "/usr/sbin/virt-install", line 474, in main() File "/usr/sbin/virt-install", line 438, in main dom = guest.start_install(conscb,progresscb) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 708, in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 725, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib/python2.5/site-packages/libvirt.py", line 573, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err "Error creating domain: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32 not supported by xen kernel, sorry\\n')") [root at localhost ~]# uname -a Linux localhost.localdomain 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 EDT 2007 i686 i686 i386 GNU/Linux [root at localhost ~]# cat /proc/cpuinfo |egrep pae flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl cid cx16 xtpr flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl cid cx16 xtpr flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl cid cx16 xtpr flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl cid cx16 xtpr Does anyone have any idea what I'm doing wrong? Please help. -- Greg Hellings From berrange at redhat.com Wed Dec 12 01:15:49 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 12 Dec 2007 01:15:49 +0000 Subject: [Fedora-xen] Problem installing a para 32 bit FC5 guest on a 32 bit FC7 domU In-Reply-To: References: Message-ID: <20071212011549.GA14367@redhat.com> On Tue, Dec 11, 2007 at 04:59:17PM -0800, Greg Hellings wrote: > I'm trying to install a 32 bit FC5 paravirt guest on a 32 bit FC7 domU and > I'm getting the following error: > > libvir: Xen Daemon error : POST operation failed: (xend.err "Error creating > domain: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type > xen-3.0-x86_32 not supported by xen kernel, sorry\\n')") > > Everything I read says this should work. The hypervisor will allow me to > install a 32 bit FC7 guest fine. The following is a cut and paste the > commands I'm actually putting in and their output; Fedora Core 5 was non-PAE, Fedora Core 6 and later are PAE. You cannot run non-PAE 32-bit guests on a PAE host, hence why the hypervisor is telling you "guest type xen-3.0-x86_32 not supported by xen kernel" Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From sa212+fcxen at cyconix.com Fri Dec 14 09:23:48 2007 From: sa212+fcxen at cyconix.com (Evan Lavelle) Date: Fri, 14 Dec 2007 09:23:48 +0000 Subject: [Fedora-xen] inittab corrupted/serial console broken on Xen-ified kernel? Message-ID: <47624BA4.60609@cyconix.com> [this is a message that I sent to xen-users yesterday, but I guess this list may be better - this looks like a problem either in Xen, or in the packaging of 2.6.21-2952.fc8xen]. I've just installed Fedora 8 / xen-2.6.21 on a headless server, but I can't get a serial console login on the Xen version of the kernel. 1 - If I boot into 2.6.23.8-63.fc8, the serial console login works as expected 2 - If I boot into 2.6.21-2952.fc8xen instead, I get all the expected serial output up to the end of the boot process, but no login. When I boot into the xen kernel, inittab is modified, and the modification removes the agetty on ttyS0. If I compare the old inittab with the new inittab, I get: 46,47c46 < # co:2345:respawn:/sbin/agetty xvc0 96 9600 vt100-nav < co:12345:respawn:/sbin/agetty ttyS0 115200 vt100 --- > co:2345:respawn:/sbin/agetty xvc0 96 9600 vt100-nav In other words, a commented entry was uncommented, and the following line was deleted, which explains why I can't log in. This is so bizarre that it almost looks like it was done on purpose (was it ? :)) Anyone seen this? Any ideas? Thanks - Evan From notting at redhat.com Fri Dec 14 16:51:51 2007 From: notting at redhat.com (Bill Nottingham) Date: Fri, 14 Dec 2007 11:51:51 -0500 Subject: [Fedora-xen] inittab corrupted/serial console broken on Xen-ified kernel? In-Reply-To: <47624BA4.60609@cyconix.com> References: <47624BA4.60609@cyconix.com> Message-ID: <20071214165151.GA9852@nostromo.devel.redhat.com> Evan Lavelle (sa212+fcxen at cyconix.com) said: > 2 - If I boot into 2.6.21-2952.fc8xen instead, I get all the expected > serial output up to the end of the boot process, but no login. > > When I boot into the xen kernel, inittab is modified, and the > modification removes the agetty on ttyS0. If I compare the old inittab > with the new inittab, I get: > > 46,47c46 > < # co:2345:respawn:/sbin/agetty xvc0 96 9600 vt100-nav > < co:12345:respawn:/sbin/agetty ttyS0 115200 vt100 > --- > > co:2345:respawn:/sbin/agetty xvc0 96 9600 vt100-nav > > In other words, a commented entry was uncommented, and the following > line was deleted, which explains why I can't log in. This is so bizarre > that it almost looks like it was done on purpose (was it ? :)) > > Anyone seen this? Any ideas? Xen takes over the serial port; it's modifying the line to point to the xen console device. Bill From sa212+fcxen at cyconix.com Fri Dec 14 17:59:01 2007 From: sa212+fcxen at cyconix.com (Evan Lavelle) Date: Fri, 14 Dec 2007 17:59:01 +0000 Subject: [Fedora-xen] inittab corrupted/serial console broken on Xen-ified kernel? In-Reply-To: <20071214165151.GA9852@nostromo.devel.redhat.com> References: <47624BA4.60609@cyconix.com> <20071214165151.GA9852@nostromo.devel.redhat.com> Message-ID: <4762C465.3010404@cyconix.com> Bill Nottingham wrote: >> 46,47c46 >> < # co:2345:respawn:/sbin/agetty xvc0 96 9600 vt100-nav >> < co:12345:respawn:/sbin/agetty ttyS0 115200 vt100 >> --- >>> co:2345:respawn:/sbin/agetty xvc0 96 9600 vt100-nav >> In other words, a commented entry was uncommented, and the following >> line was deleted, which explains why I can't log in. This is so bizarre >> that it almost looks like it was done on purpose (was it ? :)) >> >> Anyone seen this? Any ideas? > > Xen takes over the serial port; it's modifying the line to point > to the xen console device. Interesting. So the "Serial Console Login configuration" in the manual (v3.0 User's Manual, p13) is wrong? The modified inittab is also incorrect; an error message appears on the serial output, and in the system logs, every 5 minutes ("Dec 14 17:52:35 thor init: Id "co" respawning too fast: disabled for 5 minutes"). How do I get a remote login over a serial line? Is this still possible? Thanks - Evan From notting at redhat.com Fri Dec 14 19:54:23 2007 From: notting at redhat.com (Bill Nottingham) Date: Fri, 14 Dec 2007 14:54:23 -0500 Subject: [Fedora-xen] inittab corrupted/serial console broken on Xen-ified kernel? In-Reply-To: <4762C465.3010404@cyconix.com> References: <47624BA4.60609@cyconix.com> <20071214165151.GA9852@nostromo.devel.redhat.com> <4762C465.3010404@cyconix.com> Message-ID: <20071214195423.GB3614@nostromo.devel.redhat.com> Evan Lavelle (sa212+fcxen at cyconix.com) said: >> Xen takes over the serial port; it's modifying the line to point >> to the xen console device. > > Interesting. So the "Serial Console Login configuration" in the manual > (v3.0 User's Manual, p13) is wrong? The modified inittab is also incorrect; > an error message appears on the serial output, and in the system logs, > every 5 minutes ("Dec 14 17:52:35 thor init: Id "co" respawning too fast: > disabled for 5 minutes"). Yeah, the extra '96' seems wrong. Can you file a bug against kudzu? > How do I get a remote login over a serial line? Is this still possible? How are you booting xen? What's the command line? Bill From debian at herakles.homelinux.org Mon Dec 17 08:43:20 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Mon, 17 Dec 2007 17:43:20 +0900 Subject: [Fedora-xen] kvm crash on f8 Message-ID: <476636A8.2070702@herakles.homelinux.org> I looked at some images in /var/lib/xen/images/ and since they have partition tables and look, to me, just like disks, I copied part of my hard disk to /var/lib/xen/images/WindowsXP.img The reason is that I want to try the Windows XP that came preinstalled, and copying /dev/sda for a length I calculated includes the entire /dev/sda1 partition seems a likely way to test it. These are the commands: dd if=/dev/sda of=/var/lib/xen/images/WindowsXP.img count=76597082 dd of=/var/lib/xen/images/WindowsXP.img seek=320072933376 bs=1 count=0 the second makes the disk image seem to be the proper size. I tried to start it like so: qemu-kvm -boot c -snapshot -m 256 -smp 2 -std-vga \ /var/lib/xen/images/WindowsXP.img and it choked: [root at potoroo ~]# qemu-kvm -boot c -snapshot -m 256 -smp 2 -std-vga /var/lib/xen/images/WindowsXP.img vram_pointer=0x2aaac0b5d000 exception 0 (0) rax 0000000000000022 rbx 0000000000007000 rcx 000000000064e165 rdx 0000000000000100 rsi 00000000ffff7c05 rdi 000000000008ffea rsp 0000000000001ffe rbp 0000000000000000 r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 0000000000000000 r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000 rip 000000000000fce2 rflags 00033206 cs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) ds 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) es 0800 (00008000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) ss 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) fs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) gs 0000 (00000000/0000ffff p 1 dpl 3 db 0 s 1 type 3 l 0 g 0 avl 0) tr 0000 (10850000/00002088 p 1 dpl 0 db 0 s 0 type b l 0 g 0 avl 0) ldt 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 0 type 2 l 0 g 0 avl 0) gdt fad00/30 idt 0/3ff cr0 60000010 cr2 0 cr3 0 cr4 0 cr8 0 efer 0 code: d5 03 e4 fc 24 44 d5 03 3e 00 d4 03 00 c0 f8 01 00 00 d5 03 --> f6 fc 24 44 d5 03 3f 00 d4 03 00 c0 f8 01 00 00 d5 03 08 fd 24 44 d5 03 40 00 d4 03 00 c0 Aborted [root at potoroo ~]# Here is the source disk: Disk /dev/sda: 320.0 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xd42ad42a Device Boot Start End Blocks Id System /dev/sda1 * 1 8669 69633711 7 HPFS/NTFS /dev/sda2 8671 9715 8393962+ 7 HPFS/NTFS /dev/sda3 9716 9728 104422+ 72 Unknown /dev/sda4 9729 38913 234428512+ 5 Extended /dev/sda5 9729 9741 104391 83 Linux /dev/sda6 9742 38913 234324058+ 8e Linux LVM [root at potoroo ~]# Partitions 2 and up are unimportant. fdisk on the disk image reports: Command (m for help): p Disk /var/lib/xen/images/WindowsXP.img: 0 MB, 0 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xd42ad42a Device Boot Start End Blocks Id System /var/lib/xen/images/WindowsXP.img1 * 1 8669 69633711 7 HPFS/NTFS /var/lib/xen/images/WindowsXP.img2 8671 9715 8393962+ 7 HPFS/NTFS /var/lib/xen/images/WindowsXP.img3 9716 9728 104422+ 72 Unknown /var/lib/xen/images/WindowsXP.img4 9729 38913 234428512+ 5 Extended Command (m for help): q but I had to specify the number of cylinder, 38913 but qemu-kvm rejects that nonsense. Is there a better way to do this? I really want to test running this Windows under Linux before allowing it to use the real disk. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From rjones at redhat.com Mon Dec 17 10:48:55 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 17 Dec 2007 10:48:55 +0000 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <476636A8.2070702@herakles.homelinux.org> References: <476636A8.2070702@herakles.homelinux.org> Message-ID: <47665417.6040207@redhat.com> John Summerfield wrote: > > I looked at some images in /var/lib/xen/images/ and since they have > partition tables and look, to me, just like disks, I copied part of my > hard disk to /var/lib/xen/images/WindowsXP.img > > The reason is that I want to try the Windows XP that came preinstalled, > and copying /dev/sda for a length I calculated includes the entire > /dev/sda1 partition seems a likely way to test it. > These are the commands: > dd if=/dev/sda of=/var/lib/xen/images/WindowsXP.img count=76597082 > dd of=/var/lib/xen/images/WindowsXP.img seek=320072933376 bs=1 count=0 I don't understand this second command. What's the input? Are you typing something on stdin (eg. ^D)? Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From darryl.bowler at yahoo.com Tue Dec 18 05:41:26 2007 From: darryl.bowler at yahoo.com (Darryl Bowler) Date: Mon, 17 Dec 2007 21:41:26 -0800 (PST) Subject: [Fedora-xen] AMD 64 X2 5200 - XEN only detects one core Message-ID: <402472.57590.qm@web58509.mail.re3.yahoo.com> I have an ACER AM3100-UD5200A which uses an AMD 64 X2 5200. Xen only detects one of two cores First I installed Fedora 8 + Xen that ships with the distro and found that only one core was detected when DOM0 booted. Out of frustration I decided to install CentOS 5.1 as a quick resolution to the problem, but found the same problem. checking /proc/cpuinfo there is only one core [root at dom0 lib]# more /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 67 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ stepping : 2 cpu MHz : 2593.594 cache size : 1024 KB physical id : 0 siblings : 1 core id : 0 cpu cores : 1 fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush mmx fxsr sse sse2 ht sysca ll nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm cr8_legacy bogomips : 6485.48 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management: ts fid vid ttp tm stc Heres dmesg from CentOS Bootdata ok (command line is ro root=/dev/VolGroup00/LogVol00 rhgb quiet) Linux version 2.6.18-53.el5xen (mockbuild at builder6.centos.org) (gcc version 4.1.2 20070626 (Red Hat 4.1.2 -14)) #1 SMP Mon Nov 12 02:46:57 EST 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 00000000a5250000 (usable) On node 0 totalpages: 676432 DMA zone: 676432 pages, LIFO batch:31 DMI 2.5 present. ACPI: RSDP (v002 ACRSYS ) @ 0x00000000000f80c0 ACPI: RSDT (v001 ACRSYS ACRPRDCT 0x42302e31 AWRD 0x00000000) @ 0x00000000affe3000 ACPI: FADT (v001 ACRSYS ACRPRDCT 0x42302e31 AWRD 0x00000000) @ 0x00000000affe3080 ACPI: SSDT (v001 PTLTD POWERNOW 0x00000001 LTP 0x00000001) @ 0x00000000affe7cc0 ACPI: HPET (v001 ACRSYS ACRPRDCT 0x42302e31 AWRD 0x00000098) @ 0x00000000affe7f80 ACPI: SLIC (v001 ACRSYS ACRPRDCT 0x42302e31 AWRD 0x00000020) @ 0x00000000affe7fc0 ACPI: MCFG (v001 ACRSYS ACRPRDCT 0x42302e31 AWRD 0x00000000) @ 0x00000000affe8140 ACPI: MADT (v001 ACRSYS ACRPRDCT 0x42302e31 AWRD 0x00000000) @ 0x00000000affe7c40 ACPI: DSDT (v001 ACRSYS ACRPRDCT 0x00001000 MSFT 0x03000000) @ 0x0000000000000000 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) IOAPIC[0]: apic_id 2, version 33, address 0xfec00000, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) ACPI: IRQ0 used by override.Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet Initializing CPU#0 PID hash table entries: 4096 (order: 12, 32768 bytes) Xen reported: 2593.594 MHz processor. Console: colour VGA+ 80x25 Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) Software IO TLB enabled: Aperture: 64 megabytes Kernel range: 0xffff880004847000 - 0xffff880008847000 PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Memory: 2563840k/2705728k available (2357k kernel code, 133072k reserved, 1326k data, 172k init) Calibrating delay using timer specific routine.. 6485.48 BogoMIPS (lpj=12970967) 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) CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 (SMP-)alternatives turned off ACPI: Core revision 20060707 Brought up 1 CPUs sizeof(vma)=168 bytes sizeof(page)=56 bytes sizeof(inode)=560 bytes sizeof(dentry)=216 bytes sizeof(ext3inode)=760 bytes sizeof(buffer_head)=96 bytes sizeof(skbuff)=240 bytes ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Setting APIC routing to xen Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at b4000000 (gap: b0000000:30000000) Built 1 zonelists. Total pages: 676432 [2007-12-18 01:59:05 xend.XendDomainInfo 3028] DEBUG (XendDomainInfo:756) Storing VM details: {'shadow_me mory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'on_poweroff': 'destr oy', 'name': 'Domain-0', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '2635', 'o n_crash': 'restart', 'maxmem': '2635'} ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs -------------- next part -------------- An HTML attachment was scrubbed... URL: From debian at herakles.homelinux.org Tue Dec 18 08:32:07 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Tue, 18 Dec 2007 17:32:07 +0900 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <47665417.6040207@redhat.com> References: <476636A8.2070702@herakles.homelinux.org> <47665417.6040207@redhat.com> Message-ID: <47678587.3040006@herakles.homelinux.org> Richard W.M. Jones wrote: > John Summerfield wrote: >> >> I looked at some images in /var/lib/xen/images/ and since they have >> partition tables and look, to me, just like disks, I copied part of my >> hard disk to /var/lib/xen/images/WindowsXP.img >> >> The reason is that I want to try the Windows XP that came >> preinstalled, and copying /dev/sda for a length I calculated includes >> the entire /dev/sda1 partition seems a likely way to test it. >> These are the commands: >> dd if=/dev/sda of=/var/lib/xen/images/WindowsXP.img count=76597082 >> dd of=/var/lib/xen/images/WindowsXP.img seek=320072933376 bs=1 count=0 > > I don't understand this second command. What's the input? Are you > typing something on stdin (eg. ^D)? count=0 -- doesn't read anything. Its purpose is to make a 320 Gbyte file, to match the source disk in size. It becomes a sparse file, effectively with lots of zeroes between the end of data copied with the first command. I've since edited the partition table with GNU Parted, it now looks like this: [root at potoroo ~]# parted /var/lib/xen/images/WindowsXP.img GNU Parted 1.8.6 Using /var/lib/xen/images/WindowsXP.img Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Model: (file) Disk /var/lib/xen/images/WindowsXP.img: 320GB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 32.3kB 71.3GB 71.3GB primary ntfs boot (parted) q [root at potoroo ~]# It approximates to how I've copied Windows systems around on real hardware from time to time. If I were to copy that file to a real disk and boot in real hardware, I would fully expect it to work. how embarrassing. I needed to copy about 80 Gbytes, and only copied half that. Worse, the boot sector has grub in it. The good news is that the system now boots grub sans menu. I typed in the necessary information to boot windows: chainloader (hd0,0)+1 boot and windows boots all the way to a BSOD and the stuff on the screen recommends "chkdsk /f." Hmm. Type to find a rescue system. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From lamont at gurulabs.com Tue Dec 18 08:55:21 2007 From: lamont at gurulabs.com (Lamont Peterson) Date: Tue, 18 Dec 2007 01:55:21 -0700 Subject: [Fedora-xen] AMD 64 X2 5200 - XEN only detects one core In-Reply-To: <402472.57590.qm@web58509.mail.re3.yahoo.com> References: <402472.57590.qm@web58509.mail.re3.yahoo.com> Message-ID: <200712180155.27059.lamont@gurulabs.com> On Monday 17 December 2007 10:41:26 pm Darryl Bowler wrote: > I have an ACER AM3100-UD5200A which uses an AMD 64 X2 5200. > > Xen only detects one of two cores Have you checked your BIOS config? I've heard of (though none of my multi-core systems have such) support in some BIOSes to enable/disable he 'extra' cores. -- Lamont Peterson Senior Instructor Guru Labs, L.C. [ http://www.GuruLabs.com/ ] NOTE: All messages from this email address should be digitally signed with my 0xDC0DD409 GPG key. It is available on the pgp.mit.edu keyserver as well as other keyservers that sync with MIT's. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. URL: From debian at herakles.homelinux.org Tue Dec 18 08:58:24 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Tue, 18 Dec 2007 17:58:24 +0900 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <47678587.3040006@herakles.homelinux.org> References: <476636A8.2070702@herakles.homelinux.org> <47665417.6040207@redhat.com> <47678587.3040006@herakles.homelinux.org> Message-ID: <47678BB0.8060905@herakles.homelinux.org> John Summerfield wrote: > Richard W.M. Jones wrote: >> John Summerfield wrote: > > The good news is that the system now boots grub sans menu. I typed in > the necessary information to boot windows: > chainloader (hd0,0)+1 > boot > > and windows boots all the way to a BSOD and the stuff on the screen > recommends "chkdsk /f." > > Hmm. Type to find a rescue system. fwiw same happens when I boot directly from the partition. Ideas welcome. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From darryl.bowler at yahoo.com Tue Dec 18 12:41:40 2007 From: darryl.bowler at yahoo.com (Darryl Bowler) Date: Tue, 18 Dec 2007 04:41:40 -0800 (PST) Subject: [Fedora-xen] AMD 64 X2 5200 - XEN only detects one core Message-ID: <319833.85552.qm@web58503.mail.re3.yahoo.com> I'm sure its not a bios setting, because when I boot into Vista it sees 2 cpus. ----- Original Message ---- From: Lamont Peterson To: Fedora Xen Sent: Tuesday, December 18, 2007 2:55:21 AM Subject: Re: [Fedora-xen] AMD 64 X2 5200 - XEN only detects one core On Monday 17 December 2007 10:41:26 pm Darryl Bowler wrote: > I have an ACER AM3100-UD5200A which uses an AMD 64 X2 5200. > > Xen only detects one of two cores Have you checked your BIOS config? I've heard of (though none of my multi-core systems have such) support in some BIOSes to enable/disable he 'extra' cores. -- Lamont Peterson Senior Instructor Guru Labs, L.C. [ http://www.GuruLabs.com/ ] NOTE: All messages from this email address should be digitally signed with my 0xDC0DD409 GPG key. It is available on the pgp.mit.edu keyserver as well as other keyservers that sync with MIT's. ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs -------------- next part -------------- An HTML attachment was scrubbed... URL: From turtlevelo at yahoo.com Wed Dec 19 09:29:01 2007 From: turtlevelo at yahoo.com (Costa Kavanides) Date: Wed, 19 Dec 2007 01:29:01 -0800 (PST) Subject: [Fedora-xen] Booting from floppy image Message-ID: <997617.64684.qm@web30312.mail.mud.yahoo.com> I read other entries about this subject but none explain why it is not possible to boot from a floppy image with XEN even though it is possible to do so with QEMU. Under dom0(2.6.21-6.fc7xen) I issue the command: qemu -boot a -fda -hda and I get to boot from the floppy image, whereas when I use xen whose config file contains 'file:,ioemu:fda:fda,r' or 'file:,fda,r' in the clause, I get the following message in the booting window: Booting from Floppy... Boot from Floppy failed: could not read the boot disk FATAL: No bootable device. The QEMU monitor shows that, while disk-C image was taken into consideration as such, the equivalent command for the floppy disk was completely ignored. Furthermore, it expects the floppy media to be present in the drive, as the following lines from the monitor's command show: hda: type=hd removable=0 file= ro=0 drv=raw hdb: type=cdrom removable=1 locked=0 [not inserted] fda: type=floppy removable=1 locked=0 [not inserted] Can somebody explain whether that behaviour was the result of a design choice or error? Let me emphasize the importance to have this feature. Thanks, Costa ____________________________________________________________________________________ Looking for last minute shopping deals? Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping From jlayton at redhat.com Wed Dec 19 14:55:14 2007 From: jlayton at redhat.com (Jeff Layton) Date: Wed, 19 Dec 2007 09:55:14 -0500 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <47678BB0.8060905@herakles.homelinux.org> References: <476636A8.2070702@herakles.homelinux.org> <47665417.6040207@redhat.com> <47678587.3040006@herakles.homelinux.org> <47678BB0.8060905@herakles.homelinux.org> Message-ID: <20071219095514.53a79830@barsoom.rdu.redhat.com> On Tue, 18 Dec 2007 17:58:24 +0900 John Summerfield wrote: > John Summerfield wrote: > > Richard W.M. Jones wrote: > >> John Summerfield wrote: > > > > > The good news is that the system now boots grub sans menu. I typed > > in the necessary information to boot windows: > > chainloader (hd0,0)+1 > > boot > > > > and windows boots all the way to a BSOD and the stuff on the screen > > recommends "chkdsk /f." > > > > Hmm. Type to find a rescue system. > > fwiw same happens when I boot directly from the partition. Ideas > welcome. > Windows is picky about hard disk drivers. The initial installation seems to install some drivers that get loaded early for your disk hardware. QEMU emulates a different type of hardware than what you probably have and so it can't find the root disk once the kernel has booted. If you change the main disk controller on a real machine, you'll probably have the same problem. I'm not aware of a way to fix that, unfortunately. I've generally had to install my windows images from scratch. -- Jeff Layton From aleksander.adamowski at altkom.pl Wed Dec 19 14:56:37 2007 From: aleksander.adamowski at altkom.pl (Aleksander Adamowski) Date: Wed, 19 Dec 2007 15:56:37 +0100 Subject: [Fedora-xen] virt-install hangs for fc6,7 In-Reply-To: <20071205012749.GF22561@redhat.com> References: <1196817664.13064.20.camel@x60s> <20071205012749.GF22561@redhat.com> Message-ID: <47693125.4040302@altkom.com.pl> Daniel P. Berrange wrote: > This is a bug in the F7 install kernel. When running in nographics mode > it still sends boot output to the graphical console instead o the text > console. > > Add '--append console=xvc0' to the virt-install args when doing a nographics > install of Fedora 7. FC6/F8 get the text mode stuff right - only F7 is > broken in this respect. > Couldn't find a bug in Red Hat Bugzilla for this - hasn't this bug been reported yet? I experienced the problem too on Fedora Core 7 on x86_64. -- Best Regards, Aleksander Adamowski GG#: 274614 ICQ UIN: 19780575 http://olo.org.pl -- Aleksander Adamowski Administrator system?w korporacyjnych; Instruktor Altkom Akademia S.A. http://www.altkom.pl Warszawa, ul. Ch?odna 51 kom. 0-601-318-080 S?d Rejonowy dla m.st. Warszawy w Warszawie, XII Wydzia? Gospodarczy Krajowego Rejestru S?dowego, KRS: 0000120139, NIP 118-00-08-391, Kapita? zak?adowy: 1000 000 PLN. Adres rejestrowy Firmy - ul. Stawki 2, 00-193 Warszawa. Niniejsza wiadomo?? zawiera informacje zastrze?one i stanowi?ce tajemnic? przedsi?biorstwa firmy Altkom Akademia S.A. Ujawnianie tych informacji osobom trzecim lub nieuprawnione wykorzystanie ich do w?asnych cel?w jest zabronione. Je?eli otrzymali?cie Pa?stwo niniejsz? wiadomo?? omy?kowo, prosimy o niezw?oczne skontaktowanie si? z nadawc? oraz usuni?cie wszelkich kopii niniejszej wiadomo?ci. This message contains proprietary information and trade secrets of Altkom Akademia S.A. company. Unauthorized use or disclosure of this information to any third party is prohibited. If you received this message by mistake, please contact the sender immediately and delete all copies of this message. From berrange at redhat.com Wed Dec 19 14:59:30 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 19 Dec 2007 14:59:30 +0000 Subject: [Fedora-xen] virt-install hangs for fc6,7 In-Reply-To: <47693125.4040302@altkom.com.pl> References: <1196817664.13064.20.camel@x60s> <20071205012749.GF22561@redhat.com> <47693125.4040302@altkom.com.pl> Message-ID: <20071219145930.GA2973@redhat.com> On Wed, Dec 19, 2007 at 03:56:37PM +0100, Aleksander Adamowski wrote: > Daniel P. Berrange wrote: > >This is a bug in the F7 install kernel. When running in nographics mode > >it still sends boot output to the graphical console instead o the text > >console. > > > >Add '--append console=xvc0' to the virt-install args when doing a > >nographics > >install of Fedora 7. FC6/F8 get the text mode stuff right - only F7 is > >broken in this respect. > > > > Couldn't find a bug in Red Hat Bugzilla for this - hasn't this bug been > reported yet? I experienced the problem too on Fedora Core 7 on x86_64. There no point filing a BZ. It is impossible to fix it, since the problem is in the images/xen/vmlinuz from the master install tree. We never change the install kernels post-release so there's no way to fix it in F7. The only option is to append that arg, or use F8 instead. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From aleksander.adamowski at altkom.pl Wed Dec 19 15:05:15 2007 From: aleksander.adamowski at altkom.pl (Aleksander Adamowski) Date: Wed, 19 Dec 2007 16:05:15 +0100 Subject: [Fedora-xen] virt-install hangs for fc6,7 In-Reply-To: <20071205012749.GF22561@redhat.com> References: <1196817664.13064.20.camel@x60s> <20071205012749.GF22561@redhat.com> Message-ID: <4769332B.3010607@altkom.com.pl> Daniel P. Berrange wrote: > Add '--append console=xvc0' to the virt-install args when doing a nographics > install of Fedora 7. "virt-install: error: no such option: --append" You probably meant adding '-x console=xvc0'. -- Best Regards, Aleksander Adamowski GG#: 274614 ICQ UIN: 19780575 http://olo.org.pl -- Aleksander Adamowski Administrator system?w korporacyjnych; Instruktor Altkom Akademia S.A. http://www.altkom.pl Warszawa, ul. Ch?odna 51 kom. 0-601-318-080 S?d Rejonowy dla m.st. Warszawy w Warszawie, XII Wydzia? Gospodarczy Krajowego Rejestru S?dowego, KRS: 0000120139, NIP 118-00-08-391, Kapita? zak?adowy: 1000 000 PLN. Adres rejestrowy Firmy - ul. Stawki 2, 00-193 Warszawa. Niniejsza wiadomo?? zawiera informacje zastrze?one i stanowi?ce tajemnic? przedsi?biorstwa firmy Altkom Akademia S.A. Ujawnianie tych informacji osobom trzecim lub nieuprawnione wykorzystanie ich do w?asnych cel?w jest zabronione. Je?eli otrzymali?cie Pa?stwo niniejsz? wiadomo?? omy?kowo, prosimy o niezw?oczne skontaktowanie si? z nadawc? oraz usuni?cie wszelkich kopii niniejszej wiadomo?ci. This message contains proprietary information and trade secrets of Altkom Akademia S.A. company. Unauthorized use or disclosure of this information to any third party is prohibited. If you received this message by mistake, please contact the sender immediately and delete all copies of this message. From Dustin.Henning at prd-inc.com Wed Dec 19 15:07:14 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Wed, 19 Dec 2007 10:07:14 -0500 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <20071219095514.53a79830@barsoom.rdu.redhat.com> References: <476636A8.2070702@herakles.homelinux.org> <47665417.6040207@redhat.com> <47678587.3040006@herakles.homelinux.org> <47678BB0.8060905@herakles.homelinux.org> <20071219095514.53a79830@barsoom.rdu.redhat.com> Message-ID: <000901c84250$d68311b0$83893510$@Henning@prd-inc.com> If you have this system set up how you want and it required a lot of configuration, one option might be to do a full backup (including system state) of the configured system, then install windows on an hvm and do a full restore, I have read that this is a good p2v (and vice versa) method for Windows, as the system state backup apparently doesn't replace drivers. I have never tried it, so I can't tell you the caveats, but depending on your situation, it might be worth a shot (I have read similar articles about moving from one piece of hardware to another). Also, in Windows, all drivers are loaded the same way, so if the right driver can be installed from the initial hardware configuration, Windows will boot in the new configuration. I have done this many times to change HD controllers in the same system for performance reasons (going to a separate IDE controller was a big performance boost on old IDE computers). I never had much luck doing that, though, unless I could put the hardware in to install the drivers for, that may mean that it won't automatically use a driver just because it is there, it has to be associated with the specific piece of hardware. Nonetheless, depending on how much time you want to spend, you might have some options. Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Jeff Layton Sent: Wednesday, December 19, 2007 09:55 To: John Summerfield Cc: Fedora Xen Subject: Re: [Fedora-xen] kvm crash on f8 On Tue, 18 Dec 2007 17:58:24 +0900 John Summerfield wrote: > John Summerfield wrote: > > Richard W.M. Jones wrote: > >> John Summerfield wrote: > > > > > The good news is that the system now boots grub sans menu. I typed > > in the necessary information to boot windows: > > chainloader (hd0,0)+1 > > boot > > > > and windows boots all the way to a BSOD and the stuff on the screen > > recommends "chkdsk /f." > > > > Hmm. Type to find a rescue system. > > fwiw same happens when I boot directly from the partition. Ideas > welcome. > Windows is picky about hard disk drivers. The initial installation seems to install some drivers that get loaded early for your disk hardware. QEMU emulates a different type of hardware than what you probably have and so it can't find the root disk once the kernel has booted. If you change the main disk controller on a real machine, you'll probably have the same problem. I'm not aware of a way to fix that, unfortunately. I've generally had to install my windows images from scratch. -- Jeff Layton -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From paul.boin at arl.army.mil Wed Dec 19 16:17:40 2007 From: paul.boin at arl.army.mil (Boin, Paul (Cont, ARL/CISD)) Date: Wed, 19 Dec 2007 11:17:40 -0500 Subject: [Fedora-xen] Single User Mode Message-ID: <47694424.6030006@arl.army.mil> I'm testing some kickstarts on xen. Everything's OK, but I'm stuck on one part. I've researched my question well, and I'm just not getting one piece. The pw set during install is intentionally bogus. I now want to go to my grub menu, go single-user and set it via 'passwd'. ( Which we typically do on non-virtual installations. ) On RHEL, where I have much more experience, I can just "xm create -c mydomain" to get an immediate attach and see the grub menu. It looks like this newer xen/libvirt on FC8 is setup to use virsh, and it has the XML configs over in /var/lib/xend/domains/, etc. So, how do I get to the grub menu using virsh, since xm seems to want to work with plaintext configs in /etc/xen, which I do not have? Or, how would you suggest I change the bogus root pw, that no one knows? Thanks and have a fine day. # rpm -q xen xen-3.1.0-13.fc8 # rpm -q libvirt libvirt-0.3.3-2.fc8 From debian at herakles.homelinux.org Thu Dec 20 00:57:24 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Thu, 20 Dec 2007 09:57:24 +0900 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <000901c84250$d68311b0$83893510$@Henning@prd-inc.com> References: <476636A8.2070702@herakles.homelinux.org> <47665417.6040207@redhat.com> <47678587.3040006@herakles.homelinux.org> <47678BB0.8060905@herakles.homelinux.org> <20071219095514.53a79830@barsoom.rdu.redhat.com> <000901c84250$d68311b0$83893510$@Henning@prd-inc.com> Message-ID: <4769BDF4.3080501@herakles.homelinux.org> Dustin Henning wrote: > If you have this system set up how you want and it required a lot of > configuration, one option might be to do a full backup (including system > state) of the configured system, then install windows on an hvm and do a > full restore, I have read that this is a good p2v (and vice versa) method > for Windows, as the system state backup apparently doesn't replace drivers. > I have never tried it, so I can't tell you the caveats, but depending on > your situation, it might be worth a shot (I have read similar articles about > moving from one piece of hardware to another). Also, in Windows, all > drivers are loaded the same way, so if the right driver can be installed > from the initial hardware configuration, Windows will boot in the new > configuration. I have done this many times to change HD controllers in the > same system for performance reasons (going to a separate IDE controller was > a big performance boost on old IDE computers). I never had much luck doing > that, though, unless I could put the hardware in to install the drivers for, > that may mean that it won't automatically use a driver just because it is > there, it has to be associated with the specific piece of hardware. > Nonetheless, depending on how much time you want to spend, you might have > some options. > Dustin and now I think it's Jeff. > > Windows is picky about hard disk drivers. The initial installation > seems to install some drivers that get loaded early for your disk > hardware. QEMU emulates a different type of hardware than what you > probably have and so it can't find the root disk once the kernel has > booted. If you change the main disk controller on a real machine, you'll > probably have the same problem. > > I'm not aware of a way to fix that, unfortunately. I've generally had to > install my windows images from scratch. > This is a trial of what I really want to do, which includes running Windows 2003 Server and a domain of Windows XP Professional clients (not many - likely 2-3 of them) for testing and education, and ideally a Windows XP system which is to be moved to different hardware anyway, but preferably without being reinstalled. Installing drivers is okay, using xen is fine, I tried kvm because it doesn't require a special kernel. I'm a bit dismayed to see mentions of FX chipset and piix3 in the qemu-kvm doc (I remember piix4, but piix3?). Surely that won't work for Vista. I did try an install of my Windows on the HP dc7700p using the ISO in its recovery partition, but I quit as soon as it asked me for the other CD as evidence I'm licenced[1]. I suspect this version is locked to my BIOS and so doesn't require activation, so it's probably not going to work at all, but enquiring minds need to know. The backup/restore procedure might work, it's supposed to preserve user data, but if it's supposed to clean out malware then it should not. I might let it sit though, and see whether someone has another idea:-) Merry Xmas all. [1] Producing the CD isn't a problem, sticking it in the imaginary CD drive was, and while I think the needed ISO is right there too, I especially don't know how to shuffle virtual CDs. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From yabraham2 at gmail.com Fri Dec 21 00:40:01 2007 From: yabraham2 at gmail.com (yonas Abraham) Date: Thu, 20 Dec 2007 19:40:01 -0500 Subject: [Fedora-xen] Starting system message bus take very long Message-ID: <47324ed80712201640v7b1a7e7xd2a59f1beadcfc1d@mail.gmail.com> starting f8 guest on f8 host , takes very long time (like 10 min) after it printed Starting system message bus It continue with out any error message after that. any idea? /yonas From berrange at redhat.com Fri Dec 21 00:44:46 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 21 Dec 2007 00:44:46 +0000 Subject: [Fedora-xen] Starting system message bus take very long In-Reply-To: <47324ed80712201640v7b1a7e7xd2a59f1beadcfc1d@mail.gmail.com> References: <47324ed80712201640v7b1a7e7xd2a59f1beadcfc1d@mail.gmail.com> Message-ID: <20071221004446.GG4939@redhat.com> On Thu, Dec 20, 2007 at 07:40:01PM -0500, yonas Abraham wrote: > starting f8 guest on f8 host , takes very long time (like 10 min) > after it printed > > Starting system message bus > > It continue with out any error message after that. > > any idea? This doesn't sound like anything Xen related. I suggest file a bug against the appropriate application Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From shashank.rachamalla at gmail.com Fri Dec 21 01:53:56 2007 From: shashank.rachamalla at gmail.com (shashank rachamalla) Date: Fri, 21 Dec 2007 07:23:56 +0530 Subject: [Fedora-xen] problem booting xen-kernel on fedora core 6 plz help!! Message-ID: I installed fedora core 6 by turning acpi off and fc6 (kernel without xen) boots properly but the xen-kernel is not booting. i get the message "unknown interrupt" while udev is starting. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ian.Jackson at eu.citrix.com Fri Dec 21 16:30:36 2007 From: Ian.Jackson at eu.citrix.com (Ian Jackson) Date: Fri, 21 Dec 2007 16:30:36 +0000 Subject: [Fedora-xen] Preview Xen 3.2 rc* packages Message-ID: <18283.59948.237498.121335@mariner.uk.xensource.com> I've merged the patches and so on from xen-3.1.0-13.fc8.src.rpm with a recent xen-unstable tip (16635:9d447ba0c99a). With a bit of work I have managed to get a set of packages which appear to be able to work at least in my simple `does this work at all' test. I'm mentioning it here so that you can have a look at what I've done and comment on it. We'll probably be making official upstream rpms for Fedora 8. Please send me feedback either here on-list or privately. Most of the patches from -13.fc8 have been incorporated upstream so I just deleted them from my srpm. A couple of these patches I've included I have also submitted upstream and they'll be in xen-unstable.hg soon if they're not already. There were two patches that looked like they would be useful upstream: xen-qemu-bootmenu.patch pygrub-manykernels.patch but I wasn't able to find clear attribution for the source of this code. Xen upstream operates a `Signed-off-by' protocol to ensure that we don't get bitten by copyright problems. Where should I look to try to find the authors/contributors to check on the copyright status ? In my package I have included the hypervisor in the xen-*.rpm rather than making a kernel package too. This is more in line with practice upstream. The new hypervisor seems to work for me with the 2.6.21-2952.fc8xen kernel. I have not included xen-net-bridge.patch which seemed quite a surprising set of changes to me. I was rather puzzled by the part of xen-initscript.patch which removes most of xend's startup code. I agree that xend's arrangements are not entirely ideal but is there really much to be gained by making that changes, which obviously makes the patchset much more fragile ? You can find the actual files here: http://www.chiark.greenend.org.uk/~ijackson/xen-3.2rc-fedora8/ THESE PACKAGES SHOULD NOT BE USED FOR PRODUCTION - they're previews, and Xen 3.2 is still unreleased and in need of more testing. Please check the SHA256's before installing them: 1209de4470cf505113e684fe8f1f5c13faad40ad8eb4c456e8741eddbe5b6254 xen-3.1.9-0.fc8.i386.rpm 18ad4f2b35c6918ab3070e43d238487f6cbaf10a682cfc90b1d11c4640957395 xen-3.1.9-0.fc8.src.rpm 428da514ccf9064244017a5068c399ec0e7c5816c2d2f4ded17e9af031d50759 xen-debuginfo-3.1.9-0.fc8.i386.rpm 98305f6fc7de7c965b7cb0426a0bed4cb977394a8fce1cedf6fb35d6780df0c5 xen-devel-3.1.9-0.fc8.i386.rpm f45e0ed7ff40bf7ef4e8cd236f639060caba27d3573003745bfa37f3ae0f4943 xen-libs-3.1.9-0.fc8.i386.rpm Regards, Ian. From berrange at redhat.com Fri Dec 21 16:45:47 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 21 Dec 2007 16:45:47 +0000 Subject: [Fedora-xen] Preview Xen 3.2 rc* packages In-Reply-To: <18283.59948.237498.121335@mariner.uk.xensource.com> References: <18283.59948.237498.121335@mariner.uk.xensource.com> Message-ID: <20071221164547.GA25635@redhat.com> On Fri, Dec 21, 2007 at 04:30:36PM +0000, Ian Jackson wrote: > I've merged the patches and so on from xen-3.1.0-13.fc8.src.rpm with a > recent xen-unstable tip (16635:9d447ba0c99a). With a bit of work I > have managed to get a set of packages which appear to be able to work > at least in my simple `does this work at all' test. > > I'm mentioning it here so that you can have a look at what I've done > and comment on it. We'll probably be making official upstream rpms > for Fedora 8. Please send me feedback either here on-list or > privately. > > Most of the patches from -13.fc8 have been incorporated upstream so I > just deleted them from my srpm. A couple of these patches I've > included I have also submitted upstream and they'll be in > xen-unstable.hg soon if they're not already. > > There were two patches that looked like they would be useful upstream: > xen-qemu-bootmenu.patch > pygrub-manykernels.patch > but I wasn't able to find clear attribution for the source of this > code. Xen upstream operates a `Signed-off-by' protocol to ensure that > we don't get bitten by copyright problems. Where should I look to try > to find the authors/contributors to check on the copyright status ? There were both written by Jeremy, so copyright Red Hat. I'll get them posted upstream. > In my package I have included the hypervisor in the xen-*.rpm rather > than making a kernel package too. This is more in line with practice > upstream. The new hypervisor seems to work for me with the > 2.6.21-2952.fc8xen kernel. We are going to be putting the hypervisor in a 'xen-hypervisor' package for F9, so it might be work folowing same practice. > I have not included xen-net-bridge.patch which seemed quite a > surprising set of changes to me. Most of those, if not all, should be upstream in 3.2.0 > I was rather puzzled by the part of xen-initscript.patch which removes > most of xend's startup code. I agree that xend's arrangements are not > entirely ideal but is there really much to be gained by making that > changes, which obviously makes the patchset much more fragile ? The reason for this is that the upstream changset did not play nicely with standard Fedora init script good practice. IMHO duplicating stuff that is already provided by standard initscript shell functions in python is a bad idea, hence we killed it. I did post these changes upstream for review at the time by they weren't incporated. Should be in the archives somewhere.... > Please check the SHA256's before installing them: > 1209de4470cf505113e684fe8f1f5c13faad40ad8eb4c456e8741eddbe5b6254 xen-3.1.9-0.fc8.i386.rpm > 18ad4f2b35c6918ab3070e43d238487f6cbaf10a682cfc90b1d11c4640957395 xen-3.1.9-0.fc8.src.rpm > 428da514ccf9064244017a5068c399ec0e7c5816c2d2f4ded17e9af031d50759 xen-debuginfo-3.1.9-0.fc8.i386.rpm > 98305f6fc7de7c965b7cb0426a0bed4cb977394a8fce1cedf6fb35d6780df0c5 xen-devel-3.1.9-0.fc8.i386.rpm > f45e0ed7ff40bf7ef4e8cd236f639060caba27d3573003745bfa37f3ae0f4943 xen-libs-3.1.9-0.fc8.i386.rpm FYI, you might want to check the rawhide spec file - for pre-release builds we are standardizing on a numbering format of: 'xen-3.2.0-0.fc8.rc3.dev16606' NB, the leading the '0' in the release number ensures the upgrade path to the final official 3.2.0-1.fc9 package. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Fri Dec 21 16:51:34 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 21 Dec 2007 16:51:34 +0000 Subject: [Fedora-xen] Preview Xen 3.2 rc* packages In-Reply-To: <20071221164547.GA25635@redhat.com> References: <18283.59948.237498.121335@mariner.uk.xensource.com> <20071221164547.GA25635@redhat.com> Message-ID: <20071221165134.GA27601@redhat.com> On Fri, Dec 21, 2007 at 04:45:47PM +0000, Daniel P. Berrange wrote: > On Fri, Dec 21, 2007 at 04:30:36PM +0000, Ian Jackson wrote: > > I've merged the patches and so on from xen-3.1.0-13.fc8.src.rpm with a > > recent xen-unstable tip (16635:9d447ba0c99a). With a bit of work I > > have managed to get a set of packages which appear to be able to work > > at least in my simple `does this work at all' test. > > > > I'm mentioning it here so that you can have a look at what I've done > > and comment on it. We'll probably be making official upstream rpms > > for Fedora 8. Please send me feedback either here on-list or > > privately. FYI, my 3.2.0 RPMs for Fedora 9 are currently in a branch of Fedora CVS called 'private-berrange-xen-unstable' viewable here: http://cvs.fedoraproject.org/viewcvs/devel/xen/?only_with_tag=private-berrange-xen-unstable Or checkout with cvs -d :pserver:anonymous at cvs.fedoraproject.org:/cvs/pkgs checkout -r private-berrange-xen-unstable xen/devel I've not decided yet on wether to name the hypervisor '/boot/xen.gz' or include a full version '/boot/xen-3.2.0.gz', or version + release '/boot/xen-3.2.0-1.fc9'. I think i'll probably go for 'xen-3.2.0.gz' Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Fri Dec 21 17:23:05 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 21 Dec 2007 17:23:05 +0000 Subject: [Fedora-xen] Preview Xen 3.2 rc* packages In-Reply-To: <18283.59948.237498.121335@mariner.uk.xensource.com> References: <18283.59948.237498.121335@mariner.uk.xensource.com> Message-ID: <20071221172305.GC27601@redhat.com> On Fri, Dec 21, 2007 at 04:30:36PM +0000, Ian Jackson wrote: > I've merged the patches and so on from xen-3.1.0-13.fc8.src.rpm with a > recent xen-unstable tip (16635:9d447ba0c99a). With a bit of work I > have managed to get a set of packages which appear to be able to work > at least in my simple `does this work at all' test. > Please check the SHA256's before installing them: > 1209de4470cf505113e684fe8f1f5c13faad40ad8eb4c456e8741eddbe5b6254 xen-3.1.9-0.fc8.i386.rpm > 18ad4f2b35c6918ab3070e43d238487f6cbaf10a682cfc90b1d11c4640957395 xen-3.1.9-0.fc8.src.rpm > 428da514ccf9064244017a5068c399ec0e7c5816c2d2f4ded17e9af031d50759 xen-debuginfo-3.1.9-0.fc8.i386.rpm > 98305f6fc7de7c965b7cb0426a0bed4cb977394a8fce1cedf6fb35d6780df0c5 xen-devel-3.1.9-0.fc8.i386.rpm > f45e0ed7ff40bf7ef4e8cd236f639060caba27d3573003745bfa37f3ae0f4943 xen-libs-3.1.9-0.fc8.i386.rpm Can I request that you include something in the release number to indicate that these are XenSource provided RPMs - just using 'fc8' will lead to confusion with the base Fedora provide RPMs. Either add 'xs' after the initial release digit, or tag it on after the %dist tag, eg one of xen-3.1.9-0xs.fc8.i386.rpm xen-3.1.9-0.fc8.xs1.i386.rpm This ensures that if we get Bug reports it'll be clear which RPMs are being used. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From jlayton at redhat.com Fri Dec 21 17:38:36 2007 From: jlayton at redhat.com (Jeff Layton) Date: Fri, 21 Dec 2007 12:38:36 -0500 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <4769BDF4.3080501@herakles.homelinux.org> References: <476636A8.2070702@herakles.homelinux.org> <47665417.6040207@redhat.com> <47678587.3040006@herakles.homelinux.org> <47678BB0.8060905@herakles.homelinux.org> <20071219095514.53a79830@barsoom.rdu.redhat.com> <000901c84250$d68311b0$83893510$@Henning@prd-inc.com> <4769BDF4.3080501@herakles.homelinux.org> Message-ID: <20071221123836.21763058@tleilax.poochiereds.net> On Thu, 20 Dec 2007 09:57:24 +0900 John Summerfield wrote: > > [1] Producing the CD isn't a problem, sticking it in the imaginary CD > drive was, and while I think the needed ISO is right there too, I > especially don't know how to shuffle virtual CDs. > Generally, what I've had to do is run qemu-kvm from the command line with "-monitor stdio". When you need to change cd's, in the qemu monitor console you do: eject cdrom change cdrom /path/to/iso/image.iso It would be nice if there were some way to do this from virsh or the virt-manager GUI, but I don't think there is as of yet. Maybe open a BZ for it if you're feeling daring. When I do this, I usually disable networking since libvirt isn't setting it up anyway (-net none). Once the image is installed, you can boot it as usual via virt-manager or virsh with networking enabled. -- Jeff Layton From debian at herakles.homelinux.org Fri Dec 21 22:46:54 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Sat, 22 Dec 2007 07:46:54 +0900 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <20071221123836.21763058@tleilax.poochiereds.net> References: <476636A8.2070702@herakles.homelinux.org> <47665417.6040207@redhat.com> <47678587.3040006@herakles.homelinux.org> <47678BB0.8060905@herakles.homelinux.org> <20071219095514.53a79830@barsoom.rdu.redhat.com> <000901c84250$d68311b0$83893510$@Henning@prd-inc.com> <4769BDF4.3080501@herakles.homelinux.org> <20071221123836.21763058@tleilax.poochiereds.net> Message-ID: <476C425E.6090408@herakles.homelinux.org> Jeff Layton wrote: > On Thu, 20 Dec 2007 09:57:24 +0900 > John Summerfield wrote: > >> [1] Producing the CD isn't a problem, sticking it in the imaginary CD >> drive was, and while I think the needed ISO is right there too, I >> especially don't know how to shuffle virtual CDs. >> > > Generally, what I've had to do is run qemu-kvm from the command line > with "-monitor stdio". When you need to change cd's, in the qemu > monitor console you do: Most of my vms are xen; I decided to give kvm a fly when I decided I really don't like that I can't get framebuffer working on the xenified kernel. If kvm works, that's probably what I'll use where I have hardware assist, I like that I don't have to choose it at boot tine. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From avi at qumranet.com Tue Dec 18 10:33:23 2007 From: avi at qumranet.com (Avi Kivity) Date: Tue, 18 Dec 2007 12:33:23 +0200 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <47678BB0.8060905@herakles.homelinux.org> References: <476636A8.2070702@herakles.homelinux.org> <47665417.6040207@redhat.com> <47678587.3040006@herakles.homelinux.org> <47678BB0.8060905@herakles.homelinux.org> Message-ID: <4767A1F3.2050806@qumranet.com> John Summerfield wrote: > John Summerfield wrote: >> Richard W.M. Jones wrote: >>> John Summerfield wrote: > >> >> The good news is that the system now boots grub sans menu. I typed in >> the necessary information to boot windows: >> chainloader (hd0,0)+1 >> boot >> >> and windows boots all the way to a BSOD and the stuff on the screen >> recommends "chkdsk /f." >> >> Hmm. Type to find a rescue system. > > fwiw same happens when I boot directly from the partition. Ideas welcome. > > > Can you capture a screenshot of the BSOD? Maybe some info there. -- error compiling committee.c: too many arguments to function From debian at herakles.homelinux.org Sun Dec 23 00:34:41 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Sun, 23 Dec 2007 09:34:41 +0900 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <4767A1F3.2050806@qumranet.com> References: <476636A8.2070702@herakles.homelinux.org> <47665417.6040207@redhat.com> <47678587.3040006@herakles.homelinux.org> <47678BB0.8060905@herakles.homelinux.org> <4767A1F3.2050806@qumranet.com> Message-ID: <476DAD21.9060702@herakles.homelinux.org> Avi Kivity wrote: > John Summerfield wrote: >> John Summerfield wrote: >>> Richard W.M. Jones wrote: >>>> John Summerfield wrote: >> >>> >>> The good news is that the system now boots grub sans menu. I typed in >>> the necessary information to boot windows: >>> chainloader (hd0,0)+1 >>> boot >>> >>> and windows boots all the way to a BSOD and the stuff on the screen >>> recommends "chkdsk /f." >>> >>> Hmm. Type to find a rescue system. >> >> fwiw same happens when I boot directly from the partition. Ideas welcome. >> >> >> > Can you capture a screenshot of the BSOD? Maybe some info there. > This is not the same BSOD I had earlier. http://debian.merseine.nu/bsod.png I think this is: http://debian.merseine.nu/bsod0.png -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From evoltech at 2inches.com Sun Dec 23 02:16:22 2007 From: evoltech at 2inches.com (Dennison Williams) Date: Sat, 22 Dec 2007 18:16:22 -0800 Subject: [Fedora-xen] Accessing data on a xen guest disk image Message-ID: <476DC4F6.70108@2inches.com> I asked this question in the fedora forums (http://forums.fedoraforum.org/showthread.php?t=176102), but no one seemed to have a answer. I have installed and worked with a few different xen guests via the instructions at FedoraXenQuickstartFC6 (http://fedoraproject.org/wiki/FedoraXenQuickstartFC6). In doing this I installed the guests on a LVM volume and would like to access the guest disk image. There is documentation on howto do this in the above wiki (http://fedoraproject.org/wiki/FedoraXenQuickstartFC6#head-9c5408e750e8184aece3efe822be0ef6dd1871cd). The problem I have is that my dom0 has the same logical and physical volume names for its root device as my domU (ie. VolGroup00, LogVol01). Does anyone know how to get around this name space collision so that I can mount my guest disk? Sincerely, Dennison Williams From mnielsen at redhat.com Sun Dec 23 02:41:28 2007 From: mnielsen at redhat.com (Mark Nielsen) Date: Sat, 22 Dec 2007 21:41:28 -0500 Subject: [Fedora-xen] Accessing data on a xen guest disk image In-Reply-To: <476DC4F6.70108@2inches.com> References: <476DC4F6.70108@2inches.com> Message-ID: <476DCAD8.8060201@redhat.com> I name my VMs with VolGrp/LogVol, then I have 1 test/rescue VM that I create using VolGroup/LogVol. Just having that 1 VM with a different naming convention allows me to present any other VMs disks to my test/rescue VM and mount them for repairs, recoveries, etc. Mark Dennison Williams wrote: > I asked this question in the fedora forums > (http://forums.fedoraforum.org/showthread.php?t=176102), but no one > seemed to have a answer. > > I have installed and worked with a few different xen guests via the > instructions at FedoraXenQuickstartFC6 > (http://fedoraproject.org/wiki/FedoraXenQuickstartFC6). In doing this I > installed the guests on a LVM volume and would like to access the guest > disk image. There is documentation on howto do this in the above wiki > (http://fedoraproject.org/wiki/FedoraXenQuickstartFC6#head-9c5408e750e8184aece3efe822be0ef6dd1871cd). > The problem I have is that my dom0 has the same logical and physical > volume names for its root device as my domU (ie. VolGroup00, LogVol01). > Does anyone know how to get around this name space collision so that I > can mount my guest disk? > > Sincerely, > Dennison Williams > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From evoltech at 2inches.com Sun Dec 23 02:45:13 2007 From: evoltech at 2inches.com (Dennison Williams) Date: Sat, 22 Dec 2007 18:45:13 -0800 Subject: [Fedora-xen] Accessing data on a xen guest disk image In-Reply-To: <476DCAD8.8060201@redhat.com> References: <476DC4F6.70108@2inches.com> <476DCAD8.8060201@redhat.com> Message-ID: <476DCBB9.4070205@2inches.com> Mark Nielsen wrote: > I name my VMs with VolGrp/LogVol, then I have 1 test/rescue VM that I > create using VolGroup/LogVol. Just having that 1 VM with a different > naming convention allows me to present any other VMs disks to my > test/rescue VM and mount them for repairs, recoveries, etc. I don't really understand what you are saying here. What do you mean when you say "I have 1 test/rescue VM that I create using VolGroup/LogVol". Can you be a bit more explicit? cc'ing the fedora-xen mailing list so that others in the same boat can benefit from your advice. From avi at qumranet.com Sun Dec 23 16:58:31 2007 From: avi at qumranet.com (Avi Kivity) Date: Sun, 23 Dec 2007 18:58:31 +0200 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <476DAD21.9060702@herakles.homelinux.org> References: <476636A8.2070702@herakles.homelinux.org> <47665417.6040207@redhat.com> <47678587.3040006@herakles.homelinux.org> <47678BB0.8060905@herakles.homelinux.org> <4767A1F3.2050806@qumranet.com> <476DAD21.9060702@herakles.homelinux.org> Message-ID: <476E93B7.2070407@qumranet.com> John Summerfield wrote: >>> >> Can you capture a screenshot of the BSOD? Maybe some info there. >> > > This is not the same BSOD I had earlier. > http://debian.merseine.nu/bsod.png This one is due to the -no-acpi switch being passed to qemu, while the guest really wants ACPI. Don't pass -no-acpi, but do look at http://kvm.qumranet.com/kvmwiki/Windows_ACPI_Workaround. > > I think this is: > http://debian.merseine.nu/bsod0.png > This is a corrupted disk, or perhaps the IDE driver is not installed correctly. -- error compiling committee.c: too many arguments to function From mnielsen at redhat.com Sun Dec 23 18:21:00 2007 From: mnielsen at redhat.com (Mark Nielsen) Date: Sun, 23 Dec 2007 13:21:00 -0500 Subject: [Fedora-xen] Accessing data on a xen guest disk image In-Reply-To: <476DCBB9.4070205@2inches.com> References: <476DC4F6.70108@2inches.com> <476DCAD8.8060201@redhat.com> <476DCBB9.4070205@2inches.com> Message-ID: <476EA70C.7090809@redhat.com> Let me ask this first: what is it exactly that you are trying to do? If you are trying to mount a guest disk on dom0, why? The times I've needed to access a VMs disk has been when something terrible has happened to the VM and I've needed to mount the VMs disk so I can recover information of try to fsck it. I do this by having a stand-by VM that uses a different naming convention that my other VMs use. This way I can use my test/rescue VM to mount up the other VMs disks and fsck them, or recover data from them. Dennison Williams wrote: > Mark Nielsen wrote: > >> I name my VMs with VolGrp/LogVol, then I have 1 test/rescue VM that I >> create using VolGroup/LogVol. Just having that 1 VM with a different >> naming convention allows me to present any other VMs disks to my >> test/rescue VM and mount them for repairs, recoveries, etc. >> > > I don't really understand what you are saying here. What do you mean > when you say "I have 1 test/rescue VM that I create using > VolGroup/LogVol". Can you be a bit more explicit? > > cc'ing the fedora-xen mailing list so that others in the same boat can > benefit from your advice. > From evoltech at 2inches.com Sun Dec 23 22:18:15 2007 From: evoltech at 2inches.com (Dennison Williams) Date: Sun, 23 Dec 2007 14:18:15 -0800 Subject: [Fedora-xen] Accessing data on a xen guest disk image In-Reply-To: <476EA70C.7090809@redhat.com> References: <476DC4F6.70108@2inches.com> <476DCAD8.8060201@redhat.com> <476DCBB9.4070205@2inches.com> <476EA70C.7090809@redhat.com> Message-ID: <476EDEA7.3030907@2inches.com> Mark Nielsen wrote: > Let me ask this first: what is it exactly that you are trying to do? If > you are trying to mount a guest disk on dom0, why? I am trying to recover the data located on my guest disk. This guest disk is a logical volume in dom0. The guest disk and the dom0 disk are managed by LVM each with the same naming convention (VolGroup00/LogVol0[0-1]). > > The times I've needed to access a VMs disk has been when something > terrible has happened to the VM and I've needed to mount the VMs disk so > I can recover information of try to fsck it. I do this by having a > stand-by VM that uses a different naming convention that my other VMs > use. This way I can use my test/rescue VM to mount up the other VMs > disks and fsck them, or recover data from them. I am unclear about how I could access a LV on dom0 from a domU VM. Can you explain how this would be done? From mnielsen at redhat.com Sun Dec 23 22:41:29 2007 From: mnielsen at redhat.com (Mark Nielsen) Date: Sun, 23 Dec 2007 17:41:29 -0500 Subject: [Fedora-xen] Accessing data on a xen guest disk image In-Reply-To: <476EDEA7.3030907@2inches.com> References: <476DC4F6.70108@2inches.com> <476DCAD8.8060201@redhat.com> <476DCBB9.4070205@2inches.com> <476EA70C.7090809@redhat.com> <476EDEA7.3030907@2inches.com> Message-ID: <476EE419.2040002@redhat.com> Create a new VM using a naming convention different than you do in your other guests/VMs/domUs for the logical volumes. Since you are using VolGroup/LogVol, I suggest using VolGrp/LogVol... it really doesn't matter. You can call it Foo00/Bar00. People seem to overlook the fact you can name these anything you want (within reason). You can even name it just like you name the logical volume for every other VM you have in dom0, but label it something different when you install the domU. The label inside dom0 is just for dom0 to track it, you label it again when you install the VM so the VM can track it. Basically when you install a VM you have a logical volume label nested in another logical volume label. In fact, I do this sometimes on purpose. On dom0, I label a disk as VolGrp00/LogVol20, then when I install the VM I label it as xVolGrp00/LogVol20. Then I set up filters on dom0 (/etc/lvm/lvm.conf) to filter out the VM disks from dom0 seeing it. (r|^x|) Once you have the new test or recovery or utility (whatever you want to call it) VM, then present the disk that you want to recover as the recovery VMs second disk. Again, the key is to make sure whatever you labelled your root disk inside the VM is different. e.g. disk = ['phy:/dev/VolGrp00/LogVol21,sda,w', 'phy:/dev/VolGrp00/LogVol20,sdb,w' ] so, LogVol20 is whatever the root disk is of the VM that you are trying to recover. LogVol21 is whatever the root disk is for your newly created VM that you are going to use for rescue. Again, you can slice off a logical volume in dom0 (lvcreate -L10G -n LogVol21 VolGrp00) but when you installed the VM, you format/label the disk inside the VM as something different (Foo00/Bar00, or VolGroup00/LogVolume00). The disk you want to recover shows up as sdb, but you can also mount it based on the label of VolGrp00/LogVol20 because the label is there and not confused with the root disk of the recovery VM (Foo00/Bar00). Then you just simply mount it to /media or /mnt or some other mount point you create to get data off it. Or you don't even have to mount it, you can just fsck it. I've done this several times (more than I really care to remember) because of accidentally starting the same VM on 2 different cluster nodes. Imagine connecting the same disk to 2 different computers... hehe really messes things up good! Happy Holidays! Dennison Williams wrote: > Mark Nielsen wrote: > >> Let me ask this first: what is it exactly that you are trying to do? If >> you are trying to mount a guest disk on dom0, why? >> > > I am trying to recover the data located on my guest disk. This guest > disk is a logical volume in dom0. The guest disk and the dom0 disk are > managed by LVM each with the same naming convention > (VolGroup00/LogVol0[0-1]). > > >> The times I've needed to access a VMs disk has been when something >> terrible has happened to the VM and I've needed to mount the VMs disk so >> I can recover information of try to fsck it. I do this by having a >> stand-by VM that uses a different naming convention that my other VMs >> use. This way I can use my test/rescue VM to mount up the other VMs >> disks and fsck them, or recover data from them. >> > > I am unclear about how I could access a LV on dom0 from a domU VM. Can > you explain how this would be done? > > From george.refseth at arxi.no Wed Dec 26 15:57:32 2007 From: george.refseth at arxi.no (George Refseth) Date: Wed, 26 Dec 2007 16:57:32 +0100 Subject: [Fedora-xen] Are 64bit Intel Core 2 Quad fedora 8 supported? Message-ID: The 64 bit xen host kernel are unstable (timer/scheduling issue?) So I wonder if this is supported or not. Another Fedora 8 x86_64 installation on an Intel Core 2 Duo seems to run flawlessly, except it is running on a laptop, and not meant for server use. Attached are smolt output. I would be grateful for any input, this was meant to be a system where multiple services should run (several 64bit F8's) serving dns, web and mail, and replace at least two current lumps of hardware.. regards, George -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ -------------- next part -------------- A non-text attachment was scrubbed... Name: profile.tmp Type: application/octet-stream Size: 3958 bytes Desc: not available URL: From debian at herakles.homelinux.org Thu Dec 27 13:21:34 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Thu, 27 Dec 2007 22:21:34 +0900 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <476E93B7.2070407@qumranet.com> References: <476636A8.2070702@herakles.homelinux.org> <47665417.6040207@redhat.com> <47678587.3040006@herakles.homelinux.org> <47678BB0.8060905@herakles.homelinux.org> <4767A1F3.2050806@qumranet.com> <476DAD21.9060702@herakles.homelinux.org> <476E93B7.2070407@qumranet.com> Message-ID: <4773A6DE.8080704@herakles.homelinux.org> Avi Kivity wrote: > John Summerfield wrote: >>>> >>> Can you capture a screenshot of the BSOD? Maybe some info there. >>> >> >> This is not the same BSOD I had earlier. >> http://debian.merseine.nu/bsod.png > > This one is due to the -no-acpi switch being passed to qemu, while the > guest really wants ACPI. Don't pass -no-acpi, but do look at > http://kvm.qumranet.com/kvmwiki/Windows_ACPI_Workaround. the f7 key works for that. > >> >> I think this is: >> http://debian.merseine.nu/bsod0.png >> > > This is a corrupted disk, or perhaps the IDE driver is not installed > correctly. the disk is fine, I can boot it natively. The hardware emulation in qemu is very old (circa Pentium Pro CPUs). It's possible (probable, do I remember LBA supports 120 Gbytes? wasn't there an earlier max of 32 Gbytes?) the disk (320 Gbytes) is larger than the emulation supports. It's also possible that Windows is picking up garbage device geometry. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From avi at qumranet.com Thu Dec 27 15:39:22 2007 From: avi at qumranet.com (Avi Kivity) Date: Thu, 27 Dec 2007 17:39:22 +0200 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <4773A6DE.8080704@herakles.homelinux.org> References: <476636A8.2070702@herakles.homelinux.org> <47665417.6040207@redhat.com> <47678587.3040006@herakles.homelinux.org> <47678BB0.8060905@herakles.homelinux.org> <4767A1F3.2050806@qumranet.com> <476DAD21.9060702@herakles.homelinux.org> <476E93B7.2070407@qumranet.com> <4773A6DE.8080704@herakles.homelinux.org> Message-ID: <4773C72A.8080207@qumranet.com> John Summerfield wrote: > >> >>> >>> I think this is: >>> http://debian.merseine.nu/bsod0.png >>> >> >> This is a corrupted disk, or perhaps the IDE driver is not installed >> correctly. > > the disk is fine, I can boot it natively. The hardware emulation in > qemu is very old (circa Pentium Pro CPUs). It's possible (probable, do > I remember LBA supports 120 Gbytes? wasn't there an earlier max of 32 > Gbytes?) the disk (320 Gbytes) is larger than the emulation supports. > > It's also possible that Windows is picking up garbage device geometry. > Ah, I haven't tried very large disks. I'll check it out. -- error compiling committee.c: too many arguments to function From berrange at redhat.com Thu Dec 27 15:53:15 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 27 Dec 2007 15:53:15 +0000 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <4773C72A.8080207@qumranet.com> References: <476636A8.2070702@herakles.homelinux.org> <47665417.6040207@redhat.com> <47678587.3040006@herakles.homelinux.org> <47678BB0.8060905@herakles.homelinux.org> <4767A1F3.2050806@qumranet.com> <476DAD21.9060702@herakles.homelinux.org> <476E93B7.2070407@qumranet.com> <4773A6DE.8080704@herakles.homelinux.org> <4773C72A.8080207@qumranet.com> Message-ID: <20071227155315.GB7042@redhat.com> On Thu, Dec 27, 2007 at 05:39:22PM +0200, Avi Kivity wrote: > John Summerfield wrote: > > > >> > >>> > >>>I think this is: > >>>http://debian.merseine.nu/bsod0.png > >>> > >> > >>This is a corrupted disk, or perhaps the IDE driver is not installed > >>correctly. > > > >the disk is fine, I can boot it natively. The hardware emulation in > >qemu is very old (circa Pentium Pro CPUs). It's possible (probable, do > >I remember LBA supports 120 Gbytes? wasn't there an earlier max of 32 > >Gbytes?) the disk (320 Gbytes) is larger than the emulation supports. > > > >It's also possible that Windows is picking up garbage device geometry. > > > > Ah, I haven't tried very large disks. I'll check it out. Funnily enough, a change was just commited to the Xen's copy of the QEMU ROMBIOS to support disks > 128 GB which I suspect would also apply to upstream QEMU / KVM's rombios changeset: 16669:7fbc521b07a9 tag: tip user: Keir Fraser date: Thu Dec 27 13:00:40 2007 +0000 files: tools/firmware/rombios/rombios.c description: x86, hvm, rombios: INT13 LBA48 support for disks bigger than 128GB. The new limit should be 2TB. Signed-off-by: Samuel Thibault http://xenbits.xensource.com/staging/xen-unstable.hg?rev/7fbc521b07a9 Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From avi at qumranet.com Thu Dec 27 15:59:40 2007 From: avi at qumranet.com (Avi Kivity) Date: Thu, 27 Dec 2007 17:59:40 +0200 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <4773C72A.8080207@qumranet.com> References: <476636A8.2070702@herakles.homelinux.org> <47665417.6040207@redhat.com> <47678587.3040006@herakles.homelinux.org> <47678BB0.8060905@herakles.homelinux.org> <4767A1F3.2050806@qumranet.com> <476DAD21.9060702@herakles.homelinux.org> <476E93B7.2070407@qumranet.com> <4773A6DE.8080704@herakles.homelinux.org> <4773C72A.8080207@qumranet.com> Message-ID: <4773CBEC.2060103@qumranet.com> Avi Kivity wrote: >> >> the disk is fine, I can boot it natively. The hardware emulation in >> qemu is very old (circa Pentium Pro CPUs). It's possible (probable, >> do I remember LBA supports 120 Gbytes? wasn't there an earlier max of >> 32 Gbytes?) the disk (320 Gbytes) is larger than the emulation supports. >> > > Ah, I haven't tried very large disks. I'll check it out. > You were right, it was missing LBA48 support. I added it for kvm-59 (by coincidence, an LBA48 patch was posted for Xen four hours ago; so I used that). I now have Windows happily installing into a 300GB virtual disk. -- error compiling committee.c: too many arguments to function From debian at herakles.homelinux.org Thu Dec 27 20:50:40 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Fri, 28 Dec 2007 05:50:40 +0900 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <20071227155315.GB7042@redhat.com> References: <476636A8.2070702@herakles.homelinux.org> <47665417.6040207@redhat.com> <47678587.3040006@herakles.homelinux.org> <47678BB0.8060905@herakles.homelinux.org> <4767A1F3.2050806@qumranet.com> <476DAD21.9060702@herakles.homelinux.org> <476E93B7.2070407@qumranet.com> <4773A6DE.8080704@herakles.homelinux.org> <4773C72A.8080207@qumranet.com> <20071227155315.GB7042@redhat.com> Message-ID: <47741020.80301@herakles.homelinux.org> Daniel P. Berrange wrote: > On Thu, Dec 27, 2007 at 05:39:22PM +0200, Avi Kivity wrote: >> John Summerfield wrote: >>>>> I think this is: >>>>> http://debian.merseine.nu/bsod0.png >>>>> >>>> This is a corrupted disk, or perhaps the IDE driver is not installed >>>> correctly. >>> the disk is fine, I can boot it natively. The hardware emulation in >>> qemu is very old (circa Pentium Pro CPUs). It's possible (probable, do >>> I remember LBA supports 120 Gbytes? wasn't there an earlier max of 32 >>> Gbytes?) the disk (320 Gbytes) is larger than the emulation supports. >>> >>> It's also possible that Windows is picking up garbage device geometry. >>> >> Ah, I haven't tried very large disks. I'll check it out. > > Funnily enough, a change was just commited to the Xen's copy of the QEMU > ROMBIOS to support disks > 128 GB which I suspect would also apply to > upstream QEMU / KVM's rombios > > changeset: 16669:7fbc521b07a9 > tag: tip > user: Keir Fraser > date: Thu Dec 27 13:00:40 2007 +0000 > files: tools/firmware/rombios/rombios.c > description: > x86, hvm, rombios: INT13 LBA48 support for disks bigger than 128GB. > The new limit should be 2TB. > > Signed-off-by: Samuel Thibault > > > http://xenbits.xensource.com/staging/xen-unstable.hg?rev/7fbc521b07a9 > > Regards, > Dan. Thanks, Dan, that's encouraging. When is (and is) this likely to filter through to those of us who prefer to not patch their own software? -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From berrange at redhat.com Thu Dec 27 20:53:11 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 27 Dec 2007 20:53:11 +0000 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <47741020.80301@herakles.homelinux.org> References: <47665417.6040207@redhat.com> <47678587.3040006@herakles.homelinux.org> <47678BB0.8060905@herakles.homelinux.org> <4767A1F3.2050806@qumranet.com> <476DAD21.9060702@herakles.homelinux.org> <476E93B7.2070407@qumranet.com> <4773A6DE.8080704@herakles.homelinux.org> <4773C72A.8080207@qumranet.com> <20071227155315.GB7042@redhat.com> <47741020.80301@herakles.homelinux.org> Message-ID: <20071227205311.GA21227@redhat.com> On Fri, Dec 28, 2007 at 05:50:40AM +0900, John Summerfield wrote: > Daniel P. Berrange wrote: > >On Thu, Dec 27, 2007 at 05:39:22PM +0200, Avi Kivity wrote: > >>John Summerfield wrote: > >>>>>I think this is: > >>>>>http://debian.merseine.nu/bsod0.png > >>>>> > >>>>This is a corrupted disk, or perhaps the IDE driver is not installed > >>>>correctly. > >>>the disk is fine, I can boot it natively. The hardware emulation in > >>>qemu is very old (circa Pentium Pro CPUs). It's possible (probable, do > >>>I remember LBA supports 120 Gbytes? wasn't there an earlier max of 32 > >>>Gbytes?) the disk (320 Gbytes) is larger than the emulation supports. > >>> > >>>It's also possible that Windows is picking up garbage device geometry. > >>> > >>Ah, I haven't tried very large disks. I'll check it out. > > > >Funnily enough, a change was just commited to the Xen's copy of the QEMU > >ROMBIOS to support disks > 128 GB which I suspect would also apply to > >upstream QEMU / KVM's rombios > > > > changeset: 16669:7fbc521b07a9 > > tag: tip > > user: Keir Fraser > > date: Thu Dec 27 13:00:40 2007 +0000 > > files: tools/firmware/rombios/rombios.c > > description: > > x86, hvm, rombios: INT13 LBA48 support for disks bigger than 128GB. > > The new limit should be 2TB. > > > > Signed-off-by: Samuel Thibault > > > > > >http://xenbits.xensource.com/staging/xen-unstable.hg?rev/7fbc521b07a9 > > > >Regards, > >Dan. > > Thanks, Dan, that's encouraging. When is (and is) this likely to filter > through to those of us who prefer to not patch their own software? When Avi releases -59 we'll include that in rawhide. If you need the LBA-48 fix applied to other releases please file a BZ against the appropriate Fedora release and add a link to this thread in the BZ report. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From chetan.lists at gmail.com Fri Dec 28 22:31:13 2007 From: chetan.lists at gmail.com (chetan saundankar) Date: Sat, 29 Dec 2007 04:01:13 +0530 Subject: [Fedora-xen] Problem in xend http server Message-ID: <2e3912590712281431m2f8951d5xfacbbd3f42c7e56a@mail.gmail.com> Hi all, I have a problem with starting the xend http server, following are the details. I would like to know the cause of the problem and solution for the same. Thanx in advance Regards Chetan /////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// Setup: Intel core 2 duo 2.33, Intel DG33 mboard Fedora Core 8 Xen 3.1.2 Installed using xen RPM's (dom0: 2.6.21-2952.fc8xen) ////////////////////////////////////////////// xend-config.sxp //////////////////////////////////////////////////////// (Commented part removed) (xend-http-server yes) (xend-unix-server yes) (xend-unix-path /var/lib/xend/xend-socket) (xend-port 8000) (xend-address '') (xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$') (network-script network-bridge) (vif-script vif-bridge) (dom0-cpus 0) (vncpasswd '') /////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// ///////////////////////////////////////////////////// brctl show //////////////////////////////////////////////////////// bridge name bridge id STP enabled interfaces eth0 8000.0019d1960140 no peth0 virbr0 8000.000000000000 no /////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// ////////////////////////////////////////////////// xm log output //////////////////////////////////////////////////////// [?1034h[2007-12-28 04:05:58 2174] INFO (SrvDaemon:338) Xend Daemon started [2007-12-28 04:05:58 2174] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-28 04:05:58 2174] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-28 04:05:58 2174] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 19962276671L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-28 04:05:58 2174] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-28 04:05:58 2174] DEBUG (XendDomainInfo:2116) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image': '(linux (kernel ))', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '2', 'vcpu_avail': '3', 'name': 'Domain-0'} [2007-12-28 04:05:58 2174] DEBUG (XendDomainInfo:956) Storing domain details: {'name': 'Domain-0', 'console/limit': '1048576', 'memory/target': '1434332', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1'} [2007-12-28 04:05:58 2174] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-28 04:05:58 2174] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-28 04:05:58 2174] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-28 04:05:58 2174] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-28 04:05:58 2174] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-28 04:05:58 2174] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-28 04:05:58 2174] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-28 04:08:55 2174] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-28 04:08:55 2174] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-28 04:08:55 2174] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-28 04:08:55 2174] DEBUG (XendDomain:610) cleanup_domains [2007-12-28 12:17:24 2237] INFO (SrvDaemon:338) Xend Daemon started [2007-12-28 12:17:24 2237] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-28 12:17:24 2237] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-28 12:17:24 2237] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 24247516743L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-28 12:17:24 2237] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-28 12:17:24 2237] DEBUG (XendDomainInfo:2116) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image': '(linux (kernel ))', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '2', 'vcpu_avail': '3', 'name': 'Domain-0'} [2007-12-28 12:17:24 2237] DEBUG (XendDomainInfo:956) Storing domain details: {'name': 'Domain-0', 'console/limit': '1048576', 'memory/target': '1434332', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1'} [2007-12-28 12:17:24 2237] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-28 12:17:24 2237] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-28 12:17:24 2237] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-28 12:17:24 2237] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-28 12:17:24 2237] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-28 12:17:25 2237] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-28 12:17:25 2237] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-28 12:55:51 2237] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-28 12:55:51 2237] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-28 12:55:51 2237] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-28 12:55:51 2237] DEBUG (XendDomain:610) cleanup_domains [2007-12-28 13:16:19 2191] INFO (SrvDaemon:338) Xend Daemon started [2007-12-28 13:16:19 2191] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-28 13:16:19 2191] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-28 13:16:19 2191] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 21997384561L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-28 13:16:19 2191] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-28 13:16:19 2191] DEBUG (XendDomainInfo:2116) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image': '(linux (kernel ))', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '2', 'vcpu_avail': '3', 'name': 'Domain-0'} [2007-12-28 13:16:19 2191] DEBUG (XendDomainInfo:956) Storing domain details: {'name': 'Domain-0', 'console/limit': '1048576', 'memory/target': '1434332', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1'} [2007-12-28 13:16:19 2191] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-28 13:16:19 2191] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-28 13:16:19 2191] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-28 13:16:19 2191] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-28 13:16:19 2191] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-28 13:16:20 2191] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-28 13:16:20 2191] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-28 13:30:32 2191] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-28 13:30:32 2191] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-28 13:30:32 2191] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-28 13:30:32 2191] DEBUG (XendDomain:610) cleanup_domains [2007-12-28 13:46:15 2359] INFO (SrvDaemon:338) Xend Daemon started [2007-12-28 13:46:15 2359] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-28 13:46:15 2359] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-28 13:46:15 2359] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 22162061462L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-28 13:46:15 2359] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-28 13:46:15 2359] DEBUG (XendDomainInfo:2116) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image': '(linux (kernel ))', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '2', 'vcpu_avail': '3', 'name': 'Domain-0'} [2007-12-28 13:46:15 2359] DEBUG (XendDomainInfo:956) Storing domain details: {'name': 'Domain-0', 'console/limit': '1048576', 'memory/target': '1434332', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1'} [2007-12-28 13:46:15 2359] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-28 13:46:15 2359] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-28 13:46:15 2359] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-28 13:46:15 2359] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-28 13:46:16 2359] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-28 13:46:19 2359] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-28 13:46:19 2359] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-29 02:38:32 2359] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-29 02:38:32 2359] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 02:38:32 2359] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 02:38:32 2359] DEBUG (XendDomain:610) cleanup_domains [2007-12-29 02:38:34 31390] INFO (SrvDaemon:338) Xend Daemon started [2007-12-29 02:38:34 31390] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-29 02:38:34 31390] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-29 02:38:34 31390] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 5353219220361L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-29 02:38:34 31390] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-29 02:38:34 31390] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-29 02:38:34 31390] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-29 02:38:34 31390] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-29 02:38:34 31390] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-29 02:38:34 31390] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-29 02:38:34 31390] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-29 02:38:34 31390] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-29 02:52:15 31390] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-29 02:52:15 31390] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 02:52:15 31390] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 02:52:15 31390] DEBUG (XendDomain:610) cleanup_domains [2007-12-29 02:52:16 31614] INFO (SrvDaemon:338) Xend Daemon started [2007-12-29 02:52:16 31614] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-29 02:52:16 31614] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-29 02:52:16 31614] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 5461808608907L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-29 02:52:16 31614] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-29 02:52:16 31614] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-29 02:52:16 31614] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-29 02:52:16 31614] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-29 02:52:16 31614] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-29 02:52:16 31614] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-29 02:52:16 31614] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-29 02:52:16 31614] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-29 03:12:05 31614] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-29 03:12:05 31614] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 03:12:05 31614] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 03:12:05 31614] DEBUG (XendDomain:610) cleanup_domains [2007-12-29 03:12:05 32047] INFO (SrvDaemon:338) Xend Daemon started [2007-12-29 03:12:05 32047] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-29 03:12:05 32047] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-29 03:12:05 32047] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 5590097350536L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-29 03:12:05 32047] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-29 03:12:05 32047] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-29 03:12:05 32047] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-29 03:12:05 32047] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-29 03:12:05 32047] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-29 03:12:05 32047] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-29 03:12:05 32047] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-29 03:12:05 32047] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-29 03:13:48 32047] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-29 03:13:48 32047] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 03:13:48 32047] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 03:13:48 32047] DEBUG (XendDomain:610) cleanup_domains [2007-12-29 03:13:49 32119] INFO (SrvDaemon:338) Xend Daemon started [2007-12-29 03:13:49 32119] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-29 03:13:49 32119] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-29 03:13:49 32119] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 5598967971398L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-29 03:13:49 32119] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-29 03:13:49 32119] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-29 03:13:49 32119] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-29 03:13:49 32119] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-29 03:13:49 32119] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-29 03:13:49 32119] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-29 03:13:49 32119] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-29 03:13:49 32119] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-29 03:14:19 32119] ERROR (SrvServer:144) Server HttpServer did not initialise! [2007-12-29 03:36:38 32119] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-29 03:36:38 32119] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 03:36:38 32119] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 03:36:38 32119] DEBUG (XendDomain:610) cleanup_domains [2007-12-29 03:36:39 32295] INFO (SrvDaemon:338) Xend Daemon started [2007-12-29 03:36:39 32295] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-29 03:36:39 32295] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-29 03:36:39 32295] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 5758188473089L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-29 03:36:39 32295] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-29 03:36:39 32295] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-29 03:36:39 32295] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-29 03:36:39 32295] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-29 03:36:39 32295] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-29 03:36:39 32295] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-29 03:36:39 32295] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-29 03:36:39 32295] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-29 03:37:09 32295] ERROR (SrvServer:144) Server HttpServer did not initialise! [2007-12-29 03:53:40 32295] DEBUG (SrvServer:77) SrvServer.cleanup() [2007-12-29 03:53:40 32295] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 03:53:40 32295] DEBUG (XMLRPCServer:222) XMLRPCServer.cleanup() [2007-12-29 03:53:40 32295] DEBUG (XendDomain:610) cleanup_domains [2007-12-29 03:53:40 32462] INFO (SrvDaemon:338) Xend Daemon started [2007-12-29 03:53:40 32462] INFO (SrvDaemon:342) Xend changeset: unavailable. [2007-12-29 03:53:40 32462] INFO (SrvDaemon:349) Xend version: Unknown. [2007-12-29 03:53:40 32462] DEBUG (XendDomainInfo:132) XendDomainInfo.recreate({'max_vcpu_id': 1, 'cpu_time': 5937486844602L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 2, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 1434332L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-12-29 03:53:40 32462] INFO (XendDomainInfo:149) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-12-29 03:53:40 32462] DEBUG (XendDomain:443) Adding Domain: 0 [2007-12-29 03:53:40 32462] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-12-29 03:53:40 32462] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-12-29 03:53:40 32462] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: debug.get_all not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: event.get_record not found [2007-12-29 03:53:40 32462] WARNING (XendAPI:672) API call: event.get_all not found [2007-12-29 03:53:40 32462] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. [2007-12-29 03:53:40 32462] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-12-29 03:54:11 32462] ERROR (SrvServer:144) Server HttpServer did not initialise! /////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////// From sa212+fcxen at cyconix.com Sat Dec 29 15:08:00 2007 From: sa212+fcxen at cyconix.com (Evan Lavelle) Date: Sat, 29 Dec 2007 15:08:00 +0000 Subject: [Fedora-xen] Where's my VM gone? Message-ID: <477662D0.1030202@cyconix.com> I'm on F8, and decided to have a go a creating a PV guest on LVM (x86_64 F8 DomU on x86_64 F8 Dom0) using virt-install. virt-manager doesn't appear to do anything on my (out-of-the-box) F8 Dom0; you just enter a root password, and the GUI disappears. I've already done a couple of other guests 'manually' on this DomU, without problems. It took me a few hours to get through installation, because of various problems with NFS firewalls, DNS problems, and so on. I had to abort the install several times. when this happened, my previous VM name was 'used up'. xm list showed a zombie domain with that name, even if the installation had barely started. I couldn't start a new installation with the same name, because virt-install complained that the VM already existed. So, I Googled around, found others with the same problem, and found out that I could remove the zombie entry with 'virsh undefine'. I eventually created a VM with the correct name, which ran Ok, and shut down the machine. This morning I turned on the box, did an 'xm list', and found what appeared to be a zombie with the new VM name (no ID, no status; just a name). So, I virsh undefined it. This seems to have been a big mistake. I then discovered that virt-install doesn't create a config file, and there was nothing in /var/lib/xend/domains, presumably because of the undefine (none of this is documented in Fedora7VirtQuickStart, by the way). How do I get my VM back? Is there some way to get the XML config back? If not, is my only option to manually make an /etc/xen config file? There's a little bit of information in xend.log which I could use for the config file. Finally, I'm (very) confused about what exactly is 'Xen' and what exactly is 'Fedora'. You seem to have done various things which I'm guessing are Fedora-specific, but which don't seem to be documented (I've had a lot of trouble with /etc/inittab, for example). Is this documented somewhere? And am I going to run into any problems if I convert a virt-install domain back to plain-old-Xen? Thanks - Evan From sa212+fcxen at cyconix.com Sat Dec 29 16:11:13 2007 From: sa212+fcxen at cyconix.com (Evan Lavelle) Date: Sat, 29 Dec 2007 16:11:13 +0000 Subject: [Fedora-xen] Where's my VM gone? In-Reply-To: <477662D0.1030202@cyconix.com> References: <477662D0.1030202@cyconix.com> Message-ID: <477671A1.90406@cyconix.com> Evan Lavelle wrote: > How do I get my VM back? Is there some way to get the XML config back? > If not, is my only option to manually make an /etc/xen config file? There don't seem to be any surprises in the VM, and a trivial config file boots it. For anyone else who comes this way, and doesn't know how to do this, the config file is: # -*- mode: python; -*- name = "fc8-64-001" memory = 1024 vcpus = 1 vif = [ 'mac=00:0f:b5:ae:4f:2b, bridge=xenbr0' ] disk = [ 'phy:/dev/VG_Guests/FC8-64-001,hda,w' ]; bootloader ="/usr/bin/pygrub" boot = "cd" sdl = 1 vnc = 0 1 - name this file (for example) fc8-64.pv (the name doesn't matter) 2 - put it in /etc/xen 3 - change the VM name ("fc8-64-001") to whatever you want, as long as all your VM names are unique 4 - the memory line is the maximum to allocate to this VM, in MB (this config is for 1GB. 512MB is common, but don't make it less than about 256MB) 5 - 'vcpus' is the number of CPUs to allocate to this VM; it defaults to 1 anyway. I'm running on dual-core, so I allocate one to the current DomU, and one to Dom0 6 - the MAC address is optional; you'll get a random one if you delete everything before 'bridge' 7 - substitute '/dev/VG_Guests/FC8-64-001' for whatever the path to your device or image file is (for example, /var/lib/xen/images/myimage) 8 - start your VM with # /usr/sbin/xm create -c fc8-64.pv 9 - xm searches for 'fc8-64.pv' in /etc/xen (or you can put it somewhere else and supply a full path). the '-c' turns your shell into the DomU console. you'll see the DomU grub loader screen. You need to select the Xen kernel; not the stock kernel. This will be selected by default anyway, if you leave it long enough. 10 - the boot messages appear on the console; you'll get a window on the Dom0 when booting completes. Evan From evoltech at 2inches.com Sat Dec 29 20:29:03 2007 From: evoltech at 2inches.com (Dennison Williams) Date: Sat, 29 Dec 2007 12:29:03 -0800 Subject: [Fedora-xen] Accessing data on a xen guest disk image In-Reply-To: <476EE419.2040002@redhat.com> References: <476DC4F6.70108@2inches.com> <476DCAD8.8060201@redhat.com> <476DCBB9.4070205@2inches.com> <476EA70C.7090809@redhat.com> <476EDEA7.3030907@2inches.com> <476EE419.2040002@redhat.com> Message-ID: <4776AE0F.9050407@2inches.com> Mark Nielsen wrote: > Create a new VM using a naming convention different than you do in your > other guests/VMs/domUs for the logical volumes. Since you are using > VolGroup/LogVol, I suggest using VolGrp/LogVol... it really doesn't > matter. You can call it Foo00/Bar00. People seem to overlook the fact > you can name these anything you want (within reason). You can even name > it just like you name the logical volume for every other VM you have in > dom0, but label it something different when you install the domU. The > label inside dom0 is just for dom0 to track it, you label it again when > you install the VM so the VM can track it. Basically when you install a > VM you have a logical volume label nested in another logical volume > label. In fact, I do this sometimes on purpose. On dom0, I label a disk > as VolGrp00/LogVol20, then when I install the VM I label it as > xVolGrp00/LogVol20. Then I set up filters on dom0 (/etc/lvm/lvm.conf) to > filter out the VM disks from dom0 seeing it. (r|^x|) > > Once you have the new test or recovery or utility (whatever you want to > call it) VM, then present the disk that you want to recover as the > recovery VMs second disk. Again, the key is to make sure whatever you > labelled your root disk inside the VM is different. e.g. > > > disk = ['phy:/dev/VolGrp00/LogVol21,sda,w', > 'phy:/dev/VolGrp00/LogVol20,sdb,w' ] > > so, LogVol20 is whatever the root disk is of the VM that you are trying > to recover. LogVol21 is whatever the root disk is for your newly created > VM that you are going to use for rescue. Again, you can slice off a > logical volume in dom0 (lvcreate -L10G -n LogVol21 VolGrp00) but when > you installed the VM, you format/label the disk inside the VM as > something different (Foo00/Bar00, or VolGroup00/LogVolume00). > > The disk you want to recover shows up as sdb, but you can also mount it > based on the label of VolGrp00/LogVol20 because the label is there and > not confused with the root disk of the recovery VM (Foo00/Bar00). > > Then you just simply mount it to /media or /mnt or some other mount > point you create to get data off it. Or you don't even have to mount it, > you can just fsck it. > > I've done this several times (more than I really care to remember) > because of accidentally starting the same VM on 2 different cluster > nodes. Imagine connecting the same disk to 2 different computers... hehe > really messes things up good! I just wanted to follow up on this thread and let everyone know this technique works like a charm. If you are installing this "rescue" guest viz xenguest-install.py and choose a text mode installation, you will notice that you will not be able to change the name of the Volume Group in the disk partitioning section, but you will be able to change the the name of the logical volumes. Thanks Mark! From debian at herakles.homelinux.org Sat Dec 29 23:20:44 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Sun, 30 Dec 2007 08:20:44 +0900 Subject: [Fedora-xen] kvm crash on f8 In-Reply-To: <20071227205311.GA21227@redhat.com> References: <47665417.6040207@redhat.com> <47678587.3040006@herakles.homelinux.org> <47678BB0.8060905@herakles.homelinux.org> <4767A1F3.2050806@qumranet.com> <476DAD21.9060702@herakles.homelinux.org> <476E93B7.2070407@qumranet.com> <4773A6DE.8080704@herakles.homelinux.org> <4773C72A.8080207@qumranet.com> <20071227155315.GB7042@redhat.com> <47741020.80301@herakles.homelinux.org> <20071227205311.GA21227@redhat.com> Message-ID: <4776D64C.6090404@herakles.homelinux.org> Daniel P. Berrange wrote: > On Fri, Dec 28, 2007 at 05:50:40AM +0900, John Summerfield wrote: >> Daniel P. Berrange wrote: >>> On Thu, Dec 27, 2007 at 05:39:22PM +0200, Avi Kivity wrote: >>>> John Summerfield wrote: >>>>>>> I think this is: >>>>>>> http://debian.merseine.nu/bsod0.png >>>>>>> >>>>>> This is a corrupted disk, or perhaps the IDE driver is not installed >>>>>> correctly. >>>>> the disk is fine, I can boot it natively. The hardware emulation in >>>>> qemu is very old (circa Pentium Pro CPUs). It's possible (probable, do >>>>> I remember LBA supports 120 Gbytes? wasn't there an earlier max of 32 >>>>> Gbytes?) the disk (320 Gbytes) is larger than the emulation supports. >>>>> >>>>> It's also possible that Windows is picking up garbage device geometry. >>>>> >>>> Ah, I haven't tried very large disks. I'll check it out. >>> Funnily enough, a change was just commited to the Xen's copy of the QEMU >>> ROMBIOS to support disks > 128 GB which I suspect would also apply to >>> upstream QEMU / KVM's rombios >>> >>> changeset: 16669:7fbc521b07a9 >>> tag: tip >>> user: Keir Fraser >>> date: Thu Dec 27 13:00:40 2007 +0000 >>> files: tools/firmware/rombios/rombios.c >>> description: >>> x86, hvm, rombios: INT13 LBA48 support for disks bigger than 128GB. >>> The new limit should be 2TB. >>> >>> Signed-off-by: Samuel Thibault >>> >>> >>> http://xenbits.xensource.com/staging/xen-unstable.hg?rev/7fbc521b07a9 >>> >>> Regards, >>> Dan. >> Thanks, Dan, that's encouraging. When is (and is) this likely to filter >> through to those of us who prefer to not patch their own software? > > When Avi releases -59 we'll include that in rawhide. If you need the > LBA-48 fix applied to other releases please file a BZ against the > appropriate Fedora release and add a link to this thread in the BZ > report. Where? I couldn't find a matching one at RH, though I saw some that could have been created by this problem, if the disks had been big enough, and was contemplating creating one until this happened: Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later > > Regards, > Dan. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From berrange at redhat.com Sun Dec 30 18:20:22 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Sun, 30 Dec 2007 18:20:22 +0000 Subject: [Fedora-xen] Where's my VM gone? In-Reply-To: <477662D0.1030202@cyconix.com> References: <477662D0.1030202@cyconix.com> Message-ID: <20071230182022.GB9150@redhat.com> On Sat, Dec 29, 2007 at 03:08:00PM +0000, Evan Lavelle wrote: > I'm on F8, and decided to have a go a creating a PV guest on LVM (x86_64 > F8 DomU on x86_64 F8 Dom0) using virt-install. virt-manager doesn't > appear to do anything on my (out-of-the-box) F8 Dom0; you just enter a > root password, and the GUI disappears. I've already done a couple of > other guests 'manually' on this DomU, without problems. > > It took me a few hours to get through installation, because of various > problems with NFS firewalls, DNS problems, and so on. I had to abort the > install several times. when this happened, my previous VM name was 'used > up'. xm list showed a zombie domain with that name, even if the > installation had barely started. I couldn't start a new installation > with the same name, because virt-install complained that the VM already > existed. > > So, I Googled around, found others with the same problem, and found out > that I could remove the zombie entry with 'virsh undefine'. I eventually > created a VM with the correct name, which ran Ok, and shut down the machine. > > This morning I turned on the box, did an 'xm list', and found what > appeared to be a zombie with the new VM name (no ID, no status; just a > name). So, I virsh undefined it. You should 'virsh destroy' zombies, rather than 'virsh undefine'. 'Destroy' will forcably kill the VM. 'Undefine' merely removes its config file. > This seems to have been a big mistake. I then discovered that > virt-install doesn't create a config file, and there was nothing in > /var/lib/xend/domains, presumably because of the undefine (none of this > is documented in Fedora7VirtQuickStart, by the way). virt-install *does* create a config file. You explicitly deleted the config file by running 'virsh undefine'. The config files are managed by XenD in /var/lib/xend/domains, /etc/xen is a legacy location no longer used by default from Xen 3.0.4 and later. > How do I get my VM back? Is there some way to get the XML config back? Check /root/.virt-install/virt-install.log where you may well have a copy of the config file in the logs > If not, is my only option to manually make an /etc/xen config file? > There's a little bit of information in xend.log which I could use for > the config file. Re-run 'virt-install' with the same parameters and pointing to your existing installed disk image. When the installer pops up, instead of going through the install process, simply 'virsh destroy' to shutdown the guest VM. You should now have a config file for the guest again. > Finally, I'm (very) confused about what exactly is 'Xen' and what > exactly is 'Fedora'. You seem to have done various things which I'm > guessing are Fedora-specific, but which don't seem to be documented > (I've had a lot of trouble with /etc/inittab, for example). Is this > documented somewhere? And am I going to run into any problems if I > convert a virt-install domain back to plain-old-Xen? There's no difference between a VM created by 'virt-install' and one created another way. If you use the same VM config params in both approaches you'll end up with the same VM. libvirt & virt-install ultimately talk to the same underlying XenD APIs as any other tool. libvirt is simply exposing an API / toolset which is not Xen-specific / portable to virtualization like QEMU, KVM, OpenVZ etc Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|