Error to startup vitual machine

Question

Hello,
I'm trying power on vm whit:
Template created by Oracle (OS: Linux)
Error:
failed:<Exception: return=>failed:<Exception: xm create '/OVS/running_pool/353_SOA10g/vm.cfg'=>Error: Device 832 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected. > StackTrace: File "/opt/ovs-agent-2.2/OVSXXenVM.py", line 57, in xen_start_vm run_cmd(cmd) File "/opt/ovs-agent-2.2/OVSCommons.py", line 87, in run_cmd raise Exception('%s=>%s' % (cmd, p.childerr.read())) > StackTrace: File "/opt/ovs-agent-2.2/OVSSiteVM.py", line 84, in start_vm raise e
Thank!
Matt.-

Answer 1

I've run into something similar several times. When installing a new kernel or kernel update something is munching up the grub.conf to point it to a kernel file that doesn't exist. The way I've figured out to fix this is to mount the System.img file and go fix the grub.conf file. This is a trick since the System.img has an offset.
on your OVS server as root:
mkdir /x
mount -t ext3 -o loop,rw,offset=32256 /OVS/running_pool/<guest>/System.img /x
cd /x/grub
ls -la grub*
mv grub.conf grub.conf-bad
cp grub.conf.orabackup grub.conf
cd /
umount /x
This is just one way to get there, may not be exactly valid for your guest. You'll want to take a look at the grub.conf and make sure it's pointing to a valid kernel.
Then you can startup the guest. You can do it manually if you want to watch it by -->
xm create -c /OVS/running_pool/<guest>/vm.cfg
EDIT: I didn't figure this out on my own , found an article somewhere that pointed me to this. I can post the reference if needed.
Edited by: jschenck on Apr 12, 2011 3:01 PM