On 2012-02-09, at 8:11 AM, Ian Campbell wrote: There's a good chance this is a guest kernel issue. What sort of guests are they and what kernel version are they running? Is there anything in the guest kernel logs or on the guest console?
I did some digging around in the kernel logs for the guest post-migration and found an entry that indicates the failure. Feb 1 18:21:03 XX kernel: netfront: device eth0 has copying receive path. Feb 1 18:21:03 XX kernel: netfront: device eth1 has copying receive path. Feb 1 18:21:03 XX kernel: vif vif-3: 2 reading other end details from device/vif/3 Feb 1 18:21:03 XX kernel: xenbus: resume (talk_to_otherend) vif-3 failed: -2 Feb 1 18:21:03 XX kernel: Initializing CPU#1 Feb 1 18:21:03 XX kernel: Initializing CPU#2 Feb 1 18:21:03 XX kernel: Initializing CPU#3
Notice line 3&4.
I'll continue to try and replicate, but if this rings any bells, please comment.
Kris |