From: "Daniel P. Berrange" <berrange@redhat.com>
To: Grant McWilliams <grantmasterflash@gmail.com>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Xen-devel <xen-devel@lists.xensource.com>,
xen-users@lists.xensource.com
Subject: Re: Re: [Xen-devel] State of Xen in upstream Linux
Date: Fri, 1 Aug 2008 09:34:53 +0100 [thread overview]
Message-ID: <20080801083453.GB23993@redhat.com> (raw)
In-Reply-To: <ed123fa30807311054p4965f43bod78dafa6626c9c2d@mail.gmail.com>
On Thu, Jul 31, 2008 at 10:54:38AM -0700, Grant McWilliams wrote:
> >
> >
> > > Fedora 9's kernel-xen package has been based on the mainline kernel from
> > > the outset, but it is still packaged as a separate kernel. kernel-xen
> > > has been dropped from rawhide (what will become Fedora 10), and all Xen
> > > support - both 32 and 64 bit - has been rolled into the main kernel
> > > package.
> >
>
> Does this mean in the future all Fedora kernels will be Xen kernels? Is this
> wise? If I try to run VirtualBox on a Xen kernel the machine will reboot. If
> the Vbox module is loaded at runtime it will reboot forever. Yes, I know
> it's a Vbox issue but what about KVM. Can we run KVM on a Xen kernel?
The way paravirt_ops works is that the single kernel image has built in
support for a number of hypervisors, as well as, bare metal. When it boots
one of the first things the kernel does it probe to find what its running
on. It then switches in the various Xen, KVM or VMWare specific functions
as required for that platform, or continues running as bare metal. The
Fedora kernels have Xen, KVM and VMI support enabled by default now as
of Fedora 10 (VMI is 32-bit only). Basically it should 'just work' and
do the right thing out of the box.
VirtualBox is using out of tree kernel modules so all bets are off as to
whether it works on any particular kernel. If virtualbox is important to
you, then encourage their developers to get the functionality they need
into the mainline kernel because that's the only way it'll be supportable
long term. We can't guarentee that it won't break in a future Fedora
kernel update as long as it is out of tree.
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 :|
prev parent reply other threads:[~2008-08-01 8:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 0:51 State of Xen in upstream Linux Jeremy Fitzhardinge
2008-07-31 9:08 ` [Xen-devel] " Daniel P. Berrange
2008-07-31 17:54 ` Grant McWilliams
2008-07-31 18:08 ` [Xen-users] " Jeremy Fitzhardinge
2008-07-31 18:19 ` [Xen-users] Re: [Xen-devel] " Alexey Eremenko
2008-07-31 18:28 ` [Xen-users] " Jeremy Fitzhardinge
2008-07-31 18:48 ` Re: [Xen-devel] " Grant McWilliams
2008-07-31 18:58 ` [Xen-users] " Jeremy Fitzhardinge
2008-07-31 20:07 ` Re: [Xen-devel] " Grant McWilliams
2008-07-31 20:14 ` [Xen-users] " Jeremy Fitzhardinge
2008-07-31 18:36 ` [Xen-users] Re: [Xen-devel] " Dr. David Alan Gilbert
2008-07-31 18:45 ` [Xen-users] " Jeremy Fitzhardinge
2008-08-01 8:34 ` Daniel P. Berrange [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080801083453.GB23993@redhat.com \
--to=berrange@redhat.com \
--cc=grantmasterflash@gmail.com \
--cc=jeremy@goop.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).