Богомолов Дмитрий Викторович
2012-Jan-13 05:36 UTC
Re: Xen Live Migration Networking Problem
I have the same issue with the same configuration(Xen 4.1 + Ubuntu 11.10 +drbd+lvm), except i use ubuntu 10.10 domu. The issue little differ with yours. I can migrate domu from node to node2 without this network problem, but when i migrate this domu from node2 to node1 i get the issue. So i get issue only when i migrate domu from node2 to node1. I tried: ''xm network-detach'' and ''xm network-attach'' and the network bring back. When i repeat migrate to node2, and then migrate to node1 back, the domu hang up, and recreating domu on node1 fail because of error: device 0 (vif) could not be connected. Hotplug scripts not working. Only node reboot help. Nodes have some hardware and software differs. I dont think that hardware difference mean. Xen and drbd settings equal. Software difference is: node1 have 3.0.0-12-generic-pae kernel, and node2 the last 3.0.0-14-generic-pae. Maybe this is the reason. I''ll to upgrade node1, and if it help i wrote here.
Богомолов Дмитрий Викторович
2012-Jan-13 06:54 UTC
Re: Xen Live Migration Networking Problem
> I have the same issue with the same configuration(Xen 4.1 + Ubuntu 11.10 +drbd+lvm), except i use ubuntu 10.10 domu. The issue little differ with yours. I can migrate domu from node to node2 without this network problem, but when i migrate this domu from node2 to node1 i get the issue. So i get issue only when i migrate domu from node2 to node1. > I tried: ''xm network-detach'' and ''xm network-attach'' and the network bring back. When i repeat migrate to node2, and then migrate to node1 back, the domu hang up, and recreating domu on node1 fail because of error: device 0 (vif) could not be connected. Hotplug scripts not working. > Only node reboot help. > Nodes have some hardware and software differs. I dont think that hardware difference mean. Xen and drbd settings equal. Software difference is: node1 have 3.0.0-12-generic-pae kernel, and node2 the last 3.0.0-14-generic-pae. Maybe this is the reason. I''ll to upgrade node1, and if it help i wrote here.Yes this was the reason. After upgrading node1 to last kernel the issue eliminated.> _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >