http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=743

------- Comment #13 from teja...@gmail.com 2006-08-28 21:37 ------- I compiled everything from scratch to make sure I got everything rurhg and then re-started the VM's only to find they still fail to start with the same error after the first few VM's start fine.

$ sudo xm list Name D Mem(MiB) VCPUs State Time(s) Domain-0 0 869 1 r----- 456.7 vm1 8 30 2 -b---- 2.9 vm2 9 30 2 -b---- 3.0 vm3 10 30 2 -b---- 3.0 vm4 11 30 2 -b---- 13.1

$ sudo xm create -c vm5/*config Using config file "vm5/vm5-config". ... .. .. [ 1276.565042] XENBUS: Timeout connecting to device: device/vbd/769 (state 3) [ 1276.565057] XENBUS: Timeout connecting to device: device/vbd/770 (state 3) [ 1276.565065] XENBUS: Timeout connecting to device: device/vbd/771 (state 3) [ 1276.565408] VFS: Cannot open root device "hda1" or unknown-block(0,0) [ 1276.565418] Please append a correct "root=" boot option [ 1276.565425] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-bl

$ sudo xm create -c vm6/*config ##### similar error to the previous one.

$ sudo xm create -c vm8/*config Using config file "vm8/vm8-config". Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

$ sudo xm create -c vm9/*config Using config file "vm9/vm9-config". Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

$ sudo xm create -c vm10/*config Using config file "vm10/vm10-config". Error: Device 0 (vif) could not be connected. Hotplug scripts not working

The weird thing is a few VM's fail with the kernel panic (because of the root device not being available at that time in the boot sequence) while a few fail because of "vif" problems (the second error above).