WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] can't start domU via NFS

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] can't start domU via NFS
From: Anatoly Asviyan <aanatoly@xxxxxxxxxxxx>
Date: Thu, 30 Dec 2004 15:35:09 +0000
Delivery-date: Thu, 30 Dec 2004 13:34:51 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
        hi all
I have Xen-2.0 setup with dom0 starting from local disk.
I need to start domU from NFS
The NFS server works - both local and remote clients can use it.
But not domU :-(

Here is my config
======= /etc/xen/ttylinux-1 =========
kernel = "/boot/vmlinuz-2.6.9-xenU"
memory = 64
name = "ttylinux-1"
nics=1
ip = "192.168.1.1"
netmask="255.255.0.0"
gateway="192.168.1.123"
root = "/dev/nfs"
nfs_server = "192.168.1.123"
nfs_root   = '/tmp/nfsexport/ttylinux-1'
extra = "4"
======================================

domU starts booting and hangs at mounting its root via NFS


========= boot log ==============
Using config file "ttylinux-1".
Started domain ttylinux-1, console on port 9611
************ REMOTE CONSOLE: CTRL-] TO QUIT ********
Linux version 2.6.9-xenU (xenod@xxxxxxxxxxxxxxxxxxxxxx) (gcc version 3.2.2 
20030222 (Red Hat Linux 3.2.2-5)) #1 Wed Nov 17 22:29:37 GMT 2004
BIOS-provided physical RAM map:                             
 Xen: 0000000000000000 - 0000000004000000 (usable)
64MB LOWMEM available.                            
DMI not present.      
Built 1 zonelists
Kernel command line:  
ip=192.168.1.1:192.168.1.123:192.168.1.123:255.255.0.0::eth0:off root=/dev/nfs 
nfsroot=192.168.1.123:/tmp/nfsexport/ttylinux-1 4
Initializing CPU#0                                                    
PID hash table entries: 512 (order: 9, 8192 bytes)
Xen reported: 2791.178 MHz processor.             
Using tsc for high-res timesource    
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)  
Memory: 62436k/65536k available (1596k kernel code, 3060k reserved, 466k data, 
92k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)                  
CPU: Trace cache: 12K uops, L1 D cache: 8K                
CPU: L2 cache: 512K                       
CPU: Intel(R) Xeon(TM) CPU 2.80GHz stepping 09
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... disabled               
NET: Registered protocol family 16    
Initializing Cryptographic API    
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Xen virtual console successfully installed as tty                    
Event-channel device installed.                  
Starting Xen Balloon driver    
xen_blk: Initialising virtual block device driver
xen_blk: Timeout connecting to device!           
xen_net: Initialising virtual ethernet driver.
NET: Registered protocol family 2             
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
NET: Registered protocol family 1                       
NET: Registered protocol family 17
IP-Config: Complete:              
      device=eth0, addr=192.168.1.1, mask=255.255.0.0, gw=192.168.1.123,
     host=192.168.1.1, domain=, nis-domain=(none),                      
     bootserver=192.168.1.123, rootserver=192.168.1.123, rootpath=
Looking up port of RPC 100003/2 on 192.168.1.123                  
portmap: server 192.168.1.123 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 192.168.1.123                   
portmap: server 192.168.1.123 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default
mount: server 192.168.1.123 not responding, timed out                
Root-NFS: Server returned error -5 while mounting /tmp/nfsexport/ttylinux-1
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 unknown-block(2,0)
 <0>Rebooting in 1 seconds..

-- 
Regards, Anatoly


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>