[workspace-user] Kernel error during the deployement of a virtual machine (workspace Service)
Sylvain DIDELOT
didelot.sylvain at wanadoo.fr
Fri Apr 27 06:49:54 CDT 2007
Hello,
I'm a french student and during my work placement, I have to deploy the Workspace Service in a University.
My virtual image deployement works very well, but when I take the control on my virtual image (previously deployed) with xen (with this command : xm console workspace-xx) I get this kernel message :
XENBUS: Timeout connecting to devices!
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "sda1" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
I read some documentations about this error and I think it because workspace service doesn't support the ramdisk option.
Someone has released a patch to add the ramdisk support, but it's only for the Workspace Service version TP1.1 (http://www.globus.org/mail_archive/workspace-user/2006/06/msg00001.html)
When I try to create a xen image with the command "xm ceate tty-linux -c" i get the same error.
My tty-linux file contains these following lines:
------------------------------
kernel = "/boot/vmlinuz-xen"
memory = 64
name = "ttylinux"
disk = ['file:/ttylinux-xen,sda1,w']
root = "/dev/sda1 ro"
vif = ['']
------------------------------
However, when I add this line : ramdisk = "/boot/initrd-xen", my kernel boots.
The virutal image I try to deploy is a "ready-to-work" tty-linux.
Globus version : GT4.0.2
Workspace Service version : VM_TP1.2.2
DomU Linux Distro : SLES 10
Thank you in advance for your answers
Sylvain
More information about the workspace-user
mailing list