Comment 9 for bug 881542

Thanks for opening the bug. So there are a few more pieces of information that would be useful. From the dmesg I can see that the current failing version is 2.6.32-34.77. To get the exact version of the older kernel, it would be good if you could boot that one and attach the dmesg gathered there.
Also from your mail you said you use PVM, are you providing the kernel and initrd from the xen cfg, or are you using one of pygrub or pvgrub? When restore fails, are you able to connect to the xen console (xm console) and does that show any errors?

I only had a HVM lucid server install prepared which I tried with the .34 kernel. But I am also running a 4.1.1 hypervisor. So I need to try getting that started in PVM mode. Meanwhile there is an even newer kernel pending to be released. The packages can be found under the builds at https://launchpad.net/ubuntu/lucid/+source/linux/2.6.32-35.78. Maybe that already fixes the issue or at least changes the behaviour enough for it not happening.