From: Paolo Bonzini <pbonzini@redhat.com>
To: chandrashekar shastri <cshastri@linux.vnet.ibm.com>
Cc: libvir-list@redhat.com, Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, virt-tools-list@redhat.com
Subject: Re: [Qemu-devel] virsh live migration w/o shared storage fails with error as vm is not running
Date: Thu, 13 Jun 2013 17:45:53 -0400 [thread overview]
Message-ID: <51BA3D91.5020405@redhat.com> (raw)
In-Reply-To: <51BA00B1.1020003@linux.vnet.ibm.com>
Il 13/06/2013 13:26, chandrashekar shastri ha scritto:
> On 06/13/2013 02:14 PM, Stefan Hajnoczi wrote:
>> On Thu, Jun 13, 2013 at 10:31:04AM +0530, chandrashekar shastri wrote:
>>> We are testing the upstream KVM with :
>>>
>>> Kernel, Qemu, Libvirt, Virt-Manager is built from the source (git).
>>>
>>> kernel version : 3.9.0+
>>> qemu version : QEMU emulator version 1.5.0
>>> libvirt version : 1.0.5
Please try with libvirt 1.0.5.2.
>>> virt-install : 0.600.3
>>>
>>> I have followed the below steps to test the "Live migration w/o
>>> shared storage" feature :
>>>
>>> 1. Created the qemu-img create -f qcow2 vm.qcow2 12G on the
>>> destination host which is same as the source.
>>> 2. Started the guest on the source
>>> 3. Started the vncdisplay to monitor the guest
>>> 4. Initiated the migration "virsh migrate --live rhel64-64
>>> qemu+ssh://9.126.89.202/system --verbose --copy-storage-all"
I recently found a bug here related to IPv4/IPv6. I need to understand
if it is in QEMU or libvirt.
Paolo
next prev parent reply other threads:[~2013-06-13 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 5:01 [Qemu-devel] virsh live migration w/o shared storage fails with error as vm is not running chandrashekar shastri
2013-06-13 8:44 ` Stefan Hajnoczi
2013-06-13 17:26 ` chandrashekar shastri
2013-06-13 21:45 ` Paolo Bonzini [this message]
2013-06-18 11:00 ` chandrashekar shastri
2013-06-19 11:21 ` chandrashekar shastri
2013-07-05 6:23 ` chandrashekar shastri
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=51BA3D91.5020405@redhat.com \
--to=pbonzini@redhat.com \
--cc=cshastri@linux.vnet.ibm.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=virt-tools-list@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).