virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Grant McWilliams <grantmasterflash@gmail.com>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>,
	Xen-devel <xen-devel@lists.xensource.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: State of Xen in upstream Linux
Date: Thu, 31 Jul 2008 11:08:58 -0700	[thread overview]
Message-ID: <4891FFBA.1020702@goop.org> (raw)
In-Reply-To: <ed123fa30807311054p4965f43bod78dafa6626c9c2d@mail.gmail.com>

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?
>
> Or am I reading this completely wrong?

If you boot the kernel on bare hardware, the Xen parts of the kernel
will basically be switched off, and play no part in runtime.  All
hardware features and device drivers should be available as normal.  I
run kvm on pvops/xen kernels all the time.

If you boot the kernel under Xen, then VT/SVM will not be available, and
any kernel module which tries to use them - like kvm or (I presume)
virtualbox - should quietly get out of the way.  If they cause the
domain to crash, then that's a bug in those modules.

If by "the machine will reboot" you mean that the whole system crashes,
then that's definitely a bug in Xen which should be fixed.  It should
never be possible for a domU to crash the system.

    J

  reply	other threads:[~2008-07-31 18:08 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     ` Jeremy Fitzhardinge [this message]
2008-07-31 18:19       ` [Xen-users] " 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     ` Re: [Xen-devel] " Daniel P. Berrange

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=4891FFBA.1020702@goop.org \
    --to=jeremy@goop.org \
    --cc=berrange@redhat.com \
    --cc=grantmasterflash@gmail.com \
    --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).