On 08/18/2009 09:14 AM, Thomas Besser wrote:
Avi Kivity wrote:
On 08/17/2009 04:57 PM, Thomas Besser wrote:
After "migrate -d tcp:192.168.0.2:4444" info says "migration completed",
but "incoming" kvm machine dies.
What do you mean exactly by "dies"?
I'm starting the 'waiting' kvm process like this:
/usr/bin/kvm -name testbench -vnc :5 -net
nic,vlan=0,model=virtio,macaddr=00:08:15:00:09:95 -net
tap,vlan=0,ifname=tap05,script=no -m 256 -drive
file=/vm/testbench/testbench.raw,if=virtio,boot=on -daemonize -vga std -k
de -tdf -incoming tcp:0:4444
The resulting kvm process which is waiting for the incoming migration isn't
there anymore after the migration command on the 'source' host.
Please run without -daemonize and capture stdio output, monitor output,
and/or core dump.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
