From: Peter Lieven <pl@dlh.net>
To: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Qemu-KVM Livate Migration 0.12.2 -> 0.12.3/4 broken?
Date: Tue, 11 May 2010 12:59:14 +0200 [thread overview]
Message-ID: <4BE93882.8050105@dlh.net> (raw)
Hi Qemu/KVM Devel Team,
Live Migration from a 0.12.2 qemu-kvm to a 0.12.3 (and 0.12.4)
does not work: "load of migration failed"
Is there any way to find out, why exactly it fails? I have
a lot of VMs running on 0.12.2 and would like to migrate
them to 0.12.4
cmdline:
-net tap,vlan=6,script=no,downscript=no,ifname=tap7 -net
nic,vlan=6,model=e1000,macaddr=52:54:00:fe:00:88 -net
tap,vlan=651,script=no,downscript=no,ifname=tap8 -net
nic,vlan=651,model=e1000,macaddr=52:54:00:ff:00:69 -drive
file=/dev/mapper/iqn.2001-05.com.equallogic:0-8a0906-b6eca7604-6280020bc4b4bde8-quagga,if=ide,boot=on,cache=none,aio=native
-m 256 -monitor tcp:0:4090,server,nowait -vnc :90 -name 'Quagga'
-boot order=dc,menu=on -k de -incoming tcp:172.21.59.132:5090
-pidfile /var/run/qemu/vm-148.pid -rtc base=utc,clock=vm -usb
-usbdevice tablet -no-kvm-irqchip -vga cirrus
Any hints would be appreciated!
Thanks,
Peter
next reply other threads:[~2010-05-11 10:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 10:59 Peter Lieven [this message]
2010-05-11 23:11 ` [Qemu-devel] Re: Qemu-KVM Livate Migration 0.12.2 -> 0.12.3/4 broken? Juan Quintela
2010-05-12 13:42 ` Peter Lieven
2010-05-16 12:02 ` Avi Kivity
2010-05-16 14:42 ` Juan Quintela
2010-05-16 14:47 ` Avi Kivity
2010-05-16 20:04 ` Juan Quintela
2010-05-17 7:00 ` Avi Kivity
2010-05-17 8:23 ` Michael Tokarev
2010-05-17 9:07 ` Juan Quintela
2010-05-17 9:11 ` Michael Tokarev
2010-05-17 9:38 ` Alexander Graf
2010-05-16 18:03 ` Jan Kiszka
2010-05-16 20:06 ` Juan Quintela
2010-05-17 10:35 ` Jan Kiszka
2010-06-08 9:54 ` Peter Lieven
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=4BE93882.8050105@dlh.net \
--to=pl@dlh.net \
--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).