All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: PATCH 0/3: Direct linux kernel boot for HVM
Date: Wed, 19 Dec 2007 13:00:36 +0000	[thread overview]
Message-ID: <20071219130036.GA16524@redhat.com> (raw)
In-Reply-To: <C38EA76D.1A066%Keir.Fraser@cl.cam.ac.uk>

On Wed, Dec 19, 2007 at 10:48:13AM +0000, Keir Fraser wrote:
> On 19/12/07 05:38, "Daniel P. Berrange" <berrange@redhat.com> wrote:
> 
> > Those who saw Chris Wright give my Xen summit presentation a few weeks back
> > may remember one of the proposals was to support direct linux kernel boot
> > for HVM guests. ie, the ability to have a guest boot off a kernel, initrd,
> > and args instead of merely the BIOS supported disk/cdrom/network.
> 
> Is the aim to be able to boot from any device that can be plumbed to qemu,
> or to allow kernel/initrd parms to be specified from outside the HVM
> bootloader config file? If the former, Anthony Liguori's recent patch to
> implement an option ROM to allow easy cut-thru to any qemu backend device
> looks like an easier way to achieve that aim.

It is the latter - just to allow boot from external kernl/initrd/params.
This is basically making 

   qemu-dm -kernel /path/to/vmlinux -initrd /path/initrd -append 'someargs'

work in Xen the same way it works in current upstream QEMU. 

Currently this hooks in QEMU's boot by writing a fake MBR into the first
harddisk. Once anthony's option ROM patch is accepted upstream they could 
be leveraged to get rid of the MBR hook (indeed anthony's patches include
this optimization). This is only a very minor part of the code though, so
the bulk of this patch would still remain.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2007-12-19 13:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-19  5:38 PATCH 0/3: Direct linux kernel boot for HVM Daniel P. Berrange
2007-12-19  5:41 ` PATCH 1/3: XenD changes for HVM kernel boot Daniel P. Berrange
2007-12-19  5:42 ` PATCH 2/3: Support booting relocatable kernels Daniel P. Berrange
2007-12-19  5:44   ` Daniel P. Berrange
2007-12-19  5:43 ` PATCH 3/3: Support boot of NON-relocatable kernels Daniel P. Berrange
2007-12-19 10:48 ` PATCH 0/3: Direct linux kernel boot for HVM Keir Fraser
2007-12-19 13:00   ` Daniel P. Berrange [this message]
2007-12-19 14:43     ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2008-01-31 17:48 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=20071219130036.GA16524@redhat.com \
    --to=berrange@redhat.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --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.