This problem seemed to be a problem with Fedora-8 on IA64 and not a generic Xen
issue.
I installed CentOS-4.6 as a guest HVM and it works fine. I noticed a few things:
1) The disk shows up as /dev/had in CentOS while under Fedora-8 it was showing
up as /dev/sda.
2) In the multi-processor (vcpus > 1) case, there seems to be a difference in
module loading order:
ACPI: Core revision 20070126
Boot processor id 0x0/0x0
Brought up 1 CPUs
Total of 1 processors activated (3137.53 BogoMIPS).
[...]
Creating initial device nodes
Setting up hotplug.
[...]
Loading mbcache.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 ata_piix.ko module
scsi0 : ata_piix <--- Shows up after ata_piix.ko is loaded
scsi1 : ata_piix
ata1: PATA max MWDMA2 cmd 0x00000001000001f0 ctl 0x00000001000003f6 bmdma
0x000000010000c000 irq 34
ata2: PATA max MWDMA2 cmd 0x0000000100000170 ctl 0x0000000100000376 bmdma
0x000000010000c008 irq 33
Fixed BSP b0 value from CPU 1
CPU 1: synchronized ITC with CPU 0 (last diff 3 cycles, maxerr 320 cycles)
CPU 2: synchronized ITC with CPU 0 (last diff -2 cycles, maxerr 320 cycles)
CPU 3: synchronized ITC with CPU 0 (last diff -2 cycles, maxerr 320 cycles)
Brought up 4 CPUs
Total of 4 processors activated (12550.14 BogoMIPS).
[...]
Creating initial device nodes
Setting up hotplug.
[...]
SCSI subsystem initialized
Loading ext3.ko module
Loading scsi_mod.ko module
scsi0 : ata_piix <--- Happens before "Loading ata_pixx.ko"
Loading sd_mod.ko module
Loading libata.ko module
Loading ata_piix.ko module
scsi1 : ata_piix
I'm wondering if Fedora-8-IA64 is somehow parallelizing the boot/module-load
process and as a result the multi-processor case is not booting correctly.
Best regards,
---Kayvan
-----Original Message-----
From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Kayvan Sylvan
Sent: Tuesday, January 29, 2008 5:01 PM
To: Akio Takebe; Alex Williamson
Cc: xen-ia64-devel
Subject: RE: [Xen-ia64-devel] RE: Has anyone seen this before? vcpus > 1panics
DomU kernel
> Hi, Kayvan
> I suspect Linux CD-ROM driver cannot use DVD.iso image.
> So you should not specify it as cdrom.
Hi Akio,
That is an interesting idea.
I installed the HVM guest using the DVD.iso image as a CD and it worked fine,
so I don't think that is the problem.
To verify, I just removed the DVD.iso reference, set vcpus=4 and rebooted. The
same thing as before:
Loading sd_mod.ko module
Loading libata.ko module
Loading ata_piix.ko module
scsi1 : ata_piix
ata1: PATA max MWDMA2 cmd 0x00000001000001f0 ctl 0x00000001000003f6 bmdma
0x000000010000c000 irq 34
ata2: PATA max MWDMA2 cmd 0x0000000100000170 ctl 0x0000000100000376 bmdma
0x000000010000c008 irq 33
ata1.00: ATA-7: QEMU HARDDISK, 0.9.0, max UDMA/100
ata1.00: 20971520 sectors, multi 16: LBA48
ata1.00: configured for MWDMA2
scsi 0:0:0:0: Direct-Access ATA QEMU HARDDISK 0.9. PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 20971520 512-byte hardware sectors (10737 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sd 0:0:0:0: [sda] 20971520 512-byte hardware sectors (10737 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
Kernel panic - not syncing: Attempted to kill init!
Waiting for driv
When I set vcpus=1, the guest OS boots fine. :-(
Best regards,
---Kayvan
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
Home