From: chandrashekar shastri <cshastri@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: libvir-list@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] virsh live migration w/o shared storage fails with error as vm is not running
Date: Fri, 05 Jul 2013 11:53:49 +0530 [thread overview]
Message-ID: <51D66675.5000906@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130613084410.GG2633@stefanha-thinkpad.redhat.com>
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
>> 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"
>> 5. It started the copying the storage from souce to destination
>> (conitinously monitored it was growing)
>> 6. Guest on the destination was paused and was running on the source
>> 7. At some point the VM on the source shutdown and got an error on
>> the vnc display as " Viewport: write: Broken pipe (32)" and the
>> VM on the destination was undefined.
>>
>> Below is the libvirt debug log, please let me with your comments.
>>
>> Debug log:
>> --------------
> What about /var/log/libvirt/qemu/rhel64-64.log? That is the QEMU
> command-line and stderr log.
I have attached all source and destination logs, including the sosreport
of both source and destination in the bug.
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1192499
>
> Also can you try without copy-storage-all just to see if migration
> completes successfully? The guest will act weird once it migrates since
> the disk is zeroed but it will isolate the failure to
> --copy-storage-all.
Without copy-storage-all (meaning with NFS shared storage the migration
works fine).
> Stefan
>
Please let me know if you need more info.
Thanks,
Shastri
prev parent reply other threads:[~2013-07-05 6:24 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
2013-06-18 11:00 ` chandrashekar shastri
2013-06-19 11:21 ` chandrashekar shastri
2013-07-05 6:23 ` chandrashekar shastri [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=51D66675.5000906@linux.vnet.ibm.com \
--to=cshastri@linux.vnet.ibm.com \
--cc=libvir-list@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).