All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Lieven <pl@dlh.net>
To: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: qemu-kvm 0.15.0 boot order not working
Date: Mon, 29 Aug 2011 12:12:14 +0200	[thread overview]
Message-ID: <4E5B65FE.7020101@dlh.net> (raw)

Hi,

when I specify something like

qemu -boot order=dc -cdrom image.iso -drive file=img.raw,if=virtio,boot=yes

or

qemu -boot order=n -cdrom image.iso -drive file=img.raw,if=virtio,boot=yes

with qemu-kvm 0.15.0

it will always directly boot from the hardrive and not from cdrom or 
network.
is this on purpose? the behaviour was different in earlier versions.
If i omit the boot=yes in the drive specification the "-boot order" 
parameter is working
as expected.

Peter

WARNING: multiple messages have this Message-ID (diff)
From: Peter Lieven <pl@dlh.net>
To: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] qemu-kvm 0.15.0 boot order not working
Date: Mon, 29 Aug 2011 12:12:14 +0200	[thread overview]
Message-ID: <4E5B65FE.7020101@dlh.net> (raw)

Hi,

when I specify something like

qemu -boot order=dc -cdrom image.iso -drive file=img.raw,if=virtio,boot=yes

or

qemu -boot order=n -cdrom image.iso -drive file=img.raw,if=virtio,boot=yes

with qemu-kvm 0.15.0

it will always directly boot from the hardrive and not from cdrom or 
network.
is this on purpose? the behaviour was different in earlier versions.
If i omit the boot=yes in the drive specification the "-boot order" 
parameter is working
as expected.

Peter

             reply	other threads:[~2011-08-29 10:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-29 10:12 Peter Lieven [this message]
2011-08-29 10:12 ` [Qemu-devel] qemu-kvm 0.15.0 boot order not working Peter Lieven
2011-08-29 11:21 ` Ottavio
2011-08-29 11:42   ` Peter Lieven
2011-08-29 12:14     ` Michael Tokarev
2011-08-29 12:19       ` Peter Lieven

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=4E5B65FE.7020101@dlh.net \
    --to=pl@dlh.net \
    --cc=kvm@vger.kernel.org \
    --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 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.