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


Re: [Xen-devel] Booting Failures when using linux- asDomUwith pa

To: "Konrad Rzeszutek Wilk" <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Booting Failures when using linux- asDomUwith paravirt-ops support
From: "zhangxiang" <zhangxiang@xxxxxxxxxx>
Date: Tue, 20 Apr 2010 16:15:10 +0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 20 Apr 2010 01:15:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <201004191658461840246@xxxxxxxxxx>, <201004192229162684747@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hello, Konrad:
Thank you very much for your help!
There is not any partitions on /sda3/vmdisk2. I creat it using the following bash script:
dd if=/dev/zero of=vmdisk2 bs=4096 count=1310720
mkfs -t ext3 vmdisk2
mount -o loop vmdisk2 /mnt
rsync -aH /{var,root,dev,etc,usr,bin,sbin,lib,lib64,home} /mnt
mkdir /mnt/{proc,sys,tmp,mnt}
umount /mnt
I am sure that it will work, because when I use linux- (download from http://www.xen.org/ )
as DomU's kernel, the VM can boot sucessfully. The guest configuration file is the same except the 
following two lines:
kernel = "/boot/vmlinuz-"
ramdisk = "/boot/initrd-"
The whole output when booting is list as follows:
[root@node18 sda3]# xm cre -c zxxm2 
Using config file "./zxxm2".
Started domain zxxm2 (id=4)
Bootdata ok (command line is root=/dev/xvda rw ip= xencons=tty1)
Linux version (root@node18) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #2 SMP Mon Apr 19 20:47:34 CST 2010
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000020800000 (usable)
Built 1 zonelists.  Total pages: 129222
Kernel command line: root=/dev/xvda rw ip= xencons=tty1
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 16384 bytes)
Xen reported: 2412.362 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Software IO TLB disabled
Memory: 507784k/532480k available (2062k kernel code, 16496k reserved, 690k data, 132k init)
Calibrating delay using timer specific routine.. 4828.76 BogoMIPS (lpj=24143803)
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
SMP alternatives: switching to UP code
Brought up 1 CPUs
checking if image is initramfs... it is
Freeing initrd memory: 2848k freed
NET: Registered protocol family 16
SMP alternatives: switching to SMP code
Initializing CPU#1
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 1024K (64 bytes/line)
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
Brought up 2 CPUs
suspend: event channel 9
xen_mem: Initialising balloon driver.
NET: Registered protocol family 2
IP route cache hash table entries: 16384 (order: 5, 131072 bytes)
TCP established hash table entries: 65536 (order: 8, 1048576 bytes)
TCP bind hash table entries: 32768 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 65536 bind 32768)
TCP reno registered
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
netfront: Initialising virtual ethernet driver.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
xen-vbd: registered block device major 202
blkfront: xvda: barriers enabled
 xvda: unknown partition table
XENBUS: Device with no driver: device/console/0
IP-Config: Complete:
      device=eth0, addr=, mask=, gw=,
     host=, domain=, nis-domain=(none),
     bootserver=, rootserver=, rootpath=
Freeing unused kernel memory: 132k freed
Red Hat nash version starting
Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Setting up hotplug.
Creating block device nodes.
Creating root device.
Mounting root filesystem.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
Setting up other filesystems.
Setting up new root fs
no fstab.sys, mounting internal defaults
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
INIT: version 2.86 booting
Welcome to  CentOS release 5.3 (Final)
Press 'I' to enter interactive startup.
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
Setting clock  (utc): Tue Apr 20 15:40:39 CST 2010 [  OK  ]
Starting udev: [  OK  ]
Loading default keymap (us): /etc/rc.d/rc.sysinit: line 396: /dev/tty0: No such device or address
Setting hostname node182:  [  OK  ]
raidautorun: failed to open /dev/md0: No such device or address
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/xvda 
/dev/xvda: clean, 194414/1179648 files, 1177758/2359296 blocks
[  OK  ]
Remounting root filesystem in read-write mode:  [  OK  ]
Mounting local filesystems:  [  OK  ]
Enabling local filesystem quotas:  quotaon: Warning: No quota format detected in the kernel.
[  OK  ]
rm: cannot remove `/var/run/xend/boot': Is a directory
Enabling /etc/fstab swaps:  [  OK  ]
INIT: Entering runlevel: 3
Entering non-interactive startup
FATAL: Module ipv6 not found.
CRITICAL : [ipv6_test] Kernel is not compiled with IPv6 support
Bringing up loopback interface:  [  OK  ]
Bringing up interface eth0:  [  OK  ]
FATAL: Module ipv6 not found.
CRITICAL : [ipv6_test] Kernel is not compiled with IPv6 support
Starting system logger: [  OK  ]
Starting kernel logger: [  OK  ]
Starting portmap: [  OK  ]
Starting sshd: [  OK  ]
Starting xinetd: [  OK  ]
Starting NFS services:  [  OK  ]
Starting NFS quotas: [  OK  ]
Starting NFS daemon: [FAILED]
Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using for ServerName [  OK  ]
Starting xfs: [  OK  ]
Starting yum-updatesd: [  OK  ]
CentOS release 5.3 (Final)
Kernel on an x86_64
node182 login:
It aslo has the output: " xvda: unknown partition table", but it can boot up sucessfully. When
I login and run "fdisk -l", the whole output is as follows:
[root@node182 ~]# fdisk -l
Disk /dev/xvda: 9663 MB, 9663676416 bytes
255 heads, 63 sectors/track, 1174 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/xvda doesn't contain a valid partition table
However, the VM can work normally. So I do not think it is the partitions cause the problem.
I am sure that I select these following config options as "y" when compling linux-
I do not use any logical volumes, so I do not need to use LVM name when writing the guest
configuration file. In linux-, CONFIG_DM_LINEAR does not exist. Thus I select the
corresponding one as "y", which named CONFIG_BLK_DEV_DM. However, it also does not work,
and the output is the same.
It is really a difficult problem for me. Thank you again for your help!
Xiang Zhang

发件人: Konrad Rzeszutek Wilk
发送时间: 2010-04-20 00:01:42
收件人: zhangxiang
抄送: xen-devel
主题: Re: [Xen-devel] Booting Failures when using linux- asDomUwith paravirt-ops support
> blkfront: xvda: barriers enabled
> ide-gd driver 1.18
>  xvda:
It sees the disk, but no partitions on it. How did you see up
your /sda3/vmdisk2? Are there partitions on it? Did you make sure to
build the kernel with the filesystem support for this (ext2, ext3,
ext4?) Or do you have logical volumes? If so, you need to make
the root option (in you guest configuration file) use your LVM
name, not the disk name. Also this requires turning on the
Xen-devel mailing list