From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Kevin Wolf <kwolf@redhat.com>, Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, kvm-devel <kvm@vger.kernel.org>,
quintela@redhat.com
Subject: Re: [Qemu-devel] Re: KVM call agenda for Jan 11
Date: Thu, 13 Jan 2011 18:12:04 +0200 [thread overview]
Message-ID: <4D2F2454.4090305@redhat.com> (raw)
In-Reply-To: <4D2C6C78.70606@codemonkey.ws>
On 01/11/2011 04:43 PM, Anthony Liguori wrote:
>> - invalidate all buffers for that block device on machine A after
>> migration.
>> * with NFS, just close + reopen the file (and pray that nobody else
>> has it also opened)
>> * with block devices: use BLKFLBLK ioctl, and pray that nobody
>> else is
>> using the device, that device is not a ramdisk, and some more
>> things. To add injury to insult, you need to be root to be able
>> to issue that ioctl (technically have CAP_SYS_ADMIN).
>
>
> Why isn't fsync() enough for a block device?
fsync() is fine on the outgoing side, but not on the incoming side.
(the imcoming side might have valid buffers if it was the outgoing side
on the previous migration, for example, or because of automatic probing)
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-01-13 16:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 10:17 [Qemu-devel] KVM call agenda for Jan 11 Juan Quintela
2011-01-10 11:59 ` [Qemu-devel] " Juan Quintela
2011-01-10 13:05 ` Jes Sorensen
2011-01-10 13:45 ` Stefan Hajnoczi
2011-01-10 16:46 ` Peter Maydell
2011-01-10 13:32 ` Juan Quintela
2011-01-11 11:13 ` Kevin Wolf
2011-01-11 13:41 ` Juan Quintela
2011-01-11 14:43 ` Anthony Liguori
2011-01-13 16:12 ` Avi Kivity [this message]
2011-01-10 16:02 ` [Qemu-devel] " 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=4D2F2454.4090305@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).