xenserver vm fails to reboot manual recovery and repair

| | TrackBacks (0)

OK this was a incredible headache, but with care can be recovered at least to get your data off.
I think I replaced the kernel with a non-standard ie not a xen kernel.

You will need:
systemrescuecd


from the console of the xenserver:
xe vm-list
xe vm-list name-label=YOUR-CORRUPT-VM-NAME params=uuid
xe vm-param-set uuid=c37623c8-2d38-04a0-19d3-792630865172 HVM-boot-policy="BIOS order"

Go to the General Tab of your corrupt vm
click Properties
click Startup Options
adjust Boot Order For systemrescuecd.iso in virtual drive you have mounted with the CIFS ISO library option under the GUI for the xenserver console.

reboot the VM
hit enter at the systemrescuecd splash screen
at the console type this:

net-setup eth0
dhcpd eth0
mkdir /mnt/sda1
mount -t ext3 /dev/sda1 /mnt/sda1
cd /mnt/sda1

you now have a sshd server you can sftp data off of

10/13/2009 6:38:54 PM Error: Starting VM 'Rails' - The bootloader for this VM returned an error -- did the VM installation succeed? Error from bootloader: Return code: 1; Log = Traceback (most recent call last):
File "/usr/bin/pygrub", line 731, in ?
data = fs.open_file(chosencfg["kernel"]).read()
IOError: [Errno 2] No such file or directory

0 TrackBacks

Listed below are links to blogs that reference this entry: xenserver vm fails to reboot manual recovery and repair.

TrackBack URL for this entry: http://kennethhunt.com/mt/mt-tb.cgi/1921

About this Entry

This page contains a single entry by klsh published on October 13, 2009 6:39 PM.

Monitoring Boot Time Performance Bootchart vs Bootvis was the previous entry in this blog.

Are There Dangers to DNA With Terahertz Waves Radiation and Scanners? is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.