qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Anthony Liguori <anthony@codemonkey.ws>,
	Jason Baron <jbaron@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] On block interface types in general, IF_AHCI in particular
Date: Wed, 31 Oct 2012 15:46:05 +0100	[thread overview]
Message-ID: <509139AD.3000207@redhat.com> (raw)
In-Reply-To: <9D91D287-B449-49D9-BEEA-DDBF291EB9B9@suse.de>

Il 31/10/2012 15:43, Alexander Graf ha scritto:
> 
> On 31.10.2012, at 15:40, Paolo Bonzini wrote:
> 
>> Il 31/10/2012 15:20, Markus Armbruster ha scritto:
>>> One more thing: on a *major* upgrade, I'd rather deal with
>>> immediately obvious breakage (does not boot) than rotten
>>> performance.
>>> 
>>> If we make "q35 with compat IDE" the default, we'll have to tell
>>> users many, many times not to use the default :(
>> 
>> Well, compat IDE is not on the same league as writethrough for bad 
>> performance, and virtio is anyway the better choice (and not
>> available just with a different machine type).
> 
> Are you seriously considering to carry that IDE legacy around simply
> because we are too dumb to create working command line options? AHCI
> gets you at least parallel disk access, so in most cases it's a lot
> more sane than IDE.

What's wrong with "-M q35" (which would go along with "-M piix" for
absolute legacy)?

I'm just saying that the default machine type ("-M pc") should boot
Windows XP.

Paolo

  reply	other threads:[~2012-10-31 14:46 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 [this message]
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

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=509139AD.3000207@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=agraf@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=armbru@redhat.com \
    --cc=jbaron@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@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).