The data provided in comment #27 is a bit confusing. The overview reports amd64 server kernel, while the dmesg is from an i386 generic-pae guest (and I think HVM).
So can we clarify the guest setup that shows the problem (architecture, HVM or PVM)? Also is it possible to have a simple procedure to do a simple migration? Is it just xm save and xm restore on the other server? Is the second server necessary or can the same issue be re-created with only one server. If the xen version I saw in the log (3.4.2) is correct I have a system local that may be close enough and it would help to be able to re-create it there as that allows me access through dom0. There is one patch pending in the 2.6.32.y queue that fixes some issues with enabling interrupts and that could be related. Unfortunately the difference between some working kernel versions and non-working sometimes was completely out of the scope that normally should affect the Xen migration, so it feels like a highly timing related issue. Which makes verifying whether a specific patch solves anything rather hard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/838177 Title: [Lucid] New version of kernel cannot do migration between two XenServers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/838177/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
