Re: Re: Re: Re: [Xen-users] xen-3.0-x86_32 not supported by xenkernel

["Nick Couchman" <Nick.Couchman@xxxxxxxxx>]

You probably need to rebuild the initrd image used to boot so that it has the xenblk driver included.  The following messages indicate that the xenblk driver isn't loading:

XENBUS: Device with no driver: device/vbd/2057
XENBUS: Device with no driver: device/vbd/2056

-Nick

>>> <math_physics@xxxxxxx> 2008/12/08 20:14 >>>

Yes, I have editted the fstab file in /mnt/loop1/etc. Its content is modified to:

/dev/sda9               /          other parameters
/dev/sda8               swap       other parameters

-----Original message-----
From: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
Date: Dec. 9, 2008, Tu.
To: math_physics@xxxxxxx
Copy to:
Subject: Re: Re: Re: [Xen-users] xen-3.0-x86_32 not supported by xen kernel

Did you edit the fstab file in /mnt/loop1/etc with the new root information?

 

-Nick

>>> <math_physics@xxxxxxx> 2008/12/07 06:48 >>>

Hi, Nick:
  Thank you so much for you help! But I still can't solve my problem:(. I still need help:)
  I post my DomU configure file and booting messge here. Would you help me find out the answer?
  The kernal and the ramdisk file I use are installed by rpm package in the RHEL AS5.1 installation disk.
  And here is what I do: 
  1. I create a image file /home1/rh9/rh9.img and mount it to /mnt/loop1.
  2. Copy the whole rh9 system(a physical linux system installed in /dev/sda5) into /mnt/loop1;
  3. Copy the directory /lib/modules/2.6.18-53.el5xen of my RHEL AS5.1 (on /dev/sda1) into /mnt/loop1/lib/modules;
  4. Modify /mnt/loop1/etc/fstab, where mount points are fixed to match the settings of DomU configuration file.
    Thank you so much!
############ DomU configuration file:
kernel = "/boot/vmlinuz-2.6.18-53.el5xen"
ramdisk ="/boot/initrd-2.6.18-53.el5xen.img"
memory = 1024
name = "rh9"
disk = ['file:/home1/rh9/rh9.img,sda9,w','file:/home1/rh9/rh9_swap.img,sda8,w']
root = "/dev/sda9 ro"

############## Booting message:
Started domain rh9
Linux version 2.6.18-53.el5xen (brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Oct 10 17:06:12 EDT 2007
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000040800000 (usable)
304MB HIGHMEM available.
727MB LOWMEM available.
NX (Execute Disable) protection: active
ACPI in unprivileged domain disabled
Built 1 zonelists.  Total pages: 264192
Kernel command line:  root=/dev/sda9 ro
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c0727000 soft=c0707000
PID hash table entries: 4096 (order: 12, 16384 bytes)
Xen reported: 1662.499 MHz processor.
Console: colour dummy device 80x25
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: ee000000-f4ffe000, maxmem 2d7fe000
Memory: 1026984k/1056768k available (2049k kernel code, 20692k reserved, 844k data, 168k init, 311304k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 4158.11 BogoMIPS (lpj=8316221)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 13k freed
Brought up 1 CPUs
checking if image is initramfs... it is
Freeing initrd memory: 5216k freed
Grant table initialized
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread C06D7AA0 could not acquire Mutex [2] [20060707]
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread C06D7AA0 could not acquire Mutex [2] [20060707]
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1228655943.467:1): initialized
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key FF48355AC6B12D27
- 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)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Xen virtual console successfully installed as xvc0
Linux version 2.6.18-53.el5xen (brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Oct 10 17:06:12 EDT 2007
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000040800000 (usable)
304MB HIGHMEM available.
727MB LOWMEM available.
NX (Execute Disable) protection: active
ACPI in unprivileged domain disabled
Built 1 zonelists.  Total pages: 264192
Kernel command line:  root=/dev/sda9 ro
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c0727000 soft=c0707000
PID hash table entries: 4096 (order: 12, 16384 bytes)
Xen reported: 1662.499 MHz processor.
Console: colour dummy device 80x25
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: ee000000-f4ffe000, maxmem 2d7fe000
Memory: 1026984k/1056768k available (2049k kernel code, 20692k reserved, 844k data, 168k init, 311304k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 4158.11 BogoMIPS (lpj=8316221)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 13k freed
Brought up 1 CPUs
checking if image is initramfs... it is
Freeing initrd memory: 5216k freed
Grant table initialized
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread C06D7AA0 could not acquire Mutex [2] [20060707]
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread C06D7AA0 could not acquire Mutex [2] [20060707]
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 524288 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
audit: initializing netlink socket (disabled)
audit(1228655943.467:1): initialized
highmem bounce pool size: 64 pages
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key FF48355AC6B12D27
- 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)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Xen virtual console successfully installed as xvc0
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
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
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
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
XENBUS: Device with no driver: device/vbd/2057
XENBUS: Device with no driver: device/vbd/2056
Freeing unused kernel memory: 168k freed
Write protecting the kernel read-only data: 360k
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 uhci-hcd.ko module
USB Universal Host Controller Interface driver v3.0
Loading ohci-hcd.ko module
Loading ehci-hcd.ko module
Loading jbd.ko module
Loading ext3.ko module
Loading scsi_mod.ko module
SCSI subsystem initialized
Loading sd_mod.ko module
Loading libata.ko module
Loading ahci.ko module
Loading ata_piix.ko module
Waiting for driver initialization.
Scanning and configuring dmraid supported devices
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!

############## xm info gives the following message
release                : 2.6.18-53.el5xen
version                : #1 SMP Wed Oct 10 17:06:12 EDT 2007
machine                : i686
nr_cpus                : 2
nr_nodes               : 1
sockets_per_node       : 1
cores_per_socket       : 2
threads_per_core       : 1
cpu_mhz                : 1662
hw_caps                : bfebfbff:20100000:00000000:00000140:0000e39d:00000000:00000001
total_memory           : 2046
free_memory            : 1508
xen_major              : 3
xen_minor              : 1
xen_extra              : .0-53.el5
xen_caps               : xen-3.0-x86_32p
xen_pagesize           : 4096
platform_params        : virt_start=0xf5800000
xen_changeset          : unavailable
cc_compiler            : gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)
cc_compile_by          : brewbuilder
cc_compile_domain      : build.redhat.com
cc_compile_date        : Wed Oct 10 16:30:55 EDT 2007
xend_config_format     : 2

 

 

 > -----Original message-----
