On 06/18/10 15:09, Guido Günther wrote:
On Fri, Jun 18, 2010 at 02:02:44PM +0200, Harald Dunkel wrote:
--live is already in; see the bug report. /tmp/qemu.log is not
Then lets turn this around: what happens without it?
??? The whole bug report is about a live migration.
Actually I am using libvirt to avoid this kind of problems.
True but to track this down we need to find out if it's kvm of libvirt
(I suspect the former).
It seems that there is no problem using kvm. Here is the
procedure I tried:
on my desktop pc:
/usr/bin/kvm \
-enable-kvm -m 1024 -name migtest -vnc :14 \
-boot c \
-drive file=/storage/migtest/vda.img,id=drive-virtio-disk0,boot=on
(/storage is a NFS partition mounted on all virtualization hosts.)
on the new host:
/usr/bin/kvm \
-enable-kvm -m 1024 -name migtest -vnc :14 \
-boot c \
-drive file=/storage/migtest/vda.img,id=drive-virtio-disk0,boot=on \
-incoming tcp:0:4444
When the guest completed booting I entered the qemu monitor
for this guest to run
migrate -d tcp:fw02:4444
After that the kvm session on my desktop went away. I could
connect via vnc to the new host. There were no problems on
the guest.
After stopping all kvm sessions I tried the same procedure
using virsh and the same source and destination hosts: The
file system problems were back :-(.
Do you think you could try to reproduce this.
Regards
Harri
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
