From normanntp at gmail.com Sat Jan 3 14:44:41 2009 From: normanntp at gmail.com (Norman NTP) Date: Sat, 3 Jan 2009 19:44:41 +0500 Subject: [Fedora-xen] NTP problem in PAE kernel Message-ID: <80b7e2920901030644u30e5f2bdld5f42e948b889b7e@mail.gmail.com> Hello, I have a question that we are using Fedora-8 as DOM0 and Fedora-10 as DomU, how DomU can use by default clock of DOM0 so in that way if i want to change the time on DomU it wont allow me to change the time on DomU.I am using Xen Kernel on DOM0 and PAE Kernel on DomU. pls suggest. Thanks, Norman From felix.schwarz at web.de Sun Jan 4 13:14:37 2009 From: felix.schwarz at web.de (Felix Schwarz) Date: Sun, 04 Jan 2009 14:14:37 +0100 Subject: [Fedora-xen] Shutdown VM when host goes down? Message-ID: <4960B63D.4000609@web.de> Hi, I managed to migrate my F8 host with Xen to F10 with KVM and Xenner. So far this was easier than expected. :-) Of course there are some smaller issues (Xenner does not work with SElinux, NetworkManager does not support bridges) but now there is only one real issue left: How can I automatically shut down all running VMs when my host machine goes down? All VMs do poweroff if I press the 'shutdown' button in virt-manager. So I guess it's just a matter of sending this signal to all running VMs and waiting a bit. Thank you very much, fs -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3312 bytes Desc: S/MIME Cryptographic Signature URL: From normanntp at gmail.com Sun Jan 4 18:12:59 2009 From: normanntp at gmail.com (Norman NTP) Date: Sun, 4 Jan 2009 23:12:59 +0500 Subject: [Fedora-xen] Shutdown VM when host goes down? Message-ID: <80b7e2920901041012l46435e91nd25d8367fda06a34@mail.gmail.com> Hi Felix, I think you can check by xm command there are two options to shutdown complete xen. -a Shutdown all domains. Often used when doing a complete shutdown of a Xen system. -w Wait for the domain to complete shutdown before returning. xm shutdown -a -w Thanks, Norman From felix.schwarz at web.de Sun Jan 4 18:26:13 2009 From: felix.schwarz at web.de (Felix Schwarz) Date: Sun, 04 Jan 2009 19:26:13 +0100 Subject: [Fedora-xen] Re: Shutdown VM when host goes down? In-Reply-To: <80b7e2920901041012l46435e91nd25d8367fda06a34@mail.gmail.com> References: <80b7e2920901041012l46435e91nd25d8367fda06a34@mail.gmail.com> Message-ID: <4960FF45.1090509@web.de> Hi Norman, Norman NTP schrieb: > I think you can check by xm command there are two options to shutdown > complete xen. Unfortunately, there is no 'xm' command in F10. Furthermore I like to have this functionality for all VMs in libvirt, e.g. with KVM domains. 'xm' probably don't handle these. And the most important thing for me is that I don't have to do it manually. Yes, I can write my own init script but hey, this such a common use case that I think Fedora should provide something out of the box, right? But thanks for your post anyway :-) fs -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3312 bytes Desc: S/MIME Cryptographic Signature URL: From normanntp at gmail.com Sun Jan 4 19:25:04 2009 From: normanntp at gmail.com (Norman NTP) Date: Mon, 5 Jan 2009 00:25:04 +0500 Subject: [Fedora-xen] Re: Shutdown VM when host goes down? In-Reply-To: <4960FF45.1090509@web.de> References: <80b7e2920901041012l46435e91nd25d8367fda06a34@mail.gmail.com> <4960FF45.1090509@web.de> Message-ID: <80b7e2920901041125w7d7fe99aw68059d4fa3e2963a@mail.gmail.com> Hi Felix, Oh, I thought you are using Fc-8 on Dom0 :) On 1/4/09, Felix Schwarz wrote: > Hi Norman, > > Norman NTP schrieb: >> I think you can check by xm command there are two options to shutdown >> complete xen. > > Unfortunately, there is no 'xm' command in F10. Furthermore I like to have > this functionality for all VMs in libvirt, e.g. with KVM domains. 'xm' > probably don't handle these. > > And the most important thing for me is that I don't have to do it manually. > Yes, I can write my own init script but hey, this such a common use case > that > I think Fedora should provide something out of the box, right? > > But thanks for your post anyway :-) > fs > > From Alex.Upton at instinet.com Sun Jan 4 21:01:33 2009 From: Alex.Upton at instinet.com (Alex.Upton at instinet.com) Date: Sun, 4 Jan 2009 16:01:33 -0500 Subject: [Fedora-xen] AUTO: Upton, Alex is out of the office. (returning 01/05/2009) Message-ID: I am out of the office until 01/05/2009. Please direct all support related topics to "TSG SA" during this time. Issues in need of escillation should be sent directly to Bob Sinko. Thank you, Alex Note: This is an automated response to your message "[Fedora-xen] Re: Shutdown VM when host goes down?" sent on 1/4/2009 1:26:13 PM. This is the only notification you will receive while this person is away. ***************************************************************** <<>> In compliance with applicable rules and regulations, Instinet reviews and archives incoming and outgoing email communications, copies of which may be produced at the request of regulators. This message is intended only for the personal and confidential use of the recipients named above. If the reader of this email is not the intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and permanently delete the copy you received. Instinet accepts no liability for any content contained in the email, or any errors or omissions arising as a result of email transmission. Any opinions contained in this email constitute the sender's best judgment at this time and are subject to change without notice. Instinet does not make recommendations of a particular security and the information contained in this email should not be considered as a recommendation, an offer or a solicitation of an offer to buy and sell securities. ***************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From mysublists at gmail.com Mon Jan 5 12:51:04 2009 From: mysublists at gmail.com (Linux student) Date: Mon, 05 Jan 2009 17:51:04 +0500 Subject: [Fedora-xen] Re: [Xen-users] NTP problem In-Reply-To: <20090104170010.AC82F619A1D@hormel.redhat.com> References: <20090104170010.AC82F619A1D@hormel.redhat.com> Message-ID: <49620238.8000803@gmail.com> > I'm not sure everybody else here knows Fedora kernels by heart. I > don't, so you may want to give kernel versions for better support. > > But I suppose Fedora 10 uses a pvops domU kernel (2.6.26 or later), > which has no built-in support for dom0 clock sync. You have to use > NTP or some other user space method for syncing the domU clock. > -- > Feri. According to xen docs "By default, the clocks in a Linux VM are synchronized to the clock running on the control domain, and cannot be independently changed. This mode is a convenient default, since only the control domain needs to be running the NTP service to keep accurate time across all VMs." So logically speaking it should be Dom0 kernel controlling time related tasks not the DomU ? From pasik at iki.fi Mon Jan 5 20:47:44 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 5 Jan 2009 22:47:44 +0200 Subject: [Fedora-xen] [Xen-devel] ANNOUNCE: Xen 3.2.3 and 3.3.1 released! Message-ID: <20090105204744.GT15052@edu.joroinen.fi> ----- Forwarded message from Keir Fraser ----- From: Keir Fraser To: xen-devel Date: Mon, 05 Jan 2009 13:31:07 +0000 Subject: [Xen-devel] ANNOUNCE: Xen 3.2.3 and 3.3.1 released! Folks, New point releases in the 3.2 and 3.3 stable branches have just been tagged in the mercurial repositories. Source tarballs are also available from: http://bits.xensource.com/oss-xen/release/3.3.1/xen-3.3.1.tar.gz http://bits.xensource.com/oss-xen/release/3.2.3/xen-3.2.3.tar.gz -- Keir _______________________________________________ Xen-devel mailing list Xen-devel at lists.xensource.com http://lists.xensource.com/xen-devel ----- End forwarded message ----- From pasik at iki.fi Mon Jan 5 20:53:04 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Mon, 5 Jan 2009 22:53:04 +0200 Subject: [Fedora-xen] Updating Xen to 3.3.1 Message-ID: <20090105205304.GU15052@edu.joroinen.fi> Hello! Xen 3.3.1 has been released with a lot a of fixes so it would be nice to get xen hypervisor/tools/libs packages updated in fedora. Xen 3.3.1 does not yet contain pv_ops dom0 support fixes/patches from xen-unstable, so those backported patches in 3.3.0-2 are still needed for 3.3.1. -- Pasi From kraxel at redhat.com Mon Jan 5 21:15:36 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Mon, 05 Jan 2009 22:15:36 +0100 Subject: [Fedora-xen] Re: Updating Xen to 3.3.1 In-Reply-To: <20090105205304.GU15052@edu.joroinen.fi> References: <20090105205304.GU15052@edu.joroinen.fi> Message-ID: <49627878.3070008@redhat.com> Pasi K?rkk?inen wrote: > Hello! > > Xen 3.3.1 has been released with a lot a of fixes so it would be nice to get > xen hypervisor/tools/libs packages updated in fedora. > > Xen 3.3.1 does not yet contain pv_ops dom0 support fixes/patches from > xen-unstable, so those backported patches in 3.3.0-2 are still needed for > 3.3.1. I've seen the announcement. Doesn't build right now in rawhide due to bug #478663 ... cheers, Gerd From deshantm at gmail.com Wed Jan 7 06:18:23 2009 From: deshantm at gmail.com (Todd Deshane) Date: Wed, 7 Jan 2009 01:18:23 -0500 Subject: [Fedora-xen] Create multiple loopback devices In-Reply-To: References: Message-ID: <1e16a9ed0901062218p26a8ad50ld1a94b6947ae3095@mail.gmail.com> On Tue, Dec 2, 2008 at 12:34 PM, Guillaume wrote: > Hi > > I would like to know if it is possible to create multiple loopback > ethernet device. And if yes, how to create new one. > The purpose of this is to attach to many vm this interface, and then, > share this private network between these vm. > You should be able to use dummy network devices for this. They are basically equivalent to private bridges, but like you said are loopback and don't need to be associated with a physical NIC. Alternatively, you can create bridges manually and add devices to them. You can then just put the brctl commands in a script. Hope that helps. Cheers, Todd -- Todd Deshane http://todddeshane.net http://runningxen.com From pasik at iki.fi Thu Jan 8 11:13:56 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 8 Jan 2009 13:13:56 +0200 Subject: [Fedora-xen] Re: Updating Xen to 3.3.1 In-Reply-To: <49627878.3070008@redhat.com> References: <20090105205304.GU15052@edu.joroinen.fi> <49627878.3070008@redhat.com> Message-ID: <20090108111356.GN15052@edu.joroinen.fi> On Mon, Jan 05, 2009 at 10:15:36PM +0100, Gerd Hoffmann wrote: > Pasi K?rkk?inen wrote: > > Hello! > > > > Xen 3.3.1 has been released with a lot a of fixes so it would be nice to get > > xen hypervisor/tools/libs packages updated in fedora. > > > > Xen 3.3.1 does not yet contain pv_ops dom0 support fixes/patches from > > xen-unstable, so those backported patches in 3.3.0-2 are still needed for > > 3.3.1. > > I've seen the announcement. > Doesn't build right now in rawhide due to bug #478663 ... > Yep. kernel-2.6.29-0.18.rc0.git9.fc11 -------------------------------- * Wed Jan 7 17:00:00 2009 Jarod Wilson - 2.6.28-git9 - Should resolve broken byteorder.h issues (#478663) Let's hope that kernel version works. -- Pasi From berrange at redhat.com Thu Jan 8 11:18:44 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 8 Jan 2009 11:18:44 +0000 Subject: [Fedora-xen] Re: Updating Xen to 3.3.1 In-Reply-To: <20090108111356.GN15052@edu.joroinen.fi> References: <20090105205304.GU15052@edu.joroinen.fi> <49627878.3070008@redhat.com> <20090108111356.GN15052@edu.joroinen.fi> Message-ID: <20090108111844.GD26474@redhat.com> On Thu, Jan 08, 2009 at 01:13:56PM +0200, Pasi K?rkk?inen wrote: > On Mon, Jan 05, 2009 at 10:15:36PM +0100, Gerd Hoffmann wrote: > > Pasi K?rkk?inen wrote: > > > Hello! > > > > > > Xen 3.3.1 has been released with a lot a of fixes so it would be nice to get > > > xen hypervisor/tools/libs packages updated in fedora. > > > > > > Xen 3.3.1 does not yet contain pv_ops dom0 support fixes/patches from > > > xen-unstable, so those backported patches in 3.3.0-2 are still needed for > > > 3.3.1. > > > > I've seen the announcement. > > Doesn't build right now in rawhide due to bug #478663 ... > > > > Yep. > > kernel-2.6.29-0.18.rc0.git9.fc11 > -------------------------------- > * Wed Jan 7 17:00:00 2009 Jarod Wilson > - 2.6.28-git9 > - Should resolve broken byteorder.h issues (#478663) > > Let's hope that kernel version works. I've just succesfully done a KVM build against kernel-headers version 2.6.29-0.19.rc0.git9.fc11, so all is working again now. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From pasik at iki.fi Fri Jan 9 09:33:11 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Fri, 9 Jan 2009 11:33:11 +0200 Subject: [Fedora-xen] Re: Updating Xen to 3.3.1 In-Reply-To: <20090108111844.GD26474@redhat.com> References: <20090105205304.GU15052@edu.joroinen.fi> <49627878.3070008@redhat.com> <20090108111356.GN15052@edu.joroinen.fi> <20090108111844.GD26474@redhat.com> Message-ID: <20090109093311.GO15052@edu.joroinen.fi> On Thu, Jan 08, 2009 at 11:18:44AM +0000, Daniel P. Berrange wrote: > On Thu, Jan 08, 2009 at 01:13:56PM +0200, Pasi K?rkk?inen wrote: > > On Mon, Jan 05, 2009 at 10:15:36PM +0100, Gerd Hoffmann wrote: > > > Pasi K?rkk?inen wrote: > > > > Hello! > > > > > > > > Xen 3.3.1 has been released with a lot a of fixes so it would be nice to get > > > > xen hypervisor/tools/libs packages updated in fedora. > > > > > > > > Xen 3.3.1 does not yet contain pv_ops dom0 support fixes/patches from > > > > xen-unstable, so those backported patches in 3.3.0-2 are still needed for > > > > 3.3.1. > > > > > > I've seen the announcement. > > > Doesn't build right now in rawhide due to bug #478663 ... > > > > > > > Yep. > > > > kernel-2.6.29-0.18.rc0.git9.fc11 > > -------------------------------- > > * Wed Jan 7 17:00:00 2009 Jarod Wilson > > - 2.6.28-git9 > > - Should resolve broken byteorder.h issues (#478663) > > > > Let's hope that kernel version works. > > I've just succesfully done a KVM build against kernel-headers version > 2.6.29-0.19.rc0.git9.fc11, so all is working again now. > xen-3.3.1-1.fc11 ---------------- * Thu Jan 8 17:00:00 2009 Gerd Hoffmann - 3.3.1-1 - update to xen 3.3.1 release. So it seems :) -- Pasi From veillard at redhat.com Fri Jan 9 14:10:21 2009 From: veillard at redhat.com (Daniel Veillard) Date: Fri, 9 Jan 2009 15:10:21 +0100 Subject: [Fedora-xen] New Fedora virtualization list: fedora-virt Message-ID: <20090109141021.GB9484@redhat.com> As the initiator for this list, I must admit I made a mistake 3 years ago, I should have picked a list name agnostic from the hypervisor name. With the current state of Xen in Fedora recent releases it really make sense to try to correct that mistake ... it's never too late ! So https://www.redhat.com/mailman/listinfo/fedora-virt is born, I don't want to mass-subscribe people, especially as I think the current list should survive with its Xen centric focus. You can subscribe directly to the new URL above. The topic is everything concerning Fedora and virtualization including Xen. I think the current list would be a good place for people still using Fedora <= 8 with Xen, but it's just a suggestion :-) Daniel -- Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/ daniel at veillard.com | Rpmfind RPM search engine http://rpmfind.net/ http://veillard.com/ | virtualization library http://libvirt.org/ From bill at bfccomputing.com Fri Jan 9 17:48:22 2009 From: bill at bfccomputing.com (Bill McGonigle) Date: Fri, 09 Jan 2009 12:48:22 -0500 Subject: [Fedora-xen] New Fedora virtualization list: fedora-virt In-Reply-To: <20090109141021.GB9484@redhat.com> References: <20090109141021.GB9484@redhat.com> Message-ID: <49678DE6.6080103@bfccomputing.com> On 2009-01-09 9:10 AM, Daniel Veillard wrote: > I think the current list would be a good place for people > still using Fedora<= 8 with Xen, but it's just a suggestion:-) Or in a couple months the people using Xen again with F10 (probably) right? If you had decided to change this list's name I'd have had no objections. I can also subscribe to another list, make a new procmail rule, and dump the messages from both lists into the same folder, but it seems like a bunch of work replicated among n subscribers. Unless the goal is to keep down the noise from the Xen riff-raff for KVM folks. ;) Just for perspective, I'm interested in virtualization and Xen currently has the features I'm looking for; I'd guess other folks think similarly, but that's an assumption. For instance, if KVM reached a state where it was a superset of Xen and had switch-worthy benefits that's something I'd want to be reading about on this list. That's all to say I'd vote not to have balkanized fedora virtualization lists; if I need to jump through a few mailman hoops that's not a big deal even if it's not ideal. -Bill -- Bill McGonigle, Owner Work: 603.448.4440 BFC Computing, LLC Home: 603.448.1668 bill at bfccomputing.com Cell: 603.252.2606 http://www.bfccomputing.com/ Page: 603.442.1833 Blog: http://blog.bfccomputing.com/ VCard: http://bfccomputing.com/vcard/bill.vcf From berrange at redhat.com Fri Jan 9 17:52:50 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 9 Jan 2009 17:52:50 +0000 Subject: [Fedora-xen] New Fedora virtualization list: fedora-virt In-Reply-To: <49678DE6.6080103@bfccomputing.com> References: <20090109141021.GB9484@redhat.com> <49678DE6.6080103@bfccomputing.com> Message-ID: <20090109175250.GD8246@redhat.com> On Fri, Jan 09, 2009 at 12:48:22PM -0500, Bill McGonigle wrote: > On 2009-01-09 9:10 AM, Daniel Veillard wrote: > > I think the current list would be a good place for people > >still using Fedora<= 8 with Xen, but it's just a suggestion:-) > > Or in a couple months the people using Xen again with F10 (probably) right? Depends if Dom0 patches are accepted into 2.6.29 kernel or not and then whether that kernel is stable enough for a F10 update... > If you had decided to change this list's name I'd have had no > objections. I can also subscribe to another list, make a new procmail > rule, and dump the messages from both lists into the same folder, but it > seems like a bunch of work replicated among n subscribers. Unless the > goal is to keep down the noise from the Xen riff-raff for KVM folks. ;) Sadly changing mailing list names is effectively impossible with Mailman :-( Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From dlbewley at lib.ucdavis.edu Sat Jan 10 18:49:14 2009 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Sat, 10 Jan 2009 10:49:14 -0800 Subject: [Fedora-xen] New Fedora virtualization list: fedora-virt In-Reply-To: <20090109175250.GD8246@redhat.com> References: <20090109141021.GB9484@redhat.com> <49678DE6.6080103@bfccomputing.com> <20090109175250.GD8246@redhat.com> Message-ID: <1231613354.4458.21.camel@seitan.home.bewley.net> On Fri, 2009-01-09 at 17:52 +0000, Daniel P. Berrange wrote: > Sadly changing mailing list names is effectively impossible with > Mailman :-( I'm not sure if it's a good idea to rename a list with so many long referenced archived postings. If anything, perhaps the list should be deprecated or ignored until the Xen traffic on @fedora-virt becomes onerous (or not). Renaming a list is annoying, but mechanically not too hard. Here are my notes from the last time I successfully did it to a private list. I swapped in the fedora names for my names. I use postfix. cd /var/lib/mailman/lists mv fedora-xen fedora-virt cd /var/lib/mailman/archives/private mv fedora-xen fedora-virt mv fedora-xen.mbox fedora-virt.mbox mv fedora-virt.mbox/fedora-xen.mbox fedora-virt.mbox/fedora-virt.mbox /usr/lib/mailman/bin/arch fedora-virt cd /etc/mailman perl -pi -e 's/fedora-xen/fedora-virt/g' virtual-mailman postmap virtual-mailman perl -pi -e 's/fedora-xen/fedora-virt/g' aliases postalias aliases Login to http://hostname/mailman/admin/fedora-virt and change all occurrences of fedora-xen to fedora-virt. Changes made under General Options. http://www.gnu.org/software/mailman/faq.html From lamont at lamontpeterson.org Sun Jan 11 01:55:04 2009 From: lamont at lamontpeterson.org (Lamont Peterson) Date: Sat, 10 Jan 2009 18:55:04 -0700 Subject: [Fedora-xen] NTP problem in PAE kernel Message-ID: <200901101855.05898.lamont@lamontpeterson.org> On Saturday 03 January 2009 07:44:41 am Norman NTP wrote: > Hello, > > I have a question that we are using Fedora-8 as DOM0 and Fedora-10 as > DomU, how DomU can use by default clock of DOM0 so in that way if i > want to change the time on DomU it wont allow me to change the time on > DomU.I am using Xen Kernel on DOM0 and PAE Kernel on DomU. [snip] The system clock in a paravirtualized kernel cannot be set. The hardware clock in an HVM domU also cannot be set. The hadware clock and the system clock for paravirtualized domUs is controlled in dom0. I really like this, as I can set up NTP in dom0 and all of the clocks will be in sync in my domUs, just like that. I don't know of any way to configure a domU to be able to control it's own clock separately, other than taking out the source and updating the code to give you that option. I wouldn't bother. -- Lamont Peterson [ http://lamontpeterson.org/ ] GPG Key fingerprint: C51E DD83 B03F D147 A974 939C 5D13 289C 17F1 FFBE -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: From c.reiter at gmx.net Mon Jan 12 18:36:11 2009 From: c.reiter at gmx.net (Christian Reiter) Date: Mon, 12 Jan 2009 19:36:11 +0100 Subject: [Fedora-xen] unsubscribe Message-ID: <496B8D9B.7060706@gmx.net> Mit freundlichen Gr??en, /// Kind Regards, Christian Reiter -- Christian Reiter ||| c.reiter at gmx.net -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2840 bytes Desc: S/MIME Cryptographic Signature URL: From ondrejj at salstar.sk Tue Jan 13 08:42:43 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Tue, 13 Jan 2009 09:42:43 +0100 Subject: [Fedora-xen] Xen disks are read-only after some time. Message-ID: <20090113084243.GX544@salstar.sk> Hello, I have problems to run Fedora 10 guests on Fedora 8 dom0. My servers are running some time, but then they was unable to write changes to disks. There is nothing special in logs or dmesg. This happens aprox 24-48 hours after restart. When trying to log anything to disk, after reboot this is gone. I can log it over network, but don't know what to log. Can somebody help me to debug this problem? My problem was reported on RH and kernel bugzillas: https://bugzilla.redhat.com/show_bug.cgi?id=478414 http://bugzilla.kernel.org/show_bug.cgi?id=12331 but without any answer. :( May be there is something similar like in this thread: http://lkml.indiana.edu/hypermail/linux/kernel/0901.0/00121.html, just on my server there is only ext3, not ext4. Also trying to turn off daily backups (which uses snapshots) without success. After reboot to fc8 kernel everything is running fine again, but running fc8 kernel on fc10 is not a good solution (except that F8 is EOL). Thank you. SAL From markmc at redhat.com Wed Jan 14 08:14:29 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Wed, 14 Jan 2009 08:14:29 +0000 Subject: [Fedora-xen] Turning off virt-manager dhcp and dns In-Reply-To: <4910E118.1050508@talktalk.net> References: <4910E118.1050508@talktalk.net> Message-ID: <1231920869.4944.1.camel@localhost.localdomain> Hi, A late reply - just came across the question when searching for something else. On Tue, 2008-11-04 at 23:56 +0000, Stephen Johnston wrote: > I have virt-manager with a static ip'ed windows server 2003 and a win xp > client so I can play with active directory etc for work. All under > Fedora 10 beta. > > Can someone tell me if I can turn off the dhcp and dns in the > virt-manager framework (vibr0) as it is handing out an ip to my client > before the virtual windows server does. I believe this is confusing the > issue when I try to join the client to my virtual windows domain. > > I only wish the virt-manager to nat vibr0 to my physical nic so i can > provide the other config items from within my virtual network. You could try "virsh net-edit default" and take out the section. Probably need to do a "virsh net-destroy default" and "virsh net-start default" for it to take effect. Cheers, Mark. From jswanson at valuecommerce.co.jp Fri Jan 16 09:02:33 2009 From: jswanson at valuecommerce.co.jp (Jon Swanson) Date: Fri, 16 Jan 2009 18:02:33 +0900 Subject: [Fedora-xen] f10 x86_64 xen VM guests fail to boot on f8 host Message-ID: This is a cross post of the same subject on the Fedora Forums. If this is bad practice let me know and i'll never do it again. Additional log info is available at http://forums.fedoraforum.org/showthread.php?p=1149972&posted=1#post1149 972 I have two machines running fresh installs of f8 with the xen. Kernel and all software versions are the same on both. Specifically: [root at machineA boot]# uname -a Linux machineA 2.6.21.7-5.fc8xen #1 SMP Thu Aug 7 12:44:22 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux [root at machineA boot]# virsh version Compiled against library: libvir 0.4.4 Using library: libvir 0.4.4 Using API: Xen 3.0.1 Running hypervisor: Xen 3.1.0 And: [root at machineB ~]# uname -a Linux machineB 2.6.21.7-5.fc8xen #1 SMP Thu Aug 7 12:44:22 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux [root at machineB ~]# virsh version Compiled against library: libvir 0.4.4 Using library: libvir 0.4.4 Using API: Xen 3.0.1 Running hypervisor: Xen 3.1.0 MachineA has two AMD Opteron 275s. MachineB has four Intel(R) Xeon(TM) CPU 2.80GHz processors. Both machines are as up to date as possible. I can boot or create x86_64 f10 guests on MachineA with no trouble whatsoever. MachineB will not boot/create x86_64 f10 guests. The configuration files are created in the same manner, but as soon as Xen tries to unpause the newly created domain, it crashes pretty much instantly. /var/log/xen/xend.log relevant output: [2009-01-16 14:45:32 4120] DEBUG (DevController:150) Waiting for devices vtpm. [2009-01-16 14:45:32 4120] INFO (XendDomain:1130) Domain f10testB (21) unpaused. [2009-01-16 14:45:32 4120] WARNING (XendDomainInfo:1203) Domain has crashed: name=f10testB id=21. [2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1802) XendDomainInfo.destroy: domid=21 [2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1821) XendDomainInfo.destroyDomain(21) I've also tried moving a functional guest from MachineA to MachineB to boot it there, with the same results. Guest will not boot on MachineB. f8 64bit guests will boot on MachineB with no problems. f10 32bit guests will boot on MachineB with no problems. Only 64bit machines seem to be borked. Any information / help / insight as to why this is happening would be very much appreciated. The machines are pretty similar, and since the guests are paravirtualized it does not really make sense for the processors to be the cause of the problem. Thanks, jon From markmc at redhat.com Fri Jan 16 10:33:59 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Fri, 16 Jan 2009 10:33:59 +0000 Subject: [Fedora-xen] f10 x86_64 xen VM guests fail to boot on f8 host In-Reply-To: References: Message-ID: <1232102039.4479.80.camel@blaa> Hi Jon, On Fri, 2009-01-16 at 18:02 +0900, Jon Swanson wrote: > This is a cross post of the same subject on the Fedora Forums. If this > is bad practice let me know and i'll never do it again. Mailing lists can often be a better way to get help from developers, so posting here is no problem. Also, fedora-virt at redhat.com might be a better place to post questions these days - it's not clear whether the fedora-xen list has a future. > Additional log info is available at > http://forums.fedoraforum.org/showthread.php?p=1149972&posted=1#post1149 > 972 > > I have two machines running fresh installs of f8 with the xen. Kernel > and all software versions are the same on both. You've seen this then, right? http://fedoraproject.org/wiki/Bugs/F10Common#Installing_Fedora_10_DomU_on_Fedora_8_Dom0_Fails > /var/log/xen/xend.log relevant output: > > [2009-01-16 14:45:32 4120] DEBUG (DevController:150) Waiting for devices > vtpm. > [2009-01-16 14:45:32 4120] INFO (XendDomain:1130) Domain f10testB (21) > unpaused. > [2009-01-16 14:45:32 4120] WARNING (XendDomainInfo:1203) Domain has > crashed: name=f10testB id=21. > [2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1802) > XendDomainInfo.destroy: domid=21 > [2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1821) > XendDomainInfo.destroyDomain(21) > I've also tried moving a functional guest from MachineA to MachineB to > boot it there, with the same results. Guest will not boot on MachineB. > > f8 64bit guests will boot on MachineB with no problems. > f10 32bit guests will boot on MachineB with no problems. > > Only 64bit machines seem to be borked. Okay, sounds like it might "just" be a F10 kernel bug. Try doing this to get a stack trace: 1) Set "on_crash=preserve" in your domain config 2) Copy the guest kernel's System.map to the host 2) Once the guest has crashed, run: /usr/lib/xen/bin/xenctx -s System.map Cheers, Mark. From phillb at webwombat.com.au Fri Jan 16 07:10:32 2009 From: phillb at webwombat.com.au (Phillip Bertolus) Date: Fri, 16 Jan 2009 18:10:32 +1100 Subject: [Fedora-xen] FC10 domu FC8 x86_64 with/without HVM support (possible bug) Message-ID: <1232089832.20050.45.camel@phills901.wwoffice.com.au> Hi list, Just finished confirming that a PV FC10 domu won't run on FC8 without VT support. Background: Create FC8 domu x86_64. Yum upgrade to FC10 x86_64. FC8 domu runs on both hosts. FC10 domu runs only on host with VT support. FC10 runs on both with the old FC8 kernel. Both hosts indicate they are running pvm images: xc_dom_compat_check: supported guest type: xen-3.0-x86_64 <= matches however (and this may have nothing to do with anything): elf_xen_parse_note: HV_START_LOW = 0xffff800000000000 Any help most appreciated. We have lots of 64 bit servers without hardware virtualization support. Cheers Phill Machine host 1) Doesn't work (no VT in this processor). Linux office64 2.6.21.7-5.fc8xen #1 SMP Thu Aug 7 12:44:22 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux processor : 1 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Xeon(TM) CPU 3.00GHz stepping : 3 cpu MHz : 3000.106 cache size : 2048 KB physical id : 1 siblings : 1 core id : 0 cpu cores : 1 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall lm constant_tsc up pni monitor ds_cpl cid cx16 xtpr bogomips : 6007.27 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 48 bits virtual power management: [ root at office64 xen ]# rpm -qa | grep xen kernel-xen-devel-2.6.21.7-5.fc8 xen-libs-3.1.2-5.fc8 kernel-xen-2.6.21.7-5.fc8 xen-3.1.2-5.fc8 Some lines from the domain-builder-ng.log: arch_setup_bootearly: doing nothing xc_dom_compat_check: supported guest type: xen-3.0-x86_64 <= matches xc_dom_compat_check: supported guest type: xen-3.0-x86_32p xc_dom_update_guest_p2m: dst 64bit, pages 0x40000 xend.log [2009-01-16 17:55:53 30586] DEBUG (XendDomainInfo:2116) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '839a0c0f-a332-f38c-63ef-834563cde36a', 'on_reboot': 'restart', 'start_time': '1232088953.4', 'on_poweroff': 'destr oy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'vcpus': '1', 'vcpu_avail': '1', 'image': "(linux (kernel ) (notes (H V_START_LOW 18446603336221196288) (FEATURES '!writable_page_tables|pae_pgdir_above_4gb') (VIRT_BASE 18446744071562067968) (G UEST_VERSION 2.6) (PADDR_OFFSET 0) (GUEST_OS linux) (HYPERCALL_PAGE 18446744071578882048) (LOADER generic) (SUSPEND_CANCEL 1 ) (PAE_MODE yes) (ENTRY 18446744071584739840) (XEN_VERSION xen-3.0)))", 'name': 'f10.reference'} [2009-01-16 17:55:53 30586] DEBUG (XendDomainInfo:956) Storing domain details: {'console/ring-ref': '1347740', 'image/entry' : '18446744071584739840', 'console/port': '2', 'store/ring-ref': '1347741', 'image/loader': 'generic', 'vm': '/vm/839a0c0f-a 332-f38c-63ef-834563cde36a', 'control/platform-feature-multiprocessor-suspend': '1', 'image/hv-start-low': '1844660333622119 6288', 'image/guest-os': 'linux', 'image/virt-base': '18446744071562067968', 'memory/target': '1048576', 'image/guest-versio n': '2.6', 'image/pae-mode': 'yes', 'console/limit': '1048576', 'image/paddr-offset': '0', 'image/hypercall-page': '18446744 071578882048', 'image/suspend-cancel': '1', 'cpu/0/availability': 'online', 'image/features/pae-pgdir-above-4gb': '1', 'imag e/features/writable-page-tables': '0', 'name': 'f10.reference', 'domid': '110', 'image/xen-version': 'xen-3.0', 'store/port' : '1'} [2009-01-16 17:55:53 30586] WARNING (XendDomainInfo:1203) Domain has crashed: name=f10.reference id=110. [2009-01-16 17:55:53 30586] ERROR (XendDomainInfo:1317) Xend failed during restart of domain 110. Refusing to restart to av oid loops. [2009-01-16 17:55:53 30586] DEBUG (XendDomainInfo:1802) XendDomainInfo.destroy: domid=110 [2009-01-16 17:55:53 30586] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch =========================== Machine host 2) Does work. Linux seanl64 2.6.21.7-5.fc8xen #1 SMP Thu Aug 7 12:44:22 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 107 model name : AMD Athlon(tm) 64 X2 Dual Core Processor 3600+ stepping : 1 cpu MHz : 1908.705 cache size : 512 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 syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy misalignsse bogomips : 3819.31 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 100mhzsteps [root at seanl64 ~]# rpm -qa | grep xen kernel-xen-2.6.21.7-3.fc8 xen-libs-3.1.2-5.fc8 xen-3.1.2-5.fc8 kernel-xen-2.6.21.7-5.fc8 Some lines from the domain-builder-ng.log: arch_setup_bootearly: doing nothing xc_dom_compat_check: supported guest type: xen-3.0-x86_64 <= matches xc_dom_compat_check: supported guest type: xen-3.0-x86_32p xc_dom_compat_check: supported guest type: hvm-3.0-x86_32 xc_dom_compat_check: supported guest type: hvm-3.0-x86_32p xc_dom_compat_check: supported guest type: hvm-3.0-x86_64 xc_dom_update_guest_p2m: dst 64bit, pages 0x40000 >From the domu: Fedora release 10 (Cambridge) Kernel 2.6.27.9-159.fc10.x86_64 on an x86_64 (/dev/hvc0) localhost.localdomain login: From virtualization at webwombat.com.au Tue Jan 20 01:22:31 2009 From: virtualization at webwombat.com.au (Virtualization) Date: Tue, 20 Jan 2009 12:22:31 +1100 Subject: [Fedora-xen] f10 x86_64 xen VM guests fail to boot on f8 host In-Reply-To: <1232102039.4479.80.camel@blaa> References: <1232102039.4479.80.camel@blaa> Message-ID: <1232414551.2995.7.camel@phills901.wwoffice.com.au> Hi Mark, I ran the adjusted commands on our system here with the Intel CPU (which crashes in the same way as Jon's machine): [root at office64 boot]# /usr/lib64/xen/bin/xenctx -s System.map-2.6.27.9-159.fc10.x86_64 114 rip: ffffffff8100b8a2 set_page_prot+0x6d rsp: ffffffff81575f08 rax: ffffffea rbx: 000016e4 rcx: 00000055 rdx: 00000000 rsi: 800000010c2b3061 rdi: ffffffff816e4000 rbp: ffffffff81575f68 r8: 0000000f r9: ffffffff817ee350 r10: ffffffff817ee550 r11: 00000010 r12: ffffffff816e4000 r13: 800000010c2b3061 r14: 8000000000000161 r15: 00002c00 cs: 0000e033 ds: 00000000 fs: 00000000 gs: 00000000 Stack: 0000000000000055 0000000000000010 ffffffff8100b8a2 000000010000e030 0000000000010082 ffffffff81575f48 000000000000e02b ffffffff8100b89e 0000000000000200 ffffffff816e7000 0000000000000800 0000000000000016 ffffffff81575ff8 ffffffff815a5c60 0000000000002c00 0000000000000000 Code: df 54 1d 00 4c 89 e7 4c 89 ee 31 d2 e8 22 d9 ff ff 85 c0 74 04 <0f> 0b eb fe 5b 41 5c 41 5d 41 5e Call Trace: [] set_page_prot+0x6d <-- [] set_page_prot+0x6d [] set_page_prot+0x69 [] xen_start_kernel+0x5dd Cheers hope this helps Phill On Fri, 2009-01-16 at 10:33 +0000, Mark McLoughlin wrote: > Hi Jon, > > On Fri, 2009-01-16 at 18:02 +0900, Jon Swanson wrote: > > This is a cross post of the same subject on the Fedora Forums. If this > > is bad practice let me know and i'll never do it again. > > Mailing lists can often be a better way to get help from developers, so > posting here is no problem. > > Also, fedora-virt at redhat.com might be a better place to post questions > these days - it's not clear whether the fedora-xen list has a future. > > > Additional log info is available at > > http://forums.fedoraforum.org/showthread.php?p=1149972&posted=1#post1149 > > 972 > > > > I have two machines running fresh installs of f8 with the xen. Kernel > > and all software versions are the same on both. > > You've seen this then, right? > > http://fedoraproject.org/wiki/Bugs/F10Common#Installing_Fedora_10_DomU_on_Fedora_8_Dom0_Fails > > > /var/log/xen/xend.log relevant output: > > > > [2009-01-16 14:45:32 4120] DEBUG (DevController:150) Waiting for devices > > vtpm. > > [2009-01-16 14:45:32 4120] INFO (XendDomain:1130) Domain f10testB (21) > > unpaused. > > [2009-01-16 14:45:32 4120] WARNING (XendDomainInfo:1203) Domain has > > crashed: name=f10testB id=21. > > [2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1802) > > XendDomainInfo.destroy: domid=21 > > [2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1821) > > XendDomainInfo.destroyDomain(21) > > I've also tried moving a functional guest from MachineA to MachineB to > > boot it there, with the same results. Guest will not boot on MachineB. > > > > f8 64bit guests will boot on MachineB with no problems. > > f10 32bit guests will boot on MachineB with no problems. > > > > Only 64bit machines seem to be borked. > > Okay, sounds like it might "just" be a F10 kernel bug. > > Try doing this to get a stack trace: > > 1) Set "on_crash=preserve" in your domain config > > 2) Copy the guest kernel's System.map to the host > > 2) Once the guest has crashed, run: > > /usr/lib/xen/bin/xenctx -s System.map > > Cheers, > Mark. > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From jswanson at valuecommerce.co.jp Tue Jan 20 05:01:41 2009 From: jswanson at valuecommerce.co.jp (Jon Swanson) Date: Tue, 20 Jan 2009 14:01:41 +0900 Subject: [Fedora-xen] f10 x86_64 xen VM guests fail to boot on f8 host References: <1232102039.4479.80.camel@blaa> Message-ID: Hi Mark, thank you very much for your help. I took an f10host which boots on MachineA and copied it to MachineB, modified the config to include on_crash=preserve, and booted it with xm create. ------------------------------------------------------------------------ ------------------------------------------------ xenctx output: /usr/lib64/xen/bin/xenctx -s System.map-2.6.27.5-117.fc10.x86_64 46 rip: ffffffff8100b8a2 set_page_prot+0x6d rsp: ffffffff81573f08 rax: ffffffea rbx: 000016e1 rcx: 00000055 rdx: 00000000 rsi: 800000014ffc6061 rdi: ffffffff816e1000 rbp: ffffffff81573f68 r8: 0000000f r9: ffffffff817eb450 r10: ffffffff817eb650 r11: 00000010 r12: ffffffff816e1000 r13: 800000014ffc6061 r14: 8000000000000161 r15: 00000016 cs: 0000e033 ds: 00000000 fs: 00000000 gs: 00000000 Stack: 0000000000000055 0000000000000010 ffffffff8100b8a2 000000010000e030 0000000000010082 ffffffff81573f48 000000000000e02b ffffffff8100b89e 0000000000000200 ffffffff816e4000 0000000000000800 0000000000002c00 ffffffff81573ff8 ffffffff815a3c60 0000000000002c00 0000000000000000 Code: 7b 4a 1d 00 4c 89 e7 4c 89 ee 31 d2 e8 22 d9 ff ff 85 c0 74 04 <0f> 0b eb fe 5b 41 5c 41 5d 41 5e Call Trace: [] set_page_prot+0x6d <-- [] set_page_prot+0x6d [] set_page_prot+0x69 [] xen_start_kernel+0x5dd ------------------------------------------------------------------------ ------------------------------------------------ Dmesg also has something which may make sense to someone wiser than myself. Specifically: (XEN) traps.c:405:d46 Unhandled invalid opcode fault/trap [#6] in domain 46 on VCPU 0 [ec=0000] xm dmesg .... (XEN) ffffffff82035000 ffffffff82036000 ffffffff82037000 ffffffff82038000 (XEN) mm.c:1362:d46 Bad L1 flags 800000 (XEN) traps.c:405:d46 Unhandled invalid opcode fault/trap [#6] in domain 46 on VCPU 0 [ec=0000] (XEN) domain_crash_sync called from entry.S (XEN) Domain 46 (vcpu#0) crashed on cpu#2: (XEN) ----[ Xen-3.1.4 x86_64 debug=n Not tainted ]---- (XEN) CPU: 2 (XEN) RIP: e033:[] (XEN) RFLAGS: 0000000000000282 CONTEXT: guest (XEN) rax: 00000000ffffffea rbx: 00000000000016e1 rcx: 0000000000000055 (XEN) rdx: 0000000000000000 rsi: 800000014ffc6061 rdi: ffffffff816e1000 (XEN) rbp: ffffffff81573f68 rsp: ffffffff81573f08 r8: 000000000000000f (XEN) r9: ffffffff817eb450 r10: ffffffff817eb650 r11: 0000000000000010 (XEN) r12: ffffffff816e1000 r13: 800000014ffc6061 r14: 8000000000000161 (XEN) r15: 0000000000000016 cr0: 000000008005003b cr4: 00000000000006f0 (XEN) cr3: 0000000144f18000 cr2: 0000000000000000 (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 (XEN) Guest stack trace from rsp=ffffffff81573f08: (XEN) 0000000000000055 0000000000000010 ffffffff8100b8a2 000000010000e030 (XEN) 0000000000010082 ffffffff81573f48 000000000000e02b ffffffff8100b89e (XEN) 0000000000000200 ffffffff816e4000 0000000000000800 0000000000002c00 (XEN) ffffffff81573ff8 ffffffff815a3c60 0000000000002c00 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 ffffffff8208b000 (XEN) 0000000000010000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000 (XEN) 0000000000000000 0000000000000000 0000000000000000 ffffffff82008000 (XEN) ffffffff82009000 ffffffff8200a000 ffffffff8200b000 ffffffff8200c000 (XEN) ffffffff8200d000 ffffffff8200e000 ffffffff8200f000 ffffffff82010000 (XEN) ffffffff82011000 ffffffff82012000 ffffffff82013000 ffffffff82014000 (XEN) ffffffff82015000 ffffffff82016000 ffffffff82017000 ffffffff82018000 (XEN) ffffffff82019000 ffffffff8201a000 ffffffff8201b000 ffffffff8201c000 (XEN) ffffffff8201d000 ffffffff8201e000 ffffffff8201f000 ffffffff82020000 (XEN) ffffffff82021000 ffffffff82022000 ffffffff82023000 ffffffff82024000 (XEN) ffffffff82025000 ffffffff82026000 ffffffff82027000 ffffffff82028000 (XEN) ffffffff82029000 ffffffff8202a000 ffffffff8202b000 ffffffff8202c000 (XEN) ffffffff8202d000 ffffffff8202e000 ffffffff8202f000 ffffffff82030000 (XEN) ffffffff82031000 ffffffff82032000 ffffffff82033000 ffffffff82034000 (XEN) ffffffff82035000 ffffffff82036000 ffffffff82037000 ffffffff82038000 ... ------------------------------------------------------------------------ ------------------------------------------------ -----Original Message----- From: Mark McLoughlin [mailto:markmc at redhat.com] Sent: Friday, January 16, 2009 7:34 PM To: Jon Swanson Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] f10 x86_64 xen VM guests fail to boot on f8 host Hi Jon, On Fri, 2009-01-16 at 18:02 +0900, Jon Swanson wrote: > This is a cross post of the same subject on the Fedora Forums. If > this is bad practice let me know and i'll never do it again. Mailing lists can often be a better way to get help from developers, so posting here is no problem. Also, fedora-virt at redhat.com might be a better place to post questions these days - it's not clear whether the fedora-xen list has a future. > Additional log info is available at > http://forums.fedoraforum.org/showthread.php?p=1149972&posted=1#post11 > 49 > 972 > > I have two machines running fresh installs of f8 with the xen. Kernel > and all software versions are the same on both. You've seen this then, right? http://fedoraproject.org/wiki/Bugs/F10Common#Installing_Fedora_10_DomU_o n_Fedora_8_Dom0_Fails > /var/log/xen/xend.log relevant output: > > [2009-01-16 14:45:32 4120] DEBUG (DevController:150) Waiting for > devices vtpm. > [2009-01-16 14:45:32 4120] INFO (XendDomain:1130) Domain f10testB (21) > unpaused. > [2009-01-16 14:45:32 4120] WARNING (XendDomainInfo:1203) Domain has > crashed: name=f10testB id=21. > [2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1802) > XendDomainInfo.destroy: domid=21 > [2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1821) > XendDomainInfo.destroyDomain(21) > I've also tried moving a functional guest from MachineA to MachineB to > boot it there, with the same results. Guest will not boot on MachineB. > > f8 64bit guests will boot on MachineB with no problems. > f10 32bit guests will boot on MachineB with no problems. > > Only 64bit machines seem to be borked. Okay, sounds like it might "just" be a F10 kernel bug. Try doing this to get a stack trace: 1) Set "on_crash=preserve" in your domain config 2) Copy the guest kernel's System.map to the host 2) Once the guest has crashed, run: /usr/lib/xen/bin/xenctx -s System.map Cheers, Mark. From virtualization at webwombat.com.au Tue Jan 20 06:18:48 2009 From: virtualization at webwombat.com.au (Virtualization) Date: Tue, 20 Jan 2009 17:18:48 +1100 Subject: [Fedora-xen] f10 x86_64 xen VM guests fail to boot on f8 host In-Reply-To: References: <1232102039.4479.80.camel@blaa> Message-ID: <1232432328.2995.35.camel@phills901.wwoffice.com.au> Hi list, >From the Intel? Virtualization Technology Specification for the IA-32 Intel? Architecture (2005): "2.9.2 Information for VM Exits Due to Vectored Events Event-specific information is provided for VM exits due to the following vectored events: exceptions (including those generated by the instructions INT3, INTO, BOUND, and UD2); external interrupts that occur while the ?acknowledge interrupt on exit? VM-exit control is 1; and non-maskable interrupts (NMIs). This information is provided in the following fields:" .... The <0f> 0b in the "Code:" section are the UD2 instruction. Checking through the OpCode map for the Xeon processor, this is an invalid op code. In VT processors the software guide indicates that a program can communicate various events and state information to the underlying virtualization supervisor by executing a UD2 (and some others ops like it). I think that in a non-VT cpu it's actually a "real" invalid op code. The stuff (hardware) which flips over to the supervisor with all the needed info from the virtual machine isn't there. KVM uses this, from the patches I've seen Googling around for UD2 (if I understand correctly). So why a UD2 in the code? It's highly unlikely that it's just some random bytes that happen to be a UD2. Possibly the kernel thinks it's in fully virt mode at some point? The image notes do seem to indicate this. Cheers Phill. On Tue, 2009-01-20 at 14:01 +0900, Jon Swanson wrote: > Hi Mark, thank you very much for your help. > > I took an f10host which boots on MachineA and copied it to MachineB, > modified the config to include on_crash=preserve, and booted it with xm > create. > ------------------------------------------------------------------------ > ------------------------------------------------ > xenctx output: > /usr/lib64/xen/bin/xenctx -s System.map-2.6.27.5-117.fc10.x86_64 46 > rip: ffffffff8100b8a2 set_page_prot+0x6d > rsp: ffffffff81573f08 > rax: ffffffea rbx: 000016e1 rcx: 00000055 rdx: 00000000 > rsi: 800000014ffc6061 rdi: ffffffff816e1000 rbp: ffffffff81573f68 > r8: 0000000f r9: ffffffff817eb450 r10: ffffffff817eb650 r11: > 00000010 > r12: ffffffff816e1000 r13: 800000014ffc6061 r14: 8000000000000161 > r15: 00000016 > cs: 0000e033 ds: 00000000 fs: 00000000 gs: 00000000 > > Stack: > 0000000000000055 0000000000000010 ffffffff8100b8a2 000000010000e030 > 0000000000010082 ffffffff81573f48 000000000000e02b ffffffff8100b89e > 0000000000000200 ffffffff816e4000 0000000000000800 0000000000002c00 > ffffffff81573ff8 ffffffff815a3c60 0000000000002c00 0000000000000000 > > Code: > 7b 4a 1d 00 4c 89 e7 4c 89 ee 31 d2 e8 22 d9 ff ff 85 c0 74 04 <0f> 0b > eb fe 5b 41 5c 41 5d 41 5e > > Call Trace: > [] set_page_prot+0x6d <-- > [] set_page_prot+0x6d > [] set_page_prot+0x69 > [] xen_start_kernel+0x5dd > > > ------------------------------------------------------------------------ > ------------------------------------------------ > Dmesg also has something which may make sense to someone wiser than > myself. Specifically: > (XEN) traps.c:405:d46 Unhandled invalid opcode fault/trap [#6] in domain > 46 on VCPU 0 [ec=0000] > > > xm dmesg > .... > (XEN) ffffffff82035000 ffffffff82036000 ffffffff82037000 > ffffffff82038000 > (XEN) mm.c:1362:d46 Bad L1 flags 800000 > (XEN) traps.c:405:d46 Unhandled invalid opcode fault/trap [#6] in domain > 46 on VCPU 0 [ec=0000] > (XEN) domain_crash_sync called from entry.S > (XEN) Domain 46 (vcpu#0) crashed on cpu#2: > (XEN) ----[ Xen-3.1.4 x86_64 debug=n Not tainted ]---- > (XEN) CPU: 2 > (XEN) RIP: e033:[] > (XEN) RFLAGS: 0000000000000282 CONTEXT: guest > (XEN) rax: 00000000ffffffea rbx: 00000000000016e1 rcx: > 0000000000000055 > (XEN) rdx: 0000000000000000 rsi: 800000014ffc6061 rdi: > ffffffff816e1000 > (XEN) rbp: ffffffff81573f68 rsp: ffffffff81573f08 r8: > 000000000000000f > (XEN) r9: ffffffff817eb450 r10: ffffffff817eb650 r11: > 0000000000000010 > (XEN) r12: ffffffff816e1000 r13: 800000014ffc6061 r14: > 8000000000000161 > (XEN) r15: 0000000000000016 cr0: 000000008005003b cr4: > 00000000000006f0 > (XEN) cr3: 0000000144f18000 cr2: 0000000000000000 > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 > (XEN) Guest stack trace from rsp=ffffffff81573f08: > (XEN) 0000000000000055 0000000000000010 ffffffff8100b8a2 > 000000010000e030 > (XEN) 0000000000010082 ffffffff81573f48 000000000000e02b > ffffffff8100b89e > (XEN) 0000000000000200 ffffffff816e4000 0000000000000800 > 0000000000002c00 > (XEN) ffffffff81573ff8 ffffffff815a3c60 0000000000002c00 > 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0000000000000000 > ffffffff8208b000 > (XEN) 0000000000010000 0000000000000000 0000000000000000 > 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0000000000000000 > 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0000000000000000 > ffffffff82008000 > (XEN) ffffffff82009000 ffffffff8200a000 ffffffff8200b000 > ffffffff8200c000 > (XEN) ffffffff8200d000 ffffffff8200e000 ffffffff8200f000 > ffffffff82010000 > (XEN) ffffffff82011000 ffffffff82012000 ffffffff82013000 > ffffffff82014000 > (XEN) ffffffff82015000 ffffffff82016000 ffffffff82017000 > ffffffff82018000 > (XEN) ffffffff82019000 ffffffff8201a000 ffffffff8201b000 > ffffffff8201c000 > (XEN) ffffffff8201d000 ffffffff8201e000 ffffffff8201f000 > ffffffff82020000 > (XEN) ffffffff82021000 ffffffff82022000 ffffffff82023000 > ffffffff82024000 > (XEN) ffffffff82025000 ffffffff82026000 ffffffff82027000 > ffffffff82028000 > (XEN) ffffffff82029000 ffffffff8202a000 ffffffff8202b000 > ffffffff8202c000 > (XEN) ffffffff8202d000 ffffffff8202e000 ffffffff8202f000 > ffffffff82030000 > (XEN) ffffffff82031000 ffffffff82032000 ffffffff82033000 > ffffffff82034000 > (XEN) ffffffff82035000 ffffffff82036000 ffffffff82037000 > ffffffff82038000 > ... > > ------------------------------------------------------------------------ > ------------------------------------------------ > > > -----Original Message----- > From: Mark McLoughlin [mailto:markmc at redhat.com] > Sent: Friday, January 16, 2009 7:34 PM > To: Jon Swanson > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] f10 x86_64 xen VM guests fail to boot on f8 > host > > Hi Jon, > > On Fri, 2009-01-16 at 18:02 +0900, Jon Swanson wrote: > > This is a cross post of the same subject on the Fedora Forums. If > > this is bad practice let me know and i'll never do it again. > > Mailing lists can often be a better way to get help from developers, so > posting here is no problem. > > Also, fedora-virt at redhat.com might be a better place to post questions > these days - it's not clear whether the fedora-xen list has a future. > > > Additional log info is available at > > http://forums.fedoraforum.org/showthread.php?p=1149972&posted=1#post11 > > 49 > > 972 > > > > I have two machines running fresh installs of f8 with the xen. Kernel > > and all software versions are the same on both. > > You've seen this then, right? > > > http://fedoraproject.org/wiki/Bugs/F10Common#Installing_Fedora_10_DomU_o > n_Fedora_8_Dom0_Fails > > > /var/log/xen/xend.log relevant output: > > > > [2009-01-16 14:45:32 4120] DEBUG (DevController:150) Waiting for > > devices vtpm. > > [2009-01-16 14:45:32 4120] INFO (XendDomain:1130) Domain f10testB (21) > > > unpaused. > > [2009-01-16 14:45:32 4120] WARNING (XendDomainInfo:1203) Domain has > > crashed: name=f10testB id=21. > > [2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1802) > > XendDomainInfo.destroy: domid=21 > > [2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1821) > > XendDomainInfo.destroyDomain(21) > > I've also tried moving a functional guest from MachineA to MachineB to > > > boot it there, with the same results. Guest will not boot on MachineB. > > > > f8 64bit guests will boot on MachineB with no problems. > > f10 32bit guests will boot on MachineB with no problems. > > > > Only 64bit machines seem to be borked. > > Okay, sounds like it might "just" be a F10 kernel bug. > > Try doing this to get a stack trace: > > 1) Set "on_crash=preserve" in your domain config > > 2) Copy the guest kernel's System.map to the host > > 2) Once the guest has crashed, run: > > /usr/lib/xen/bin/xenctx -s System.map > > Cheers, > Mark. > > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From jswanson at valuecommerce.co.jp Tue Jan 20 06:34:47 2009 From: jswanson at valuecommerce.co.jp (Jon Swanson) Date: Tue, 20 Jan 2009 15:34:47 +0900 Subject: [Fedora-xen] f10 x86_64 xen VM guests fail to boot on f8 host References: <1232102039.4479.80.camel@blaa> <1232432328.2995.35.camel@phills901.wwoffice.com.au> Message-ID: Hi Phil, Most of what you said went right over my head. It sounds like processor related information may be useful though: MachineA works, MachineB does not. [root at MachineA f10copy]# egrep 'cpu fam|model|flags' /proc/cpuinfo cpu family : 15 model : 33 model name : Dual Core AMD Opteron(tm) Processor 275 flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_lm cmp_legacy ... [root at MachineB ~]# egrep 'cpu fam|model|flags' /proc/cpuinfo cpu family : 15 model : 4 model name : Intel(R) Xeon(TM) CPU 2.80GHz flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall lm constant_tsc pni monitor ds_cpl est cid cx16 xtpr lahf_lm ... I was unable to simulate the crash on MachineA, but I created the same vm with the following command: xm create -p -c f10copy.config And ran xenctx against the freshly created domain: /usr/lib64/xen/bin/xenctx -s /tmp/System.map-2.6.27.5-117.fc10.x86_64 39 rip: ffffffff810093aa _stext+0x3aa rsp: ffffffff81573ea0 rax: 00000000 rbx: ffffffff81572000 rcx: ffffffff810093aa rdx: 00000000 rsi: 00000000 rdi: 00000001 rbp: ffffffff81573eb8 r8: 00000000 r9: ffff8800020b2348 r10: 00000001 r11: 00000246 r12: 6db6db6db6db6db7 r13: ffffffff815d2660 r14: ffffffff815d4cc0 r15: 00000016 cs: 0000e033 ds: 00000000 fs: 00000000 gs: 00000000 Stack: ffffffff81766a78 0000000000000003 ffffffff8100a709 ffffffff81573ed8 ffffffff8100ba06 ffffffff81573ed8 ffffffff816d60e8 ffffffff81573ef8 ffffffff8100f279 ffffffff815d4cc0 0000000000000000 ffffffff81573f08 ffffffff8131ed7d ffffffff81573f48 ffffffff8159dd46 ffffffff81573f48 Code: cc cc cc cc cc cc cc cc cc cc cc 51 41 53 b8 1d 00 00 00 0f 05 <41> 5b 59 c3 cc cc cc cc cc cc cc Call Trace: [] _stext+0x3aa <-- [] xen_safe_halt+0x10 [] xen_idle+0x55 [] cpu_idle+0xb2 [] rest_init+0x61 [] start_kernel+0x39f [] x86_64_start_reservations+0xa5 [] xen_start_kernel+0x7e1 -----Original Message----- From: Virtualization [mailto:virtualization at webwombat.com.au] Sent: Tuesday, January 20, 2009 3:19 PM To: Jon Swanson Cc: fedora-xen at redhat.com Subject: RE: [Fedora-xen] f10 x86_64 xen VM guests fail to boot on f8 host Hi list, >From the Intel(r) Virtualization Technology Specification for the IA-32 Intel(r) Architecture (2005): "2.9.2 Information for VM Exits Due to Vectored Events Event-specific information is provided for VM exits due to the following vectored events: exceptions (including those generated by the instructions INT3, INTO, BOUND, and UD2); external interrupts that occur while the "acknowledge interrupt on exit" VM-exit control is 1; and non-maskable interrupts (NMIs). This information is provided in the following fields:" .... The <0f> 0b in the "Code:" section are the UD2 instruction. Checking through the OpCode map for the Xeon processor, this is an invalid op code. In VT processors the software guide indicates that a program can communicate various events and state information to the underlying virtualization supervisor by executing a UD2 (and some others ops like it). I think that in a non-VT cpu it's actually a "real" invalid op code. The stuff (hardware) which flips over to the supervisor with all the needed info from the virtual machine isn't there. KVM uses this, from the patches I've seen Googling around for UD2 (if I understand correctly). So why a UD2 in the code? It's highly unlikely that it's just some random bytes that happen to be a UD2. Possibly the kernel thinks it's in fully virt mode at some point? The image notes do seem to indicate this. Cheers Phill. On Tue, 2009-01-20 at 14:01 +0900, Jon Swanson wrote: > Hi Mark, thank you very much for your help. > > I took an f10host which boots on MachineA and copied it to MachineB, > modified the config to include on_crash=preserve, and booted it with > xm create. > ---------------------------------------------------------------------- > -- > ------------------------------------------------ > xenctx output: > /usr/lib64/xen/bin/xenctx -s System.map-2.6.27.5-117.fc10.x86_64 46 > rip: ffffffff8100b8a2 set_page_prot+0x6d > rsp: ffffffff81573f08 > rax: ffffffea rbx: 000016e1 rcx: 00000055 rdx: 00000000 > rsi: 800000014ffc6061 rdi: ffffffff816e1000 rbp: ffffffff81573f68 > r8: 0000000f r9: ffffffff817eb450 r10: ffffffff817eb650 r11: > 00000010 > r12: ffffffff816e1000 r13: 800000014ffc6061 r14: 8000000000000161 > r15: 00000016 > cs: 0000e033 ds: 00000000 fs: 00000000 gs: 00000000 > > Stack: > 0000000000000055 0000000000000010 ffffffff8100b8a2 000000010000e030 > 0000000000010082 ffffffff81573f48 000000000000e02b ffffffff8100b89e > 0000000000000200 ffffffff816e4000 0000000000000800 0000000000002c00 > ffffffff81573ff8 ffffffff815a3c60 0000000000002c00 0000000000000000 > > Code: > 7b 4a 1d 00 4c 89 e7 4c 89 ee 31 d2 e8 22 d9 ff ff 85 c0 74 04 <0f> 0b > eb fe 5b 41 5c 41 5d 41 5e > > Call Trace: > [] set_page_prot+0x6d <-- > [] set_page_prot+0x6d > [] set_page_prot+0x69 > [] xen_start_kernel+0x5dd > > > ---------------------------------------------------------------------- > -- > ------------------------------------------------ > Dmesg also has something which may make sense to someone wiser than > myself. Specifically: > (XEN) traps.c:405:d46 Unhandled invalid opcode fault/trap [#6] in > domain > 46 on VCPU 0 [ec=0000] > > > xm dmesg > .... > (XEN) ffffffff82035000 ffffffff82036000 ffffffff82037000 > ffffffff82038000 > (XEN) mm.c:1362:d46 Bad L1 flags 800000 > (XEN) traps.c:405:d46 Unhandled invalid opcode fault/trap [#6] in > domain > 46 on VCPU 0 [ec=0000] > (XEN) domain_crash_sync called from entry.S > (XEN) Domain 46 (vcpu#0) crashed on cpu#2: > (XEN) ----[ Xen-3.1.4 x86_64 debug=n Not tainted ]---- > (XEN) CPU: 2 > (XEN) RIP: e033:[] > (XEN) RFLAGS: 0000000000000282 CONTEXT: guest > (XEN) rax: 00000000ffffffea rbx: 00000000000016e1 rcx: > 0000000000000055 > (XEN) rdx: 0000000000000000 rsi: 800000014ffc6061 rdi: > ffffffff816e1000 > (XEN) rbp: ffffffff81573f68 rsp: ffffffff81573f08 r8: > 000000000000000f > (XEN) r9: ffffffff817eb450 r10: ffffffff817eb650 r11: > 0000000000000010 > (XEN) r12: ffffffff816e1000 r13: 800000014ffc6061 r14: > 8000000000000161 > (XEN) r15: 0000000000000016 cr0: 000000008005003b cr4: > 00000000000006f0 > (XEN) cr3: 0000000144f18000 cr2: 0000000000000000 > (XEN) ds: 0000 es: 0000 fs: 0000 gs: 0000 ss: e02b cs: e033 > (XEN) Guest stack trace from rsp=ffffffff81573f08: > (XEN) 0000000000000055 0000000000000010 ffffffff8100b8a2 > 000000010000e030 > (XEN) 0000000000010082 ffffffff81573f48 000000000000e02b > ffffffff8100b89e > (XEN) 0000000000000200 ffffffff816e4000 0000000000000800 > 0000000000002c00 > (XEN) ffffffff81573ff8 ffffffff815a3c60 0000000000002c00 > 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0000000000000000 > ffffffff8208b000 > (XEN) 0000000000010000 0000000000000000 0000000000000000 > 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0000000000000000 > 0000000000000000 > (XEN) 0000000000000000 0000000000000000 0000000000000000 > ffffffff82008000 > (XEN) ffffffff82009000 ffffffff8200a000 ffffffff8200b000 > ffffffff8200c000 > (XEN) ffffffff8200d000 ffffffff8200e000 ffffffff8200f000 > ffffffff82010000 > (XEN) ffffffff82011000 ffffffff82012000 ffffffff82013000 > ffffffff82014000 > (XEN) ffffffff82015000 ffffffff82016000 ffffffff82017000 > ffffffff82018000 > (XEN) ffffffff82019000 ffffffff8201a000 ffffffff8201b000 > ffffffff8201c000 > (XEN) ffffffff8201d000 ffffffff8201e000 ffffffff8201f000 > ffffffff82020000 > (XEN) ffffffff82021000 ffffffff82022000 ffffffff82023000 > ffffffff82024000 > (XEN) ffffffff82025000 ffffffff82026000 ffffffff82027000 > ffffffff82028000 > (XEN) ffffffff82029000 ffffffff8202a000 ffffffff8202b000 > ffffffff8202c000 > (XEN) ffffffff8202d000 ffffffff8202e000 ffffffff8202f000 > ffffffff82030000 > (XEN) ffffffff82031000 ffffffff82032000 ffffffff82033000 > ffffffff82034000 > (XEN) ffffffff82035000 ffffffff82036000 ffffffff82037000 > ffffffff82038000 > ... > > ---------------------------------------------------------------------- > -- > ------------------------------------------------ > > > -----Original Message----- > From: Mark McLoughlin [mailto:markmc at redhat.com] > Sent: Friday, January 16, 2009 7:34 PM > To: Jon Swanson > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] f10 x86_64 xen VM guests fail to boot on f8 > host > > Hi Jon, > > On Fri, 2009-01-16 at 18:02 +0900, Jon Swanson wrote: > > This is a cross post of the same subject on the Fedora Forums. If > > this is bad practice let me know and i'll never do it again. > > Mailing lists can often be a better way to get help from developers, > so posting here is no problem. > > Also, fedora-virt at redhat.com might be a better place to post questions > these days - it's not clear whether the fedora-xen list has a future. > > > Additional log info is available at > > http://forums.fedoraforum.org/showthread.php?p=1149972&posted=1#post > > 11 > > 49 > > 972 > > > > I have two machines running fresh installs of f8 with the xen. > > Kernel and all software versions are the same on both. > > You've seen this then, right? > > > http://fedoraproject.org/wiki/Bugs/F10Common#Installing_Fedora_10_DomU > _o > n_Fedora_8_Dom0_Fails > > > /var/log/xen/xend.log relevant output: > > > > [2009-01-16 14:45:32 4120] DEBUG (DevController:150) Waiting for > > devices vtpm. > > [2009-01-16 14:45:32 4120] INFO (XendDomain:1130) Domain f10testB > > (21) > > > unpaused. > > [2009-01-16 14:45:32 4120] WARNING (XendDomainInfo:1203) Domain has > > crashed: name=f10testB id=21. > > [2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1802) > > XendDomainInfo.destroy: domid=21 > > [2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1821) > > XendDomainInfo.destroyDomain(21) > > I've also tried moving a functional guest from MachineA to MachineB > > to > > > boot it there, with the same results. Guest will not boot on MachineB. > > > > f8 64bit guests will boot on MachineB with no problems. > > f10 32bit guests will boot on MachineB with no problems. > > > > Only 64bit machines seem to be borked. > > Okay, sounds like it might "just" be a F10 kernel bug. > > Try doing this to get a stack trace: > > 1) Set "on_crash=preserve" in your domain config > > 2) Copy the guest kernel's System.map to the host > > 2) Once the guest has crashed, run: > > /usr/lib/xen/bin/xenctx -s System.map > > Cheers, > Mark. > > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From markmc at redhat.com Tue Jan 20 10:05:46 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Tue, 20 Jan 2009 10:05:46 +0000 Subject: [Fedora-xen] FC10 domu FC8 x86_64 with/without HVM support (possible bug) In-Reply-To: <1232089832.20050.45.camel@phills901.wwoffice.com.au> References: <1232089832.20050.45.camel@phills901.wwoffice.com.au> Message-ID: <1232445946.24817.0.camel@blaa> Hi Phillip, On Fri, 2009-01-16 at 18:10 +1100, Phillip Bertolus wrote: > Hi list, > > Just finished confirming that a PV FC10 domu won't run on FC8 without VT > support. > > Background: > > Create FC8 domu x86_64. Yum upgrade to FC10 x86_64. > FC8 domu runs on both hosts. > FC10 domu runs only on host with VT support. > FC10 runs on both with the old FC8 kernel. > > Both hosts indicate they are running pvm images: > xc_dom_compat_check: supported guest type: xen-3.0-x86_64 <= matches > > however (and this may have nothing to do with anything): > elf_xen_parse_note: HV_START_LOW = 0xffff800000000000 > > Any help most appreciated. > > We have lots of 64 bit servers without hardware virtualization support. Does this info help? http://fedoraproject.org/wiki/Bugs/F10Common#Installing_Fedora_10_DomU_on_Fedora_8_Dom0_Fails Cheers, Mark. From avi at redhat.com Wed Jan 21 07:30:25 2009 From: avi at redhat.com (Avi Kivity) Date: Wed, 21 Jan 2009 09:30:25 +0200 Subject: [Fedora-xen] f10 x86_64 xen VM guests fail to boot on f8 host In-Reply-To: <1232432328.2995.35.camel@phills901.wwoffice.com.au> References: <1232102039.4479.80.camel@blaa> <1232432328.2995.35.camel@phills901.wwoffice.com.au> Message-ID: <4976CF11.40505@redhat.com> Virtualization wrote: > Hi list, > > >From the Intel? Virtualization Technology Specification > for the IA-32 Intel? Architecture (2005): > > "2.9.2 Information for VM Exits Due to Vectored Events > Event-specific information is provided for VM exits due to the following vectored events: > exceptions (including those generated by the instructions INT3, INTO, BOUND, and UD2); > external interrupts that occur while the ?acknowledge interrupt on exit? VM-exit control is 1; > and non-maskable interrupts (NMIs). This information is provided in the following fields:" .... > > The <0f> 0b in the "Code:" section are the UD2 instruction. > > Checking through the OpCode map for the Xeon processor, this is an > invalid op code. In VT processors the software guide indicates that a > program can communicate various events and state information to the > underlying virtualization supervisor by executing a UD2 (and some others > ops like it). > > I think that in a non-VT cpu it's actually a "real" invalid op code. The > stuff (hardware) which flips over to the supervisor with all the needed > info from the virtual machine isn't there. > > KVM uses this, from the patches I've seen Googling around for UD2 (if I > understand correctly). > > So why a UD2 in the code? It's highly unlikely that it's just some > random bytes that happen to be a UD2. Possibly the kernel thinks it's in > fully virt mode at some point? The image notes do seem to indicate this. > The guest kernel uses UD2 as part of the implementation of an assertion. In this case, UD2 is used by the guest to communicate with itself. Every BUG: report you see will have the code containing 0f 0b. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain. From sa212+fcxen at cyconix.com Wed Jan 21 08:15:00 2009 From: sa212+fcxen at cyconix.com (Evan Lavelle) Date: Wed, 21 Jan 2009 08:15:00 +0000 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? Message-ID: <4976D984.9080407@cyconix.com> It seems I've been a bit thick. It's been pretty obvious recently that Xen isn't flavour of the month around here, but I assumed there were good reasons for that. Now, rather belatedly, I've found http://www.redhat.com/about/news/prarchive/2008/qumranet.html In short, RedHat paid $107 million for Qumranet in September 2008. The acquisition includes KVM. I've got 2 years invested in Xen, on FC8, and I can't help feeling that I've been shafted. Am I alone? -Evan From ondrejj at salstar.sk Wed Jan 21 08:20:48 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Wed, 21 Jan 2009 09:20:48 +0100 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <4976D984.9080407@cyconix.com> References: <4976D984.9080407@cyconix.com> Message-ID: <20090121082048.GD9111@salstar.sk> On Wed, Jan 21, 2009 at 08:15:00AM +0000, Evan Lavelle wrote: > It seems I've been a bit thick. It's been pretty obvious recently that > Xen isn't flavour of the month around here, but I assumed there were > good reasons for that. Now, rather belatedly, I've found > > http://www.redhat.com/about/news/prarchive/2008/qumranet.html > > In short, RedHat paid $107 million for Qumranet in September 2008. The > acquisition includes KVM. > > I've got 2 years invested in Xen, on FC8, and I can't help feeling that > I've been shafted. Am I alone? Not alone, same situation for me. I am using Xen aprox 2 years too on our university, but with end of F8 there is not a fully functional Xen Dom0 and also DomU kernel for any stable Fedora. KVM is still not a replacement for paravirtualized machines and I think fully virtualized KVM will be slower like a paravirtualized XEN. Also I am missing some howtos for migration to KVM/xenner. Jan ONDREJ (SAL) From abraxis at telkomsa.net Wed Jan 21 09:44:35 2009 From: abraxis at telkomsa.net (Neil Thompson) Date: Wed, 21 Jan 2009 11:44:35 +0200 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <4976D984.9080407@cyconix.com> References: <4976D984.9080407@cyconix.com> Message-ID: <20090121094435.GC9213@wol.32.boerneef.vornavalley> On Wed, Jan 21, 2009 at 08:15:00AM +0000, Evan Lavelle wrote: > It seems I've been a bit thick. It's been pretty obvious recently that > Xen isn't flavour of the month around here, but I assumed there were > good reasons for that. Now, rather belatedly, I've found > > http://www.redhat.com/about/news/prarchive/2008/qumranet.html > > In short, RedHat paid $107 million for Qumranet in September 2008. The > acquisition includes KVM. > > I've got 2 years invested in Xen, on FC8, and I can't help feeling that > I've been shafted. Am I alone? > Xen (paravirt) is in the process of going into the Mainstream kernel, also RHEL5, which has a number of years left, includes xen - I don't think Red Hat are going to mess their corporate clients around by removing it. The problem with F8 is that the kernel people could no longer drag an obsolete (2.6.21) kernel around just for xen, and decided to concentrate on helping get it into the mainstream kernel. This has taken longer than expected. RHEL (and CentOS) 5.3 has support for Fedora 10 (and above) domUs, and Fedora 11 should have, as well. Another thing the Red Hat people are working on is to make the management interface (and the images, I think - please correct me if I'm wrong RH folks) the same for Qemu, KVM and xen, so the impact of moving from one to the other is very small. Shafted?...I don't think so. We're just in a blip at the moment. -- Cheers! (Relax...have a homebrew) Neil ...aliquando et insanire iucundum est. -- Lucius Annaeus Seneca From ondrejj at salstar.sk Wed Jan 21 09:51:07 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Wed, 21 Jan 2009 10:51:07 +0100 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121094435.GC9213@wol.32.boerneef.vornavalley> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> Message-ID: <20090121095107.GG9111@salstar.sk> On Wed, Jan 21, 2009 at 11:44:35AM +0200, Neil Thompson wrote: > On Wed, Jan 21, 2009 at 08:15:00AM +0000, Evan Lavelle wrote: > RHEL (and CentOS) 5.3 has support for Fedora 10 (and above) domUs, and Fedora 11 > should have, as well. Just there is at least one critical problem with Fedora 10 DomU and also one for Fedora 9 DomU, so Fedora 10 kernels can't run stable. :( https://bugzilla.redhat.com/show_bug.cgi?id=478414 SAL From abraxis at telkomsa.net Wed Jan 21 10:04:34 2009 From: abraxis at telkomsa.net (Neil Thompson) Date: Wed, 21 Jan 2009 12:04:34 +0200 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121095107.GG9111@salstar.sk> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> Message-ID: <20090121100434.GD9213@wol.32.boerneef.vornavalley> On Wed, Jan 21, 2009 at 10:51:07AM +0100, Jan ONDREJ (SAL) wrote: > On Wed, Jan 21, 2009 at 11:44:35AM +0200, Neil Thompson wrote: > > On Wed, Jan 21, 2009 at 08:15:00AM +0000, Evan Lavelle wrote: > > RHEL (and CentOS) 5.3 has support for Fedora 10 (and above) domUs, and Fedora 11 > > should have, as well. > > Just there is at least one critical problem with Fedora 10 DomU and also one > for Fedora 9 DomU, so Fedora 10 kernels can't run stable. :( > > https://bugzilla.redhat.com/show_bug.cgi?id=478414 > Your problem is with an F8 Dom0...the 2.6.29 kernel that will (hopefully) be in F11 should sort out most of the paravirt problems, from what I can see. I'm not sure what the status of the code in EL5.3 is, maybe the RH people can comment. I don't think your problem qualifies as "shafted". -- Cheers! (Relax...have a homebrew) Neil ...aliquando et insanire iucundum est. -- Lucius Annaeus Seneca From berrange at redhat.com Wed Jan 21 10:20:04 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 21 Jan 2009 10:20:04 +0000 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <4976D984.9080407@cyconix.com> References: <4976D984.9080407@cyconix.com> Message-ID: <20090121102004.GB28254@redhat.com> On Wed, Jan 21, 2009 at 08:15:00AM +0000, Evan Lavelle wrote: > It seems I've been a bit thick. It's been pretty obvious recently that > Xen isn't flavour of the month around here, but I assumed there were > good reasons for that. Now, rather belatedly, I've found > > http://www.redhat.com/about/news/prarchive/2008/qumranet.html > > In short, RedHat paid $107 million for Qumranet in September 2008. The > acquisition includes KVM. > > I've got 2 years invested in Xen, on FC8, and I can't help feeling that > I've been shafted. Am I alone? The acqusition of Qumranet has had absolutely *zero* impact on the availability Xen kernels in Fedora. The sole reason for not having Xen support in Fedora 9/10 is that the Dom0 kernel is not yet merged upstream, and this problem existed long long before Qumranet joined Red Hat. When we first shipped Xen in Fedora Core 5 (or was it 4?) none of the Xen code was merged into the mainline Linux kernel tree. For several releases we spent a great deal of time forward porting Xen to newer kernels. When we got to Fedora 9 the guest side was merged into the main kernel, but the host side was not. Unfortunately the Xen host kernel was still on 2.6.18 while Fedora was on 2.6.24 and the kernel was just too old to work with the userspace tools. We did not want to drop Xen Dom0 host from Fedora 9, but we had no viable options to continue with it in the short term. Since that time though, Jeremy Fitzhardinge has done alot of work on getting Dom0 patches in shape for merging in upstream Linux. It it still hard to say just when these will be accepted upstream, but there is a semi-reasonable we'll be able to turn Xen Dom0 back on in Fedora 11 kernels. While we (Red Hat) think KVM is a very compelling technology, as long as Xen is open source, actively maintained upstream & in mainline Linux kernels, there's no reason why it shouldn't be available in Fedora. So once the Dom0 kernel is merged, Fedora users will be able to have a choice between Xen and KVM for many future releases. We have also put effort into developing Xenner which allows paravirt Xen guests to be run under KVM without having to re-configure the guest kernel, giving people a potential migration strategy if they need one. As for RHEL-5, that continues to support Xen, and will do for the entire of its 7 year lifetime. If you don't want official Red Hat support, there is also the option of using CentOS 5 as a Xen host which again will have Xen support it in for whole of its 7 year lifetime. So while it is definitely unfortunate that we don't have a Xen Dom0 kernel in Fedora 9/10, we are *not* trying to shaft anyone & will re-introduce Xen Dom0 kernels to Fedora when they become available. Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From sa212+fcxen at cyconix.com Wed Jan 21 10:22:07 2009 From: sa212+fcxen at cyconix.com (Evan Lavelle) Date: Wed, 21 Jan 2009 10:22:07 +0000 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121094435.GC9213@wol.32.boerneef.vornavalley> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> Message-ID: <4976F74F.2080903@cyconix.com> Neil Thompson wrote: > Xen (paravirt) is in the process of going into the Mainstream kernel, also > RHEL5, which has a number of years left, includes xen - I don't think > Red Hat are going to mess their corporate clients around by removing it. I hope you're right, but that $107 million is saying something else. -Evan From ondrejj at salstar.sk Wed Jan 21 10:28:17 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Wed, 21 Jan 2009 11:28:17 +0100 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121100434.GD9213@wol.32.boerneef.vornavalley> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> <20090121100434.GD9213@wol.32.boerneef.vornavalley> Message-ID: <20090121102817.GH9111@salstar.sk> On Wed, Jan 21, 2009 at 12:04:34PM +0200, Neil Thompson wrote: > On Wed, Jan 21, 2009 at 10:51:07AM +0100, Jan ONDREJ (SAL) wrote: > > On Wed, Jan 21, 2009 at 11:44:35AM +0200, Neil Thompson wrote: > > > On Wed, Jan 21, 2009 at 08:15:00AM +0000, Evan Lavelle wrote: > > > RHEL (and CentOS) 5.3 has support for Fedora 10 (and above) domUs, and Fedora 11 > > > should have, as well. > > > > Just there is at least one critical problem with Fedora 10 DomU and also one > > for Fedora 9 DomU, so Fedora 10 kernels can't run stable. :( > > > > https://bugzilla.redhat.com/show_bug.cgi?id=478414 > > > > Your problem is with an F8 Dom0... Not exactly. On my F8 Dom0 Fedora 10 works well with latest fc8 domU kernel. Just when trying to boot and run .fc10. PAE or x86_64 kernel, it fails in less than 48 hours. > the 2.6.29 kernel that will (hopefully) be in > F11 should sort out most of the paravirt problems, from what I can see. I'm > not sure what the status of the code in EL5.3 is, maybe the RH people > can comment. I think it will not be in 2.6.29. Although http://wiki.xensource.com/xenwiki/XenParavirtOps says thatit's planned for 2.6.29, I can't see any progres in 2.6.29-rc2 changelog: http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.29-rc2 http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.29-rc1 I think, 2.6.29 is closed for large changes. Or I missed something? SAL From fedora at guagua.fi Wed Jan 21 11:40:55 2009 From: fedora at guagua.fi (=?ISO-8859-1?Q?Veli-Pekka_Kestil=E4?=) Date: Wed, 21 Jan 2009 13:40:55 +0200 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121102817.GH9111@salstar.sk> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> <20090121100434.GD9213@wol.32.boerneef.vornavalley> <20090121102817.GH9111@salstar.sk> Message-ID: <497709C7.7080301@guagua.fi> Jan ONDREJ (SAL) wrote: > On Wed, Jan 21, 2009 at 12:04:34PM +0200, Neil Thompson wrote: > >> On Wed, Jan 21, 2009 at 10:51:07AM +0100, Jan ONDREJ (SAL) wrote: >> >>> On Wed, Jan 21, 2009 at 11:44:35AM +0200, Neil Thompson wrote: >>> >>>> On Wed, Jan 21, 2009 at 08:15:00AM +0000, Evan Lavelle wrote: >>>> RHEL (and CentOS) 5.3 has support for Fedora 10 (and above) domUs, and Fedora 11 >>>> should have, as well. >>>> >>> Just there is at least one critical problem with Fedora 10 DomU and also one >>> for Fedora 9 DomU, so Fedora 10 kernels can't run stable. :( >>> >>> https://bugzilla.redhat.com/show_bug.cgi?id=478414 >>> >>> >> Your problem is with an F8 Dom0... >> > > Not exactly. On my F8 Dom0 Fedora 10 works well with latest fc8 domU kernel. > Just when trying to boot and run .fc10. PAE or x86_64 kernel, it fails > in less than 48 hours. > > I would really recommend you to change the Dom0 to be CentOS 5.2 or newer, Fedora 8 has been "Dead" about ?-month allready and will not get any updates be it KVM, QEMU or Xen. So the bugs will not be fixed and there will be no security updates for F8. I have some virtual environments running still vith Xen and F7 or F8, but will migrate them soon to CentOS for stability and long term support and I quite much expect them to be still supported 5-years from now. Also I don't think kvm will be that different or hard to learn if it becomes to that. It actually has paravirtual network drivers for windows from Qumranet which you can get without extra fee so I think if you are having windows clients it could be way to go in future. For xen you need to pay to Novell for that priviledge. So all in all I think for me this aquisition is good news. I think most problems with xen comes from xensource as it's they only product generating income and for that reason the opensource version seems to get less care than the version you can buy from them. (This is just my opinion so it's not necessarily so) Greetings, Veli-Pekka From m.a.young at durham.ac.uk Wed Jan 21 11:47:55 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Wed, 21 Jan 2009 11:47:55 +0000 (GMT) Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121095107.GG9111@salstar.sk> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> Message-ID: On Wed, 21 Jan 2009, Jan ONDREJ (SAL) wrote: > On Wed, Jan 21, 2009 at 11:44:35AM +0200, Neil Thompson wrote: >> On Wed, Jan 21, 2009 at 08:15:00AM +0000, Evan Lavelle wrote: >> RHEL (and CentOS) 5.3 has support for Fedora 10 (and above) domUs, and Fedora 11 >> should have, as well. > > Just there is at least one critical problem with Fedora 10 DomU and also one > for Fedora 9 DomU, so Fedora 10 kernels can't run stable. :( > > https://bugzilla.redhat.com/show_bug.cgi?id=478414 That might actually be nothing to do with xen. Dovecot provides a very successful way of hammering the file locking code, and you might just be exposing bugs or race conditions in the underlying kernel rather than the xen specific code. I suggest you check to see if the processes involved are waiting to access locked files. Michael Young From rjones at redhat.com Wed Jan 21 11:50:39 2009 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 21 Jan 2009 11:50:39 +0000 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121082048.GD9111@salstar.sk> References: <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> Message-ID: <20090121115039.GA7741@amd.home.annexia.org> On Wed, Jan 21, 2009 at 09:20:48AM +0100, Jan ONDREJ (SAL) wrote: > KVM is still not a replacement for paravirtualized machines and I think > fully virtualized KVM will be slower like a paravirtualized XEN. KVM is a great replacement for Xen. It's much easier to use for a start -- no more rebooting into a completely separate kernel^W hypervisor. As long as you have the virtio drivers in the guest, which is the default for all new Linux distros, performance is roughly the same. > Also I am missing some howtos for migration to KVM/xenner. Install a recent Linux kernel in the guest, adjust the configuration file[1], and reboot. You only need Xenner if you want to run the Xen PV guest unchanged (ie. without installing a new guest kernel). Rich. [1] 'virsh edit domname', and edit the domain type, and fields, as detailed here: http://libvirt.org/drvqemu.html -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v From pasik at iki.fi Wed Jan 21 11:53:19 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 21 Jan 2009 13:53:19 +0200 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <497709C7.7080301@guagua.fi> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> <20090121100434.GD9213@wol.32.boerneef.vornavalley> <20090121102817.GH9111@salstar.sk> <497709C7.7080301@guagua.fi> Message-ID: <20090121115318.GX15052@edu.joroinen.fi> On Wed, Jan 21, 2009 at 01:40:55PM +0200, Veli-Pekka Kestil? wrote: > Jan ONDREJ (SAL) wrote: > >On Wed, Jan 21, 2009 at 12:04:34PM +0200, Neil Thompson wrote: > > > >>On Wed, Jan 21, 2009 at 10:51:07AM +0100, Jan ONDREJ (SAL) wrote: > >> > >>>On Wed, Jan 21, 2009 at 11:44:35AM +0200, Neil Thompson wrote: > >>> > >>>>On Wed, Jan 21, 2009 at 08:15:00AM +0000, Evan Lavelle wrote: > >>>>RHEL (and CentOS) 5.3 has support for Fedora 10 (and above) domUs, and > >>>>Fedora 11 > >>>>should have, as well. > >>>> > >>>Just there is at least one critical problem with Fedora 10 DomU and also > >>>one > >>>for Fedora 9 DomU, so Fedora 10 kernels can't run stable. :( > >>> > >>>https://bugzilla.redhat.com/show_bug.cgi?id=478414 > >>> > >>> > >>Your problem is with an F8 Dom0... > >> > > > >Not exactly. On my F8 Dom0 Fedora 10 works well with latest fc8 domU > >kernel. > >Just when trying to boot and run .fc10. PAE or x86_64 kernel, it fails > >in less than 48 hours. > > > > > I would really recommend you to change the Dom0 to be CentOS 5.2 or > newer, Fedora 8 has been "Dead" about ?-month allready and will not get > any updates be it KVM, QEMU or Xen. So the bugs will not be fixed and > there will be no security updates for F8. I have some virtual > environments running still vith Xen and F7 or F8, but will migrate them > soon to CentOS for stability and long term support and I quite much > expect them to be still supported 5-years from now. > > Also I don't think kvm will be that different or hard to learn if it > becomes to that. It actually has paravirtual network drivers for windows > from Qumranet which you can get without extra fee so I think if you are > having windows clients it could be way to go in future. For xen you need > to pay to Novell for that priviledge. > You can always use "GPLPV" Windows drivers for Xen. They're open source. > So all in all I think for me this aquisition is good news. I think most > problems with xen comes from xensource as it's they only product > generating income and for that reason the opensource version seems to > get less care than the version you can buy from them. (This is just my > opinion so it's not necessarily so) > I think Xensource is putting a lot of effort into opensource Xen. It's just the dom0/pv_ops mess that's causing problems atm.. that _should_ get fixed in the near future. -- Pasi From sa212+fcxen at cyconix.com Wed Jan 21 12:00:35 2009 From: sa212+fcxen at cyconix.com (Evan Lavelle) Date: Wed, 21 Jan 2009 12:00:35 +0000 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <497709C7.7080301@guagua.fi> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> <20090121100434.GD9213@wol.32.boerneef.vornavalley> <20090121102817.GH9111@salstar.sk> <497709C7.7080301@guagua.fi> Message-ID: <49770E63.2010603@cyconix.com> Veli-Pekka Kestil? wrote: > Also I don't think kvm will be that different or hard to learn if it > becomes to that. It actually has paravirtual network drivers for windows > from Qumranet which you can get without extra fee so I think if you are > having windows clients it could be way to go in future. For xen you need > to pay to Novell for that priviledge. Has anyone tried the Qumranet drivers? My XP clients on Xen are very slow. There are free Windows drivers at http://wiki.xensource.com/xenwiki/XenWindowsGplPv, but I think they still need some development. -Evan From erenoglu at gmail.com Wed Jan 21 12:03:42 2009 From: erenoglu at gmail.com (Emre Erenoglu) Date: Wed, 21 Jan 2009 13:03:42 +0100 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <49770E63.2010603@cyconix.com> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> <20090121100434.GD9213@wol.32.boerneef.vornavalley> <20090121102817.GH9111@salstar.sk> <497709C7.7080301@guagua.fi> <49770E63.2010603@cyconix.com> Message-ID: On Wed, Jan 21, 2009 at 1:00 PM, Evan Lavelle > wrote: > Veli-Pekka Kestil? wrote: > > Also I don't think kvm will be that different or hard to learn if it >> becomes to that. It actually has paravirtual network drivers for windows >> from Qumranet which you can get without extra fee so I think if you are >> having windows clients it could be way to go in future. For xen you need to >> pay to Novell for that priviledge. >> > > Has anyone tried the Qumranet drivers? My XP clients on Xen are very slow. > There are free Windows drivers at > http://wiki.xensource.com/xenwiki/XenWindowsGplPv, but I think they still > need some development. > I tried, they were running OK for me. -- Emre -------------- next part -------------- An HTML attachment was scrubbed... URL: From ondrejj at salstar.sk Wed Jan 21 12:10:06 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Wed, 21 Jan 2009 13:10:06 +0100 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <497709C7.7080301@guagua.fi> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> <20090121100434.GD9213@wol.32.boerneef.vornavalley> <20090121102817.GH9111@salstar.sk> <497709C7.7080301@guagua.fi> Message-ID: <20090121121006.GK9111@salstar.sk> On Wed, Jan 21, 2009 at 01:40:55PM +0200, Veli-Pekka Kestil? wrote: > I would really recommend you to change the Dom0 to be CentOS 5.2 or > newer, Fedora 8 has been "Dead" about ?-month allready and will not get It's not easy to convert my Dom0 to CentOS, but may be it will be only one whing which I can do. But I am still not sure, if it helps. My fc8 domU works well. May be there are some API changes between fc8 xen dom0 and fc10 domU, which causes my problems. > So all in all I think for me this aquisition is good news. I think most > problems with xen comes from xensource as it's they only product > generating income and for that reason the opensource version seems to > get less care than the version you can buy from them. (This is just my > opinion so it's not necessarily so) Destination of KVM looks good, but it's still not ready to replace Xen. May be after 1-2 years of testing it will be better like xen. SAL From ondrejj at salstar.sk Wed Jan 21 12:12:52 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Wed, 21 Jan 2009 13:12:52 +0100 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121115039.GA7741@amd.home.annexia.org> References: <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> Message-ID: <20090121121252.GM9111@salstar.sk> On Wed, Jan 21, 2009 at 11:50:39AM +0000, Richard W.M. Jones wrote: > On Wed, Jan 21, 2009 at 09:20:48AM +0100, Jan ONDREJ (SAL) wrote: > > KVM is still not a replacement for paravirtualized machines and I think > > fully virtualized KVM will be slower like a paravirtualized XEN. > > KVM is a great replacement for Xen. It's much easier to use for a > start -- no more rebooting into a completely separate kernel^W > hypervisor. As long as you have the virtio drivers in the guest, > which is the default for all new Linux distros, performance is roughly > the same. > > > Also I am missing some howtos for migration to KVM/xenner. > > Install a recent Linux kernel in the guest, adjust the configuration > file[1], and reboot. You only need Xenner if you want to run the Xen > PV guest unchanged (ie. without installing a new guest kernel). For F10 there is no need to change domU kernel. It's same. But after reboot to KVM, my virtual machine has an 8139 network card. Is it paravirtualized? How I can tell my machine to use "virtio" drivers? SAL From ondrejj at salstar.sk Wed Jan 21 12:16:36 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Wed, 21 Jan 2009 13:16:36 +0100 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> Message-ID: <20090121121636.GO9111@salstar.sk> On Wed, Jan 21, 2009 at 11:47:55AM +0000, M A Young wrote: > On Wed, 21 Jan 2009, Jan ONDREJ (SAL) wrote: > >> On Wed, Jan 21, 2009 at 11:44:35AM +0200, Neil Thompson wrote: >>> On Wed, Jan 21, 2009 at 08:15:00AM +0000, Evan Lavelle wrote: >>> RHEL (and CentOS) 5.3 has support for Fedora 10 (and above) domUs, and Fedora 11 >>> should have, as well. >> >> Just there is at least one critical problem with Fedora 10 DomU and also one >> for Fedora 9 DomU, so Fedora 10 kernels can't run stable. :( >> >> https://bugzilla.redhat.com/show_bug.cgi?id=478414 > > That might actually be nothing to do with xen. Dovecot provides a very > successful way of hammering the file locking code, and you might just be > exposing bugs or race conditions in the underlying kernel rather than the > xen specific code. I suggest you check to see if the processes involved > are waiting to access locked files. I know, why dovecot fails. And it's not only dovecot, also mysql, apache, ... This bug describes only one example, when I was able to make some logs. My problem is, that command "sync" and may be similar kernel function called from dovecot, mysql, ... stays in "D" state. File cache is not stored on my media. I can read all changed data back from cache, but they are not stored on disks. After reboot all data written to cache is lost. May be my english is not perfect, I am sorry. :( SAL From rjones at redhat.com Wed Jan 21 12:19:31 2009 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 21 Jan 2009 12:19:31 +0000 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121121252.GM9111@salstar.sk> References: <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> Message-ID: <20090121121931.GA8157@amd.home.annexia.org> On Wed, Jan 21, 2009 at 01:12:52PM +0100, Jan ONDREJ (SAL) wrote: > On Wed, Jan 21, 2009 at 11:50:39AM +0000, Richard W.M. Jones wrote: > > On Wed, Jan 21, 2009 at 09:20:48AM +0100, Jan ONDREJ (SAL) wrote: > > > KVM is still not a replacement for paravirtualized machines and I think > > > fully virtualized KVM will be slower like a paravirtualized XEN. > > > > KVM is a great replacement for Xen. It's much easier to use for a > > start -- no more rebooting into a completely separate kernel^W > > hypervisor. As long as you have the virtio drivers in the guest, > > which is the default for all new Linux distros, performance is roughly > > the same. > > > > > Also I am missing some howtos for migration to KVM/xenner. > > > > Install a recent Linux kernel in the guest, adjust the configuration > > file[1], and reboot. You only need Xenner if you want to run the Xen > > PV guest unchanged (ie. without installing a new guest kernel). > > For F10 there is no need to change domU kernel. It's same. > > But after reboot to KVM, my virtual machine has an 8139 network card. > Is it paravirtualized? How I can tell my machine to use "virtio" drivers? You have to tell the host to give the guest a virtio network card - change the NIC as described here: http://libvirt.org/formatdomain.html#elementsNICS The guest needs to have a relatively up to date kernel which has drivers for the virtio network card - that's included in all recent Linux kernels (virtio_net.ko). Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top From fedora at guagua.fi Wed Jan 21 12:20:19 2009 From: fedora at guagua.fi (=?ISO-8859-1?Q?Veli-Pekka_Kestil=E4?=) Date: Wed, 21 Jan 2009 14:20:19 +0200 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121115318.GX15052@edu.joroinen.fi> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> <20090121100434.GD9213@wol.32.boerneef.vornavalley> <20090121102817.GH9111@salstar.sk> <497709C7.7080301@guagua.fi> <20090121115318.GX15052@edu.joroinen.fi> Message-ID: <49771303.7050902@guagua.fi> Pasi K?rkk?inen wrote: > On Wed, Jan 21, 2009 at 01:40:55PM +0200, Veli-Pekka Kestil? wrote: > >> >> Also I don't think kvm will be that different or hard to learn if it >> becomes to that. It actually has paravirtual network drivers for windows >> from Qumranet which you can get without extra fee so I think if you are >> having windows clients it could be way to go in future. For xen you need >> to pay to Novell for that priviledge. >> >> > > You can always use "GPLPV" Windows drivers for Xen. They're open source. > > Thanks for the tip, I have quite many Windows hosts running with Xen and have been looking for drivers, but haven't found these. Have to test them out when I get my new testing machine. >> So all in all I think for me this aquisition is good news. I think most >> problems with xen comes from xensource as it's they only product >> generating income and for that reason the opensource version seems to >> get less care than the version you can buy from them. (This is just my >> opinion so it's not necessarily so) >> > > I think Xensource is putting a lot of effort into opensource Xen. > > It's just the dom0/pv_ops mess that's causing problems atm.. that _should_ > get fixed in the near future. > > I have noticed that. But main reason for my feeling is that they should have started the push much more early than they did. Or maybe it wasn't feasible before. Anyway it's just have been my feeling of the whole thing and I think it's good to have two competing techs as it will provide that both will advance. Veli-Pekka From jos at xos.nl Wed Jan 21 12:26:18 2009 From: jos at xos.nl (Jos Vos) Date: Wed, 21 Jan 2009 13:26:18 +0100 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121115318.GX15052@edu.joroinen.fi> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> <20090121100434.GD9213@wol.32.boerneef.vornavalley> <20090121102817.GH9111@salstar.sk> <497709C7.7080301@guagua.fi> <20090121115318.GX15052@edu.joroinen.fi> Message-ID: <20090121122618.GE23056@jasmine.xos.nl> On Wed, Jan 21, 2009 at 01:53:19PM +0200, Pasi K?rkk?inen wrote: > I think Xensource is putting a lot of effort into opensource Xen. I've heard totally different stories from others. For almost every problem you report, they'll tell you that "it is fixed in the commercial version". Unfortunately, many companies just "use" open source as marketing instrument, sometimes they even *abuse* the term (i.e. call software with no OSI-compliant license open source -- which is not the case with Xen b.t.w.). -- -- Jos Vos -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 From kanarip at kanarip.com Wed Jan 21 12:30:41 2009 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Wed, 21 Jan 2009 13:30:41 +0100 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <4976F74F.2080903@cyconix.com> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <4976F74F.2080903@cyconix.com> Message-ID: <49771571.2060404@kanarip.com> Evan Lavelle wrote: > Neil Thompson wrote: > >> Xen (paravirt) is in the process of going into the Mainstream kernel, >> also >> RHEL5, which has a number of years left, includes xen - I don't think >> Red Hat are going to mess their corporate clients around by removing it. > > I hope you're right, but that $107 million is saying something else. > And http://www.redhat.com/promo/qumranet/ again says Neil's right. Kind regards, Jeroen van Meeuwen -kanarip From ondrejj at salstar.sk Wed Jan 21 13:28:36 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Wed, 21 Jan 2009 14:28:36 +0100 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121121931.GA8157@amd.home.annexia.org> References: <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <20090121121931.GA8157@amd.home.annexia.org> Message-ID: <20090121132836.GP9111@salstar.sk> On Wed, Jan 21, 2009 at 12:19:31PM +0000, Richard W.M. Jones wrote: > On Wed, Jan 21, 2009 at 01:12:52PM +0100, Jan ONDREJ (SAL) wrote: > > You have to tell the host to give the guest a virtio network card - > change the NIC as described here: Many thanks. Works well. > http://libvirt.org/formatdomain.html#elementsNICS There is nothing interesant on this URL. Part elementsNICS is not found, but also thanks. On Wed, Jan 21, 2009 at 01:23:06PM +0100, Emre Erenoglu wrote: > you need to read the KVM virtio wiki pages, you need to disable that 8139 > emulated card driver (blacklist), then change some line in guest > configuration file, and probe virtio driver at boot. > > http://wiki.libvirt.org/page/Virtio > > http://kvm.qumranet.com/kvmwiki?action=fullsearch&context=180&value=virtio&titlesearch=Ba%C5%9Fl%C4%B1klar > > find /lib/modules | grep virtio will give you the list of modules (if they > are compiled as modules) > > You also need to have a recent kernel such as 2.6.25 which has built-in > virtio support. Thanks. I have it. virtio_net works well, but I have trouble to boot from virtio_blk. I can add second disk as virto block device, but I can't boot from first disk. When using sedond disk, everything works well. When booting via grub, this is on console: input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3 Setting up hotplug. Creating block device nodes. Creating character device nodes. Loading pata_acpi module Loading ata_generic module Loading virtio_blk module Creating root device. Mounting root filesystem. mount: error mounting /dev/root on /sysroot as ext3: No such file or directory Setting up hotplug. Creating block device nodes. Creating character device nodes. Loading pata_acpi module Loading ata_generic module Loading virtio_blk module Creating root device. Mounting root filesystem. mount: error mounting /dev/root on /sysroot as ext3: No such file or directory I am using UUID in GRUB, my initrd has been regenerated with virtio_blk module. I think, nash can't create /dev/vda* devices or something similar. Any ideas, how to debug this or how to fix this? SAL From rjones at redhat.com Wed Jan 21 13:45:52 2009 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 21 Jan 2009 13:45:52 +0000 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121132836.GP9111@salstar.sk> References: <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <20090121121931.GA8157@amd.home.annexia.org> <20090121132836.GP9111@salstar.sk> Message-ID: <20090121134552.GA17614@amd.home.annexia.org> On Wed, Jan 21, 2009 at 02:28:36PM +0100, Jan ONDREJ (SAL) wrote: > virtio_net works well, but I have trouble to boot from virtio_blk. > > I can add second disk as virto block device, but I can't boot from first > disk. When using sedond disk, everything works well. When booting via grub, > this is on console: Upgrading to using virtio_blk is very complicated. You have to rebuild initrd, and there's a difficult circular dependency to be resolved when doing this because you need to be using virtio_blk in order for mkinitrd to believe that you need it, although possibly mkinitrd supports some command line argument to override this. I actually gave up at this point. For newly installed guests, recent anaconda just works everything out for you and puts the correct drivers into initrd. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/ From markmc at redhat.com Wed Jan 21 13:48:30 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Wed, 21 Jan 2009 13:48:30 +0000 Subject: Switching from IDE to virtio_blk [qas Re: [Fedora-xen] Goodbye Xen on RH/Fedora?] In-Reply-To: <20090121132836.GP9111@salstar.sk> References: <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <20090121121931.GA8157@amd.home.annexia.org> <20090121132836.GP9111@salstar.sk> Message-ID: <1232545710.5013.68.camel@blaa> (This is all getting offtopic for fedora-xen, we should really move to fedora-virt) On Wed, 2009-01-21 at 14:28 +0100, Jan ONDREJ (SAL) wrote: > virtio_net works well, but I have trouble to boot from virtio_blk. > > I can add second disk as virto block device, but I can't boot from > first disk. When switching from IDE to virtio, you need to first build a new initrd in the guest with e.g.: $> mkinitrd --with virtio_pci --with virtio_blk -f /boot/initrd-$(kernelversion) $(kernelversion) You only need to do this once. After that, if a new kernel is installed while you're booted off a virtio disk, then mkinitrd will include the modules automatically. Cheers, Mark. From berrange at redhat.com Wed Jan 21 13:48:54 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 21 Jan 2009 13:48:54 +0000 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121134552.GA17614@amd.home.annexia.org> References: <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <20090121121931.GA8157@amd.home.annexia.org> <20090121132836.GP9111@salstar.sk> <20090121134552.GA17614@amd.home.annexia.org> Message-ID: <20090121134854.GE28254@redhat.com> On Wed, Jan 21, 2009 at 01:45:52PM +0000, Richard W.M. Jones wrote: > On Wed, Jan 21, 2009 at 02:28:36PM +0100, Jan ONDREJ (SAL) wrote: > > virtio_net works well, but I have trouble to boot from virtio_blk. > > > > I can add second disk as virto block device, but I can't boot from first > > disk. When using sedond disk, everything works well. When booting via grub, > > this is on console: > > Upgrading to using virtio_blk is very complicated. You have to > rebuild initrd, and there's a difficult circular dependency to be > resolved when doing this because you need to be using virtio_blk in > order for mkinitrd to believe that you need it, although possibly > mkinitrd supports some command line argument to override this. I > actually gave up at this point. Just tell it to include virtio_blk module explicitly eg mkinitrd --with=virtio_blk .....other option... Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From kraxel at redhat.com Wed Jan 21 14:08:18 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Wed, 21 Jan 2009 15:08:18 +0100 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121102817.GH9111@salstar.sk> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> <20090121100434.GD9213@wol.32.boerneef.vornavalley> <20090121102817.GH9111@salstar.sk> Message-ID: <49772C52.7060106@redhat.com> > I think it will not be in 2.6.29. Although > http://wiki.xensource.com/xenwiki/XenParavirtOps says thatit's planned for > 2.6.29, I can't see any progres in 2.6.29-rc2 changelog: > http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.29-rc2 > http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.29-rc1 > > I think, 2.6.29 is closed for large changes. Or I missed something? Yea, looks like most of the dom0 stuff missed the boat. Some prelimary stuff might be in though (swiotlb patches ran over lkml at least, didn't check whenever they are actually made it). You can combine a self-compiled pv_ops/dom0 kernel with the Rawhide xen packages and help testing/debugging/get-stuff-upstream this way. You should follow xen-devel for the latest news & patches if you do so. The pv_ops/dom0 kernel has some not-yet debugged storage issues (disk controller either fails after a while or doesn't work at all), which is the major stumbling block right now. If you are lucky and the box stays up long enougth you can start guests. cheers, Gerd From kraxel at redhat.com Wed Jan 21 14:10:18 2009 From: kraxel at redhat.com (Gerd Hoffmann) Date: Wed, 21 Jan 2009 15:10:18 +0100 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121134854.GE28254@redhat.com> References: <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <20090121121931.GA8157@amd.home.annexia.org> <20090121132836.GP9111@salstar.sk> <20090121134552.GA17614@amd.home.annexia.org> <20090121134854.GE28254@redhat.com> Message-ID: <49772CCA.9080509@redhat.com> Hi, > Just tell it to include virtio_blk module explicitly eg > > mkinitrd --with=virtio_blk .....other option... virtio_pci too (which is probably the issue in this case, as the reporter sayed virtio_blk is included already). cheers, Gerd From erenoglu at gmail.com Wed Jan 21 14:06:43 2009 From: erenoglu at gmail.com (Emre Erenoglu) Date: Wed, 21 Jan 2009 15:06:43 +0100 Subject: Switching from IDE to virtio_blk [qas Re: [Fedora-xen] Goodbye Xen on RH/Fedora?] In-Reply-To: <1232545710.5013.68.camel@blaa> References: <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <20090121121931.GA8157@amd.home.annexia.org> <20090121132836.GP9111@salstar.sk> <1232545710.5013.68.camel@blaa> Message-ID: On Wed, Jan 21, 2009 at 2:48 PM, Mark McLoughlin wrote: > (This is all getting offtopic for fedora-xen, we should really move to > fedora-virt) > > On Wed, 2009-01-21 at 14:28 +0100, Jan ONDREJ (SAL) wrote: > > virtio_net works well, but I have trouble to boot from virtio_blk. > > > > I can add second disk as virto block device, but I can't boot from > > first disk. > > When switching from IDE to virtio, you need to first build a new initrd > in the guest with e.g.: > > $> mkinitrd --with virtio_pci --with virtio_blk -f > /boot/initrd-$(kernelversion) $(kernelversion) > > You only need to do this once. After that, if a new kernel is installed > while you're booted off a virtio disk, then mkinitrd will include the > modules automatically. You will also need to specify /dev/vdX on the kernel root= line and make sure your init script inside your initrd triggers the virtio drivers at boot so that the /dev/vdX are created. -- Emre -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjones at redhat.com Wed Jan 21 14:45:27 2009 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 21 Jan 2009 14:45:27 +0000 Subject: Switching from IDE to virtio_blk [qas Re: [Fedora-xen] Goodbye Xen on RH/Fedora?] In-Reply-To: References: <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <20090121121931.GA8157@amd.home.annexia.org> <20090121132836.GP9111@salstar.sk> <1232545710.5013.68.camel@blaa> Message-ID: <20090121144527.GA18495@amd.home.annexia.org> On Wed, Jan 21, 2009 at 03:06:43PM +0100, Emre Erenoglu wrote: > On Wed, Jan 21, 2009 at 2:48 PM, Mark McLoughlin wrote: > > > (This is all getting offtopic for fedora-xen, we should really move to > > fedora-virt) > > > > On Wed, 2009-01-21 at 14:28 +0100, Jan ONDREJ (SAL) wrote: > > > virtio_net works well, but I have trouble to boot from virtio_blk. > > > > > > I can add second disk as virto block device, but I can't boot from > > > first disk. > > > > When switching from IDE to virtio, you need to first build a new initrd > > in the guest with e.g.: > > > > $> mkinitrd --with virtio_pci --with virtio_blk -f > > /boot/initrd-$(kernelversion) $(kernelversion) > > > > You only need to do this once. After that, if a new kernel is installed > > while you're booted off a virtio disk, then mkinitrd will include the > > modules automatically. > > > You will also need to specify /dev/vdX on the kernel root= line and make > sure your init script inside your initrd triggers the virtio drivers at boot > so that the /dev/vdX are created. Yes I have to agree with Emre here - I don't think it's as simple as just rebuilding mkinitrd. I got that far but gave up later on. /me checks notes ... Yup, I got as far as working out that you would have to edit fstab and possibly /boot/grub/device.map and /boot/grub/menu.lst, before giving up. If anyone would like to fill in the wiki page here on the subject: http://wiki.libvirt.org/page/Virtio I'd like to reiterate that _none_ of this complexity is required when installing a new guest. Anaconda sets up everything for you. Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/ From erenoglu at gmail.com Wed Jan 21 14:51:16 2009 From: erenoglu at gmail.com (Emre Erenoglu) Date: Wed, 21 Jan 2009 15:51:16 +0100 Subject: Switching from IDE to virtio_blk [qas Re: [Fedora-xen] Goodbye Xen on RH/Fedora?] In-Reply-To: <20090121144527.GA18495@amd.home.annexia.org> References: <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <20090121121931.GA8157@amd.home.annexia.org> <20090121132836.GP9111@salstar.sk> <1232545710.5013.68.camel@blaa> <20090121144527.GA18495@amd.home.annexia.org> Message-ID: On Wed, Jan 21, 2009 at 3:45 PM, Richard W.M. Jones wrote: > On Wed, Jan 21, 2009 at 03:06:43PM +0100, Emre Erenoglu wrote: > > On Wed, Jan 21, 2009 at 2:48 PM, Mark McLoughlin > wrote: > > > > > (This is all getting offtopic for fedora-xen, we should really move to > > > fedora-virt) > > > > > > On Wed, 2009-01-21 at 14:28 +0100, Jan ONDREJ (SAL) wrote: > > > > virtio_net works well, but I have trouble to boot from virtio_blk. > > > > > > > > I can add second disk as virto block device, but I can't boot from > > > > first disk. > > > > > > When switching from IDE to virtio, you need to first build a new initrd > > > in the guest with e.g.: > > > > > > $> mkinitrd --with virtio_pci --with virtio_blk -f > > > /boot/initrd-$(kernelversion) $(kernelversion) > > > > > > You only need to do this once. After that, if a new kernel is installed > > > while you're booted off a virtio disk, then mkinitrd will include the > > > modules automatically. > > > > > > You will also need to specify /dev/vdX on the kernel root= line and make > > sure your init script inside your initrd triggers the virtio drivers at > boot > > so that the /dev/vdX are created. > > Yes I have to agree with Emre here - I don't think it's as simple as > just rebuilding mkinitrd. I got that far but gave up later on. Well what I did was that I created a special initramfs, with virtio-net and virtio-blk drivers, as well as all of their dependencies (virtio-pci, virti-baloon and possibly one more), edited the init script going inside the initrd image so that it triggers the virtio drivers, then booted up on that ROOT filesystem using the kernel command line. on system side, it's better to edit fstab but root is anyway mounted. You may need to boot to shell at your initrd to see what's going on, or probe by hand to see the devices are created etc. You also need to use the correct guest configuration file so that virtio-type devices are created instead of emulated ones. -- Emre -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jean-Noel.Chardron at dr15.cnrs.fr Wed Jan 21 15:03:55 2009 From: Jean-Noel.Chardron at dr15.cnrs.fr (=?ISO-8859-1?Q?jean-No=EBl_Chardron?=) Date: Wed, 21 Jan 2009 16:03:55 +0100 Subject: [Fedora-xen] Migration from Xen to KVM Message-ID: <4977395B.20902@dr15.cnrs.fr> Hello, rjones at redhat.com wrotes about migration : >Install a recent Linux kernel in the guest, adjust the configuration >file[1], and reboot. You only need Xenner if you want to run the Xen >PV guest unchanged (ie. without installing a new guest kernel). > >Rich. >[1] 'virsh edit domname', and edit the domain type, and > fields, as detailed here: http://libvirt.org/drvqemu.html I tried an centos5.2 dom0 with a domu centos5.2 It is not trivial the tools virsh and xm are not functional to start the domain So how do you start the domu As When I launch the command : #qemu-kvm /etc/xen/domuAKVM as domuAKVM is a new configuration file simply like the configuration of the old xen domu in the console the message is "Boot from hard disk failed : no bootable disk" So I have no more domU From Jean-Noel.Chardron at dr15.cnrs.fr Wed Jan 21 15:22:16 2009 From: Jean-Noel.Chardron at dr15.cnrs.fr (=?ISO-8859-1?Q?jean-No=EBl_Chardron?=) Date: Wed, 21 Jan 2009 16:22:16 +0100 Subject: [Fedora-xen] Migration from Xen to KVM In-Reply-To: <4977395B.20902@dr15.cnrs.fr> References: <4977395B.20902@dr15.cnrs.fr> Message-ID: <49773DA8.8050406@dr15.cnrs.fr> jean-No?l Chardron a ?crit : > Hello, > > rjones at redhat.com wrotes about migration : > >> Install a recent Linux kernel in the guest, adjust the configuration >> file[1], and reboot. You only need Xenner if you want to run the Xen >> PV guest unchanged (ie. without installing a new guest kernel). >> >> Rich. > >> [1] 'virsh edit domname', and edit the domain type, and >> fields, as detailed here: http://libvirt.org/drvqemu.html > > I tried an centos5.2 dom0 with a domu centos5.2 > It is not trivial > the tools virsh and xm are not functional to start the domain Oups I did a mistake in fact the command : # virsh -c qemu:///system list seems working but there is an other error with the command : # virsh -c qemu:///system create domuAKVM.xml.v1 libvir: QEMU erreur : Invalid harddisk device name: xvda erreur : Impossible de cr?er le domaine depuis domuAKVM.xml.v1 From markmc at redhat.com Wed Jan 21 16:29:36 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Wed, 21 Jan 2009 16:29:36 +0000 Subject: [Fedora-xen] Migration from Xen to KVM In-Reply-To: <49773DA8.8050406@dr15.cnrs.fr> References: <4977395B.20902@dr15.cnrs.fr> <49773DA8.8050406@dr15.cnrs.fr> Message-ID: <1232555376.5013.113.camel@blaa> On Wed, 2009-01-21 at 16:22 +0100, jean-No?l Chardron wrote: > jean-No?l Chardron a ?crit : > > Hello, > > > > rjones at redhat.com wrotes about migration : > > > >> Install a recent Linux kernel in the guest, adjust the configuration > >> file[1], and reboot. You only need Xenner if you want to run the Xen > >> PV guest unchanged (ie. without installing a new guest kernel). > >> > >> Rich. > > > >> [1] 'virsh edit domname', and edit the domain type, and > >> fields, as detailed here: http://libvirt.org/drvqemu.html > > > > I tried an centos5.2 dom0 with a domu centos5.2 > > It is not trivial > > the tools virsh and xm are not functional to start the domain > Oups I did a mistake in fact the command : > > # virsh -c qemu:///system list > seems working > but there is an other error with the command : > # virsh -c qemu:///system create domuAKVM.xml.v1 > libvir: QEMU erreur : Invalid harddisk device name: xvda Try replacing xvda with vda in the domain's config. Cheers, Mark. From pasik at iki.fi Wed Jan 21 16:31:43 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Wed, 21 Jan 2009 18:31:43 +0200 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <49771303.7050902@guagua.fi> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> <20090121100434.GD9213@wol.32.boerneef.vornavalley> <20090121102817.GH9111@salstar.sk> <497709C7.7080301@guagua.fi> <20090121115318.GX15052@edu.joroinen.fi> <49771303.7050902@guagua.fi> Message-ID: <20090121163143.GZ15052@edu.joroinen.fi> On Wed, Jan 21, 2009 at 02:20:19PM +0200, Veli-Pekka Kestil? wrote: > >>So all in all I think for me this aquisition is good news. I think most > >>problems with xen comes from xensource as it's they only product > >>generating income and for that reason the opensource version seems to > >>get less care than the version you can buy from them. (This is just my > >>opinion so it's not necessarily so) > >> > > > >I think Xensource is putting a lot of effort into opensource Xen. > > > >It's just the dom0/pv_ops mess that's causing problems atm.. that _should_ > >get fixed in the near future. > > > > > I have noticed that. But main reason for my feeling is that they should > have started the push much more early than they did. Or maybe it wasn't > feasible before. Anyway it's just have been my feeling of the whole > thing and I think it's good to have two competing techs as it will > provide that both will advance. > Yeah well.. IIRC Xen patches were first sent for 2.6.15 kernel. Those were rejected and not integrated into vanilla kernel. I can't remember the reason for that. Next attempt failed when others wanted to have the paravirt ops (pv_ops) framework instead, which enables Linux kernel PV support for any hypervisor, not just for Xen. Then it took a while to get the generic pv_ops framework done and merged into Linux kernel. And after that it has taken a lot of time to port the Xen domU from the original "Xenlinux" to pv_ops framework. pv_ops Xen domU support has been in mainline Linux kernel since 2.6.23. And now there is active development going on to get the pv_ops dom0 working and merged into Linux. Btw Redhat started this work earlier, and it is now being continued by Xensource (Jeremy Fitzhardinge). http://wiki.xensource.com/xenwiki/XenParavirtOps -- Pasi From Ian.Jackson at eu.citrix.com Wed Jan 21 17:45:54 2009 From: Ian.Jackson at eu.citrix.com (Ian Jackson) Date: Wed, 21 Jan 2009 17:45:54 +0000 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <20090121122618.GE23056@jasmine.xos.nl> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> <20090121100434.GD9213@wol.32.boerneef.vornavalley> <20090121102817.GH9111@salstar.sk> <497709C7.7080301@guagua.fi> <20090121115318.GX15052@edu.joroinen.fi> <20090121122618.GE23056@jasmine.xos.nl> Message-ID: <18807.24402.993030.247497@mariner.uk.xensource.com> Jos Vos writes ("Re: [Fedora-xen] Goodbye Xen on RH/Fedora?"): > On Wed, Jan 21, 2009 at 01:53:19PM +0200, Pasi K?rkk?inen wrote: > > I think Xensource is putting a lot of effort into opensource Xen. > > I've heard totally different stories from others. For almost every > problem you report, they'll tell you that "it is fixed in the > commercial version". I don't know where you're asking. As far as I know Citrix (who bought Xensource) don't offer paid end-user support as a service for the upstream version of Xen. On the other hand they do pay the salaries of various people who work on it (including me and of course Keir). If you find bugs in upstream Xen we're certainly interested; we spend most of our time trying to keep the quality up and manage the incoming patchstream. It's true that lists like xen-users aren't that well-read by developers like me but I think you'll find that's often true with a Free Software project; many developers prefer to try to help improve the code than to help individual users one at a time. As you can see at least some of us do read this list. I keep an eye on things here as well as on other distro lists - despite my Debian background :-) - to see if there's anything we can do to improve things. Most of the issues reported here are about Fedora-specific packaging of course, which I'm no expert on. It's true that the situation with the kernel is very disappointing. I don't think I can really explain what I see as the causes. It's too much of a political hot potato and I don't want to offend anyone, particularly my hosts here. Fortunately we now have Jeremy Fitzhardinge in charge of getting Xen support into Linux upstream and that seems to be making reasonable progress - although of course we would all prefer it to be faster. Regards, Ian. NB this is not the official position of Citrix about anything, just my personal opinion. From Dustin.Henning at prd-inc.com Wed Jan 21 18:34:48 2009 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Wed, 21 Jan 2009 13:34:48 -0500 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <49770E63.2010603@cyconix.com> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> <20090121100434.GD9213@wol.32.boerneef.vornavalley> <20090121102817.GH9111@salstar.sk> <497709C7.7080301@guagua.fi> <49770E63.2010603@cyconix.com> Message-ID: <008201c97bf6$f068c8a0$d13a59e0$@Henning@prd-inc.com> I tried the Qumranet drivers before I went with Xen. I don't think there is necessarily a problem with the Qumranet drivers, in fact, they could potentially have better inbound speeds than the GPLPV ones (though it seems unlikely as much as people test and James works on them on the xen-users list). The reason the Qumranet drivers don't cut it is because they are only network drivers. This means your data access (and possibly other stuff GPLPV hits) is still fully virtualized. Another reason I went with Xen is the PHY: option. I use a physical data source, as opposed to a file, for my guests. Each one has its own HD, actually, though partitions or RAID arrays would obviously work as well. If I remember correctly, when I tried this (some time ago), KVM had no such option. Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Evan Lavelle Sent: Wednesday, January 21, 2009 07:01 To: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Goodbye Xen on RH/Fedora? Veli-Pekka Kestil? wrote: > Also I don't think kvm will be that different or hard to learn if it > becomes to that. It actually has paravirtual network drivers for windows > from Qumranet which you can get without extra fee so I think if you are > having windows clients it could be way to go in future. For xen you need > to pay to Novell for that priviledge. Has anyone tried the Qumranet drivers? My XP clients on Xen are very slow. There are free Windows drivers at http://wiki.xensource.com/xenwiki/XenWindowsGplPv, but I think they still need some development. -Evan -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From Dustin.Henning at prd-inc.com Wed Jan 21 18:40:38 2009 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Wed, 21 Jan 2009 13:40:38 -0500 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <008201c97bf6$f068c8a0$d13a59e0$@Henning@prd-inc.com> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> <20090121100434.GD9213@wol.32.boerneef.vornavalley> <20090121102817.GH9111@salstar.sk> <497709C7.7080301@guagua.fi> <49770E63.2010603@cyconix.com> <008201c97bf6$f068c8a0$d13a59e0$@Henning@prd-inc.com> Message-ID: <008401c97bf7$c11c0f70$43542e50$@Henning@prd-inc.com> Also, while I'm on the topic, PCI-passthrough was a factor in my decision as well. Unfortunately, I'm stuck on F8 as well, because I can't get networking to work on CentOS Xen with my hardware. However, I understand what is going on, so I'm just holding my breath. Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Dustin Henning Sent: Wednesday, January 21, 2009 13:35 To: 'Evan Lavelle'; fedora-xen at redhat.com Subject: RE: [Fedora-xen] Goodbye Xen on RH/Fedora? I tried the Qumranet drivers before I went with Xen. I don't think there is necessarily a problem with the Qumranet drivers, in fact, they could potentially have better inbound speeds than the GPLPV ones (though it seems unlikely as much as people test and James works on them on the xen-users list). The reason the Qumranet drivers don't cut it is because they are only network drivers. This means your data access (and possibly other stuff GPLPV hits) is still fully virtualized. Another reason I went with Xen is the PHY: option. I use a physical data source, as opposed to a file, for my guests. Each one has its own HD, actually, though partitions or RAID arrays would obviously work as well. If I remember correctly, when I tried this (some time ago), KVM had no such option. Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Evan Lavelle Sent: Wednesday, January 21, 2009 07:01 To: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Goodbye Xen on RH/Fedora? Veli-Pekka Kestil? wrote: > Also I don't think kvm will be that different or hard to learn if it > becomes to that. It actually has paravirtual network drivers for windows > from Qumranet which you can get without extra fee so I think if you are > having windows clients it could be way to go in future. For xen you need > to pay to Novell for that priviledge. Has anyone tried the Qumranet drivers? My XP clients on Xen are very slow. There are free Windows drivers at http://wiki.xensource.com/xenwiki/XenWindowsGplPv, but I think they still need some development. -Evan -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From avi at redhat.com Wed Jan 21 18:43:17 2009 From: avi at redhat.com (Avi Kivity) Date: Wed, 21 Jan 2009 20:43:17 +0200 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <008201c97bf6$f068c8a0$d13a59e0$@Henning@prd-inc.com> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> <20090121100434.GD9213@wol.32.boerneef.vornavalley> <20090121102817.GH9111@salstar.sk> <497709C7.7080301@guagua.fi> <49770E63.2010603@cyconix.com> <008201c97bf6$f068c8a0$d13a59e0$@Henning@prd-inc.com> Message-ID: <49776CC5.9010203@redhat.com> Dustin Henning wrote: > I tried the Qumranet drivers before I went with Xen. I don't think > there is necessarily a problem with the Qumranet drivers, in fact, they > could potentially have better inbound speeds than the GPLPV ones (though it > seems unlikely as much as people test and James works on them on the > xen-users list). The reason the Qumranet drivers don't cut it is because > they are only network drivers. This means your data access (and possibly > other stuff GPLPV hits) is still fully virtualized. Storage drivers are in the works, hopefully out soon. > Another reason I went > with Xen is the PHY: option. I use a physical data source, as opposed to a > file, for my guests. Each one has its own HD, actually, though partitions > or RAID arrays would obviously work as well. If I remember correctly, when > I tried this (some time ago), KVM had no such option kvm has had this from day 1; 'qemu /dev/volgroup/logvol' will start a guest from the specified logical volume. For good performance I recommend 'qemu -drive file=/dev/volgroup/logvol,cache=off'. Of course, libvirt will handle all that for you. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain. From Dustin.Henning at prd-inc.com Wed Jan 21 18:47:34 2009 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Wed, 21 Jan 2009 13:47:34 -0500 Subject: Switching from IDE to virtio_blk [qas Re: [Fedora-xen] Goodbye Xen on RH/Fedora?] In-Reply-To: <1232545710.5013.68.camel@blaa> References: <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <20090121121931.GA8157@amd.home.annexia.org> <20090121132836.GP9111@salstar.sk> <1232545710.5013.68.camel@blaa> Message-ID: <008601c97bf8$b95f5bb0$2c1e1310$@Henning@prd-inc.com> It is probably worth noting that if someone were to run a kernel update with a package manager after getting this working (using information from later posts in this thread), they would need to do a manual mkinitrd. At least that was my experience some time ago when switching from hda to sda in CentOS, future kernel-xen versions installed via yum tried to boot to hda and failed. However, I think I actually recompiled originally, though, as opposed to adding the new drivers to initrd, so I could be wrong. Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Mark McLoughlin Sent: Wednesday, January 21, 2009 08:49 To: Jan ONDREJ (SAL) Cc: Fedora Xen Subject: Switching from IDE to virtio_blk [qas Re: [Fedora-xen] Goodbye Xen on RH/Fedora?] (This is all getting offtopic for fedora-xen, we should really move to fedora-virt) On Wed, 2009-01-21 at 14:28 +0100, Jan ONDREJ (SAL) wrote: > virtio_net works well, but I have trouble to boot from virtio_blk. > > I can add second disk as virto block device, but I can't boot from > first disk. When switching from IDE to virtio, you need to first build a new initrd in the guest with e.g.: $> mkinitrd --with virtio_pci --with virtio_blk -f /boot/initrd-$(kernelversion) $(kernelversion) You only need to do this once. After that, if a new kernel is installed while you're booted off a virtio disk, then mkinitrd will include the modules automatically. Cheers, Mark. -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From ondrejj at salstar.sk Wed Jan 21 19:05:16 2009 From: ondrejj at salstar.sk ('Jan ONDREJ (SAL)') Date: Wed, 21 Jan 2009 20:05:16 +0100 Subject: Switching from IDE to virtio_blk [qas Re: [Fedora-xen] Goodbye Xen on RH/Fedora?] In-Reply-To: <008601c97bf8$b95f5bb0$2c1e1310$@Henning@prd-inc.com> References: <20090121121252.GM9111@salstar.sk> <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <20090121121931.GA8157@amd.home.annexia.org> <20090121132836.GP9111@salstar.sk> <1232545710.5013.68.camel@blaa> <008601c97bf8$b95f5bb0$2c1e1310$@Henning@prd-inc.com> Message-ID: <20090121190516.GC30939@salstar.sk> You missed, that I am migrating not only my packages, but my whole virtual machine from paravirtualized Xen to paravirt. driver KVM. This mkinitrd magic is only required for disk driver change (xenblk_front to virtio_blk). So it's something different, like your upgrade of CentOS. SAL On Wed, Jan 21, 2009 at 01:47:34PM -0500, Dustin Henning wrote: > It is probably worth noting that if someone were to run a kernel > update with a package manager after getting this working (using information > from later posts in this thread), they would need to do a manual mkinitrd. > At least that was my experience some time ago when switching from hda to sda > in CentOS, future kernel-xen versions installed via yum tried to boot to hda > and failed. However, I think I actually recompiled originally, though, as > opposed to adding the new drivers to initrd, so I could be wrong. > Dustin > > -----Original Message----- > From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] > On Behalf Of Mark McLoughlin > Sent: Wednesday, January 21, 2009 08:49 > To: Jan ONDREJ (SAL) > Cc: Fedora Xen > Subject: Switching from IDE to virtio_blk [qas Re: [Fedora-xen] Goodbye Xen > on RH/Fedora?] > > (This is all getting offtopic for fedora-xen, we should really move to > fedora-virt) > > On Wed, 2009-01-21 at 14:28 +0100, Jan ONDREJ (SAL) wrote: > > virtio_net works well, but I have trouble to boot from virtio_blk. > > > > I can add second disk as virto block device, but I can't boot from > > first disk. > > When switching from IDE to virtio, you need to first build a new initrd > in the guest with e.g.: > > $> mkinitrd --with virtio_pci --with virtio_blk -f > /boot/initrd-$(kernelversion) $(kernelversion) > > You only need to do this once. After that, if a new kernel is installed > while you're booted off a virtio disk, then mkinitrd will include the > modules automatically. > > Cheers, > Mark. > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From berrange at redhat.com Wed Jan 21 20:08:26 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 21 Jan 2009 20:08:26 +0000 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? Message-ID: <20090121200826.GC2921@redhat.com> On Wed, Jan 21, 2009 at 01:40:38PM -0500, Dustin Henning wrote: > Also, while I'm on the topic, PCI-passthrough was a factor in my > decision as well. Unfortunately, I'm stuck on F8 as well, because I can't > get networking to work on CentOS Xen with my hardware. However, I > understand what is going on, so I'm just holding my breath. PCI passthrough for KVM is now available, and will be supported in the next libvirt....which reminds me that we never supported PCI pasthrough for Xen in libvirt... Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From berrange at redhat.com Wed Jan 21 20:10:55 2009 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 21 Jan 2009 20:10:55 +0000 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? Message-ID: <20090121201055.GD2921@redhat.com> On Wed, Jan 21, 2009 at 01:34:48PM -0500, Dustin Henning wrote: > I tried the Qumranet drivers before I went with Xen. I don't think > there is necessarily a problem with the Qumranet drivers, in fact, they > could potentially have better inbound speeds than the GPLPV ones (though it > seems unlikely as much as people test and James works on them on the > xen-users list). The reason the Qumranet drivers don't cut it is because > they are only network drivers. This means your data access (and possibly > other stuff GPLPV hits) is still fully virtualized. Another reason I went > with Xen is the PHY: option. I use a physical data source, as opposed to a > file, for my guests. Each one has its own HD, actually, though partitions > or RAID arrays would obviously work as well. If I remember correctly, when > I tried this (some time ago), KVM had no such option. KVM / QEMU don't make any artificial distinction between block devices and files, like Xen did. You can use any block device, lvm volume or file with QEMU / KVM - should be parity with Xen here. Network driver is by far the most important one to virtualize since it suffers much worse degradation when emulated, which is why PV net for Windows was done as a priority. SCSI in QEMU should offer pretty good performance - significantly better than IDE, and much closer to PV disk. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From Dustin.Henning at prd-inc.com Wed Jan 21 20:55:24 2009 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Wed, 21 Jan 2009 15:55:24 -0500 Subject: [Fedora-xen] Goodbye Xen on RH/Fedora? In-Reply-To: <49776CC5.9010203@redhat.com> References: <4976D984.9080407@cyconix.com> <20090121094435.GC9213@wol.32.boerneef.vornavalley> <20090121095107.GG9111@salstar.sk> <20090121100434.GD9213@wol.32.boerneef.vornavalley> <20090121102817.GH9111@salstar.sk> <497709C7.7080301@guagua.fi> <49770E63.2010603@cyconix.com> <008201c97bf6$f068c8a0$d13a59e0$@Henning@prd-inc.com> <49776CC5.9010203@redhat.com> Message-ID: <009e01c97c0a$94f6f6e0$bee4e4a0$@Henning@prd-inc.com> Wow, maybe the F8 documentation doesn't cover that, or maybe I'm remembering wrong, but good to know for future testing. Thanks. -----Original Message----- From: Avi Kivity [mailto:avi at redhat.com] Sent: Wednesday, January 21, 2009 13:43 To: Dustin.Henning at prd-inc.com Cc: 'Evan Lavelle'; fedora-xen at redhat.com Subject: Re: [Fedora-xen] Goodbye Xen on RH/Fedora? Dustin Henning wrote: > I tried the Qumranet drivers before I went with Xen. I don't think > there is necessarily a problem with the Qumranet drivers, in fact, they > could potentially have better inbound speeds than the GPLPV ones (though it > seems unlikely as much as people test and James works on them on the > xen-users list). The reason the Qumranet drivers don't cut it is because > they are only network drivers. This means your data access (and possibly > other stuff GPLPV hits) is still fully virtualized. Storage drivers are in the works, hopefully out soon. > Another reason I went > with Xen is the PHY: option. I use a physical data source, as opposed to a > file, for my guests. Each one has its own HD, actually, though partitions > or RAID arrays would obviously work as well. If I remember correctly, when > I tried this (some time ago), KVM had no such option kvm has had this from day 1; 'qemu /dev/volgroup/logvol' will start a guest from the specified logical volume. For good performance I recommend 'qemu -drive file=/dev/volgroup/logvol,cache=off'. Of course, libvirt will handle all that for you. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain. From markmc at redhat.com Thu Jan 22 09:20:35 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Thu, 22 Jan 2009 09:20:35 +0000 Subject: Switching from IDE to virtio_blk [qas Re: [Fedora-xen] Goodbye Xen on RH/Fedora?] In-Reply-To: <008601c97bf8$b95f5bb0$2c1e1310$@Henning@prd-inc.com> References: <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <20090121121931.GA8157@amd.home.annexia.org> <20090121132836.GP9111@salstar.sk> <1232545710.5013.68.camel@blaa> <008601c97bf8$b95f5bb0$2c1e1310$@Henning@prd-inc.com> Message-ID: <1232616035.4964.5.camel@blaa> On Wed, 2009-01-21 at 13:47 -0500, Dustin Henning wrote: > It is probably worth noting that if someone were to run a kernel > update with a package manager after getting this working (using > information > from later posts in this thread), they would need to do a manual > mkinitrd. No. If you boot off /dev/vda and update the kernel, mkinitrd will build an initrd containing the virtio modules. Cheers, Mark. From erenoglu at gmail.com Thu Jan 22 10:06:33 2009 From: erenoglu at gmail.com (Emre Erenoglu) Date: Thu, 22 Jan 2009 11:06:33 +0100 Subject: Switching from IDE to virtio_blk [qas Re: [Fedora-xen] Goodbye Xen on RH/Fedora?] In-Reply-To: <1232616035.4964.5.camel@blaa> References: <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <20090121121931.GA8157@amd.home.annexia.org> <20090121132836.GP9111@salstar.sk> <1232545710.5013.68.camel@blaa> <1232616035.4964.5.camel@blaa> Message-ID: On Thu, Jan 22, 2009 at 10:20 AM, Mark McLoughlin wrote: > On Wed, 2009-01-21 at 13:47 -0500, Dustin Henning wrote: > > It is probably worth noting that if someone were to run a kernel > > update with a package manager after getting this working (using > > information > > from later posts in this thread), they would need to do a manual > > mkinitrd. > > No. If you boot off /dev/vda and update the kernel, mkinitrd will build > an initrd containing the virtio modules. Well, that may depend if you use mkinitrd or mkinitramfs, and your distribution mkinitramfs or mkinitrd may not be checking which device type he's working on. Emre -------------- next part -------------- An HTML attachment was scrubbed... URL: From markmc at redhat.com Thu Jan 22 10:21:50 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Thu, 22 Jan 2009 10:21:50 +0000 Subject: Switching from IDE to virtio_blk [qas Re: [Fedora-xen] Goodbye Xen on RH/Fedora?] In-Reply-To: References: <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <20090121121931.GA8157@amd.home.annexia.org> <20090121132836.GP9111@salstar.sk> <1232545710.5013.68.camel@blaa> <1232616035.4964.5.camel@blaa> Message-ID: <1232619710.4964.25.camel@blaa> On Thu, 2009-01-22 at 11:06 +0100, Emre Erenoglu wrote: > > On Thu, Jan 22, 2009 at 10:20 AM, Mark McLoughlin > wrote: > On Wed, 2009-01-21 at 13:47 -0500, Dustin Henning wrote: > > It is probably worth noting that if someone were to run a > kernel > > update with a package manager after getting this working > (using > > information > > from later posts in this thread), they would need to do a > manual > > mkinitrd. > > > No. If you boot off /dev/vda and update the kernel, mkinitrd > will build > an initrd containing the virtio modules. > > > Well, that may depend if you use mkinitrd or mkinitramfs, and your > distribution mkinitramfs or mkinitrd may not be checking which device > type he's working on. Yes, since we're on a Fedora mailing list, I'm assuming Fedora mkinitrd :-) Cheers, Mark. From ondrejj at salstar.sk Thu Jan 22 10:36:04 2009 From: ondrejj at salstar.sk (Jan ONDREJ (SAL)) Date: Thu, 22 Jan 2009 11:36:04 +0100 Subject: Switching from IDE to virtio_blk [qas Re: [Fedora-xen] Goodbye Xen on RH/Fedora?] In-Reply-To: <1232619710.4964.25.camel@blaa> References: <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <20090121121931.GA8157@amd.home.annexia.org> <20090121132836.GP9111@salstar.sk> <1232545710.5013.68.camel@blaa> <1232616035.4964.5.camel@blaa> <1232619710.4964.25.camel@blaa> Message-ID: <20090122103604.GE30939@salstar.sk> On Thu, Jan 22, 2009 at 10:21:50AM +0000, Mark McLoughlin wrote: > On Thu, 2009-01-22 at 11:06 +0100, Emre Erenoglu wrote: > > > > On Thu, Jan 22, 2009 at 10:20 AM, Mark McLoughlin > > wrote: > > On Wed, 2009-01-21 at 13:47 -0500, Dustin Henning wrote: > > > It is probably worth noting that if someone were to run a > > kernel > > > update with a package manager after getting this working > > (using > > > information > > > from later posts in this thread), they would need to do a > > manual > > > mkinitrd. > > > > No. If you boot off /dev/vda and update the kernel, mkinitrd > > will build > > an initrd containing the virtio modules. > > > > Well, that may depend if you use mkinitrd or mkinitramfs, and your > > distribution mkinitramfs or mkinitrd may not be checking which device > > type he's working on. May be adding virtio disk drivers to initrd files always may help all users. I don't know, if there is anything, why initrd have to be small. SAL From markmc at redhat.com Thu Jan 22 10:39:08 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Thu, 22 Jan 2009 10:39:08 +0000 Subject: Switching from IDE to virtio_blk [qas Re: [Fedora-xen] Goodbye Xen on RH/Fedora?] In-Reply-To: <20090121144527.GA18495@amd.home.annexia.org> References: <4976D984.9080407@cyconix.com> <20090121082048.GD9111@salstar.sk> <20090121115039.GA7741@amd.home.annexia.org> <20090121121252.GM9111@salstar.sk> <20090121121931.GA8157@amd.home.annexia.org> <20090121132836.GP9111@salstar.sk> <1232545710.5013.68.camel@blaa> <20090121144527.GA18495@amd.home.annexia.org> Message-ID: <1232620748.4964.27.camel@blaa> On Wed, 2009-01-21 at 14:45 +0000, Richard W.M. Jones wrote: > On Wed, Jan 21, 2009 at 03:06:43PM +0100, Emre Erenoglu wrote: > > On Wed, Jan 21, 2009 at 2:48 PM, Mark McLoughlin wrote: > > > > > (This is all getting offtopic for fedora-xen, we should really move to > > > fedora-virt) > > > > > > On Wed, 2009-01-21 at 14:28 +0100, Jan ONDREJ (SAL) wrote: > > > > virtio_net works well, but I have trouble to boot from virtio_blk. > > > > > > > > I can add second disk as virto block device, but I can't boot from > > > > first disk. > > > > > > When switching from IDE to virtio, you need to first build a new initrd > > > in the guest with e.g.: > > > > > > $> mkinitrd --with virtio_pci --with virtio_blk -f > > > /boot/initrd-$(kernelversion) $(kernelversion) > > > > > > You only need to do this once. After that, if a new kernel is installed > > > while you're booted off a virtio disk, then mkinitrd will include the > > > modules automatically. > > > > > > You will also need to specify /dev/vdX on the kernel root= line and make > > sure your init script inside your initrd triggers the virtio drivers at boot > > so that the /dev/vdX are created. > > Yes I have to agree with Emre here - I don't think it's as simple as > just rebuilding mkinitrd. I got that far but gave up later on. > > /me checks notes ... > > Yup, I got as far as working out that you would have to edit fstab and > possibly /boot/grub/device.map and /boot/grub/menu.lst, before giving > up. Could this have been an x86_64 Fedora 9 xen guest? If so, you probably hit a nasty special case - the F9 x86_64 xen kernel didn't have support for running 32 bit binaries like grub, so the bootloader would never have been installed into the MBR. That works fine for pygrub, but not with KVM's real BIOS. > If anyone would like to fill in the wiki page here on the subject: > > http://wiki.libvirt.org/page/Virtio Okay, added some bits. Cheers, Mark. From pasik at iki.fi Thu Jan 22 14:32:22 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 22 Jan 2009 16:32:22 +0200 Subject: [Fedora-xen] Allow Xen hypervisor boot bzImage dom0 kernel patches In-Reply-To: <1228900754.5384.5.camel@blaa> References: <20081125214440.GH15052@edu.joroinen.fi> <1227667152.28887.26.camel@tofu.lib.ucdavis.edu> <20081126091658.GI15052@edu.joroinen.fi> <1227692057.9579.29.camel@blaa> <20081126094823.GJ15052@edu.joroinen.fi> <1227693446.9579.38.camel@blaa> <20081209162412.GX15052@edu.joroinen.fi> <1228900754.5384.5.camel@blaa> Message-ID: <20090122143222.GC15052@edu.joroinen.fi> On Wed, Dec 10, 2008 at 09:19:14AM +0000, Mark McLoughlin wrote: > On Tue, 2008-12-09 at 18:24 +0200, Pasi K?rkk?inen wrote: > > > If I find some extra time I might try building some testing RPMs with Xen pv_ops > > dom0 patches included.. > > > > Should this new unified kernel-package work out of the box (after adding > > dom0 patches), or should I use the latest kernel-xen as a starting point? > > > > I was thinking about grub menu.lst generation etc.. > > Well, the two outstanding work items that no-one is looking at are: > > * Allow the hypervisor to boot bzImage kernels > http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00685.html http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00694.html Those two patches should be it.. ? > * Make 'new-kernel-pkg' aware of HYPERVISOR setting > in /etc/sysconfig/xen > > Each of these mean that building the standard kernel with the dom0 > patches won't be enough, so you could build a kernel-xen-dom0 RPM which > a) ships a vmlinuz kernel instead of bzImage and b) adds xen.gz to > grub.conf. > > In the long run, though, what would be most useful would be if someone > started working on those two work items. > -- Pasi From markmc at redhat.com Thu Jan 22 15:05:23 2009 From: markmc at redhat.com (Mark McLoughlin) Date: Thu, 22 Jan 2009 15:05:23 +0000 Subject: [Fedora-xen] Allow Xen hypervisor boot bzImage dom0 kernel patches In-Reply-To: <20090122143222.GC15052@edu.joroinen.fi> References: <20081125214440.GH15052@edu.joroinen.fi> <1227667152.28887.26.camel@tofu.lib.ucdavis.edu> <20081126091658.GI15052@edu.joroinen.fi> <1227692057.9579.29.camel@blaa> <20081126094823.GJ15052@edu.joroinen.fi> <1227693446.9579.38.camel@blaa> <20081209162412.GX15052@edu.joroinen.fi> <1228900754.5384.5.camel@blaa> <20090122143222.GC15052@edu.joroinen.fi> Message-ID: <1232636723.4533.29.camel@blaa> On Thu, 2009-01-22 at 16:32 +0200, Pasi K?rkk?inen wrote: > On Wed, Dec 10, 2008 at 09:19:14AM +0000, Mark McLoughlin wrote: > > On Tue, 2008-12-09 at 18:24 +0200, Pasi K?rkk?inen wrote: > > > > > If I find some extra time I might try building some testing RPMs with Xen pv_ops > > > dom0 patches included.. > > > > > > Should this new unified kernel-package work out of the box (after adding > > > dom0 patches), or should I use the latest kernel-xen as a starting point? > > > > > > I was thinking about grub menu.lst generation etc.. > > > > Well, the two outstanding work items that no-one is looking at are: > > > > * Allow the hypervisor to boot bzImage kernels > > > > http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00685.html > http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00694.html > > Those two patches should be it.. ? Excellent, yep that's it. Care to update the wiki? https://fedoraproject.org/wiki/Features/XenPvopsDom0 Cheers, Mark. From pasik at iki.fi Thu Jan 22 15:59:12 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 22 Jan 2009 17:59:12 +0200 Subject: [Fedora-xen] Allow Xen hypervisor boot bzImage dom0 kernel patches In-Reply-To: <1232636723.4533.29.camel@blaa> References: <20081125214440.GH15052@edu.joroinen.fi> <1227667152.28887.26.camel@tofu.lib.ucdavis.edu> <20081126091658.GI15052@edu.joroinen.fi> <1227692057.9579.29.camel@blaa> <20081126094823.GJ15052@edu.joroinen.fi> <1227693446.9579.38.camel@blaa> <20081209162412.GX15052@edu.joroinen.fi> <1228900754.5384.5.camel@blaa> <20090122143222.GC15052@edu.joroinen.fi> <1232636723.4533.29.camel@blaa> Message-ID: <20090122155912.GF15052@edu.joroinen.fi> On Thu, Jan 22, 2009 at 03:05:23PM +0000, Mark McLoughlin wrote: > On Thu, 2009-01-22 at 16:32 +0200, Pasi K?rkk?inen wrote: > > On Wed, Dec 10, 2008 at 09:19:14AM +0000, Mark McLoughlin wrote: > > > On Tue, 2008-12-09 at 18:24 +0200, Pasi K?rkk?inen wrote: > > > > > > > If I find some extra time I might try building some testing RPMs with Xen pv_ops > > > > dom0 patches included.. > > > > > > > > Should this new unified kernel-package work out of the box (after adding > > > > dom0 patches), or should I use the latest kernel-xen as a starting point? > > > > > > > > I was thinking about grub menu.lst generation etc.. > > > > > > Well, the two outstanding work items that no-one is looking at are: > > > > > > * Allow the hypervisor to boot bzImage kernels > > > > > > > http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00685.html > > http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00694.html > > > > Those two patches should be it.. ? > > Excellent, yep that's it. > > Care to update the wiki? > > https://fedoraproject.org/wiki/Features/XenPvopsDom0 > Or actually this (complete/fixed) patch: http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00699.html I'm in the process of creating my Fedora account so let's see if I get it done and can edit that page then.. -- Pasi From pasik at iki.fi Thu Jan 22 16:14:57 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 22 Jan 2009 18:14:57 +0200 Subject: [Fedora-xen] Allow Xen hypervisor boot bzImage dom0 kernel patches In-Reply-To: <20090122155912.GF15052@edu.joroinen.fi> References: <1227667152.28887.26.camel@tofu.lib.ucdavis.edu> <20081126091658.GI15052@edu.joroinen.fi> <1227692057.9579.29.camel@blaa> <20081126094823.GJ15052@edu.joroinen.fi> <1227693446.9579.38.camel@blaa> <20081209162412.GX15052@edu.joroinen.fi> <1228900754.5384.5.camel@blaa> <20090122143222.GC15052@edu.joroinen.fi> <1232636723.4533.29.camel@blaa> <20090122155912.GF15052@edu.joroinen.fi> Message-ID: <20090122161457.GH15052@edu.joroinen.fi> On Thu, Jan 22, 2009 at 05:59:12PM +0200, Pasi K?rkk?inen wrote: > On Thu, Jan 22, 2009 at 03:05:23PM +0000, Mark McLoughlin wrote: > > On Thu, 2009-01-22 at 16:32 +0200, Pasi K?rkk?inen wrote: > > > On Wed, Dec 10, 2008 at 09:19:14AM +0000, Mark McLoughlin wrote: > > > > On Tue, 2008-12-09 at 18:24 +0200, Pasi K?rkk?inen wrote: > > > > > > > > > If I find some extra time I might try building some testing RPMs with Xen pv_ops > > > > > dom0 patches included.. > > > > > > > > > > Should this new unified kernel-package work out of the box (after adding > > > > > dom0 patches), or should I use the latest kernel-xen as a starting point? > > > > > > > > > > I was thinking about grub menu.lst generation etc.. > > > > > > > > Well, the two outstanding work items that no-one is looking at are: > > > > > > > > * Allow the hypervisor to boot bzImage kernels > > > > > > > > > > http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00685.html > > > http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00694.html > > > > > > Those two patches should be it.. ? > > > > Excellent, yep that's it. > > > > Care to update the wiki? > > > > https://fedoraproject.org/wiki/Features/XenPvopsDom0 > > > > Or actually this (complete/fixed) patch: > http://lists.xensource.com/archives/html/xen-devel/2009-01/msg00699.html > > I'm in the process of creating my Fedora account so let's see if I get it > done and can edit that page then.. > Ok, XenPvopsDom0 wiki page modified.. I added the link to the patch. -- Pasi From pasik at iki.fi Sat Jan 24 13:36:35 2009 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Sat, 24 Jan 2009 15:36:35 +0200 Subject: [Fedora-xen] Features/XenPvops wiki page updated Message-ID: <20090124133635.GO15052@edu.joroinen.fi> Hello! I updated Features/XenPvops wiki page.. I added a note about information there being outdated, and a link to current upstream pv_ops status page, and a note about kernel-xen being dropped. And a couple of other small changes. https://fedoraproject.org/wiki/Features/XenPvops -- Pasi From crobinso at redhat.com Mon Jan 26 20:02:23 2009 From: crobinso at redhat.com (Cole Robinson) Date: Mon, 26 Jan 2009 15:02:23 -0500 Subject: [Fedora-xen] [ANNOUNCE] New release virt-manager 0.6.1 Message-ID: <497E16CF.2080209@redhat.com> I'm happy to announce a new virt-manager release, version 0.6.1. The release can be downloaded from: http://virt-manager.org/download.html The direct download link is: http://virt-manager.org/download/sources/virt-manager/virt-manager-0.6.1.tar.gz This release includes: - VM disk and network stats reporting (Guido Gunther) - VM Migration support (Shigeki Sakamoto) - Support for adding sound devices to an existing VM - Enumerate host devices attached to an existing VM - Allow specifying a device model when adding a network device to an existing VM - Combine the serial console view with the VM Details window - Allow connection to multiple VM serial consoles - Bug fixes and many minor improvements. Thanks to everyone who has contributed to this release through testing, bug reporting, submitting patches, and otherwise sending in feedback! Thanks, Cole From crobinso at redhat.com Mon Jan 26 20:02:32 2009 From: crobinso at redhat.com (Cole Robinson) Date: Mon, 26 Jan 2009 15:02:32 -0500 Subject: [Fedora-xen] [ANNOUNCE] New release virtinst 0.400.1 Message-ID: <497E16D8.8080601@redhat.com> I'm happy to announce a new virtinst release, version 0.4.1. The release can be downloaded from: http://virt-manager.org/download.html The direct download link is: http://virt-manager.org/download/sources/virtinst/virtinst-0.400.1.tar.gz This release includes: - Add virt-image -> vmx support to virt-convert, replacing virt-pack (Joey Boggs) - Add disk checksum support to virt-image (Joey Boggs) - Enhanced URL install support: Debian Xen paravirt, Ubuntu kernel and boot.iso, Mandriva kernel, and Solaris Xen Paravirt (Guido Gunther, John Levon, Cole Robinson) - Expanded test suite - Numerous bug fixes, cleanups, and minor improvements Thanks to everyone who has contributed to this release through testing, bug reporting, submitting patches, and otherwise sending in feedback! Thanks, Cole From m.a.young at durham.ac.uk Wed Jan 28 11:58:05 2009 From: m.a.young at durham.ac.uk (M A Young) Date: Wed, 28 Jan 2009 11:58:05 +0000 (GMT) Subject: [Fedora-xen] Should kernel 2.6.27.5-41.fc9 boot as xen guest? In-Reply-To: <1227883984.3643.34.camel@blaa> References: <1227883984.3643.34.camel@blaa> Message-ID: On Fri, 28 Nov 2008, Mark McLoughlin wrote: > The F-9 kernel-xen packages are the only ones expected to work for an > F-9 Xen DomU, but it does appear the F-9 2.6.27 kernels (32 and 64 bit > x86) are being built with CONFIG_XEN ... so, they may well work. The latest kernel 2.6.27.12-78.2.8.fc9.i686.PAE does indeed work as a Xen Guest, possibly as a result of the xen execshield patches being added. Michael Young From fedora at guagua.fi Sat Jan 31 10:03:41 2009 From: fedora at guagua.fi (=?ISO-8859-1?Q?Veli-Pekka_Kestil=E4?=) Date: Sat, 31 Jan 2009 12:03:41 +0200 Subject: [Fedora-xen] Problem with DomU networking Message-ID: <498421FD.8030708@guagua.fi> Hi, I have following problem with paravirtualised setup: - Have Fedora 7 Dom0 (Yeah I know it's old, but haven't gotten client to upgrade it yet to CentOS) - DomU is CentOS5.2 On testing environment everything works fine, but in production CentOS can't get ip-addess from Dom0 Strange thing is that FC7 client works without a problem with exactly same xen config From logs I can see that dhcpd server running on Dom0 sees the DHCPREQUEST messages and answers to them, but DomU never recives them. Greetings, Veli-Pekka From fedora at guagua.fi Sat Jan 31 13:46:28 2009 From: fedora at guagua.fi (=?ISO-8859-1?Q?Veli-Pekka_Kestil=E4?=) Date: Sat, 31 Jan 2009 15:46:28 +0200 Subject: [Fedora-xen] Problem with DomU networking In-Reply-To: <498421FD.8030708@guagua.fi> References: <498421FD.8030708@guagua.fi> Message-ID: <49845634.7050602@guagua.fi> Veli-Pekka Kestil? wrote: > > Hi, > > I have following problem with paravirtualised setup: > > - Have Fedora 7 Dom0 (Yeah I know it's old, but haven't gotten > client to upgrade it yet to CentOS) > - DomU is CentOS5.2 > > On testing environment everything works fine, but in production CentOS > can't get ip-addess from Dom0 > Strange thing is that FC7 client works without a problem with exactly > same xen config > > From logs I can see that dhcpd server running on Dom0 sees the > DHCPREQUEST messages and answers to them, but DomU never recives them. Small addition: With fixed ip everything works and what I saw from tcpdump it seems that only servers DHCP-responses to client get lost inside the bridge. Greetings, Veli-Pekka