[workspace-user] Kernel error during the deployement of a virtual machine (workspace Service)
tfreeman at mcs.anl.gov
Fri Apr 27 10:04:48 CDT 2007
On Fri, 27 Apr 2007 13:49:54 +0200 (CEST)
Sylvain DIDELOT <didelot.sylvain at wanadoo.fr> wrote:
> 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.
I think so too. An alternative for now is to use a kernel with the right disk
modules compiled in.
When multiple file propagation is included we could look at supporting this
outright since it's a popular way to do kernels. workspace-control can support
initrds, it would not be a stretch to add a particular initrd for the default
kernel option (where propagation is not an issue).
We're also planning on supporting bootable hard disk images soon (where one
could include whatever kernel/initrd that is necessary).
More information about the workspace-user