R: [Netkit.users] error: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(98, 1)

[Massimo Rimondini]

Hi Pietro,

I apologize for the delay in answering you.

However, after performing some tests, I can confirm that Netkit and NFS do
not always interplay well. In particular, placing the filesystem (.disk
file) of a virtual machine inside a mounted NFS share causes trouble with
file locks. In fact, when launching the virtual machine again (after the
first time) there's a stale lock on the .disk file which prevents the Netkit
kernel from starting up properly.
You can see the error by launching the virtual machine with
options --verbose and --con0=this.

A possible solution is to disable file locking by mounting the NFS share
with the option "nolock". For example:
hostname:/root# mount -o nolock nfsserver:/nfs/share/ /home

Since a single .disk file is always accessed by just one Netkit kernel
(i.e., virtual machine) at a time, this should not be improper, and is
likely to fix your problem.

Regards,
Massimo.


> -----Messaggio originale-----
> Da: netkit.users-bounces a list.dia.uniroma3.it
> [mailto:netkit.users-bounces a list.dia.uniroma3.it]Per conto di Pietro
> Rango
> Inviato: giovedì 12 gennaio 2006 13.03
> A: netkit.users a list.dia.uniroma3.it
> Oggetto: [Netkit.users] error: Kernel panic - not syncing: VFS: Unable
> to mount root fs on unknown-block(98,1)
>
>
> Hi,
> I'm a network administrator and i use a nis server with /home in nfs.
>  From a loca installation i don't have any problems but from a nis
> client with an nfs /home and the netkit home in /home/netkit2 if i try
> to start a machine with vstart pc1 it start.
> But if I close it and try to restart it I receive this error:
> Kernel panic - not syncing: VFS: Unable to mount root fs on
> unknown-block(98,1)
>
> I don't undestand why.
>
> Thanks.
>
>