From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Juan Quintela <quintela@redhat.com>,
qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: [Qemu-devel] Re: [PATCH 3/3] disk: don't read from disk until the guest starts
Date: Mon, 13 Sep 2010 08:42:42 -0500 [thread overview]
Message-ID: <4C8E2A52.1000708@linux.vnet.ibm.com> (raw)
In-Reply-To: <4C8E2981.7000304@redhat.com>
On 09/13/2010 08:39 AM, Kevin Wolf wrote:
>> Yeah, one of the key design points of live migration is to minimize the
>> number of failure scenarios where you lose a VM. If someone typed the
>> wrong command line or shared storage hasn't been mounted yet and we
>> delay failure until live migration is in the critical path, that would
>> be terribly unfortunate.
>>
> We would catch most of them if we try to open the image when migration
> starts and immediately close it again until migration is (almost)
> completed, so that no other code can possibly use it before the source
> has really closed it.
>
I think the only real advantage is that we fix NFS migration, right?
But if we do invalidate_cache() as you suggested with a close/open of
the qcow2 layer, and also acquire and release a lock in the file layer
by propagating the invalidate_cache(), that should work robustly with NFS.
I think that's a simpler change. Do you see additional advantages to
delaying the open?
Regards,
anthony Liguori
> Kevin
>
next prev parent reply other threads:[~2010-09-13 13:42 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-11 14:04 [Qemu-devel] [RFC][PATCH 0/3] Fix caching issues with live migration Anthony Liguori
2010-09-11 14:04 ` [Qemu-devel] [PATCH 1/3] block: allow migration to work with image files Anthony Liguori
2010-09-12 10:37 ` Avi Kivity
2010-09-12 13:06 ` Anthony Liguori
2010-09-12 13:28 ` Avi Kivity
2010-09-12 15:26 ` Anthony Liguori
2010-09-12 16:06 ` Avi Kivity
2010-09-12 17:10 ` Anthony Liguori
2010-09-12 17:51 ` Avi Kivity
2010-09-15 16:00 ` [Qemu-devel] " Juan Quintela
2010-09-15 15:57 ` Juan Quintela
2010-09-13 8:21 ` Kevin Wolf
2010-09-13 13:27 ` Anthony Liguori
2010-09-15 16:03 ` Juan Quintela
2010-09-16 7:54 ` Kevin Wolf
2010-09-15 15:53 ` Juan Quintela
2010-09-11 14:04 ` [Qemu-devel] [PATCH 2/3] block-nbd: fix use of protocols in backing files and nbd probing Anthony Liguori
2010-09-11 16:53 ` Stefan Hajnoczi
2010-09-11 17:27 ` Anthony Liguori
2010-09-11 17:45 ` Anthony Liguori
2010-09-15 16:06 ` [Qemu-devel] " Juan Quintela
2010-09-16 15:40 ` Anthony Liguori
2010-09-17 8:53 ` Kevin Wolf
2010-09-16 8:08 ` Kevin Wolf
2010-09-16 13:00 ` Anthony Liguori
2010-09-16 14:08 ` Kevin Wolf
2010-09-11 14:04 ` [Qemu-devel] [PATCH 3/3] disk: don't read from disk until the guest starts Anthony Liguori
2010-09-11 17:24 ` Stefan Hajnoczi
2010-09-11 17:34 ` Anthony Liguori
2010-09-12 10:42 ` Avi Kivity
2010-09-12 13:08 ` Anthony Liguori
2010-09-12 13:26 ` Avi Kivity
2010-09-12 15:29 ` Anthony Liguori
2010-09-12 16:04 ` Avi Kivity
2010-09-15 16:10 ` [Qemu-devel] " Juan Quintela
2010-09-13 8:32 ` Kevin Wolf
2010-09-13 13:29 ` Anthony Liguori
2010-09-13 13:39 ` Kevin Wolf
2010-09-13 13:42 ` Anthony Liguori [this message]
2010-09-13 14:13 ` Kevin Wolf
2010-09-13 14:34 ` Anthony Liguori
2010-09-14 9:47 ` Avi Kivity
2010-09-14 12:51 ` Anthony Liguori
2010-09-14 13:16 ` Avi Kivity
2010-09-13 19:29 ` Stefan Hajnoczi
2010-09-13 20:03 ` Kevin Wolf
2010-09-13 20:09 ` Anthony Liguori
2010-09-14 8:28 ` Kevin Wolf
2010-09-15 16:16 ` Juan Quintela
2010-09-12 10:46 ` [Qemu-devel] [RFC][PATCH 0/3] Fix caching issues with live migration Avi Kivity
2010-09-12 13:12 ` Anthony Liguori
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=4C8E2A52.1000708@linux.vnet.ibm.com \
--to=aliguori@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@linux.vnet.ibm.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).