virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <linux@treblig.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>,
	Grant McWilliams <grantmasterflash@gmail.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	Xen-devel <xen-devel@lists.xensource.com>,
	xen-users@lists.xensource.com
Subject: Re: [Xen-users] Re: [Xen-devel] State of Xen in upstream Linux
Date: Thu, 31 Jul 2008 19:36:35 +0100	[thread overview]
Message-ID: <20080731183634.GA27147@gallifrey> (raw)
In-Reply-To: <4891FFBA.1020702@goop.org>

* Jeremy Fitzhardinge (jeremy@goop.org) wrote:
> Grant McWilliams wrote:

<snip>

> > 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.

Does that include things like /proc/cpuinfo?  Current Dom0's seem
to lose some of the physical IDs information from there.

Dave
-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    | Running GNU/Linux on Alpha,68K| Happy  \ 
\ gro.gilbert @ treblig.org | MIPS,x86,ARM,SPARC,PPC & HPPA | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/

  parent reply	other threads:[~2008-07-31 18:36 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       ` Dr. David Alan Gilbert [this message]
2008-07-31 18:45         ` 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=20080731183634.GA27147@gallifrey \
    --to=linux@treblig.org \
    --cc=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).