From: Christopher Covington <cov@codeaurora.org>
To: Xiongzi Ge <gexxx132@umn.edu>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Live Migration with different block devices
Date: Tue, 24 Jun 2014 17:39:03 -0400 [thread overview]
Message-ID: <53A9EFF7.6020703@codeaurora.org> (raw)
In-Reply-To: <CACtCCo8mqEPNDtN9Tw5En=Cb46a7n8VKvAj0WZ+e2TqS85FQ+Q@mail.gmail.com>
On 06/24/2014 05:26 PM, Xiongzi Ge wrote:
> Hi ,
>
> This is just related to migration, but it may be not in the standard
> migration. The cache device in different hosts can only be accessed by the vm
> running in the host. The problem for me is to find the interface of the cache
> in the guest or like first doing it in the qemu, after migration, this cache
> should recognize that the cache content storing in the disk has been
> changed. DOes anyone has good suggestions? Thanks !
I don't know much about storage and don't really understand what you're
describing (what is a cache device?), but I've been using Checkpoint and
Restore in Userspace (CRIU) [1] to move Linux processes between systems with
different (simulated) hardware. The kernels end up with non-identical state,
but that's fine for my purposes.
http://www.criu.org/Main_Page
Christopher
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.
next prev parent reply other threads:[~2014-06-24 21:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 19:18 [Qemu-devel] Live Migration with different block devices 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-24 19:22 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
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=53A9EFF7.6020703@codeaurora.org \
--to=cov@codeaurora.org \
--cc=gexxx132@umn.edu \
--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.