From: Michael Tokarev <mjt@tls.msk.ru>
To: John Snow <jsnow@redhat.com>, Kevin Wolf <kwolf@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Are -cdrom/-hda (or -drive if=ide) supposed to work in q35?
Date: Sat, 02 Aug 2014 00:17:36 +0400 [thread overview]
Message-ID: <53DBF5E0.7000105@msgid.tls.msk.ru> (raw)
In-Reply-To: <53DBF43F.9050804@redhat.com>
02.08.2014 00:10, John Snow wrote:
[]
> For at least the immediate future, the AHCI device doesn't support the mixed-mode SATA/PATA access models, though I suppose we could, it seems like a more obvious and simple solution to just allow the shorthand syntactic sugar commands to use the native bus of the system until you specify otherwise.
One more comment.
With -M q35, -drive file=foo,if=ide definitions are silently ignored.
But -drive file=foo,if=none,id=x -device ide-drive,drive=x works.
This is the same issue as the reported -cdrom/-hda.
/mjt
next prev parent reply other threads:[~2014-08-01 20:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 6:30 [Qemu-devel] Are -cdrom/-hda (or -drive if=ide) supposed to work in q35? Michael Tokarev
2014-06-10 6:34 ` Paolo Bonzini
2014-06-10 8:10 ` Michael Tokarev
2014-06-10 8:14 ` Paolo Bonzini
2014-06-12 9:03 ` Markus Armbruster
2014-08-01 20:10 ` John Snow
2014-08-01 20:17 ` Michael Tokarev [this message]
2014-08-05 8:30 ` Kevin Wolf
2014-08-05 9:13 ` Markus Armbruster
2014-08-05 9:30 ` Kevin Wolf
2014-08-05 9:32 ` Michael Tokarev
2014-08-05 11:05 ` Markus Armbruster
2014-08-05 11:01 ` Markus Armbruster
2014-08-05 21:14 ` John Snow
2014-08-06 9:07 ` Kevin Wolf
2014-08-14 20:09 ` [Qemu-devel] IF_AHCI RFC (Was Re: Are -cdrom/-hda (or -drive if=ide) supposed to work in q35?) John Snow
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=53DBF5E0.7000105@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=afaerber@suse.de \
--cc=armbru@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@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 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.