From: Laine Stump <laine@redhat.com>
To: qemu list <qemu-devel@nongnu.org>
Subject: [Qemu-devel] which machinetypes have an integrated/implied IDE controller?
Date: Thu, 12 Nov 2015 15:01:26 -0500 [thread overview]
Message-ID: <5644F016.6060206@redhat.com> (raw)
For a long time, libvirt assumed by default that all types of virtual
machines had an integrated IDE controller named "ide" that wasn't
specified on the qemu commandline. Since that caused problems
specifically for the Q35 machine type (which has an *ahci* controller
that it perplexingly calls "ide"), I added code to libvirt to only make
that assumption for i440fx-based machinetypes, and to log an error and
fail in all other cases where someone tried to create a disk attached to
an IDE controller:
http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=eadd757
(libvirt doesn't support explicitly adding IDE controllers on the qemu
commandline, under the assumption that 1) there are lots of better ways
to attach a disk and 2) nobody has asked for it up to now, and we don't
want to encourage them to start using something that is slow and
unnecessary).
But I just received an email from someone who informed me that the
"ppc-beigeg3" machine type also has an IDE controller, and that
additionally this is the *only* method of connecting a disk on this
particular machine. So now I'm wondering how I can determine what other
machinetypes have an integrated IDE controller, so that I can add them
to this check. (I would also like to find out which qemu binary supports
the "ppc-beigeg3" machinetype - I tried running "qemu-blah -M ?" for
every qemu binary on my Fedora 22 system, and didn't see anything like
that).
next reply other threads:[~2015-11-12 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 20:01 Laine Stump [this message]
2015-11-13 10:24 ` [Qemu-devel] which machinetypes have an integrated/implied IDE controller? Paolo Bonzini
2015-11-13 13:03 ` Markus Armbruster
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=5644F016.6060206@redhat.com \
--to=laine@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).