|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: Re: Re: Re: Re: [Xen-users] xen-3.0-x86_32 not supported by
This is because dom0 loads standard storage drivers associated with whatever hardware you're actually using. The domUs, on the other hand, load drivers that allow them to use the devices exported by dom0 (or by a stub domain, in the case of Xen 3.3). So, your dom0 will use an IDE driver or SCSI driver, while the domU needs xenblk to operate correctly. To rebuild the initrd, use "mkinitrd" in the RH9 system - mount it in a temporary location, chroot to it, then use mkinitrd: mkinitrd -f --with=xenblk /boot/initrd-2.6.18-53.el5xen.img 2.6.18-53.el5xen -Nick -----Original Message----- From: math_physics@xxxxxxx To: Nick Couchman <Nick.Couchman@xxxxxxxxx> Cc: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx> Subject: Re: Re: Re: Re: Re: [Xen-users] xen-3.0-x86_32 not supported by Date: Wed, 10 Dec 2008 22:30:39 +0800 (CST) xenkernel MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_131682_27459552.1228919439475" X-Originating-IP: [118.181.8.116] X-Priority: 3 X-Mailer: Coremail Webmail Server Version XT_Ux_snapshot build 081119(6371.2087.2083) Copyright (c) 2002-2008 www.mailtech.cn 163com ------=_Part_131682_27459552.1228919439475 Content-Type: text/plain; charset=GBK Content-Transfer-Encoding: 7bit Hi, Nick: Two questions: 1. The initrd image "initrd-2.6.18-53.el5xen.img" works well for Dom0 and the following is the content of file grub.conf. Why doesn't it work for DomU? ########## title Red Hat Enterprise Linux Server AS5.1 (2.6.18-53.el5xen) root (hd0,0) kernel /boot/xen.gz-2.6.18-53.el5 dom0_mem=512M module /boot/vmlinuz-2.6.18-53.el5xen ro root=LABEL=/1 rhgb quiet module /boot/initrd-2.6.18-53.el5xen.img ############ 2. How to rebuild initrd image to include xenblk? Thank you so much! -----Original message----- From: "Nick Couchman" <Nick.Couchman@xxxxxxxxx> Date: Dec.10, 2008, Wed To: math_physics@xxxxxxx Copy: xen-users@xxxxxxxxxxxxxxxxxxx Subject: Re: Re: Re: Re: [Xen-users] xen-3.0-x86_32 not supported by xenkernel 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. ------=_Part_131682_27459552.1228919439475 Content-Type: text/html; charset=GBK Content-Transfer-Encoding: quoted-printable Hi, Nick:<br> Two questions:<br> 1. The initrd image "ini= trd-2.6.18-53.el5xen.img" works well for Dom0 and the following is the cont= ent of file grub.conf. Why doesn't it work for DomU?<br>##########<br>title= Red Hat Enterprise Linux Server AS5.1 (2.6.18-53.el5xen)<br> &n= bsp; root (hd0,0)<br> = kernel /boot/xen.gz-2.6.18-53.el5 dom0_mem=3D512M<br> &nb= sp; module /boot/vmlinuz-2.6.18-53.el5xen ro = root=3DLABEL=3D/1 rhgb quiet<br> = module /boot/initrd-2.6.18-53.el5xen.img<br>############<br><br>2. How to r= ebuild initrd image to include xenblk? <br><br> Thank you so much!<br= ><br><span> =20 </span><br><blockquote style=3D"border-left: 2px solid rgb(160, 198, 22= 9); padding-left: 5px; margin-left: 5px; margin-right: 0pt;">-----Original = message-----<br> <b>From:</b> "Nick Couchman" <Nick.Couchman@xxxxxxxxx><br> <b>Date:</b> Dec.10, 2008, Wed<br> <b>To:</b> math_physics@xxxxxxx<br> <b>Copy:</b> xen-users@xxxxxxxxxxxxxxxxxxx<br> <b>Subject:</b> Re: Re: Re: Re: [Xen-users] xen-3.0-x86_32 not supported b= y =09xenkernel<br><br> <div>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:</div> <div>XENBUS: Device with no driver: device/vbd/2057<br>XENBUS: Device with = no driver: device/vbd/2056<br></div> <div>-Nick<br><br>>>> <<a href="" href="mailto:math_physics@xxxxxxx">mailto:math_physics@xxxxxxx">= math_physics@xxxxxxx</a>> 2008/12/08 20:14 >>><br></div> <p>Yes, I have editted the fstab file in /mnt/loop1/etc. Its content is mod= ified to:</p> <p>/dev/sda9 &nb= sp; / &nbs= p; other parameters<br>/dev/sda8 &= nbsp; swap  = ; other parameters<br><br><span></span><br></p> <blockquote style=3D"border-left: 2px solid rgb(160, 198, 229); padding-lef= t: 5px; margin-left: 5px; margin-right: 0px;">-----Original message-----<br= ><b>From:</b> "Nick Couchman" <<a href="" href="mailto:Nick.Couchman@xxxxxxxxx">mailto:Nick.Couchman@xxxxxxxxx= ">Nick.Couchman@xxxxxxxxx</a>><br><b>Date:</b> Dec. 9, 2008, Tu.<br><b>T= o:</b> <a href="" href="mailto:math_physics@xxxxxxx">mailto:math_physics@xxxxxxx">math_physics@xxxxxxx</a><br>= <b>Copy to:</b> <br><b>Subject:</b> Re: Re: Re: [Xen-users] xen-3.0-x86_32 = not supported by xen kernel<br><br> <div>Did you edit the fstab file in /mnt/loop1/etc with the new root inform= ation?</div> <div> </div> <div>-Nick<br><br>>>> <<a href="" href="mailto:math_physics@xxxxxxx">mailto:math_physics@xxxxxxx">= math_physics@xxxxxxx</a>> 2008/12/07 06:48 >>><br></div> <div>Hi, Nick:<br> Thank you so much for you help! But I still can't = solve my problem:(. I still need help:)<br> I post my DomU configure = file and booting messge here. Would you help me find out the answer?<br>&nb= sp; The kernal and the ramdisk file I use are installed by rpm package in t= he RHEL AS5.1 installation disk. <br> And here is what I do: <b= r> 1. I create a image file /home1/rh9/rh9.img and mount it to /mnt/l= oop1. <br> 2. Copy the whole rh9 system(a physical linux system insta= lled in /dev/sda5) into /mnt/loop1;<br> 3. Copy the directory /lib/mo= dules/2.6.18-53.el5xen of my RHEL AS5.1 (on /dev/sda1) into /mnt/loop1/lib/= modules;<br> 4. Modify /mnt/loop1/etc/fstab, where mount points are f= ixed to match the settings of DomU configuration file.<br>  = ; Thank you so much!<br>############ DomU configuration file:<br>kernel =3D= "/boot/vmlinuz-2.6.18-53.el5xen"<br>ramdisk =3D"/boot/initrd-2.6.18-53.el5= xen.img"<br>memory =3D 1024<br>name =3D "rh9"<br>disk =3D ['file:/home1/rh9= /rh9.img,sda9,w','file:/home1/rh9/rh9_swap.img,sda8,w']<br>root =3D "/dev/s= da9 ro"<br><br>############## Booting message: <br>Started domain rh9<br>Li= nux version 2.6.18-53.el5xen (<a href="" href="mailto:brewbuilder@xxxxxxxxxxxxxxx">mailto:brewbuilder@xxxxxxxxxxxxxxx= d.redhat.com">brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxx</a>) (gcc version 4.1= 2 20070626 (Red Hat 4.1.2-14)) #1 SMP Wed Oct 10 17:06:12 EDT 2007<br>BIOS= -provided physical RAM map:<br> Xen: 0000000000000000 - 00000000408000= 00 (usable)<br>304MB HIGHMEM available.<br>727MB LOWMEM available.<br>NX (E= xecute Disable) protection: active<br>ACPI in unprivileged domain disabled<= br>Built 1 zonelists. Total pages: 264192<br>Kernel command line:&nbs= p; root=3D/dev/sda9 ro<br>Enabling fast FPU save and restore... done.<br>En= abling unmasked SIMD FPU exception support... done.<br>Initializing CPU#0<b= r>CPU 0 irqstacks, hard=3Dc0727000 soft=3Dc0707000<br>PID hash table entrie= s: 4096 (order: 12, 16384 bytes)<br>Xen reported: 1662.499 MHz processor.<b= r>Console: colour dummy device 80x25<br>Dentry cache hash table entries: 13= 1072 (order: 7, 524288 bytes)<br>Inode-cache hash table entries: 65536 (ord= er: 6, 262144 bytes)<br>Software IO TLB disabled<br>vmalloc area: ee000000-= f4ffe000, maxmem 2d7fe000<br>Memory: 1026984k/1056768k available (2049k ker= nel code, 20692k reserved, 844k data, 168k init, 311304k highmem)<br>Checki= ng if this processor honours the WP bit even in supervisor mode... Ok.<br>C= alibrating delay using timer specific routine.. 4158.11 BogoMIPS (lpj=3D831= 6221)<br>Security Framework v1.0.0 initialized<br>SELinux: Initializi= ng.<br>selinux_register_security: Registering secondary module capabi= lity<br>Capability LSM initialized as secondary<br>Mount-cache hash table e= ntries: 512<br>CPU: L1 I cache: 32K, L1 D cache: 32K<br>CPU: L2 cache: 2048= K<br>Checking 'hlt' instruction... OK.<br>SMP alternatives: switching to UP= code<br>Freeing SMP alternatives: 13k freed<br>Brought up 1 CPUs<br>checki= ng if image is initramfs... it is<br>Freeing initrd memory: 5216k freed<br>= Grant table initialized<br>NET: Registered protocol family 16<br>ACPI Excep= tion (utmutex-0262): AE_BAD_PARAMETER, Thread C06D7AA0 could not acquire Mu= tex [2] [20060707]<br>ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thre= ad C06D7AA0 could not acquire Mutex [2] [20060707]<br>Brought up 1 CPUs<br>= PCI: setting up Xen PCI frontend stub<br>ACPI: Interpreter disabled.<br>Lin= ux Plug and Play Support v0.97 (c) Adam Belay<br>pnp: PnP ACPI: disabled<br= >xen_mem: Initialising balloon driver.<br>usbcore: registered new driver us= bfs<br>usbcore: registered new driver hub<br>PCI: System does not support P= CI<br>PCI: System does not support PCI<br>NetLabel: Initializing<br>NetLabe= l: domain hash size =3D 128<br>NetLabel: protocols =3D UNLABELE= D CIPSOv4<br>NetLabel: unlabeled traffic allowed by default<br>NET: R= egistered protocol family 2<br>IP route cache hash table entries: 32768 (or= der: 5, 131072 bytes)<br>TCP established hash table entries: 131072 (order:= 8, 1048576 bytes)<br>TCP bind hash table entries: 65536 (order: 7, 524288 = bytes)<br>TCP: Hash tables configured (established 131072 bind 65536)<br>TC= P reno registered<br>audit: initializing netlink socket (disabled)<br>audit= (1228655943.467:1): initialized<br>highmem bounce pool size: 64 pages<br>VF= S: Disk quotas dquot_6.5.1<br>Dquot-cache hash table entries: 1024 (order 0= , 4096 bytes)<br>Initializing Cryptographic API<br>ksign: Installing public= key data<br>Loading keyring<br>- Added public key FF48355AC6B12D27<br>- Us= er ID: Red Hat, Inc. (Kernel Module GPG key)<br>io scheduler noop registere= d<br>io scheduler anticipatory registered<br>io scheduler deadline register= ed<br>io scheduler cfq registered (default)<br>pci_hotplug: PCI Hot Plug PC= I Core version: 0.5<br>rtc: IRQ 8 is not free.<br>Non-volatile memory drive= r v1.2<br>Linux agpgart interface v0.101 (c) Dave Jones<br>RAMDISK driver i= nitialized: 16 RAM disks of 16384K size 4096 blocksize<br>Xen virtual conso= le successfully installed as xvc0<br>Linux version 2.6.18-53.el5xen (<a hre= f=3D"mailto:brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxx">brewbuilder@hs20-bc2-3= .build.redhat.com</a>) (gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 S= MP Wed Oct 10 17:06:12 EDT 2007<br>BIOS-provided physical RAM map:<br> = ;Xen: 0000000000000000 - 0000000040800000 (usable)<br>304MB HIGHMEM availab= le.<br>727MB LOWMEM available.<br>NX (Execute Disable) protection: active<b= r>ACPI in unprivileged domain disabled<br>Built 1 zonelists. Total pa= ges: 264192<br>Kernel command line: root=3D/dev/sda9 ro<br>Enabling f= ast FPU save and restore... done.<br>Enabling unmasked SIMD FPU exception s= upport... done.<br>Initializing CPU#0<br>CPU 0 irqstacks, hard=3Dc0727000 s= oft=3Dc0707000<br>PID hash table entries: 4096 (order: 12, 16384 bytes)<br>= Xen reported: 1662.499 MHz processor.<br>Console: colour dummy device 80x25= <br>Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)<br>Ino= de-cache hash table entries: 65536 (order: 6, 262144 bytes)<br>Software IO = TLB disabled<br>vmalloc area: ee000000-f4ffe000, maxmem 2d7fe000<br>Memory:= 1026984k/1056768k available (2049k kernel code, 20692k reserved, 844k data= , 168k init, 311304k highmem)<br>Checking if this processor honours the WP = bit even in supervisor mode... Ok.<br>Calibrating delay using timer specifi= c routine.. 4158.11 BogoMIPS (lpj=3D8316221)<br>Security Framework v1.0.0 i= nitialized<br>SELinux: Initializing.<br>selinux_register_security:&nb= sp; Registering secondary module capability<br>Capability LSM initialized a= s secondary<br>Mount-cache hash table entries: 512<br>CPU: L1 I cache: 32K,= L1 D cache: 32K<br>CPU: L2 cache: 2048K<br>Checking 'hlt' instruction... O= K.<br>SMP alternatives: switching to UP code<br>Freeing SMP alternatives: 1= 3k freed<br>Brought up 1 CPUs<br>checking if image is initramfs... it is<br= >Freeing initrd memory: 5216k freed<br>Grant table initialized<br>NET: Regi= stered protocol family 16<br>ACPI Exception (utmutex-0262): AE_BAD_PARAMETE= R, Thread C06D7AA0 could not acquire Mutex [2] [20060707]<br>ACPI Exception= (utmutex-0262): AE_BAD_PARAMETER, Thread C06D7AA0 could not acquire Mutex = [2] [20060707]<br>Brought up 1 CPUs<br>PCI: setting up Xen PCI frontend stu= b<br>ACPI: Interpreter disabled.<br>Linux Plug and Play Support v0.97 (c) A= dam Belay<br>pnp: PnP ACPI: disabled<br>xen_mem: Initialising balloon drive= r.<br>usbcore: registered new driver usbfs<br>usbcore: registered new drive= r hub<br>PCI: System does not support PCI<br>PCI: System does not support P= CI<br>NetLabel: Initializing<br>NetLabel: domain hash size =3D 128<br= >NetLabel: protocols =3D UNLABELED CIPSOv4<br>NetLabel: unlabel= ed traffic allowed by default<br>NET: Registered protocol family 2<br>IP ro= ute cache hash table entries: 32768 (order: 5, 131072 bytes)<br>TCP establi= shed hash table entries: 131072 (order: 8, 1048576 bytes)<br>TCP bind hash = table entries: 65536 (order: 7, 524288 bytes)<br>TCP: Hash tables configure= d (established 131072 bind 65536)<br>TCP reno registered<br>audit: initiali= zing netlink socket (disabled)<br>audit(1228655943.467:1): initialized<br>h= ighmem bounce pool size: 64 pages<br>VFS: Disk quotas dquot_6.5.1<br>Dquot-= cache hash table entries: 1024 (order 0, 4096 bytes)<br>Initializing Crypto= graphic API<br>ksign: Installing public key data<br>Loading keyring<br>- Ad= ded public key FF48355AC6B12D27<br>- User ID: Red Hat, Inc. (Kernel Module = GPG key)<br>io scheduler noop registered<br>io scheduler anticipatory regis= tered<br>io scheduler deadline registered<br>io scheduler cfq registered (d= efault)<br>pci_hotplug: PCI Hot Plug PCI Core version: 0.5<br>rtc: IRQ 8 is= not free.<br>Non-volatile memory driver v1.2<br>Linux agpgart interface v0= .101 (c) Dave Jones<br>RAMDISK driver initialized: 16 RAM disks of 16384K s= ize 4096 blocksize<br>Xen virtual console successfully installed as xvc0<br= >Event-channel device installed.<br>Uniform Multi-Platform E-IDE driver Rev= ision: 7.00alpha2<br>ide: Assuming 50MHz system bus speed for PIO modes; ov= erride with idebus=3Dxx<br>ide-floppy driver 0.99.newide<br>usbcore: regist= ered new driver hiddev<br>usbcore: registered new driver usbhid<br>drivers/= usb/input/hid-core.c: v2.6:USB HID core driver<br>PNP: No PS/2 controller f= ound. Probing ports directly.<br>i8042.c: No controller found.<br>mice: PS/= 2 mouse device common for all mice<br>md: md driver 0.90.3 MAX_MD_DEVS=3D25= 6, MD_SB_DISKS=3D27<br>md: bitmap version 4.39<br>TCP bic registered<br>Ini= tializing IPsec netlink socket<br>NET: Registered protocol family 1<br>NET:= Registered protocol family 17<br>Using IPI No-Shortcut mode<br>XENBUS: Dev= ice with no driver: device/vbd/2057<br>XENBUS: Device with no driver: devic= e/vbd/2056<br>Freeing unused kernel memory: 168k freed<br>Write protecting = the kernel read-only data: 360k<br>Red Hat nash version 5.1.19.6 starting<b= r>Mounting proc filesystem<br>Mounting sysfs filesystem<br>Creating /dev<br= >Creating initial device nodes<br>Setting up hotplug.<br>Creating block dev= ice nodes.<br>Loading uhci-hcd.ko module<br>USB Universal Host Controller I= nterface driver v3.0<br>Loading ohci-hcd.ko module<br>Loading ehci-hcd.ko m= odule<br>Loading jbd.ko module<br>Loading ext3.ko module<br>Loading scsi_mo= d.ko module<br>SCSI subsystem initialized<br>Loading sd_mod.ko module<br>Lo= ading libata.ko module<br>Loading ahci.ko module<br>Loading ata_piix.ko mod= ule<br>Waiting for driver initialization.<br>Scanning and configuring dmrai= d supported devices<br>Creating root device.<br>Mounting root filesystem.<b= r>mount: could not find filesystem '/dev/root'<br>Setting up other filesyst= ems.<br>Setting up new root fs<br>setuproot: moving /dev failed: No such fi= le or directory<br>no fstab.sys, mounting internal defaults<br>setuproot: e= rror mounting /proc: No such file or directory<br>setuproot: error mounting= /sys: No such file or directory<br>Switching to new root and running init.= <br>unmounting old /dev<br>unmounting old /proc<br>unmounting old /sys<br>s= witchroot: mount failed: No such file or directory<br>Kernel panic - not sy= ncing: Attempted to kill init!<br><br>############## xm info gives the foll= owing message<br>release &nb= sp; : 2.6.18-53.el5xen<br>version = &nb= sp; : #1 SMP Wed Oct 10 17:06:12 EDT 2007<br>machine  = ; := i686<br>nr_cpus  = ; : 2<br>nr_nodes &nbs= p; : 1<br>sockets_per= _node : 1<br>cores_per_socket &nbs= p; : 2<br>threads_per_core &= nbsp; : 1<br>cpu_mhz &= nbsp; : 1662<br>hw_caps &nbs= p; = : bfebfbff:20100000:00000000:00000140:0000e39d:00000000:00000001<br>total_m= emory : 2046<br= >free_memory &nb= sp; : 1508<br>xen_major &nbs= p; : 3<br>xen_minor &n= bsp; : 1<br>xen_extra = : .0-53.= el5<br>xen_caps = : xen-3.0-x86_32p <br>xen_pagesize &nbs= p; : 4096<br>platform_params = ; : virt_start=3D0xf5800000<br>xen_chan= geset : unavailable<b= r>cc_compiler &n= bsp; : gcc version 4.1.2 20070626 (Red Hat 4.1.2-14)<br>cc_compile_by = : brewbuilder<br>cc_compil= e_domain : build.redhat.com<br>cc_compile_dat= e : Wed Oct 10 16:30:55 EDT 2007<= br>xend_config_format : 2</div> <div> </div> <div> </div><pre> > -----Original message----- > From: "Nick Couchman" <<a href="" href="mailto:Nick.Couchman@xxxxxxxxx">mailto:Nick.Couchman@xxxxxxxxx">N= ick.Couchman@xxxxxxxxx</a>> > Date: Dec 6, 2008, Sat. > To: <a href="" href="mailto:math_physics@xxxxxxx">mailto:math_physics@xxxxxxx">math_physics@xxxxxxx</a> > Copy to: <a href="" href="mailto:xen-users@xxxxxxxxxxxxxxxxxxx">mailto:xen-users@xxxxxxxxxxxxxxxxxxx">xen-users@li= sts.xensource.com</a> > Subject: Re: Re: [Xen-users] xen-3.0-x86_32 not supported by xen kerne= l >=20 > 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=20 > -----Original Message----- > From: <<a href="" href="mailto:math_physics@xxxxxxx">mailto:math_physics@xxxxxxx">math_physics@xxxxxxx= </a>> > To: Nick Couchman <<a href="" href="mailto:Nick.Couchman@xxxxxxxxx">mailto:Nick.Couchman@xxxxxxxxx">Nick.= Couchman@xxxxxxxxx</a>> >=20 > Sent: 12/5/2008 8:38:21 PM > Subject: Re: Re: [Xen-users] xen-3.0-x86_32 not supported by xen kern= el >=20 > Hi, Nick: >=20 > Should the kernel version of Dom0 be the same with the kernel version = of > DomU?=20 >=20 > 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).=20 >=20 > Then I boot xenU kernel in RHEL AS 5.1, and it gives me the error > messege. >=20 >=20 > Thank you ! >=20 >=20 >=20 >=20 > -----Original message----- > From: "Nick Couchman" <<a href="" href="mailto:Nick.Couchman@xxxxxxxxx">mailto:Nick.Couchman@xxxxxxxxx">N= ick.Couchman@xxxxxxxxx</a>> > Date: Dec 6, 2008, Sat. > To: <a href="" href="mailto:math_physics@xxxxxxx">mailto:math_physics@xxxxxxx">math_physics@xxxxxxx</a> > Copy: <a href="" href="mailto:xen-users@xxxxxxxxxxxxxxxxxxx">mailto:xen-users@xxxxxxxxxxxxxxxxxxx">xen-users@lists= .xensource.com</a> > Subject: Re: [Xen-users] xen-3.0-x86_32 not supported by xen kernel >=20 > Use xm info to figure out which kernels are supported - I suggest tryi= ng > a 32-bit PAE kernel - my SLES10 64-bit Linux builds don't support plai= n > 32-bit kernels, but they do support 32-bit PAE (big/huge) kernels. >=20 > -Nick >=20 >=20 > -----Original Message----- > From: <a href="" href="mailto:math_physics@xxxxxxx">mailto:math_physics@xxxxxxx">math_physics@xxxxxxx</a> > To: Xen MailList <<a href="" href="mailto:xen-users@xxxxxxxxxxxxxxxxxxx">mailto:xen-users@xxxxxxxxxxxxxxxxxxx">= xen-users@xxxxxxxxxxxxxxxxxxx</a>> > Subject: [Xen-users] xen-3.0-x86_32 not supported by xen kernel > Date: Fri, 5 Dec 2008 09:56:45 +0800 (CST) >=20 >=20 > I build a DomU kernel on RHEL AS5.1. But when I boot this Guest DomU > with the kernel, it gives me error message: >=20 > Error: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type > xen-3.0-x86_32 not supported by xen kernel, sorry\n') >=20 >=20 > Can someone give me any suggestion about this problem? > =20 > Thank you! >=20 > Joe >=20 >=20 >=20 >=20 >=20 > 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 th= e > 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, distributi= ng > or otherwise using this message, its contents or attachments in any wa= y. > If you have received this message in error, please notify us immediate= ly > 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. >=20 >=20 > This e-mail may contain confidential and privileged material for the s= ole 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 (SE= AKR) 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 th= is message that does not relate to the business of SEAKR is neither endorse= d by nor attributable to SEAKR. </pre><br><br> <hr> <div> <p></p> <hr> This e-mail may contain confidential and privileged material for the sole u= se 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 recip= ient, please note that this message may contain SEAKR Engineering (SEAKR) P= rivileged/Proprietary Information. In such a case, you are strictly prohibi= ted from downloading, photocopying, distributing or otherwise using this me= ssage, its contents or attachments in any way. If you have received this me= ssage in error, please notify us immediately by replying to this e-mail and= delete the message from your mailbox. Information contained in this messag= e that does not relate to the business of SEAKR is neither endorsed by nor = attributable to SEAKR. </div></blockquote><br><br> <hr> <font style=3D"font-size: 12px; line-height: 15px;">[??] </font><font style= =3D"font-size: 12px; line-height: 15px;"></font><a style=3D"font-size: 12px= ; color: blue; line-height: 15px; text-decoration: underline;" href="" ://popme.163.com/link/003985_1010_7027.html">2008???????</a> <div><p></p><hr> This e-mail may contain confidential and privileged material for the sole u= se of the intended recipient. If this email is not intended for you, or yo= u are not responsible for the delivery of this message to the intended reci= pient, please note that this message may contain SEAKR Engineering (SEAKR) = Privileged/Proprietary Information. In such a case, you are strictly prohi= bited 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 me= ssage that does not relate to the business of SEAKR is neither endorsed by = nor attributable to SEAKR. </div> </blockquote><br><!-- footer --><br><hr/> <a href="" href="http://www.yeah.net">http://www.yeah.net">=CD=F8=D2=D7=C3=E2=B7=D1=D3=CA=A3=AC=C8=AB= =C7=F2=D7=EE=B4=F3=B5=C4=D6=D0=CE=C4=C3=E2=B7=D1=D3=CA=CF=E4</a> ------=_Part_131682_27459552.1228919439475-- 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
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |