Hi Anthony,
My KVM-version is:
Kernel: b41e5014dd8712e8de2b656617f7a7a158cd992a
Userspace: 86e8eba8f8349d2e02e3b0ae0ce7c1993f4352fb
This is the latest commit which is built at 2007-07-24 by us. And there is
no any extra patch. We can do remote migration successfully before, but failed
this time. I am sure that machine A and B can ping each other successfully.
BTW, the method of migrate "exec://dd of=foo.img" is to save the KVM-guest,
and we restore it. I guess the live migration for KVM is different from that.
Thank you.
-----Original Message-----
From: Anthony Liguori [mailto:[EMAIL PROTECTED]
Sent: 2007年7月25日 11:20
To: Zhang, Jingke
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [kvm-devel] remoted migration KVM-guest failed
Zhang, Jingke wrote:
>
> Hi all,
>
> I test the migration in KVM-ia32e (using two machines to do remote
> migration), but it failed.
>
> But if I do it in the local host, it can pass. Does anyone meet the
> same issue? Please give me some help, thank you very much!
>
> The command I used on the destination (machine B) point is:
>
> qemu-system-x86_64 . -m 512 -net
> nic,macaddr=00:16:3e:3a:2d:56,model=rtl8139 -net
> tap,script=/etc/kvm/qemu-ifup -hda /root/hvm/ia32e_fc6.img �Cincoming
> tcp://0:4444
>
> The command I used on the source (machine A) point is:
>
> qemu-system-x86_64 . -m 512 -net
> nic,macaddr=00:16:3e:3a:2d:56,model=rtl8139 -net
> tap,script=/etc/kvm/qemu-ifup -hda /root/hvm/ia32e_fc6.img and (qemu)
> migrate �Cd tcp://192.168.199.69:4444
>
> Then the (machine B) shows errors:
>
> Migrate_incoming_fd failed (rc=233)
>
> Migration failed rc=233
>
Curious, it indicates that the migration stream is corrupted. Can you do
something like:
On machine A:
(qemu) migrate "exec://dd of=foo.img"
And then on machine B:
cat foo.img | qemu-system-x86_64 . -m 512 -net
nic,macaddr=00:16:3e:3a:2d:56,model=rtl8139 -net
tap,script=/etc/kvm/qemu-ifup -hda /root/hvm/ia32e_fc6.img �Cincoming stdio
What version of KVM is this? Are there any patches applied?
Regards,
Anthony Liguori
> BTW, dmesg on machine B shows:
>
> ====================
>
> sw0: port 2(tap0) entering disabled state
>
> device tap0 left promiscuous mode
>
> sw0: port 2(tap0) entering disabled state
>
> ====================
>
> Thank you, Zhangjingke
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> ------------------------------------------------------------------------
>
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
