From: Vincent Hanquez <vincent.hanquez-mvvWK6WmYclDPfheJLI6IQ@public.gmane.org>
To: Dave Scott <Dave.Scott-mvvWK6WmYclDPfheJLI6IQ@public.gmane.org>
Cc: "Xen API"
<xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>,
"xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org"
<xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>,
"'Pasi Kärkkäinen'" <pasik-X3B1VOXEql0@public.gmane.org>,
Stodden <Daniel.Stodden-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
Subject: Re: [Xen-devel] [XCP] XCP project suggestions on the wiki
Date: Wed, 24 Mar 2010 22:41:39 +0000 [thread overview]
Message-ID: <4BAA9523.90706@eu.citrix.com> (raw)
In-Reply-To: <81A73678E76EA642801C8F2E4823AD21565E55423F-aFusIB7tbcLeU4JHVX8hdHnr0TU713UqXqFh9Ls21Oc@public.gmane.org>
On 24/03/10 20:11, Dave Scott wrote:
>> - Live Migration without shared storage (I think Qemu already has
>> support for this)
>
> Does qemu remote the block I/O itself? This would also be quite interesting.
it copies the storage to the destination along with the memory.
--
Vincent
next prev parent reply other threads:[~2010-03-24 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 17:45 [XCP] XCP project suggestions on the wiki Dave Scott
[not found] ` <81A73678E76EA642801C8F2E4823AD21565E554199-aFusIB7tbcLeU4JHVX8hdHnr0TU713UqXqFh9Ls21Oc@public.gmane.org>
2010-03-10 18:16 ` [Xen-devel] " Pasi Kärkkäinen
2010-03-24 19:08 ` Pasi Kärkkäinen
[not found] ` <20100324190819.GP1878-GxtO3QLqHcLR7s880joybQ@public.gmane.org>
2010-03-24 20:11 ` [Xen-devel] " Dave Scott
[not found] ` <81A73678E76EA642801C8F2E4823AD21565E55423F-aFusIB7tbcLeU4JHVX8hdHnr0TU713UqXqFh9Ls21Oc@public.gmane.org>
2010-03-24 22:41 ` Vincent Hanquez [this message]
[not found] ` <4BAA9523.90706-mvvWK6WmYclDPfheJLI6IQ@public.gmane.org>
2010-03-25 9:31 ` Pasi Kärkkäinen
2010-03-29 16:58 ` Pasi Kärkkäinen
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=4BAA9523.90706@eu.citrix.com \
--to=vincent.hanquez-mvvwk6wmycldpfhejli6iq@public.gmane.org \
--cc=Daniel.Stodden-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org \
--cc=Dave.Scott-mvvWK6WmYclDPfheJLI6IQ@public.gmane.org \
--cc=pasik-X3B1VOXEql0@public.gmane.org \
--cc=xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
--cc=xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.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.