qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hans de Bruin <bruinjm@xs4all.nl>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] virtio disk
Date: Tue, 11 Aug 2009 19:13:10 +0200	[thread overview]
Message-ID: <4A81A6A6.50006@xs4all.nl> (raw)
In-Reply-To: <4A815E3C.7060506@redhat.com>

Avi Kivity wrote:
 > On 08/10/2009 10:58 PM, Hans de Bruin wrote:
 >> I am trying to get my qemu vm to boot of 'VIRTIO_BLOCK', but am not
 >> very successful. I have got two setups:
 >>
 >> A two day old qemu tree from git://git.savannah.nongnu.org/qemu
 >> on a jetway board with a non kvm capable via c7 proc (30W),
 >>
 >> and an older qemu-kvm (kvm-88-6-g2ebe329 (10.?)) on a AMD proc (130W)
 >>
 >> The AMD boots guests with virtio_block, either with the -kernel switch
 >> or via the bios. The ViaC7 wil not. Nor the bios nor the kernel detect
 >> the vitio block device.
 >>
 >> Somewhere on the internet I found this qemu-kvm option:
 >>
 >>  -drive file=vmdisk1,if=virtio,boot=on
 >>
 >> This boot=on, isn't in either of the man pages. qemu doesn't accept
 >> this option. qemu-kvm needs it to let the bios boot from the
 >> virtio_block device. I also noticed the qemu-kvm bios has a boot menu
 >> which can be accessed by F12. qemu has not.
 >>
 >
 > boot=on is in qemu-kvm.git but not in qemu.git yet.

That is clear, but with or without boot=on, the qemu tree should provide 
my guest with a blockdevice, which somehow I am missing. For me the 
solution is simple just switch to the kvm tree.

In wat way will this boot=on eventually end up in the man pages? In both 
trees the MAINTAINERS file does not contain a word about documentation.

-- 
Hans

  reply	other threads:[~2009-08-11 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 19:58 [Qemu-devel] virtio disk Hans de Bruin
2009-08-11 12:04 ` Avi Kivity
2009-08-11 17:13   ` Hans de Bruin [this message]
2009-08-11 18:51     ` Hans de Bruin

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=4A81A6A6.50006@xs4all.nl \
    --to=bruinjm@xs4all.nl \
    --cc=avi@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).