This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] nfs - another question

To: XEN User - listmembers <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] nfs - another question
From: Stephan Seitz <s.seitz@xxxxxxxxxxxx>
Date: Thu, 17 Nov 2005 17:36:18 +0100
Delivery-date: Thu, 17 Nov 2005 16:36:26 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Openpgp: id=46F31C36
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (X11/20050331)
Hash: SHA1


i've got a very weird problem, when using root_nfs in domU's.

i'm currently running cownfsd, which i am able to use locally and
remotely via
mount -t nfs

but, when using this share in a domU, it doesn't mount as root.

domU shows following bootmsg:

- ------
Linux version (root@xen-01) (gcc-Version 3.4.4 20050314
(prerelease) (Debian 3.4.3-13)) #6 SMP Thu Nov 17 12:20:09 CET 2005
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000006000000 (usable)
104MB LOWMEM available.
IRQ lockup detection disabled
Built 1 zonelists
Kernel command line:
root=/dev/nfs rw nfsroot= 2VMID=1
Initializing CPU#0
PID hash table entries: 512 (order: 9, 8192 bytes)
Xen reported: 2090.552 MHz processor.
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
vmalloc area: c7000000-fbff5000, maxmem 34000000
Memory: 92672k/106496k available (2820k kernel code, 5368k reserved,
748k data, 164k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor
mode... Ok.
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... disabled
Brought up 1 CPUs
NET: Registered protocol family 16
Brought up 1 CPUs
xen_mem: Initialising balloon driver.
SCSI subsystem initialized
Grant table initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Coda Kernel/Venus communications, v6.0.0, coda@xxxxxxxxxx
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: loaded (max 8 devices)
nbd: registered device at major 43
Xen virtual console successfully installed as tty1
Event-channel device installed.
Registering block device major 8
xen_net: Initialising virtual ethernet driver.
register_blkdev: cannot get major 8 for sd
aoe: aoe_init: AoE v2.6-10 initialised.
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: automatically using best checksumming function: pIII_sse
   pIII_sse  :  3386.400 MB/sec
raid5: using function: pIII_sse (3386.400 MB/sec)
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@xxxxxxxxxx
device-mapper: dm-multipath version 1.0.4 loaded
device-mapper: dm-round-robin version 1.0.0 loaded
NET: Registered protocol family 2
IP: routing cache hash table of 256 buckets, 4Kbytes
TCP established hash table entries: 4096 (order: 4, 65536 bytes)
TCP bind hash table entries: 4096 (order: 3, 49152 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
NET: Registered protocol family 1
NET: Registered protocol family 10
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
IP-Config: Complete:
      device=eth0, addr=, mask=,
     host=mosixen-01, domain=, nis-domain=(none),
     bootserver=, rootserver=, rootpath=
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
Looking up port of RPC 100003/2 on
Looking up port of RPC 100005/1 on
RPC: call_verify: program 100005, version 1 unsupported by server
Root-NFS: Server returned error -5 while mounting /mosiXen-01
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "nfs" or unknown-block(2,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on
- ----

as said, mount works:

- ----
xen-01:~# mount -t nfs /mnt
xen-01:~# df
                        976568    488280    488288  50% /mnt
- ----

i don't know what to setup in the domU's kernel, to get this working.

If someone of you does have any idea about this error?

I'm pretty sure that my settings /etc/xen/mosixen settings are right, as
this machine works without changing the settings, but with kernel-nfsd
at dom0 as server.


Stephan Seitz
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org


Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] nfs - another question, Stephan Seitz <=