All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Nate Carlson <natecars@natecarlson.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen Paravirt
Date: Wed, 18 Jul 2007 22:04:01 -0700	[thread overview]
Message-ID: <469EF0C1.80907@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0707182305170.6206@tungsten.msp.technicality.org>

Nate Carlson wrote:
> On Wed, 18 Jul 2007, Jeremy Fitzhardinge wrote:
>> If you build the kernel with CONFIG_PARAVIRT=y, CONFIG_XEN=y and
>> enable the Xen console, block and net devices (they will default =y),
>> then you should be able to use the resulting kernel with an existing
>> Xen installation (it will also boot native).  Unfortunately you can't
>> use the same actual kernel image file in both cases, but you can use
>> the same modules.
>
> Just curious, will that change?  :)

Yeah, it's a work in progress.  I have some test patches to extend the
bzImage format to contain ELF notes, and a corresponding Xen patch to
add a new file format for the domain builder. But its a bit
up-in-the-air because nobody has agreed to the bzImage format changes,
and its all a bit subtle to make sure it keeps working with a wide range
of fairly poorly implemented bootloaders.

    J

  reply	other threads:[~2007-07-19  5:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-18 22:45 Xen Paravirt Chuck Short
2007-07-18 23:46 ` Jeremy Fitzhardinge
2007-07-19  4:05   ` Nate Carlson
2007-07-19  5:04     ` Jeremy Fitzhardinge [this message]
2007-07-19  6:17 ` Ian Campbell

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=469EF0C1.80907@goop.org \
    --to=jeremy@goop.org \
    --cc=natecars@natecarlson.com \
    --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.