Re: [Fedora-xen] [fedora-virt] f20 guest on centos5 xen host
On Fri, Jan 24, 2014 at 08:51:46AM +, Bruno Postle wrote: On Wed 22-Jan-2014 at 22:35 +, Bruno Postle wrote: On Tue 21-Jan-2014 at 21:57 +, 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=d513814db6af2b298b8776d7ffc5fb1261e176f4 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 -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [fedora-virt] f20 guest on centos5 xen host
On 01/21/2014 09:12 AM, Cole Robinson wrote: On 01/20/2014 03:59 PM, Bruno Postle wrote: Hi, I'm having trouble installing a fedora f20 guest on a centos5 host, I previously had a working f16 guest, so I guess I want to know if this is possible or not. virt-install seems to work ok as before, but then the reboot fails with this error: Error starting domain: POST operation failed: xend_post: error from xen daemon: (xend.err Error creating domain: Boot loader didn't return any data!) I've tried formatting /boot as ext2 and ext3 with the same result, now I'm out of ideas. Here is my virt-install command: virt-install --paravirt --name honk --ram 2048 --disk \ path=/dev/VolGroup02/LogVol12 --vnc --location \ http://dl.fedoraproject.org/pub/fedora/linux/releases/20/Fedora/x86_64/os/ F20 as a paravirt guest should work, but I think nowadays most people are using fullvirt xen, so maybe paravirt isn't tested as much with new distros. I'm just guessing though Regardless, you'll probably have to dig in xen logs to or do some googling to find more info: I don't have any idea. It's very unlikely to be a virt-install/libvirt issue though Sorry, I thought this email went to the upstream virt-manager list, hence I was focusing on that :) RHEL5 xen is an old frankenstein monster at this point as well, so could be a xen issue that just hasn't been backported. CCing fedora xen list as well, maybe they have ideas. - Cole -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
Re: [Fedora-xen] [fedora-virt] f20 guest on centos5 xen host
On Tue, 21 Jan 2014, Cole Robinson wrote: On 01/21/2014 09:12 AM, Cole Robinson wrote: On 01/20/2014 03:59 PM, Bruno Postle wrote: Hi, I'm having trouble installing a fedora f20 guest on a centos5 host, I previously had a working f16 guest, so I guess I want to know if this is possible or not. virt-install seems to work ok as before, but then the reboot fails with this error: Error starting domain: POST operation failed: xend_post: error from xen daemon: (xend.err Error creating domain: Boot loader didn't return any data!) I've tried formatting /boot as ext2 and ext3 with the same result, now I'm out of ideas. Here is my virt-install command: virt-install --paravirt --name honk --ram 2048 --disk \ path=/dev/VolGroup02/LogVol12 --vnc --location \ http://dl.fedoraproject.org/pub/fedora/linux/releases/20/Fedora/x86_64/os/ F20 as a paravirt guest should work, but I think nowadays most people are using fullvirt xen, so maybe paravirt isn't tested as much with new distros. I'm just guessing though Regardless, you'll probably have to dig in xen logs to or do some googling to find more info: I don't have any idea. It's very unlikely to be a virt-install/libvirt issue though Sorry, I thought this email went to the upstream virt-manager list, hence I was focusing on that :) RHEL5 xen is an old frankenstein monster at this point as well, so could be a xen issue that just hasn't been backported. CCing fedora xen list as well, maybe they have ideas. I would need to see more logs to be sure, but I would guess pygrub is missing at least one update and this one http://xenbits.xenproject.org/gitweb/?p=xen.git;a=commit;h=d513814db6af2b298b8776d7ffc5fb1261e176f4http://xenbits.xenproject.org/gitweb/?p=xen.git;a=commit;h=d513814db6af2b298b8776d7ffc5fb1261e176f4 is a possibility. You could test if it is pygrub by running directly - in your case try /usr/bin/pygrub /dev/VolGroup02/LogVol12 as root - it should give you a choice of kernels and return the details for the one you pick. Michael Young -- xen mailing list xen@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/xen