> From: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
> Date: Dec 6, 2008, Sat.
> To: math_physics@xxxxxxx
> Copy to: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: Re: [Xen-users] xen-3.0-x86_32 not supported by xen kernel
> 
> The kernel version doesn't matter so much as the Xen version in the
> kernel as well as the type of kernel.  Try installing a bigmem or
> hugemem Xen kernel as those should include PAE support and see if that
> helps.
> Nick Couchman
> Manager, Information Technology 
> -----Original Message-----
> From: <math_physics@xxxxxxx>
> To: Nick Couchman <Nick.Couchman@xxxxxxxxx>
> 
> Sent: 12/5/2008 8:38:21 PM
> Subject: Re:  Re: [Xen-users] xen-3.0-x86_32 not supported by xen kernel
> 
> Hi, Nick:
> 
> Should the kernel version of Dom0 be the same with the kernel version of
> DomU? 
> 
> I install xen packages on my RHEL AS 5.1 using rpm package, but I can't
> find xenU kernel. I only found kernel files whose name include string
> 'xen' only. So I built a xenU kernel (2.6.16). 
> 
> Then I boot xenU kernel in RHEL AS 5.1, and it gives me the error
> messege.
> 
> 
> Thank you !
> 
> 
> 
> 
> -----Original message-----
> From: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
> Date: Dec 6, 2008, Sat.
> To: math_physics@xxxxxxx
> Copy: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-users] xen-3.0-x86_32 not supported by xen kernel
> 
> Use xm info to figure out which kernels are supported - I suggest trying
> a 32-bit PAE kernel - my SLES10 64-bit Linux builds don't support plain
> 32-bit kernels, but they do support 32-bit PAE (big/huge) kernels.
> 
> -Nick
> 
> 
> -----Original Message-----
> From: math_physics@xxxxxxx
> To: Xen MailList <xen-users@xxxxxxxxxxxxxxxxxxx>
> Subject: [Xen-users] xen-3.0-x86_32 not supported by xen kernel
> Date: Fri, 5 Dec 2008 09:56:45 +0800 (CST)
> 
> 
> I build a DomU kernel on RHEL AS5.1. But when I boot this Guest DomU
> with the kernel, it gives me error message:
> 
> Error: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type
> xen-3.0-x86_32 not supported by xen kernel, sorry\n')
> 
> 
> Can someone give me any suggestion about this problem?
>  
> Thank you!
> 
> Joe
> 
> 
> 
> 

> 
> This e-mail may contain confidential and privileged material for the
> sole use of the intended recipient. If this email is not intended for
> you, or you are not responsible for the delivery of this message to the
> intended recipient, please note that this message may contain SEAKR
> Engineering (SEAKR) Privileged/Proprietary Information. In such a case,
> you are strictly prohibited from downloading, photocopying, distributing
> or otherwise using this message, its contents or attachments in any way.
> If you have received this message in error, please notify us immediately
> by replying to this e-mail and delete the message from your mailbox.
> Information contained in this message that does not relate to the
> business of SEAKR is neither endorsed by nor attributable to SEAKR.
> 
> 
> This e-mail may contain confidential and privileged material for the sole use of the intended recipient.  If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information.  In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way.  If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox.  Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

---

---

This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

---

[??] 2008???????

---

This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

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