remoted migration KVM-guest failed

remoted migration KVM-guest failed

[Zhang, Jingke]

[-- Attachment #1.1: Type: text/plain, Size: 1105 bytes --]

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 -incoming
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 -d tcp://192.168.199.69:4444

 

Then the (machine B) shows errors:

Migrate_incoming_fd failed (rc=233)

Migration failed rc=233

 

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

 


[-- Attachment #1.2: Type: text/html, Size: 7944 bytes --]

[-- Attachment #2: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: remoted migration KVM-guest failed

[Anthony Liguori]

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 –incoming 
> 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 –d 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 –incoming 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-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> 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/

Re: remoted migration KVM-guest failed

[Zhang, Jingke]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb2312", Size: 3163 bytes --]

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:anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org] 
Sent: 2007Äê7ÔÂ25ÈÕ 11:20
To: Zhang, Jingke
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
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-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>   


[-- Attachment #2: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel

Re: remoted migration KVM-guest failed

[Anthony Liguori]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=GB2312, Size: 3735 bytes --]

Zhang, Jingke wrote:
> 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.  
>   

It's almost exactly the same code path. If you can reproduce with an
"exec://" URL, then that gives us an easy way to reproduce and we can
examine the traffic by hand to see what went wrong. If you cannot
reproduce with an exec:// URL, it suggests that the bug your seeing is
part of the tcp:// URI handling code (and there's not a lot of that).

Regards,

Anthony Liguori

>     Thank you.
>
>
>
>
> -----Original Message-----
> From: Anthony Liguori [mailto:anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org] 
> Sent: 2007Äê7ÔÂ25ÈÕ 11:20
> To: Zhang, Jingke
> Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> 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-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
>> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>>   
>>     
>
>   



[-- Attachment #2: Type: text/plain, Size: 315 bytes --]

-------------------------------------------------------------------------
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/

[-- Attachment #3: Type: text/plain, Size: 186 bytes --]

_______________________________________________
kvm-devel mailing list
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/kvm-devel