qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Bruce Rogers <brogers@novell.com>
Cc: qemu-devel@nongnu.org, Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] Is this an invalid combination?
Date: Tue, 15 Feb 2011 14:21:41 -0600	[thread overview]
Message-ID: <4D5AE055.1090102@codemonkey.ws> (raw)
In-Reply-To: <4D5A7A8D02000048000AA029@novprvoes0310.provo.novell.com>

On 02/15/2011 02:07 PM, Bruce Rogers wrote:
> Hi,
>
> We just noticed an issue flagged by a libvirt based test.  This same command line didn't used to fail, and I wanted to be sure that this is behaving as intended.
>
> When the following command line is used on the current qemu version:
>
> x86_64-softmmu/qemu-system-x86_64 -kernel /boot/vmlinuz -drive file=~/disk0.raw,if=none,id=foo,boot=on -device virtio-blk-pci,drive=foo
>
> We get the following error reported:
> Two devices with same boot index 0
>
> Previous versions of qemu did not flag this as an error condition.
>    

Upstream QEMU does not have a boolean boot flag although I guess we 
ignore it in -drive which sucks :-/

In upstream QEMU, the BIOS can boot just fine from a virtio device.  
What you're seeing is that we've apparently overloaded the boot flag in 
upstream qemu to mean boot index.

Gleb, what's the right invocation here?

Regards,

ANthony Liguori

> I can see that we are indicating two different boot sources here, so I would guess the command line is invalid, but wanted to be sure.
>
> Bruce
>
>
>    

  reply	other threads:[~2011-02-15 20:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15 20:07 [Qemu-devel] Is this an invalid combination? Bruce Rogers
2011-02-15 20:21 ` Anthony Liguori [this message]
2011-02-15 20:28   ` Gleb Natapov
2011-02-15 20:30     ` Gleb Natapov
2011-02-15 20:32       ` Bruce Rogers
2011-02-15 20:28   ` Bruce Rogers

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=4D5AE055.1090102@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=brogers@novell.com \
    --cc=gleb@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).