qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
	xen-devel@lists.xensource.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] Option ROM for booting from SCSI/PV disks
Date: Thu, 20 Dec 2007 13:45:46 +0200	[thread overview]
Message-ID: <476A55EA.7020508@qumranet.com> (raw)
In-Reply-To: <4756D0E0.2040500@us.ibm.com>

Anthony Liguori wrote:
> Hi,
>
> The attached patch is an option ROM that allows x86 guests to boot
> from any block device supported by QEMU (and the guest kernel).  It
> works by hijacking the BIOS int13 function and then uses a very simply
> protocol to communicate all block requests to QEMU.
>
> This patch also adds a "boot=on|off" parameter to the -drive option. 
> When this option is specified, the extboot option ROM is automatically
> loaded and this device will be exposes by int13 as '0x80'.  What
> '-boot c' really means is boot from the first disk driver or BIOS
> drive '0x80' so the -boot option is complimentary to this new boot flag.
>
> I have successfully booted Linux, Win2k, and WinXP from SCSI with this
> patch.  Windows takes a bit of prep work to be able to boot from
> SCSI.   For win2k, you just need to make sure you have the right
> driver installed.  WinXP, however, seems to require that it be
> installed on SCSI to boot from SCSI.  If anyone knows how to modify
> WinXP after the fact, please let me know.
>
> I can also use this new flag to boot a Linux guest from my previously
> posted virtio blk driver.
>
> This patch is against my previous virtio patches but does not strictly
> depend on them.  When applying this patch, you'll have to build
> extboot in extboot/ and then copy extboot/extboot.bin to
> pc-bios/extboot.bin.

Now that we have scsi support (with -drive) I would like to apply this
to the kvm tree (I already applied the CHS refactoring patch).  But as
qemu seems to shy away from sources which can only compile on x86, can
you rearrange it to build outside the qemu/ dir (i.e. a new toplevel
extboot/)?

The qemu changes should be in a separate patch.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

      reply	other threads:[~2007-12-21 10:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-05 16:25 [Qemu-devel] [PATCH 2/2] Option ROM for booting from SCSI/PV disks Anthony Liguori
2007-12-20 11:45 ` Avi Kivity [this message]

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=476A55EA.7020508@qumranet.com \
    --to=avi@qumranet.com \
    --cc=aliguori@us.ibm.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=qemu-devel@nongnu.org \
    --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 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).