From: Gerd Hoffmann <kraxel@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel@nongnu.org, Jason Baron <jbaron@redhat.com>,
Alexander Graf <agraf@suse.de>,
Markus Armbruster <armbru@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] On block interface types in general, IF_AHCI in particular
Date: Thu, 01 Nov 2012 09:50:29 +0100 [thread overview]
Message-ID: <509237D5.1040602@redhat.com> (raw)
In-Reply-To: <509000E8.9090703@redhat.com>
Hi,
> The main drawback of if=ahci is, as pointed out by Markus, that you
> would have to provide both controllers on-board. I think a real ICH9
> has the compatibility IDE controller on a separate PCI address from the
> SATA controller, so creating both of them is not really out of question.
I think this can be turned on and off by the bios. When configured in
ahci mode there is no IDE controller. It shows up when you switch to
IDE in the bios though.
[ side note: I suspect this could be the reason why the *BSDs don't
work with our AHCI emulation, might be they try to look
at the ich9-specific registers which control ahci/ide mode
and we don't emulate that properly. ]
> Obvious disadvantage, it would depart from real hardware. Linux should
> not care, not sure about SeaBIOS and Windows.
> At the same time, if all we want is a quick way to switch between IDE
> and AHCI, we could just use machine types. So another proposal is to
> have two machine types, one for ICH9-IDE (pc, the default), one for
> ICH9-AHCI (q35), one for PIIX3-IDE (piix3). Each QEMU release would add
> (up to) three machine types.
I'd tend to just point people to pc-piix for guests too old to be
shipped with ahci drivers and be done with it. Chances are high that
they have more issues with q35 anyway.
cheers,
Gerd
prev parent reply other threads:[~2012-11-01 8:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 14:43 [Qemu-devel] On block interface types in general, IF_AHCI in particular Markus Armbruster
2012-10-30 15:16 ` Jason Baron
2012-10-30 16:31 ` Paolo Bonzini
2012-10-30 17:04 ` Kevin Wolf
2012-10-30 19:03 ` Anthony Liguori
2012-10-30 21:12 ` Anthony Liguori
2012-10-31 13:58 ` Markus Armbruster
2012-10-31 14:01 ` Peter Maydell
2012-10-31 14:09 ` Paolo Bonzini
2012-10-31 14:20 ` Markus Armbruster
2012-10-31 14:40 ` Paolo Bonzini
2012-10-31 14:43 ` Alexander Graf
2012-10-31 14:46 ` Paolo Bonzini
2012-10-31 16:00 ` Anthony Liguori
2012-10-31 16:05 ` Alexander Graf
2012-10-31 16:46 ` Anthony Liguori
2012-10-31 16:57 ` Alexander Graf
2012-10-31 18:32 ` Anthony Liguori
2012-10-31 16:48 ` Paolo Bonzini
2012-10-31 16:21 ` Kevin Wolf
2012-10-31 16:32 ` Paolo Bonzini
2012-10-31 16:35 ` Alexander Graf
2012-10-31 16:50 ` Paolo Bonzini
2012-11-01 8:50 ` Gerd Hoffmann [this message]
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=509237D5.1040602@redhat.com \
--to=kraxel@redhat.com \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=armbru@redhat.com \
--cc=jbaron@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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).