From: Brian Jackson <iggy@theiggy.com>
To: Nils Cant <nils.cant@kangaroot.net>
Cc: kvm@vger.kernel.org
Subject: Re: Is it possible to live migrate guest OS'es between different versions of kvm/qemu-kvm?
Date: Mon, 30 Aug 2010 15:16:09 -0500 [thread overview]
Message-ID: <201008301516.09914.iggy@theiggy.com> (raw)
In-Reply-To: <4C7B9E63.6060804@kangaroot.net>
On Monday, August 30, 2010 07:04:51 am Nils Cant wrote:
> Hey guys,
>
> next try is without libvirt, but still no joy.
>
> After issuing 'migrate -d <url>' on my sending host (qemu-kvm 0.11.0), I
> get the following output on the receiving host (qemu-kvm 0.12.4):
A quick search of this and/or the qemu mailing lists would have told you this
is unsupported.
>
> (qemu) Unknown savevm section or instance 'slirp' 0
> load of migration failed
>
> ... leaving my vm broken.
>
> Am I doing something wrong, or is the format of the savevm file just
> different and should I abandon all hope of ever doing a live migration
> to a newer version of qemu-kvm?
>
> Thanks in advance,
>
>
> Nils
>
> ---
>
> Here are my upstart options on the 'sender':
>
> /usr/bin/kvm -S \
> -M pc-0.11 \
> -enable-kvm \
> -m 512 \
> -smp 2,sockets=2,cores=1,threads=1 \
> -name testserver \
> -uuid 890a0156-0542-32d8-66d7-b36a711084cc \
> -monitor
> unix:/var/lib/libvirt/qemu/testserver.monitor,server,nowait \
> -boot c \
> -drive
> file=/dev/disk/by-path/ip-192.168.3.100:3260-iscsi-iqn.2003-10.com.lefthand
> networks:lefthand0:64:testserver-lun-0,if=virtio,boot=on \
> -drive media=cdrom \
> -usb \
> -vnc 0.0.0.0:10 \
> -k en-us \
> -vga cirrus &
>
> And the 'receiver':
>
> /usr/bin/kvm -S \
> -M pc-0.11 \
> -enable-kvm \
> -m 512 \
> -smp 2,sockets=2,cores=1,threads=1 \
> -name testserver \
> -uuid 890a0156-0542-32d8-66d7-b36a711084cc \
> -nodefaults \
> -chardev
> socket,id=monitor,path=/var/lib/libvirt/qemu/testserver.monitor,server,nowa
> it \
> -mon chardev=monitor,mode=readline \
> -boot c \
> -drive
> file=/dev/disk/by-path/ip-192.168.3.100:3260-iscsi-iqn.2003-10.com.lefthand
> networks:lefthand0:64:testserver-lun-0,if=none,id=drive-virtio-disk0,boot=o
> n \
> -drive if=none,media=cdrom,id=drive-ide0-1-0 \
> -device
> ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 \
> -device
> virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0
> \ -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 \ -chardev
> pty,id=serial0 \
> -device isa-serial,chardev=serial0 \
> -usb \
> -vnc 0.0.0.0:0 \
> -k en-us \
> -vga cirrus \
> -incoming tcp:0:4444 &
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-08-30 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 14:07 Is it possible to live migrate guest OS'es between different versions of kvm/qemu-kvm? Nils Cant
2010-08-30 12:04 ` Nils Cant
2010-08-30 20:16 ` Brian Jackson [this message]
2010-08-31 12:24 ` Avi Kivity
2010-09-03 11:35 ` Nils Cant
2010-09-05 8:39 ` Avi Kivity
2010-09-07 7:23 ` Nils Cant
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=201008301516.09914.iggy@theiggy.com \
--to=iggy@theiggy.com \
--cc=kvm@vger.kernel.org \
--cc=nils.cant@kangaroot.net \
/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).