All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Duffy <cduffy@spamcop.net>
To: xen-devel@lists.xensource.com
Subject: Re: VT-X processors , xen 3.0 , drives and virtualization (in 32 bit environment)
Date: Tue, 27 Dec 2005 06:42:18 -0600	[thread overview]
Message-ID: <dorcrb$3j8$1@sea.gmane.org> (raw)
In-Reply-To: <d0383f90512270103q6d9d1957l951220f32f2755ec@mail.gmail.com>

Ian Brown wrote:
>  1) True to now and the current xen-3.0 version: When running Xen 3.0
>  on these VT processors, can we run an unmodified kernel ?

For your DomUs, yes. For your Dom0, no. Running a modified DomU kernel 
should be more performant.

>  and in such a case, what about the device drivers - isn't there a
>  problem with them ?

Emulated hardware, based off of drivers borrowed from QEMU, is provided 
to VMX domains. The drivers they need will be for the emulated cards, 
not for the real devices in the machine.

> I mean , in practical terms , if I will set my bootloader to have the
> following entry on a machine with VT-x processor:
>  kernel /xen.gz dom0_mem=x
>  module /vmlinuz-#version ro root=...
>  (and initrd if needed)

No, that won't work, because that's trying to use an unmodified kernel 
as Dom0.

> will I be
> able to create a new domain based also on unmodified vmlinuz-#version
> kernel ?

Yes, though VMX domains work a bit differently from non-VMX ones -- the 
process won't be exactly the same except with a non-Xen-enabled kernel.

  reply	other threads:[~2005-12-27 12:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-27  9:03 VT-X processors , xen 3.0 , drives and virtualization (in 32 bit environment) Ian Brown
2005-12-27 12:42 ` Charles Duffy [this message]
2005-12-27 19:09   ` Ian Brown
2005-12-28  2:07     ` Anthony Liguori

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='dorcrb$3j8$1@sea.gmane.org' \
    --to=cduffy@spamcop.net \
    --cc=xen-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.