qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] KVM call agenda for October 25
Date: Wed, 26 Oct 2011 11:41:52 +0200	[thread overview]
Message-ID: <4EA7D5E0.7070101@redhat.com> (raw)
In-Reply-To: <m3bot49m0j.fsf@blackfin.pond.sub.org>

On 10/26/2011 10:48 AM, Markus Armbruster wrote:
> Sector size is a device property.
>
> If the user asks for a 4K sector disk, and the backend can't support
> that, we need to reject the configuration.  Just like we reject
> read-only backends for read/write disks.

Isn't it the other way round, i.e. the user asks for a 512-byte sector 
disk (i.e. the default) with cache=none but the disk has 4k sectors? 
We're basically saying "choose between NFS and migration if you have 4k 
sector disks but your guest doesn't support them".  Understandable 
perhaps, but not exactly kind, and virtualization is also about 
shielding from this kind of hardware dependency even at the cost of 
performance.  QEMU should just warn about performance degradations, 
erroring out would be a policy decision that should be up to management.

> It's okay to default device properties to some backend-dependent value,
> if that improves usability.

On the other hand, not all guests support 4k-sectors properly.

Paolo

  reply	other threads:[~2011-10-26  9:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24 11:04 [Qemu-devel] KVM call agenda for October 25 Juan Quintela
2011-10-24 11:35 ` Paolo Bonzini
2011-10-24 12:02   ` Peter Maydell
2011-10-24 13:06     ` Andreas Färber
2011-10-24 15:34     ` Luiz Capitulino
2011-10-25 12:35   ` Kevin Wolf
2011-10-25 13:05     ` Anthony Liguori
2011-10-25 13:18       ` Dor Laor
2011-10-25 13:28         ` Anthony Liguori
2011-10-25 13:40         ` Andreas Färber
2011-10-25 13:56       ` Kevin Wolf
2011-10-25 14:06         ` Anthony Liguori
2011-10-25 15:32           ` Kevin Wolf
2011-10-25 22:19             ` Alexander Graf
2011-10-26 20:41             ` Anthony Liguori
2011-10-26  8:15           ` Kevin Wolf
2011-10-26  8:48             ` Markus Armbruster
2011-10-26  9:41               ` Paolo Bonzini [this message]
2011-10-26 11:12                 ` Markus Armbruster
2011-10-26  9:57               ` Daniel P. Berrange
2011-10-26 11:23                 ` Kevin Wolf
2011-10-26 11:39                   ` Daniel P. Berrange
2011-10-26 12:18                     ` Kevin Wolf

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=4EA7D5E0.7070101@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kwolf@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).