From: Guenther Hutzl <hutzl@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Should migration with slirp networking (-netdev user) be backward compatible?
Date: Mon, 13 Jun 2016 15:39:02 +0200 [thread overview]
Message-ID: <c7b46127-5ba4-3b44-1ac6-1e717fd9417c@linux.vnet.ibm.com> (raw)
Hello!
I have a problem with migration from qemu-v2.6.0 to qemu-v2.5.0. It looks like
the slirp networking (-netdev user) is not backward compatible. This is the
output I am seeing on the receiving side:
qemu-system-x86_64: savevm: unsupported version 4 for 'slirp' v3
qemu-system-x86_64: load of migration failed: Invalid argument
This is the little test machine I am trying to migrate (using tiny core linux iso):
qemu-system-x86_64-2.6.0 -machine pc-i440fx-2.5 \
-m 512 \
-cdrom core-current.iso \
-boot d \
-nographic \
-curses \
-netdev user,id=mynet0 \
-device virtio-net,netdev=mynet0,id=net0
The target machine looks like this:
qemu-system-x86_64-2.5.0 -machine pc-i440fx-2.5 \
-m 512 \
-cdrom core-current.iso \
-boot d \
-nographic \
-curses \
-netdev user,id=mynet0 \
-device virtio-net,netdev=mynet0,id=net0 \
-incoming tcp:0:4444
I am selecting a v2.5-compatible machine so migration to qemu-2.5 should be
possible. The question is: Is the migration of slirp networking backward
compatible or is this unsupported for some reason?
I tested migration from v2.6 to v2.6 with this configuration and it worked.
Thank you,
Guenther Hutzl.
IBM Deutschland Research & Development GmbH
Vorsitzende des Aufsichtsrats: Martina Koederitz
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
next reply other threads:[~2016-06-13 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 13:39 Guenther Hutzl [this message]
2016-06-13 14:21 ` [Qemu-devel] Should migration with slirp networking (-netdev user) be backward compatible? Paolo Bonzini
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=c7b46127-5ba4-3b44-1ac6-1e717fd9417c@linux.vnet.ibm.com \
--to=hutzl@linux.vnet.ibm.com \
--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).