Booting Failures when using linux-2.6.33.2 as DomU with paravirt-ops support

Booting Failures when using linux-2.6.33.2 as DomU with paravirt-ops support

[zhangxiang]

[-- Attachment #1.1: Type: text/plain, Size: 2794 bytes --]

Hello, everyone!

   I am trying to boot linux-2.6.33.2 as DomU' kernel in my virtualization platform 
(Xen-3.4.2, linux-2.6.18.8 as Dom0, paravirtualization, AMD Opteron 2216, 
CentOS 5.3 without virtualization support). But it is always core-dump when 
booting. The messages are as follows:

Loading aic79xx.ko module
Loading sata_nv.ko module
Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.33.2 #13
Call Trace:
 [<ffffffff81042d00>] panic+0xa0/0x1a0
 [<ffffffff810075df>] ? xen_restore_fl_direct_end+0x0/0x1
 [<ffffffff81078e40>] ? call_rcu_sched+0x10/0x20
 [<ffffffff81078e59>] ? call_rcu+0x9/0x10
 [<ffffffff8104521e>] ? put_files_struct+0x7e/0xd0
 [<ffffffff81457955>] ? _raw_write_lock_irq+0x15/0x30
 [<ffffffff8104d4b7>] ? exit_ptrace+0xb7/0x140
 [<ffffffff81046a8f>] do_exit+0x6df/0x7a0
 [<ffffffff8102c7af>] ? do_page_fault+0x14f/0x310
 [<ffffffff81046b90>] do_group_exit+0x40/0xd0
 [<ffffffff81046c32>] sys_exit_group+0x12/0x20
 [<ffffffff8100af02>] system_call_fastpath+0x16/0x1b


The DomU's configuration file is as follows:
kernel = "/boot/vmlinuz-2.6.33.2" 
ramdisk = "/boot/initrd-2.6.33.2.img" 
memory = 512 
name = "vmtmp" 
vcpus = 2 
vif = [ '' ] 
ip = "10.10.135.182" 
netmask = "255.255.0.0" 
disk = [ 'file:/sda3/vmdisk2,xvda,w'] 
root = "/dev/xvda rw" 
extra = "4" 
extra='xencons=hvc0' 


I do this experiment depend on the link:
http://wiki.xensource.com/xenwiki/XenParavirtOps 

I download linux-2.6.33.2 from www.kernel.org, and make sure that all the following 
config options are selected when compling:
CONFIG_PARAVIRT_GUEST 
CONFIG_XEN 
CONFIG_HVC_DRIVER and CONFIG_HVC_XEN 
CONFIG_XEN_BLKDEV_FRONTEND 
CONFIG_XEN_NETDEV_FRONTEND

I also use /dev/xvdX instead of /dev/sda1 in both DomU's configurion file and /etc/fstab.

So I really do not know why the experiment always fails.
Could somebody help me with this?
Thank you very much for your help!

Xiang Zhang
Apr 19th, 2010


---------------------------------------------------------------------
 National Research Center for Intelligent Computing System
 Institute of Computing Technology
 Chinese Academy of Sciences
 P.O. Box 2704, Beijing 100190, P. R. China
 Tel: +86-10-6260 1009
---------------------------------------------------------------------

[-- Attachment #1.2: Type: text/html, Size: 7240 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Booting Failures when using linux-2.6.33.2 as DomU with paravirt-ops support

[Konrad Rzeszutek Wilk]

On Mon, Apr 19, 2010 at 04:58:46PM +0800, zhangxiang wrote:
> Hello, everyone!
> 
>    I am trying to boot linux-2.6.33.2 as DomU' kernel in my virtualization platform 
> (Xen-3.4.2, linux-2.6.18.8 as Dom0, paravirtualization, AMD Opteron 2216, 
> CentOS 5.3 without virtualization support). But it is always core-dump when 
> booting. The messages are as follows:

You need to attach the whole output to help you along.
> 
> Loading aic79xx.ko module
> Loading sata_nv.ko module
> Creating root device.
> Mounting root filesystem.
> mount: could not find filesystem '/dev/root'
> Setting up other filesystems.
> Setting up new root fs
> setuproot: moving /dev failed: No such file or directory
> no fstab.sys, mounting internal defaults
> setuproot: error mounting /proc: No such file or directory
> setuproot: error mounting /sys: No such file or directory
> Switching to new root and running init.
> unmounting old /dev
> unmounting old /proc
> unmounting old /sys
> switchroot: mount failed: No such file or directory
> Kernel panic - not syncing: Attempted to kill init!
> Pid: 1, comm: init Not tainted 2.6.33.2 #13
> Call Trace:
>  [<ffffffff81042d00>] panic+0xa0/0x1a0
>  [<ffffffff810075df>] ? xen_restore_fl_direct_end+0x0/0x1
>  [<ffffffff81078e40>] ? call_rcu_sched+0x10/0x20
>  [<ffffffff81078e59>] ? call_rcu+0x9/0x10
>  [<ffffffff8104521e>] ? put_files_struct+0x7e/0xd0
>  [<ffffffff81457955>] ? _raw_write_lock_irq+0x15/0x30
>  [<ffffffff8104d4b7>] ? exit_ptrace+0xb7/0x140
>  [<ffffffff81046a8f>] do_exit+0x6df/0x7a0
>  [<ffffffff8102c7af>] ? do_page_fault+0x14f/0x310
>  [<ffffffff81046b90>] do_group_exit+0x40/0xd0
>  [<ffffffff81046c32>] sys_exit_group+0x12/0x20
>  [<ffffffff8100af02>] system_call_fastpath+0x16/0x1b
> 
> 
> The DomU's configuration file is as follows:
> kernel = "/boot/vmlinuz-2.6.33.2" 
> ramdisk = "/boot/initrd-2.6.33.2.img" 
> memory = 512 
> name = "vmtmp" 
> vcpus = 2 
> vif = [ '' ] 
> ip = "10.10.135.182" 
> netmask = "255.255.0.0" 
> disk = [ 'file:/sda3/vmdisk2,xvda,w'] 
> root = "/dev/xvda rw" 
> extra = "4" 
> extra='xencons=hvc0' 
> 
> 
> I do this experiment depend on the link:
> http://wiki.xensource.com/xenwiki/XenParavirtOps 
> 
> I download linux-2.6.33.2 from www.kernel.org, and make sure that all the following 
> config options are selected when compling:

By selected you mean 'y', correct?


> CONFIG_PARAVIRT_GUEST 
> CONFIG_XEN 
> CONFIG_HVC_DRIVER and CONFIG_HVC_XEN 
> CONFIG_XEN_BLKDEV_FRONTEND 
> CONFIG_XEN_NETDEV_FRONTEND

I thought there was also a FBDEV and KBDDEV, but I could be wrong.
> 
> I also use /dev/xvdX instead of /dev/sda1 in both DomU's configurion file and /etc/fstab.
> 
> So I really do not know why the experiment always fails.
> Could somebody help me with this?
> Thank you very much for your help!
> 
> Xiang Zhang
> Apr 19th, 2010
> 
> 
> ---------------------------------------------------------------------
>  National Research Center for Intelligent Computing System
>  Institute of Computing Technology
>  Chinese Academy of Sciences
>  P.O. Box 2704, Beijing 100190, P. R. China
>  Tel: +86-10-6260 1009
> ---------------------------------------------------------------------

> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

Re: Booting Failures when using linux-2.6.33.2 as DomUwith paravirt-ops support

[zhangxiang]

[-- Attachment #1.1: Type: text/plain, Size: 13857 bytes --]

Hello, Konrad!

   Thank you very much for your reply.

   Firstly, I select following config options as "y" when compling linux-2.6.33.2:
   CONFIG_PARAVIRT_GUEST=y
   CONFIG_XEN=y
   CONFIG_HVC_DRIVER=y
   CONFIG_HVC_XEN=y
   CONFIG_XEN_BLKDEV_FRONTEND=y
   CONFIG_XEN_NETDEV_FRONTEND=y

   Secondly, I also select CONFIG_XEN_FBDEV_FRONTEND and CONFIG_XEN_KBDDEV_FRONTEND as "y",
and it also core-dumps when booting.
  
   Finally, the whole output is list as follows:

[root@node18 sda3]# xm cre -c zxxmtmp 
Using config file "./zxxmtmp".
Started domain zxxmtmp (id=3)
Linux version 2.6.33.2 (root@node18) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #14 SMP Mon Apr 19 22:22:52 CST 2010
Command line: root=/dev/xvda rw ip=10.10.135.182:127.0.255.255::255.255.0.0::eth0:off xencons=hvc0
ACPI in unprivileged domain disabled
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 00000000000a0000 (usable)
 Xen: 00000000000a0000 - 0000000000100000 (reserved)
 Xen: 0000000000100000 - 0000000020000000 (usable)
NX (Execute Disable) protection: active
DMI not present or invalid.
No AGP bridge found
last_pfn = 0x20000 max_arch_pfn = 0x400000000
init_memory_mapping: 0000000000000000-0000000020000000
RAMDISK: 017f0000 - 01b22000
(8 early reservations) ==> bootmem [0000000000 - 0020000000]
  #0 [0000000000 - 0000001000]   BIOS data page ==> [0000000000 - 0000001000]
  #1 [0001c25000 - 0001c38000]   XEN PAGETABLES ==> [0001c25000 - 0001c38000]
  #2 [0001000000 - 00017cfed4]    TEXT DATA BSS ==> [0001000000 - 00017cfed4]
  #3 [00017f0000 - 0001b22000]          RAMDISK ==> [00017f0000 - 0001b22000]
  #4 [0001b22000 - 0001c25000]   XEN START INFO ==> [0001b22000 - 0001c25000]
  #5 [0000001000 - 0000003000]       TRAMPOLINE ==> [0000001000 - 0000003000]
  #6 [0000003000 - 0000007000]      ACPI WAKEUP ==> [0000003000 - 0000007000]
  #7 [0000100000 - 00001ec000]          PGTABLE ==> [0000100000 - 00001ec000]
Zone PFN ranges:
  DMA      0x00000000 -> 0x00001000
  DMA32    0x00001000 -> 0x00100000
  Normal   0x00100000 -> 0x00100000
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
    0: 0x00000000 -> 0x000000a0
    0: 0x00000100 -> 0x00020000
SMP: Allowing 2 CPUs, 0 hotplug CPUs
No local APIC present
APIC: disable apic facility
APIC: switched to apic NOOP
Allocating PCI resources starting at 20000000 (gap: 20000000:e0000000)
Booting paravirtualized kernel on Xen
Xen version: 3.4.2 (preserve-AD)
setup_percpu: NR_CPUS:4 nr_cpumask_bits:4 nr_cpu_ids:2 nr_node_ids:1
PERCPU: Embedded 27 pages/cpu @ffff880001c42000 s77912 r8192 d24488 u110592
pcpu-alloc: s77912 r8192 d24488 u110592 alloc=27*4096
pcpu-alloc: [0] 0 [0] 1 
Xen: using vcpu_info placement
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 128941
Kernel command line: root=/dev/xvda rw ip=10.10.135.182:127.0.255.255::255.255.0.0::eth0:off xencons=hvc0
PID hash table entries: 2048 (order: 2, 16384 bytes)
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Checking aperture...
No AGP bridge found
Memory: 501684k/524288k available (4488k kernel code, 384k absent, 21600k reserved, 2459k data, 552k init)
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is enabled.
NR_IRQS:384
Console: colour dummy device 80x25
console [tty0] enabled
console [hvc0] enabled
installing Xen timer for CPU 0
Detected 2412.360 MHz processor.
Calibrating delay loop (skipped), value calculated using timer frequency.. 4824.72 BogoMIPS (lpj=24123600)
Mount-cache hash table entries: 256
CPU: Physical Processor ID: 1
CPU: Processor Core ID: 0
Performance Events:
no APIC, boot with the "lapic" boot parameter to force-enable it.
no hardware sampling interrupt available.
AMD PMU driver.
... version:                0
... bit width:              48
... generic registers:      4
... value mask:             0000ffffffffffff
... max period:             00007fffffffffff
... fixed-purpose events:   0
... event mask:             000000000000000f
SMP alternatives: switching to UP code
cpu 0 spinlock event irq 1
installing Xen timer for CPU 1
cpu 1 spinlock event irq 7
SMP alternatives: switching to SMP code
Brought up 2 CPUs
Grant table initialized
NET: Registered protocol family 16
PCI: Fatal: No config space access function found
bio: create slab <bio-0> at 0
ACPI: Interpreter disabled.
xen_balloon: Initialising balloon driver.
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: System does not support PCI
PCI: System does not support PCI
Switching to clocksource xen
pnp: PnP ACPI: disabled
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 3272k freed
platform rtc_cmos: registered platform RTC device (no PNP device found)
microcode: no support for this CPU vendor
msgmni has been set to 987
alg: No test for stdrng (krng)
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Event-channel device installed.
Floppy drive(s): fd0 is unknown type 15 (usb?), fd1 is unknown type 15 (usb?)
floppy0: Unable to grab IRQ6 for the floppy driver
brd: module loaded
loop: module loaded
Compaq SMART2 Driver (v 2.6.0)
HP CISS Driver (v 3.6.20)
Uniform Multi-Platform E-IDE driver
ide_generic: please use "probe_mask=0x3f" module parameter for probing all legacy ISA IDE ports
ide_generic: I/O resource 0x1F0-0x1F7 not free.
ide_generic: I/O resource 0x170-0x177 not free.
blkfront: xvda: barriers enabled
ide-gd driver 1.18
 xvda:
ide-cd driver 5.00
Adaptec aacraid driver 1.1-5[24702]-ms
3ware Storage Controller device driver for Linux v1.26.02.002.
Intel(R) PRO/1000 Network Driver - version 7.3.21-k5-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e1000e: Intel(R) PRO/1000 Network Driver - 1.0.2-k2
e1000e: Copyright (c) 1999 - 2009 Intel Corporation.
Intel(R) Gigabit Ethernet Network Driver - version 2.1.0-k2
Copyright (c) 2007-2009 Intel Corporation.
Intel(R) Virtual Function Network Driver - version 1.0.0-k0
Copyright (c) 2009 Intel Corporation.
pcnet32.c:v1.35 21.Apr.2008 tsbogend@alpha.franken.de
Initialising Xen virtual ethernet driver.
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Fusion MPT base driver 3.04.13
Copyright (c) 1999-2008 LSI Corporation
Fusion MPT SPI Host driver 3.04.13
Fusion MPT FC Host driver 3.04.13
Fusion MPT SAS Host driver 3.04.13
Fusion MPT misc device (ioctl) driver 3.04.13
mptctl: Registered with Fusion MPT base driver
mptctl: /dev/mptctl @ (major,minor=10,220)
usbmon: debugfs is not available
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
device-mapper: ioctl: 4.16.0-ioctl (2009-11-05) initialised: dm-devel@redhat.com
cpuidle: using governor ladder
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
TCP cubic registered
NET: Registered protocol family 17
 unknown partition table
XENBUS: Device with no driver: device/console/0
BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
EDD information not available.
IP-Config: Complete:
     device=eth0, addr=10.10.135.182, mask=255.255.0.0, gw=255.255.255.255,
     host=10.10.135.182, domain=, nis-domain=(none),
     bootserver=127.0.255.255, rootserver=127.0.255.255, rootpath=
Freeing unused kernel memory: 552k freed
Red Hat nash version 5.1.19.6 starting
Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Setting up hotplug.
Creating block device nodes.
Loading ehci-hcd.ko module
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Loading ohci-hcd.ko module
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Loading uhci-hcd.ko module
uhci_hcd: USB Universal Host Controller Interface driver
mount: could not find filesystem '/proc/bus/usb'
Loading aic79xx.ko module
Loading sata_nv.ko module
Creating root device.
Mounting root filesystem.
mount: could not find filesystem '/dev/root'
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.33.2 #14
Call Trace:
 [<ffffffff81042d00>] panic+0xa0/0x1a0
 [<ffffffff810075df>] ? xen_restore_fl_direct_end+0x0/0x1
 [<ffffffff81078e40>] ? call_rcu_sched+0x10/0x20
 [<ffffffff81078e59>] ? call_rcu+0x9/0x10
 [<ffffffff8104521e>] ? put_files_struct+0x7e/0xd0
 [<ffffffff8145f365>] ? _raw_write_lock_irq+0x15/0x30
 [<ffffffff8104d4b7>] ? exit_ptrace+0xb7/0x140
 [<ffffffff81046a8f>] do_exit+0x6df/0x7a0
 [<ffffffff8102c7af>] ? do_page_fault+0x14f/0x310
 [<ffffffff81046b90>] do_group_exit+0x40/0xd0
 [<ffffffff81046c32>] sys_exit_group+0x12/0x20
 [<ffffffff8100af02>] system_call_fastpath+0x16/0x1b

It really troubles me a lot. Thank you again for your help!

Xiang Zhang
Apr 19th, 2010








zhangxiang
2010-04-19



发件人： Konrad Rzeszutek Wilk
发送时间： 2010-04-19 21:59:00
收件人： zhangxiang
抄送： xen-devel
主题： Re: [Xen-devel] Booting Failures when using linux-2.6.33.2 as DomUwith paravirt-ops support

On Mon, Apr 19, 2010 at 04:58:46PM +0800, zhangxiang wrote:
> Hello, everyone!
> 
>    I am trying to boot linux-2.6.33.2 as DomU' kernel in my virtualization platform 
> (Xen-3.4.2, linux-2.6.18.8 as Dom0, paravirtualization, AMD Opteron 2216, 
> CentOS 5.3 without virtualization support). But it is always core-dump when 
> booting. The messages are as follows:
You need to attach the whole output to help you along.
> 
> Loading aic79xx.ko module
> Loading sata_nv.ko module
> Creating root device.
> Mounting root filesystem.
> mount: could not find filesystem '/dev/root'
> Setting up other filesystems.
> Setting up new root fs
> setuproot: moving /dev failed: No such file or directory
> no fstab.sys, mounting internal defaults
> setuproot: error mounting /proc: No such file or directory
> setuproot: error mounting /sys: No such file or directory
> Switching to new root and running init.
> unmounting old /dev
> unmounting old /proc
> unmounting old /sys
> switchroot: mount failed: No such file or directory
> Kernel panic - not syncing: Attempted to kill init!
> Pid: 1, comm: init Not tainted 2.6.33.2 #13
> Call Trace:
>  [<ffffffff81042d00>] panic+0xa0/0x1a0
>  [<ffffffff810075df>] ? xen_restore_fl_direct_end+0x0/0x1
>  [<ffffffff81078e40>] ? call_rcu_sched+0x10/0x20
>  [<ffffffff81078e59>] ? call_rcu+0x9/0x10
>  [<ffffffff8104521e>] ? put_files_struct+0x7e/0xd0
>  [<ffffffff81457955>] ? _raw_write_lock_irq+0x15/0x30
>  [<ffffffff8104d4b7>] ? exit_ptrace+0xb7/0x140
>  [<ffffffff81046a8f>] do_exit+0x6df/0x7a0
>  [<ffffffff8102c7af>] ? do_page_fault+0x14f/0x310
>  [<ffffffff81046b90>] do_group_exit+0x40/0xd0
>  [<ffffffff81046c32>] sys_exit_group+0x12/0x20
>  [<ffffffff8100af02>] system_call_fastpath+0x16/0x1b
> 
> 
> The DomU's configuration file is as follows:
> kernel = "/boot/vmlinuz-2.6.33.2" 
> ramdisk = "/boot/initrd-2.6.33.2.img" 
> memory = 512 
> name = "vmtmp" 
> vcpus = 2 
> vif = [ '' ] 
> ip = "10.10.135.182" 
> netmask = "255.255.0.0" 
> disk = [ 'file:/sda3/vmdisk2,xvda,w'] 
> root = "/dev/xvda rw" 
> extra = "4" 
> extra='xencons=hvc0' 
> 
> 
> I do this experiment depend on the link:
> http://wiki.xensource.com/xenwiki/XenParavirtOps 
> 
> I download linux-2.6.33.2 from www.kernel.org, and make sure that all the following 
> config options are selected when compling:
By selected you mean 'y', correct?
> CONFIG_PARAVIRT_GUEST 
> CONFIG_XEN 
> CONFIG_HVC_DRIVER and CONFIG_HVC_XEN 
> CONFIG_XEN_BLKDEV_FRONTEND 
> CONFIG_XEN_NETDEV_FRONTEND
I thought there was also a FBDEV and KBDDEV, but I could be wrong.
> 
> I also use /dev/xvdX instead of /dev/sda1 in both DomU's configurion file and /etc/fstab.
> 
> So I really do not know why the experiment always fails.
> Could somebody help me with this?
> Thank you very much for your help!
> 
> Xiang Zhang
> Apr 19th, 2010
> 
> 
> ---------------------------------------------------------------------
>  National Research Center for Intelligent Computing System
>  Institute of Computing Technology
>  Chinese Academy of Sciences
>  P.O. Box 2704, Beijing 100190, P. R. China
>  Tel: +86-10-6260 1009
> ---------------------------------------------------------------------
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

[-- Attachment #1.2: Type: text/html, Size: 31929 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Booting Failures when using linux-2.6.33.2 as DomUwith paravirt-ops support

[Konrad Rzeszutek Wilk]

> 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
CONFIG_DM_LINEAR option.

Re: Booting Failures when using linux-2.6.33.2 asDomUwith paravirt-ops support

[zhangxiang]

[-- Attachment #1.1: Type: text/plain, Size: 7947 bytes --]

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}
sync
umount /mnt

I am sure that it will work, because when I use linux-2.6.18.8 (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-2.6.18.8-xenU" 
ramdisk = "/boot/initrd-2.6.18.8-xenU.img" 

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=10.10.135.182:127.0.255.255::255.255.0.0::eth0:off xencons=tty1)
Linux version 2.6.18.8-xenU (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=10.10.135.182:127.0.255.255::255.255.0.0::eth0:off 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
migration_cost=0
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
migration_cost=546
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=10.10.135.182, mask=255.255.0.0, gw=255.255.255.255,
     host=10.10.135.182, domain=, nis-domain=(none),
     bootserver=127.0.255.255, rootserver=127.0.255.255, rootpath=
Freeing unused kernel memory: 132k freed
Red Hat nash version 5.1.19.6 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
[FAILED]
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 127.0.0.1 for ServerName [  OK  ] 
Starting xfs: [  OK  ] 
Starting yum-updatesd: [  OK  ] 
CentOS release 5.3 (Final) 
Kernel 2.6.18.8-xenU 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-2.6.33.2:

CONFIG_EXT2_FS=y 
CONFIG_EXT3_FS=y 
CONFIG_EXT3_FS_XATTR=y 

I do not use any logical volumes, so I do not need to use LVM name when writing the guest
configuration file. In linux-2.6.33.2, 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
2010-4-20






发件人： Konrad Rzeszutek Wilk
发送时间： 2010-04-20 00:01:42
收件人： zhangxiang
抄送： xen-devel
主题： Re: [Xen-devel] Booting Failures when using linux-2.6.33.2 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
CONFIG_DM_LINEAR option.

[-- Attachment #1.2: Type: text/html, Size: 25299 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Booting Failures when using linux-2.6.33.2 asDomUwith paravirt-ops support

[Konrad Rzeszutek Wilk]

> I do not use any logical volumes, so I do not need to use LVM name when writing the guest
> configuration file. In linux-2.6.33.2, 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!

I believe you are hitting in the problem that your initrd was created
with older tools (say RHEL5 ones) which expect a certain SysFS layout. The new kernels
have a different one and require this options to be turned on:

CONFIG_SYSFS_DEPRECATED_V2=y

Re: Booting Failures when using linux-2.6.33.2asDomUwith paravirt-ops support

[zhangxiang]

[-- Attachment #1.1: Type: text/plain, Size: 199 bytes --]

Hello, Konrad!

   I select CONFIG_SYSFS_DEPRECATED_V2=y as you said when compiling linux-2.6.33.2,
and the VM boots up sucessfully.
   Thank you very much for your help!

Xiang Zhang
Apr 21th, 2010

[-- Attachment #1.2: Type: text/html, Size: 2311 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: Booting Failures when using linux-2.6.33.2asDomUwith paravirt-ops support

[Konrad Rzeszutek Wilk]

On Wed, Apr 21, 2010 at 03:41:51PM +0800, zhangxiang wrote:
> Hello, Konrad!
> 
>    I select CONFIG_SYSFS_DEPRECATED_V2=y as you said when compiling linux-2.6.33.2,
> and the VM boots up sucessfully.

Oh that's great. You might want also to take a look at this Wiki if you
have see other issues:
HTTP://WIki.xensource.com/xenwiki/2.6.18-to-2.6.31-and-higher