From: Anthony Liguori <anthony@codemonkey.ws>
To: dlaor@redhat.com
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] KVM call agenda for October 25
Date: Tue, 25 Oct 2011 08:28:29 -0500 [thread overview]
Message-ID: <4EA6B97D.7050002@codemonkey.ws> (raw)
In-Reply-To: <4EA6B730.3040609@redhat.com>
On 10/25/2011 08:18 AM, Dor Laor wrote:
> On 10/25/2011 03:05 PM, Anthony Liguori wrote:
>> On 10/25/2011 07:35 AM, Kevin Wolf wrote:
>>> Am 24.10.2011 13:35, schrieb Paolo Bonzini:
>>>> On 10/24/2011 01:04 PM, Juan Quintela wrote:
>>>>>
>>>>> Hi
>>>>>
>>>>> Please send in any agenda items you are interested in covering.
>>>>
>>>> - What's left to merge for 1.0.
>>>
>>> I would still like to cache the default cache mode (probably to
>>> cache=writeback). We don't allow guests to toggle WCE yet which Anthony
>>> would have liked to see before doing the change. Is it a strict
>>> requirement?
>>
>> I don't see a way around it. If the default mode is cache=writeback,
>> then we're open to data corruption in any guest where barrier=0. With
>> guest togglable WCE, it ends up being a guest configuration issue so we
>> can more or less defer responsibility.
>>
>> Do you think it's a good idea to change the default mode w/o guest WCE
>> toggle support? What's your view about older guests if we change the
>> default mode? What's your main motivation for wanting to change the
>> default mode?
>>
>> I'd be much more open to changing the default mode to cache=none FWIW
>> since the risk of data loss there is much, much lower.
>
> A bit related to this, it would be nice to mark a VM un-migratable if
> cache!=none. Juan reports that currently it such VMs are exposed to data
> integrity issues so we need to fail migrating them automatically.
That's not correct. cache!=none is perfectly safe *if* you have coherent shared
storage.
Regards,
Anthony Liguori
>
>>
>> Regards,
>>
>> Anthony Liguori
>>
>>>
>>> Kevin
>>>
>>
>>
>
>
next prev parent reply other threads:[~2011-10-25 13:28 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 11:04 KVM call agenda for October 25 Juan Quintela
2011-10-24 11:04 ` [Qemu-devel] " Juan Quintela
2011-10-24 11:35 ` Paolo Bonzini
2011-10-24 11:35 ` [Qemu-devel] " Paolo Bonzini
2011-10-24 12:02 ` Peter Maydell
2011-10-24 13:06 ` Andreas Färber
2011-10-24 13:06 ` [Qemu-devel] " Andreas Färber
2011-10-24 15:34 ` Luiz Capitulino
2011-10-25 12:35 ` Kevin Wolf
2011-10-25 12:35 ` [Qemu-devel] " Kevin Wolf
2011-10-25 13:05 ` Anthony Liguori
2011-10-25 13:18 ` Dor Laor
2011-10-25 13:28 ` Anthony Liguori [this message]
2011-10-25 13:40 ` Andreas Färber
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-25 22:19 ` [Qemu-devel] " Alexander Graf
2011-10-26 20:41 ` Anthony Liguori
2011-10-26 8:15 ` Kevin Wolf
2011-10-26 8:15 ` [Qemu-devel] " Kevin Wolf
2011-10-26 8:48 ` Markus Armbruster
2011-10-26 8:48 ` Markus Armbruster
2011-10-26 9:41 ` Paolo Bonzini
2011-10-26 9:41 ` Paolo Bonzini
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:23 ` Kevin Wolf
2011-10-26 11:39 ` Daniel P. Berrange
2011-10-26 11:39 ` Daniel P. Berrange
2011-10-26 12:18 ` Kevin Wolf
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=4EA6B97D.7050002@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=dlaor@redhat.com \
--cc=kvm@vger.kernel.org \
--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.