From: Paolo Bonzini <pbonzini@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>,
qemu-devel <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
marcel@redhat.com, Laszlo Ersek <lersek@redhat.com>,
armbru@redhat.com, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-block] How to generate custom fw paths for IDE devices?
Date: Fri, 27 Jul 2018 12:47:18 +0200 [thread overview]
Message-ID: <a0593954-0e97-7317-f0ff-f54c194cb137@redhat.com> (raw)
In-Reply-To: <16432a45-ad8b-6c09-b50d-ab7101214912@ilande.co.uk>
On 27/07/2018 12:43, Mark Cave-Ayland wrote:
> The issue here seems to be that according to "info qtree" there is
> *always* an ide-cd device plugged into the location equivalent to that
> of -cdrom, and so with the above command QEMU ends up adding a second
> ide-cd device to the ide.1 bus which confuses OpenBIOS. Is this
> deliberate behaviour?
Yes, the default CD-ROM is always placed as secondary/master.
If you use -device ide-cd the implicit CD-ROM should go away. However,
-drive alone doesn't have that effect (probably for backwards
compatibility reasons, this predates me even though by only a few months).
Alternatively, you can use -nodefaults of course.
Thanks,
Paolo
next prev parent reply other threads:[~2018-07-27 10:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 21:13 [Qemu-devel] How to generate custom fw paths for IDE devices? Mark Cave-Ayland
2018-07-19 8:10 ` Thomas Huth
2018-07-19 16:46 ` Mark Cave-Ayland
2018-07-19 8:29 ` Laszlo Ersek
2018-07-19 17:19 ` Mark Cave-Ayland
2018-07-19 19:03 ` Laszlo Ersek
2018-07-25 13:03 ` [Qemu-devel] [Qemu-block] " Paolo Bonzini
2018-07-27 10:43 ` Mark Cave-Ayland
2018-07-27 10:47 ` Paolo Bonzini [this message]
2018-07-27 11:00 ` Mark Cave-Ayland
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=a0593954-0e97-7317-f0ff-f54c194cb137@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=lersek@redhat.com \
--cc=marcel@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-block@nongnu.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 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).