initrd - Spheron1 https://www.spheron1.uk Thu, 28 Apr 2011 10:07:24 +0000 en-GB hourly 1 https://wordpress.org/?v=7.0 Missing kernel initial RAM disk with SolusVM and Xen https://www.spheron1.uk/2011/04/28/missing-kernel-initial-ram-disk-with-solusvm-and-xen/ https://www.spheron1.uk/2011/04/28/missing-kernel-initial-ram-disk-with-solusvm-and-xen/#respond Thu, 28 Apr 2011 10:07:24 +0000 https://www.spheron1.uk/?p=368 If for any reason your /boot/solus-vmlinuz symlink as well the /boot/solus-initrd.img initial RAM disk are missing or incorrect in Dom0 on one of your SolusVM Xen slaves, then you can force SolusVM to regenerate them using the latest Xen enabled copy of the kernel installed on the server using the following command in Dom0 on the slave: php /usr/local/solusvm/includes/xenkernel.php This...

The post Missing kernel initial RAM disk with SolusVM and Xen first appeared on Spheron1.

]]> If for any reason your /boot/solus-vmlinuz symlink as well the /boot/solus-initrd.img initial RAM disk are missing or incorrect in Dom0 on one of your SolusVM Xen slaves, then you can force SolusVM to regenerate them using the latest Xen enabled copy of the kernel installed on the server using the following command in Dom0 on the slave:

php /usr/local/solusvm/includes/xenkernel.php

This not only re-creates the /boot/solus-vmlinuz symlink to the appropriate vmlinuz file, but also builds the necessary /boot/solus-initrd.img initial RAM disk to boot your DomU machines.

Of course, if you are using PyGrub then you don’t use these files in Dom0 🙂

The post Missing kernel initial RAM disk with SolusVM and Xen first appeared on Spheron1.

]]> https://www.spheron1.uk/2011/04/28/missing-kernel-initial-ram-disk-with-solusvm-and-xen/feed/ 0