From: Avi Kivity <avi@redhat.com>
To: Onkar Mahajan <kern.devel@gmail.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] KVM migration with different source and dest paths
Date: Mon, 09 May 2011 11:45:53 +0300 [thread overview]
Message-ID: <4DC7A9C1.8040305@redhat.com> (raw)
In-Reply-To: <BANLkTinEShpQNRP0GtDiPikj8iKr-xZi6w@mail.gmail.com>
On 05/06/2011 12:30 PM, Onkar Mahajan wrote:
> Is it possible to migrate KVM guest to different paths like this:
>
> path of the image of guest01 on host A
> /home/joe/guest01.img
>
> path of the image of guest01 on host B
> /home/bill/image/temp/guest01.img
>
>
> is this possible ?
>
> if it is any pointers as to how to do this ?
>
Are you referring to a single image which is accessible via two paths?
Or two different images?
Both are possible (the former by simply using the new path for the
destination, the latter by using the migrate -b switch.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2011-05-09 8:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 9:30 [Qemu-devel] KVM migration with different source and dest paths Onkar Mahajan
2011-05-09 8:45 ` Avi Kivity [this message]
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=4DC7A9C1.8040305@redhat.com \
--to=avi@redhat.com \
--cc=kern.devel@gmail.com \
--cc=kvm@vger.kernel.org \
--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 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).