Nils Goroll
2009-Apr-19 09:28 UTC
CentOS DomU 2.6.18-128.1.6.el5 crashing on boot when xenpv_hvm drivers are loaded / snv_111 Xen 3.1 Dom0
Hi, can anyone provide any pointers as to how to avoid this issue? A CentOS 5.3 domU on snv_111 dom0 is crashing on bott unless I remove /lib/modules/2.6.18-128.1.6.el5/kernel/drivers/xenpv_hvm dom0: haggis:~$ uname -a SunOS haggis 5.11 snv_111 i86pc i386 i86xpv Name: SUNWxvm Summary: Hypervisor Header Files Category: System/Virtualization State: Installed Publisher: dev Version: 3.1 Build Release: 5.11 Branch: 0.111 Packaging Date: Tue Mar 31 09:19:53 2009 Size: 0.00 B FMRI: pkg:/SUNWxvm@3.1,5.11-0.111:20090331T091953Z root@haggis:~# prtdiag -v System Configuration: Hewlett-Packard HP Compaq 8510w BIOS Configuration: Hewlett-Packard 68MVD Ver. F.13 06/24/2008 ==== Processor Sockets =================================== Version Location Tag -------------------------------- -------------------------- Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz U10 domU: [root@localhost ~]# uname -a Linux localhost.localdomain 2.6.18-128.1.6.el5 #1 SMP Wed Apr 1 09:10:25 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux domUs last words: type=1404 audit(1240132330.658:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 type=1403 audit(1240132332.558:3): policy loaded auid=4294967295 ses=4294967295 INIT: version 2.86 booting Welcome to CentOS release 5.3 (Final) Press ''I'' to enter interactive startup. Setting clock (utc): Sun Apr 19 11:12:22 CEST 2009 [ OK ] Starting udev: Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP: [<ffffffff80064b3e>] _spin_lock+0x1/0xa PGD d77e067 PUD c536067 PMD 0 Oops: 0002 [1] SMP last sysfs file: /class/net/lo/type CPU 0 Modules linked in: xen_vbd xen_vnif xen_balloon ide_cd 8139too parport_pc xen_platform_pci cdrom 8139cp parport serio_raw i2c_piix4 mii pcspkr i2c_core dm_raid45 dm_message dm_region_hash dm_log dm_mod dm_mem_cache ata_piix libata sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd Pid: 895, comm: modprobe Not tainted 2.6.18-128.1.6.el5 #1 RIP: 0010:[<ffffffff80064b3e>] [<ffffffff80064b3e>] _spin_lock+0x1/0xa RSP: 0018:ffff81000d507ec0 EFLAGS: 00010292 RAX: 0000000000000001 RBX: ffff81000fa58470 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffffffff8014954e RDI: 0000000000000000 RBP: ffff81000fa58448 R08: 000000001c3a7138 R09: ffffffff8014954e R10: ffffffff803d9520 R11: ffffffff881cfcf4 R12: 0000000000000000 R13: ffffffff881de848 R14: 000000001c3a7138 R15: 000000001c3b08e0 FS: 00002b652c15b6e0(0000) GS:ffffffff803ac000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000000 CR3: 000000000d0be000 CR4: 00000000000006e0 Process modprobe (pid: 895, threadinfo ffff81000d506000, task ffff81000d4cd0c0) Stack: ffffffff8026f625 ffffffff80320730 ffff81000fa58448 ffff81000d05a500 ffffffff801b5267 ffffffff8014954e ffff81000fa58448 ffff81000d05a7c0 ffff81000d05a500 000000001c3b08e0 ffffffff801b540b ffff81000fa58448 Call Trace: [<ffffffff8026f625>] klist_del+0x15/0x2a [<ffffffff801b5267>] device_del+0x22/0x1a9 [<ffffffff8014954e>] kobject_release+0x0/0x9 [<ffffffff801b540b>] device_unregister+0x9/0x12 [<ffffffff881cf051>] :xen_platform_pci:xvd_dev_shutdown+0x55/0x84 [<ffffffff8824a014>] :xen_vbd:xlblk_init+0x14/0x18 [<ffffffff800a3ee4>] sys_init_module+0xaf/0x1e8 [<ffffffff8005d116>] system_call+0x7e/0x83 Code: ff 0f 0f 88 6c 01 00 00 c3 90 81 2f 00 00 00 01 74 05 e8 c3 RIP [<ffffffff80064b3e>] _spin_lock+0x1/0xa RSP <ffff81000d507ec0> CR2: 0000000000000000 <0>Kernel panic - not syncing: Fatal exception
John Levon
2009-Apr-20 14:01 UTC
Re: CentOS DomU 2.6.18-128.1.6.el5 crashing on boot when xenpv_hvm drivers are loaded / snv_111 Xen 3.1 Dom0
On Sun, Apr 19, 2009 at 11:28:37AM +0200, Nils Goroll wrote:> can anyone provide any pointers as to how to avoid this issue? > > A CentOS 5.3 domU on snv_111 dom0 is crashing on bott unless I remove > /lib/modules/2.6.18-128.1.6.el5/kernel/drivers/xenpv_hvmI believe this is: http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6817196 6817196 RHEL 5.3 HVM panics after installation We don''t yet know what the problem is. regards john
Fajar A. Nugraha
2009-Apr-20 14:34 UTC
Re: CentOS DomU 2.6.18-128.1.6.el5 crashing on boot when xenpv_hvm drivers are loaded / snv_111 Xen 3.1 Dom0
On Mon, Apr 20, 2009 at 9:01 PM, John Levon <john.levon@sun.com> wrote:> I believe this is: > > http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6817196 > 6817196 RHEL 5.3 HVM panics after installation > > We don''t yet know what the problem is. >Looking at your virt-install line, I see you use tap:vdisk. Try changing that. I had some discussion with Russ Blaine some time ago about GPLPV on opensolaris where he had problems while my installation worked fine. Turns out to be a problem in tap:vdisk. Using phy:/ to a zvol, or using raw file backend worked fine. Since GPLPV works similarly to Linux PV drivers, I suspect the source of problem is the same, so for the time being using phy:/ with zvol MIGHT work. Regards, Fajar
Mark Johnson
2009-May-07 12:52 UTC
Re: CentOS DomU 2.6.18-128.1.6.el5 crashing on boot when xenpv_hvm drivers are loaded / snv_111 Xen 3.1 Dom0
Nils, Nils Goroll wrote:> Hi, > > can anyone provide any pointers as to how to avoid this issue? > > A CentOS 5.3 domU on snv_111 dom0 is crashing on bott unless I remove > /lib/modules/2.6.18-128.1.6.el5/kernel/drivers/xenpv_hvmDo you know if this works on a Linux dom0? Thanks, MRJ> dom0: > > haggis:~$ uname -a > SunOS haggis 5.11 snv_111 i86pc i386 i86xpv > > Name: SUNWxvm > Summary: Hypervisor Header Files > Category: System/Virtualization > State: Installed > Publisher: dev > Version: 3.1 > Build Release: 5.11 > Branch: 0.111 > Packaging Date: Tue Mar 31 09:19:53 2009 > Size: 0.00 B > FMRI: pkg:/SUNWxvm@3.1,5.11-0.111:20090331T091953Z > > > root@haggis:~# prtdiag -v > System Configuration: Hewlett-Packard HP Compaq 8510w > BIOS Configuration: Hewlett-Packard 68MVD Ver. F.13 06/24/2008 > > ==== Processor Sockets ===================================> > Version Location Tag > -------------------------------- -------------------------- > Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz U10 > > domU: > > > [root@localhost ~]# uname -a > Linux localhost.localdomain 2.6.18-128.1.6.el5 #1 SMP Wed Apr 1 09:10:25 > EDT 2009 x86_64 x86_64 x86_64 GNU/Linux > > > domUs last words: > > type=1404 audit(1240132330.658:2): enforcing=1 old_enforcing=0 > auid=4294967295 ses=4294967295 > type=1403 audit(1240132332.558:3): policy loaded auid=4294967295 > ses=4294967295 > INIT: version 2.86 booting > Welcome to CentOS release 5.3 (Final) > Press ''I'' to enter interactive startup. > Setting clock (utc): Sun Apr 19 11:12:22 CEST 2009 [ OK ] > Starting udev: Unable to handle kernel NULL pointer dereference at > 0000000000000000 RIP: > [<ffffffff80064b3e>] _spin_lock+0x1/0xa > PGD d77e067 PUD c536067 PMD 0 > Oops: 0002 [1] SMP > last sysfs file: /class/net/lo/type > CPU 0 > Modules linked in: xen_vbd xen_vnif xen_balloon ide_cd 8139too > parport_pc xen_platform_pci cdrom 8139cp parport serio_raw i2c_piix4 mii > pcspkr i2c_core dm_raid45 dm_message dm_region_hash dm_log dm_mod > dm_mem_cache ata_piix libata sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd > ehci_hcd > Pid: 895, comm: modprobe Not tainted 2.6.18-128.1.6.el5 #1 > RIP: 0010:[<ffffffff80064b3e>] [<ffffffff80064b3e>] _spin_lock+0x1/0xa > RSP: 0018:ffff81000d507ec0 EFLAGS: 00010292 > RAX: 0000000000000001 RBX: ffff81000fa58470 RCX: 0000000000000000 > RDX: 0000000000000000 RSI: ffffffff8014954e RDI: 0000000000000000 > RBP: ffff81000fa58448 R08: 000000001c3a7138 R09: ffffffff8014954e > R10: ffffffff803d9520 R11: ffffffff881cfcf4 R12: 0000000000000000 > R13: ffffffff881de848 R14: 000000001c3a7138 R15: 000000001c3b08e0 > FS: 00002b652c15b6e0(0000) GS:ffffffff803ac000(0000) > knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b > CR2: 0000000000000000 CR3: 000000000d0be000 CR4: 00000000000006e0 > Process modprobe (pid: 895, threadinfo ffff81000d506000, task > ffff81000d4cd0c0) > Stack: ffffffff8026f625 ffffffff80320730 ffff81000fa58448 ffff81000d05a500 > ffffffff801b5267 ffffffff8014954e ffff81000fa58448 ffff81000d05a7c0 > ffff81000d05a500 000000001c3b08e0 ffffffff801b540b ffff81000fa58448 > Call Trace: > [<ffffffff8026f625>] klist_del+0x15/0x2a > [<ffffffff801b5267>] device_del+0x22/0x1a9 > [<ffffffff8014954e>] kobject_release+0x0/0x9 > [<ffffffff801b540b>] device_unregister+0x9/0x12 > [<ffffffff881cf051>] :xen_platform_pci:xvd_dev_shutdown+0x55/0x84 > [<ffffffff8824a014>] :xen_vbd:xlblk_init+0x14/0x18 > [<ffffffff800a3ee4>] sys_init_module+0xaf/0x1e8 > [<ffffffff8005d116>] system_call+0x7e/0x83 > > > Code: ff 0f 0f 88 6c 01 00 00 c3 90 81 2f 00 00 00 01 74 05 e8 c3 > RIP [<ffffffff80064b3e>] _spin_lock+0x1/0xa > RSP <ffff81000d507ec0> > CR2: 0000000000000000 > <0>Kernel panic - not syncing: Fatal exception > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
Fajar A. Nugraha
2009-May-07 13:10 UTC
Re: CentOS DomU 2.6.18-128.1.6.el5 crashing on boot when xenpv_hvm drivers are loaded / snv_111 Xen 3.1 Dom0
On Thu, May 7, 2009 at 7:52 PM, Mark Johnson <Mark.Johnson@sun.com> wrote:> Nils Goroll wrote: >> A CentOS 5.3 domU on snv_111 dom0 is crashing on bott unless I remove >> /lib/modules/2.6.18-128.1.6.el5/kernel/drivers/xenpv_hvm > > > Do you know if this works on a Linux dom0?Yup. Works perfectly. Tested on RHEL5.3 with Xen 3.3.1 Regards, Fajar
Mark Johnson
2009-May-07 13:58 UTC
Re: CentOS DomU 2.6.18-128.1.6.el5 crashing on boot when xenpv_hvm drivers are loaded / snv_111 Xen 3.1 Dom0
Fajar A. Nugraha wrote:> On Thu, May 7, 2009 at 7:52 PM, Mark Johnson <Mark.Johnson@sun.com> wrote: >> Nils Goroll wrote: >>> A CentOS 5.3 domU on snv_111 dom0 is crashing on bott unless I remove >>> /lib/modules/2.6.18-128.1.6.el5/kernel/drivers/xenpv_hvm >> >> Do you know if this works on a Linux dom0? > > Yup. Works perfectly. > Tested on RHEL5.3 with Xen 3.3.1Just to be clear, a RHEL 5.3 HVM guest with PV drivers works fine on a Linux dom0 (and the PV drivers are actually being used)? Thanks, MRJ> Regards, > > Fajar
Fajar A. Nugraha
2009-May-07 14:25 UTC
Re: CentOS DomU 2.6.18-128.1.6.el5 crashing on boot when xenpv_hvm drivers are loaded / snv_111 Xen 3.1 Dom0
On Thu, May 7, 2009 at 8:58 PM, Mark Johnson <Mark.Johnson@sun.com> wrote:> Fajar A. Nugraha wrote: >>> Nils Goroll wrote: >>>> >>>> A CentOS 5.3 domU on snv_111 dom0 is crashing on bott unless I remove >>>> /lib/modules/2.6.18-128.1.6.el5/kernel/drivers/xenpv_hvm >>> >>> Do you know if this works on a Linux dom0? >> >> Yup. Works perfectly. >> Tested on RHEL5.3 with Xen 3.3.1 > > Just to be clear, a RHEL 5.3 HVM guest with PV drivers works > fine on a Linux dom0 (and the PV drivers are actually being used)?Correct. And I can get it running on opensolaris dom0 as well, with a workaround. It''s quite a long story. I''m using RHEL5.3 x86_64 as dom0 and Centos 5.3 x86_64 HVM domU, with Xen 3.3.1. By default PV drivers are LOADED, but not USED. hda is still handled by ata_piix, and eth0 handled by 8139cp. xen-vbd is loaded, but it does not have any devices (because hda is already handled by ata_piix). xen-net is loaded and got eth1 with the same MAC address as eth0. During boot, you can see that xen-vbd tries to grab hda but cannot (I''ll get to this later). This works fine in Linux, domU can continue to boot. To get domU to actually USE the PV drivers for hda and eth0, some steps are required : http://pastebin.com/fb6fe631 The point here is that on Linux dom0, whatever driver handles hda, domU can continue to work. Now here comes the funny part. In opensolaris dom0, the process of xen-vbd trying to grab hda actually cause KERNEL PANIC. So here''s what I did to get it working on opensolaris dom0: - do a zvol-backed fresh-install of Centos 5.3 on opensolaris dom0. I got kernel-2.6.18-128.el5. It panics on the first reboot. - export the zvol with iscsi, mount on linux, move /lib/modules/2.6.18-128.el5/kernel/drivers/xenpv_hvm/blkfront/xen-vbd.ko out of the way (I simply rename it to xen-vbd.ko.disabled) - startup domU again on opensolaris - edit /etc/modprobe.conf, add "alias scsi_hostadapter2 xen-vbd". This will ensure xen-vbd is included on initrd later. - yum -y install kernel. I''ll get kernel-2.6.18-128.1.6.el5, and during the installation process it also generates initrd-2.6.18-128.1.6.el5.img which contains xen-vbd.ko. - edit /boot/grub/menu.lst to look like this title CentOS (2.6.18-128.1.6.el5) root (hd0,0) kernel /boot/vmlinuz-2.6.18-128.1.6.el5 ro root=LABEL=/ ide0=noprobe initrd /boot/initrd-2.6.18-128.1.6.el5.img the part "ide0=noprobe" tells ata_piix (or is it libata?) to NOT probe hda and hdb. - reboot On the reboot process you can see that xen-vbd now handles hda. Note that hdc (the cdrom) is still handled by ide-cd. As a bonus, xen-net now handles eth0. [root@localhost ~]# ls -lad /sys/block/hd*/device /sys/block/hd*/device/driver/module /sys/class/net/eth*/device/driver/module lrwxrwxrwx 1 root root 0 May 8 03:57 /sys/block/hda/device -> ../../devices/xen/vbd-768 lrwxrwxrwx 1 root root 0 May 8 04:19 /sys/block/hda/device/driver/module -> ../../../../module/xen_vbd lrwxrwxrwx 1 root root 0 May 8 03:57 /sys/block/hdc/device -> ../../devices/pci0000:00/0000:00:01.1/ide1/1.0 lrwxrwxrwx 1 root root 0 May 8 04:19 /sys/block/hdc/device/driver/module -> ../../../../module/ide_cd lrwxrwxrwx 1 root root 0 May 8 04:17 /sys/class/net/eth0/device/driver/module -> ../../../../module/xen_vnif lrwxrwxrwx 1 root root 0 May 8 04:19 /sys/class/net/eth1/device/driver/module -> ../../../../module/8139cp Regards, Fajar
Mark Johnson
2009-May-07 16:03 UTC
Re: CentOS DomU 2.6.18-128.1.6.el5 crashing on boot when xenpv_hvm drivers are loaded / snv_111 Xen 3.1 Dom0
Fajar A. Nugraha wrote:> On Thu, May 7, 2009 at 8:58 PM, Mark Johnson <Mark.Johnson@sun.com> wrote: >> Fajar A. Nugraha wrote: >>>> Nils Goroll wrote: >>>>> A CentOS 5.3 domU on snv_111 dom0 is crashing on bott unless I remove >>>>> /lib/modules/2.6.18-128.1.6.el5/kernel/drivers/xenpv_hvm >>>> Do you know if this works on a Linux dom0? >>> Yup. Works perfectly. >>> Tested on RHEL5.3 with Xen 3.3.1 >> Just to be clear, a RHEL 5.3 HVM guest with PV drivers works >> fine on a Linux dom0 (and the PV drivers are actually being used)? > > Correct. And I can get it running on opensolaris dom0 as well, with a > workaround. It''s quite a long story. > > I''m using RHEL5.3 x86_64 as dom0 and Centos 5.3 x86_64 HVM domU, with > Xen 3.3.1. By default PV drivers are LOADED, but not USED. hda is > still handled by ata_piix, and eth0 handled by 8139cp. xen-vbd is > loaded, but it does not have any devices (because hda is already > handled by ata_piix). xen-net is loaded and got eth1 with the same MAC > address as eth0. > > During boot, you can see that xen-vbd tries to grab hda but cannot > (I''ll get to this later). This works fine in Linux, domU can continue > to boot. To get domU to actually USE the PV drivers for hda and eth0, > some steps are required : http://pastebin.com/fb6fe631 > > The point here is that on Linux dom0, whatever driver handles hda, > domU can continue to work. > > Now here comes the funny part. In opensolaris dom0, the process of > xen-vbd trying to grab hda actually cause KERNEL PANIC.Yeah, I''m trying to debug that panic right now.. As you say below, you can remove the following to avoid the panic.. /lib/modules/2.6.18-128.el5/kernel/drivers/xenpv_hvm/blkfront/> So here''s what I did to get it working on opensolaris dom0: > - do a zvol-backed fresh-install of Centos 5.3 on opensolaris dom0. I > got kernel-2.6.18-128.el5. It panics on the first reboot. > - export the zvol with iscsi, mount on linux, move > /lib/modules/2.6.18-128.el5/kernel/drivers/xenpv_hvm/blkfront/xen-vbd.ko > out of the way (I simply rename it to xen-vbd.ko.disabled) > - startup domU again on opensolaris > - edit /etc/modprobe.conf, add "alias scsi_hostadapter2 xen-vbd". This > will ensure xen-vbd is included on initrd later. > - yum -y install kernel. I''ll get kernel-2.6.18-128.1.6.el5, and > during the installation process it also generates > initrd-2.6.18-128.1.6.el5.img which contains xen-vbd.ko. > - edit /boot/grub/menu.lst to look like this > > title CentOS (2.6.18-128.1.6.el5) > root (hd0,0) > kernel /boot/vmlinuz-2.6.18-128.1.6.el5 ro root=LABEL=/ ide0=noprobe > initrd /boot/initrd-2.6.18-128.1.6.el5.img > > the part "ide0=noprobe" tells ata_piix (or is it libata?) to NOT probe > hda and hdb. > - reboot > > On the reboot process you can see that xen-vbd now handles hda. Note > that hdc (the cdrom) is still handled by ide-cd. As a bonus, xen-net > now handles eth0.Oh, very cool... It''s good to know that the PV driver works, just not when overlapped with the ide controller. Are your guest settings the same on the linux dom0 and solaris dom0? i.e. are acpi and apic settings the same? Thanks, MRJ> [root@localhost ~]# ls -lad /sys/block/hd*/device > /sys/block/hd*/device/driver/module > /sys/class/net/eth*/device/driver/module > lrwxrwxrwx 1 root root 0 May 8 03:57 /sys/block/hda/device -> > ../../devices/xen/vbd-768 > lrwxrwxrwx 1 root root 0 May 8 04:19 > /sys/block/hda/device/driver/module -> ../../../../module/xen_vbd > lrwxrwxrwx 1 root root 0 May 8 03:57 /sys/block/hdc/device -> > ../../devices/pci0000:00/0000:00:01.1/ide1/1.0 > lrwxrwxrwx 1 root root 0 May 8 04:19 > /sys/block/hdc/device/driver/module -> ../../../../module/ide_cd > lrwxrwxrwx 1 root root 0 May 8 04:17 > /sys/class/net/eth0/device/driver/module -> > ../../../../module/xen_vnif > lrwxrwxrwx 1 root root 0 May 8 04:19 > /sys/class/net/eth1/device/driver/module -> ../../../../module/8139cp > > Regards, > > Fajar
Fajar A. Nugraha
2009-May-08 01:38 UTC
Re: CentOS DomU 2.6.18-128.1.6.el5 crashing on boot when xenpv_hvm drivers are loaded / snv_111 Xen 3.1 Dom0
On Thu, May 7, 2009 at 11:03 PM, Mark Johnson <Mark.Johnson@sun.com> wrote:> Oh, very cool... It''s good to know that the PV driver works, just > not when overlapped with the ide controller. > > Are your guest settings the same on the linux dom0 and solaris dom0? > i.e. are acpi and apic settings the same?acpi, apic, and pae=1. They''re required to run 64bit HVM domU (at least that''s what I get testing with Windows2008 and Centos). Regards, Fajar
John Levon
2009-May-08 16:37 UTC
Re: CentOS DomU 2.6.18-128.1.6.el5 crashing on boot when xenpv_hvm drivers are loaded / snv_111 Xen 3.1 Dom0
On Thu, May 07, 2009 at 09:25:27PM +0700, Fajar A. Nugraha wrote:> I''m using RHEL5.3 x86_64 as dom0 and Centos 5.3 x86_64 HVM domU, with > Xen 3.3.1. By default PV drivers are LOADED, but not USED. hda isThis is interesting - I didn''t realise they weren''t used. There''s a much simpler workaround though, simply alter your config to specify ''xvda'' instead of ''hda''. Can you add your comment about RHEL5.3 to https://bugzilla.redhat.com/show_bug.cgi?id=497356 ? regards john
Fajar A. Nugraha
2009-May-08 20:22 UTC
Re: CentOS DomU 2.6.18-128.1.6.el5 crashing on boot when xenpv_hvm drivers are loaded / snv_111 Xen 3.1 Dom0
On Fri, May 8, 2009 at 11:37 PM, John Levon <john.levon@sun.com> wrote:> On Thu, May 07, 2009 at 09:25:27PM +0700, Fajar A. Nugraha wrote: > >> I''m using RHEL5.3 x86_64 as dom0 and Centos 5.3 x86_64 HVM domU, with >> Xen 3.3.1. By default PV drivers are LOADED, but not USED. hda is > > This is interesting - I didn''t realise they weren''t used. There''s a much > simpler workaround though, simply alter your config to specify ''xvda'' > instead of ''hda''.On opensolaris snv_111a dom0 it simply refuses to boot with "Boot from Hard Disk failed: could not read the boot disk". It should work for non-boot disk though.> > Can you add your comment about RHEL5.3 to > https://bugzilla.redhat.com/show_bug.cgi?id=497356 ?Done. I saw your entry there. Looks like you managed to get both hda and xvda activated at once. Weird. Are you using the new development Xen 3.3 (or at least the qemu part) on opensolaris perhaps? Regards, Fajar
John Levon
2009-May-11 16:36 UTC
Re: CentOS DomU 2.6.18-128.1.6.el5 crashing on boot when xenpv_hvm drivers are loaded / snv_111 Xen 3.1 Dom0
On Sat, May 09, 2009 at 03:22:03AM +0700, Fajar A. Nugraha wrote:> >> I''m using RHEL5.3 x86_64 as dom0 and Centos 5.3 x86_64 HVM domU, with > >> Xen 3.3.1. By default PV drivers are LOADED, but not USED. hda is > > > > This is interesting - I didn''t realise they weren''t used. There''s a much > > simpler workaround though, simply alter your config to specify ''xvda'' > > instead of ''hda''. > > On opensolaris snv_111a dom0 it simply refuses to boot with "Boot from > Hard Disk failed: could not read the boot disk". It should work for > non-boot disk though.That''s expected since pygrub doesn''t have the ext3 fixes - that''s coming with 3.3> > Can you add your comment about RHEL5.3 to > > https://bugzilla.redhat.com/show_bug.cgi?id=497356 ? > > I saw your entry there. Looks like you managed to get both hda and > xvda activated at once. Weird. Are you using the new development Xen > 3.3 (or at least the qemu part) on opensolaris perhaps?3.3 indeed. regards john