From: Paolo Bonzini <pbonzini@redhat.com>
To: Xiongzi Ge <gexxx132@umn.edu>
Cc: Brian Jackson <iggy@theiggy.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Live Migration with different block devices
Date: Wed, 25 Jun 2014 16:39:19 +0200 [thread overview]
Message-ID: <53AADF17.1050602@redhat.com> (raw)
In-Reply-To: <CACtCCo9aAaActU=MQyMW0kFyT6DJeOp7AF_xLbuXjy0yyv7m6A@mail.gmail.com>
Il 25/06/2014 16:32, Xiongzi Ge ha scritto:
> I should make it clearer. I want to use a device for caching for the
> guest in host A. Then after the guest migrating to Host B, there is also
> a device for caching in Host B. I want to the guest can access the new
> cache device in Host B at first automatically. I also want the guest can
> access the previous cache device in Host A, if it gets a miss. Here, I
> may need to modify some interfaces. Is there a simple way to do this?
If your caching is done in the guest, the guest must use O_DIRECT to
open the block device.
Paolo
next prev parent reply other threads:[~2014-06-25 14:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 19:22 [Qemu-devel] Live Migration with different block devices Xiongzi Ge
2014-06-24 21:29 ` Brian Jackson
2014-06-24 23:16 ` Eric Blake
2014-06-25 0:08 ` Xiongzi Ge
2014-06-25 2:10 ` Eric Blake
2014-06-25 6:18 ` Paolo Bonzini
2014-06-25 14:14 ` Xiongzi Ge
2014-06-25 14:18 ` Paolo Bonzini
2014-06-25 14:32 ` Xiongzi Ge
2014-06-25 14:39 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-24 19:18 Xiongzi Ge
2014-06-24 19:37 ` Paolo Bonzini
2014-06-24 19:55 ` Xiongzi Ge
2014-06-24 20:25 ` Paolo Bonzini
2014-06-24 20:34 ` Xiongzi Ge
2014-06-24 20:41 ` Eric Blake
2014-06-24 20:47 ` Paolo Bonzini
2014-06-24 21:26 ` Xiongzi Ge
2014-06-24 21:39 ` Christopher Covington
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=53AADF17.1050602@redhat.com \
--to=pbonzini@redhat.com \
--cc=gexxx132@umn.edu \
--cc=iggy@theiggy.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.