All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Fixing XENBUS, Xen 3.1 CentOS 6 DomU errors under PYGRUB
I had been recieving boot error like this:
XENBUS: Device with no driver: device/vbd/51713
XENBUS: Device with no driver: device/vbd/51714
XENBUS: Device with no driver: device/vif/0
This was also causing the VMs to boot and run very slowly as the VM was not finding the blockfront.
The fix was simple, but google provided no answers, thus this post. After trial and error and creating a new VM using a Stacklet Template... I relaized the issue was in /boot/grub/grub.conf
The old grub.conf looked like this:
default=0
timeout=5
title CentOS (2.6.32-279.el6.x86_64)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-279.14.1.el6.x86_64 console=hvc0 xencons=tty0 root=/dev/xvda1 ro
initrd /boot/initramfs-2.6.32-279.14.1.el6.x86_64.img
title vmlinuz-2.6.32-279.el6.x86_64
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-279.el6.x86_64 console=hvc0 xencons=tty0 root=/dev/xvda1 ro
initrd /boot/initramfs-2.6.32-279.el6.x86_64.img
The new like this:
default=0
timeout=5
title CentOS (2.6.32-279.14.1.el6.x86_64)
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-279.14.1.el6.x86_64 console=hvc0 xencons=tty0 root=/dev/xvda1 ro crashkernel=auto LANG=C
initrd /boot/initramfs-2.6.32-279.14.1.el6.x86_64.img
title vmlinuz-2.6.32-279.el6.x86_64
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-279.el6.x86_64 console=hvc0 xencons=tty0 root=/dev/xvda1 ro
initrd /boot/initramfs-2.6.32-279.el6.x86_64.img
Problem solved. I hope this helps someone out there as the info on google was somewhat spotty and esoteric.
Cheers.
Comments
I have also reposted this in my knowledgebase: bitronictech.net/knowledgebase/250/Fixing-XENBUS-Xen-31-CentOS-6-DomU-errors-under-PYGRUB.html
good
but guest os can't change it, need master server solve the template
No in this case the changes were made from the DomU, the guest server. The guest was booted using pygrub so the master server's grub config is irrelevant as well as the initrd from the master server. The issue in this case was that cPanel on the guest had modified the guest grub.conf incorrectly after an automatic OS update.