Hey, When this build finishes:
http://koji.fedoraproject.org/koji/buildinfo?buildID=57402
rawhide kernel-PAE.i686 and kernel.x86_64 will contain support for i686 and x86_64 Xen DomU guests.
We've added Obsoletes/Provides, so a simple yum update should work fine[1].
Today the world has been made a little more sane. Rejoice :-)
Cheers, Mark.
[1] - With the caveat that the new kernel won't be made the default in grub.conf ... I'll fix up that soon, see:
On Thu, 24 Jul 2008, Mark McLoughlin wrote:
When this build finishes:
http://koji.fedoraproject.org/koji/buildinfo?buildID=57402
rawhide kernel-PAE.i686 and kernel.x86_64 will contain support for i686 and x86_64 Xen DomU guests.
We've added Obsoletes/Provides, so a simple yum update should work fine[1].
Today the world has been made a little more sane. Rejoice :-)
But not dom0 right?
Is there a doc somewhere to say how to migrate from Xen boots using rootfs (not bootable disk image) to kvm?
Paul
On Thu, 2008-07-24 at 14:24 -0400, Paul Wouters wrote:
On Thu, 24 Jul 2008, Mark McLoughlin wrote:
When this build finishes:
http://koji.fedoraproject.org/koji/buildinfo?buildID=57402
rawhide kernel-PAE.i686 and kernel.x86_64 will contain support for i686 and x86_64 Xen DomU guests.
We've added Obsoletes/Provides, so a simple yum update should work fine[1].
Today the world has been made a little more sane. Rejoice :-)
But not dom0 right?
Correct; no dom0 support.
Is there a doc somewhere to say how to migrate from Xen boots using rootfs (not bootable disk image) to kvm?
You mean it's a disk image with no partition table and bootloader?
So, you're booting the guest by specifying a kernel and initrd along with the disk image?
If so, you should be able to do exactly the same with KVM - you'll just need to manually create a suitable initrd using whatever method you used to create the original initrd for Xen.
But no, I don't know of any good docs describing how to migrate xen guests to KVM ... it'd be very cool if someone could write something up on fedoraproject.org/wiki as they go through the process, though ...
Cheers, Mark.
On Fri, Jul 25, 2008 at 03:46:33PM +0100, Mark McLoughlin wrote:
On Thu, 2008-07-24 at 14:24 -0400, Paul Wouters wrote:
On Thu, 24 Jul 2008, Mark McLoughlin wrote:
When this build finishes:
http://koji.fedoraproject.org/koji/buildinfo?buildID=57402
rawhide kernel-PAE.i686 and kernel.x86_64 will contain support for i686 and x86_64 Xen DomU guests.
We've added Obsoletes/Provides, so a simple yum update should work fine[1].
Today the world has been made a little more sane. Rejoice :-)
But not dom0 right?
Correct; no dom0 support.
I rebuilt my test/debug box with fedora 9 to find that it will not do dom0. I am going to have to wipe & install fedora 8 or CentOS 5 or something.
1) will dom0 appear (be added back) at some point in fedora 9 lifetime ?
2) why was it taken out ?
I gather that dom0 support will be added back in fedora 10.
Hi,
All your questions are covered in the archives, btw ...
On Fri, 2008-07-25 at 15:59 +0100, Alain Williams wrote:
- will dom0 appear (be added back) at some point in fedora 9 lifetime ?
Highly unlikely it'll appear as an F9 update, no.
- why was it taken out ?
kernel-xen lagged the bare-metal kernel by several release; we no longer wanted to waste time forward porting the 2.6.18 tree, so we switched over to what's upstream - 32 and 64 bit pv_ops DomU
See also:
http://markmc.fedorapeople.org/XenSummit.pdf
I gather that dom0 support will be added back in fedora 10.
That's looking rather unlikely at this point since there hasn't been much progress of late.
It'll be in Fedora as soon (and maybe even shortly before) it's available upstream in Linus's tree.
Cheers, Mark.
Mark McLoughlin wrote:
On Thu, 2008-07-24 at 14:24 -0400, Paul Wouters wrote:
On Thu, 24 Jul 2008, Mark McLoughlin wrote:
When this build finishes:
http://koji.fedoraproject.org/koji/buildinfo?buildID=57402
rawhide kernel-PAE.i686 and kernel.x86_64 will contain support for i686 and x86_64 Xen DomU guests.
We've added Obsoletes/Provides, so a simple yum update should work fine[1].
Today the world has been made a little more sane. Rejoice :-)
But not dom0 right?
Correct; no dom0 support.
Is there a doc somewhere to say how to migrate from Xen boots using rootfs (not bootable disk image) to kvm?
You mean it's a disk image with no partition table and bootloader?
So, you're booting the guest by specifying a kernel and initrd along with the disk image?
If so, you should be able to do exactly the same with KVM - you'll just need to manually create a suitable initrd using whatever method you used to create the original initrd for Xen.
But no, I don't know of any good docs describing how to migrate xen guests to KVM ... it'd be very cool if someone could write something up on fedoraproject.org/wiki as they go through the process, though ...
There's a tool, I don't have the name handy, but I saw it on either the rawhide or FC9-testing update notices. Give me an hour or two to look on the machine I use for that stuff and I'll post it.
On Thu, 2008-07-24 at 14:24 -0400, Paul Wouters wrote:
Is there a doc somewhere to say how to migrate from Xen boots using rootfs (not bootable disk image) to kvm?
There are some of us with some fairly substantial servers bought just a few years ago that don't have hardware virtualization support. I believe KVM still requires such support, and I don't know if that's ever going to change.
So, until there is a new dom0 in Fedora there will be us poor souls living back on F8 with little budget to swap out and buy HVM capable hardware. As long as future fedora domU's continue to work on F8 dom0, I suppose we can float along for a couple of releases until something changes.
It's a little worrisome that patches won't be forthcoming for F8, but we can mitigate that somewhat by running little more than the hypervisor on the dom0.
Keep up the great work and forward momentum, but have pity on those of us using Fedora in production with the above limitations.
On Sat, Jul 26, 2008 at 10:35 AM, Dale Bewley dlbewley@lib.ucdavis.edu wrote:
On Thu, 2008-07-24 at 14:24 -0400, Paul Wouters wrote:
Is there a doc somewhere to say how to migrate from Xen boots using rootfs (not bootable disk image) to kvm?
There are some of us with some fairly substantial servers bought just a few years ago that don't have hardware virtualization support. I believe KVM still requires such support, and I don't know if that's ever going to change.
So, until there is a new dom0 in Fedora there will be us poor souls living back on F8 with little budget to swap out and buy HVM capable hardware. As long as future fedora domU's continue to work on F8 dom0, I suppose we can float along for a couple of releases until something changes.
It's a little worrisome that patches won't be forthcoming for F8, but we can mitigate that somewhat by running little more than the hypervisor on the dom0.
Keep up the great work and forward momentum, but have pity on those of us using Fedora in production with the above limitations.
I think that in those cases for long term support you will want to Look at running RHEL/CentOS-5 for the Dom0. This should allow you to have the DomU's to be newer versions and keep the non-HVM hardware useful.
-- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
On Sat, Jul 26, 2008 at 09:35:51AM -0700, Dale Bewley wrote:
On Thu, 2008-07-24 at 14:24 -0400, Paul Wouters wrote:
Is there a doc somewhere to say how to migrate from Xen boots using rootfs (not bootable disk image) to kvm?
There are some of us with some fairly substantial servers bought just a few years ago that don't have hardware virtualization support. I believe KVM still requires such support, and I don't know if that's ever going to change.
So, until there is a new dom0 in Fedora there will be us poor souls living back on F8 with little budget to swap out and buy HVM capable hardware. As long as future fedora domU's continue to work on F8 dom0, I suppose we can float along for a couple of releases until something changes.
It's a little worrisome that patches won't be forthcoming for F8, but we can mitigate that somewhat by running little more than the hypervisor on the dom0.
Keep up the great work and forward momentum, but have pity on those of us using Fedora in production with the above limitations.
We feel the pain too. We'd love to be able to offer a virtualization host which didn't require hardware virt support, but its just not viable until Dom0 is ported to pv_ops. The best bet if you want something to use in a production scenario is to use RHEL-5 or CentOS-5, since these have a much longer lifetime than Fedora for updates & hardware enablement (Fedora 8 will go end-of-life shortly after f10 comes out).
Daniel
xen@lists.stg.fedoraproject.org