On Fri, Jan 24, 2014 at 08:51:46AM +0000, Bruno Postle wrote:
On Wed 22-Jan-2014 at 22:35 +0000, Bruno Postle wrote:
On Tue 21-Jan-2014 at 21:57 +0000, Bruno Postle wrote:
Though it now fails to come back up after yum update and reboot:
[2014-01-21 21:42:50 xend.XendDomainInfo 3625] WARNING (XendDomainInfo:1262) Domain has crashed: name=honk id=28. [2014-01-21 21:42:50 xend.XendDomainInfo 3625] ERROR (XendDomainInfo:2864) VM honk restarting too fast (Elapsed time: 1.151586 seconds). Refusing to restart to avoid loops.
I have some more info on this second problem, the first problem is clearly the same as described in this patch/workaround: http://xenbits.xenproject.org/gitweb/?p=xen.git;a=commit;h=d513814db6af2b298...
Now the system will come back up on reboot, but not if I upgrade the kernel on the guest (I can upgrade everything else).
Any ideas? it is either that there is some new incompatibility between kernel 3.11.10 and 3.12.8 on f20, or pygrub on centos5 can't cope with two kernel entries.
Further info, I did the obvious test here: I installed this new f20 kernel and removed the old f20 kernel entry from the grub.cfg file. The guest crashes, so I suppose the f20 3.12.8 kernel is incompatible with centos5 xen.
Can you please paste the full domU kernel verbose debug output, so we can see what goes wrong?
-- Pasi
-
Pasi Kärkkäinen