qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: gpxe@etherboot.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] [virtio] Add virtio block device sanboot support
Date: Wed, 06 Jan 2010 10:27:52 +0100	[thread overview]
Message-ID: <4B445798.7040401@redhat.com> (raw)
In-Reply-To: <fbd9d3991001051246xfce2a6dx6c97f31895d4d955@mail.gmail.com>

On 01/05/10 21:46, Stefan Hajnoczi wrote:
> This patch adds virtio block device support alongside the existing iSCSI,
> ATA-over-Ethernet, and ramdisk block devices.  The virtio block device provides
> storage in virtualized environments.
>
> Using this patch, a gPXE option ROM can boot a QEMU/KVM virtual machine
> directly from a virtio block device.

Great.

> Here is an example QEMU invocation:
> qemu -drive if=virtio,file=debian.qcow2 -option-rom gpxe/src/bin/1af41001.rom

> Perhaps the first available device should be chosen if virtio_blk: is given
> without PCI bus, device, and function.  I am open to suggestions on how virtio
> block device option ROMs should work.

Clear answer: as PCI ROM.

Try this (requires qemu 0.12):

qemu -drive if=none,id=boot,file=debian.qcow2 \
      -device virtio-blk-pci,drive=boot,romfile=gpxe/src/bin/1af41001.rom

You should end up with a virtio-blk device with a pci rom bar holding 
the option rom.  seabios should load and run the rom.  The disk should 
appear in the boot menu (enabled by '-boot menu=on').

cheers,
   Gerd

      reply	other threads:[~2010-01-06  9:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-05 20:46 [Qemu-devel] [PATCH] [virtio] Add virtio block device sanboot support Stefan Hajnoczi
2010-01-06  9:27 ` Gerd Hoffmann [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=4B445798.7040401@redhat.com \
    --to=kraxel@redhat.com \
    --cc=gpxe@etherboot.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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).