[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Vm creation problem through NFS Mount.


  • To: <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Nitesh Gangarde, Noida" <nitesh.g@xxxxxx>
  • Date: Thu, 13 Jul 2006 11:22:51 +0530
  • Cc: "Sudha Mohan Panda, Noida" <sudhap@xxxxxx>, "Iqbal Ashraf, Noida" <iqbal.a@xxxxxx>, "Shweta Kumari, Noida" <shwetak@xxxxxx>
  • Delivery-date: Wed, 12 Jul 2006 22:55:03 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcamQJQS7nBG+rK0SuKY5MohVBvTLw==
  • Thread-topic: Vm creation problem through NFS Mount.

Hi

 

 I am trying to create a domU using the nfs mount. But I am getting

 some problem which I am listing down. I need your help in solving the same.

 xm create -c nfs vmid=1 gives the following error : Error that I am getting is listed in red

 Font color.

 

 Linux version 2.6.16-1.2122_FC5xenU

 (bhcompile@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.0 20060304

 (Red Hat 4.1.0-3)) #1 SMP Sun May 21 15:52:00 EDT 2006 BIOS-provided

 physical RAM map:

  Xen: 0000000000000000 - 0000000020000000 (usable) 0MB HIGHMEM

 available.

 520MB LOWMEM available.

 Using x86 segment limits to approximate NX protection IRQ lockup

 detection disabled Built 1 zonelists Kernel command line:

 ip=10.112.77.71:10.112.69.119::255.255.255.0::eth0:off root=/dev/nfs

 nfsroot=10.112.69.119:/linuxfs Enabling fast FPU save and restore...

 done.

 Enabling unmasked SIMD FPU exception support... done.

 Initializing CPU#0

 PID hash table entries: 4096 (order: 12, 65536 bytes) Xen reported:

 2666.756 MHz processor.

 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)

 Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)

 Software IO TLB disabled vmalloc area: e1000000-fb3fe000, maxmem

 33ffe000

 Memory: 514048k/532480k available (1655k kernel code, 9896k reserved,

 618k data, 132k init, 0k highmem) Checking if this processor honours

 the WP bit even in supervisor mode...

 Ok.

 calibrate_delay_direct() failed to get a good estimate for

 loops_per_jiffy.

 Probably due to long platform interrupts. Consider using "lpj=" boot

 option.

 Security Framework v1.0.0 initialized

 SELinux:  Initializing.

 SELinux:  Starting in permissive mode

 selinux_register_security:  Registering secondary module capability

 Capability LSM initialized as secondary Mount-cache hash table

 entries: 512

 CPU: Trace cache: 12K uops, L1 D cache: 16K

 CPU: L2 cache: 1024K

 Checking 'hlt' instruction... OK.

 Brought up 1 CPUs

 0

 Grant table initialized

 NET: Registered protocol family 16

 Brought up 1 CPUs

 xen_mem: Initialising balloon driver.

 audit: initializing netlink socket (disabled)

 audit(1152271275.312:1): initialized

 VFS: Disk quotas dquot_6.5.1

 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

 SELinux:  Registering netfilter hooks

 Initializing Cryptographic API

 ksign: Installing public key data

 Loading keyring

 - Added public key 43645308A4C9E5AD

 - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop

 registered io scheduler anticipatory registered io scheduler deadline

 registered io scheduler cfq registered (default)

 rtc: IRQ 8 is not free.

 i8042.c: No controller found.

 RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize

 Xen virtual console successfully installed as tty1 Event-channel

 device installed.

 Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2

 ide: Assuming 50MHz system bus speed for PIO modes; override with

 idebus=xx ide-floppy driver 0.99.newide

 mice: PS/2 mouse device common for all mice

 md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27

 md: bitmap version 4.39

 NET: Registered protocol family 2

 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP

 established hash table entries: 131072 (order: 9, 2621440 bytes) TCP

 bind hash table entries: 65536 (order: 8, 1310720 bytes)

 TCP: Hash tables configured (established 131072 bind 65536) TCP reno

 registered TCP bic registered Initializing IPsec netlink socket

 NET: Registered protocol family 1

 NET: Registered protocol family 17

 Using IPI No-Shortcut mode

 XENBUS: Timeout connecting to devices!

 md: Autodetecting RAID arrays.

 md: autorun ....

 md: ... autorun DONE.

 

 VFS: Cannot open root device "nfs" or unknown-block(0,255) Please

 append a correct "root=" boot option Kernel panic - not syncing: VFS:

 Unable to mount root fs on

 unknown-block(0,255)

  [<c01178a0>] panic+0x3c/0x188

  [<c033ca24>] mount_block_root+0x19c/0x1aa  [<c033ca7b>]

 mount_root+0x49/0x4e  [<c033cb40>] prepare_namespace+0xc0/0xf1 

 [<c0102267>] init+0x23e/0x2fe  [<c0102029>] init+0x0/0x2fe 

 [<c01029ad>] kernel_thread_helper+0x5/0xb

 

 The config file nfs that I am using is :

 

 kernel = "/boot/vmlinuz-2.6.16-1.2122_FC5xenU"

 memory = 512

 name = "vm01"

 vif = [ '' ]

 ip = "10.112.77.71"

 netmask= '255.255.255.0'

 root = "/dev/nfs"

 nfs_server = '10.112.69.119'

 nfs_root   = '/linuxfs'

 

 The whole filesystem is copied on 10.112.69.119 under /linuxfs. And I

 am able to mount this on any remote system.

 Actually , the problem here lies with "root=/dev/nfs", what it

 actually points to ?

 

 Can any body help me out to solve this problem?

 

 

Thanks & Regards

Nitesh Gangrade

DISCLAIMER:
-----------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in
this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates.
Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of
this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have
received this email in error please delete it and notify the sender immediately. Before opening any mail and
attachments please check them for viruses and defect.
-----------------------------------------------------------------------------------------------------------------------
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.