>Hi,Dor >I cannot reproduce your issue on my test env. >I can boot 64bit fc6 guest against latest lapic2 branch. >My test machine is a Harwitch+paxville. >The host os is RHEL5, kernel is kvm lapic2 branch with kvm build-in. >How about yours? > >Thanks >Yunfeng
My host is FC6 with latest 2.6.23-rc1 kernel + kvm modules from the lapic2 branch. The cpu is Intel core 2 6400. I found out that I can run some kernels with it (.6.21-rc5) but the one below can't run using apic. > >>-----Original Message----- >>From: Dor Laor [mailto:[EMAIL PROTECTED] >>Sent: 2007年7月31日 3:10 >>To: Zhao, Yunfeng; kvm-devel@lists.sourceforge.net; Dong, Eddie; He, >Qing >>Subject: RE: [kvm-devel] lapic2 branch >> >>>What fedora distribution is in the guest? >>>Could you give more detailed config info? >>>Before I tried to boot 64bit RHEL4U3 against lapic2 branch, I didn't >>>meet the problem. >>> >>>Thanks >>>Yunfeng >> >>It's FC6, kernel version 2.6.20-1.2948.fc6. >>I also tried 2.6.22-rc4 without luck. >>The config file for the kernel is attached (default). >> >>> >>>>-----Original Message----- >>>>From: [EMAIL PROTECTED] >>>>[mailto:[EMAIL PROTECTED] On Behalf Of Dor >Laor >>>>Sent: 2007年7月31日 16:18 >>>>To: kvm-devel@lists.sourceforge.net; Dong, Eddie; He, Qing >>>>Subject: [kvm-devel] lapic2 branch >>>> >>>>Hello to the brave apic pioneers, >>>>While trying to use the lapic2 branch for fedora 64bit guest over >Intel >>>>host 2.6.22 I got the following: >>>>=========== >>>>ide: Assuming 33MHz system bus speed for PIO modes; override with >>>>idebus=xx >>>>PIIX3: IDE controller at PCI slot 0000:00:01.1 >>>>PIIX3: chipset revision 0 >>>>PIIX3: not 100% native mode: will probe irqs later >>>> ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:pio, hdb:pio >>>> ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:pio >>>>hda: QEMU HARDDISK, ATA DISK drive >>>>irq 14: nobody cared (try booting with the "irqpoll" option) >>>> >>>>Call Trace: >>>> <IRQ> [<ffffffff802582ab>] __report_bad_irq+0x30/0x72 >>>> [<ffffffff802584b7>] note_interrupt+0x1ca/0x20f >>>> [<ffffffff80258a71>] handle_edge_irq+0xf9/0x128 >>>> [<ffffffff8020a61c>] call_softirq+0x1c/0x28 >>>> [<ffffffff8020b93d>] do_IRQ+0xf1/0x160 >>>> [<ffffffff80209971>] ret_from_intr+0x0/0xa >>>> <EOI> [<ffffffff8038474f>] ide_outb+0x0/0x9 >>>> [<ffffffff8041112c>] _spin_unlock_irqrestore+0xc/0x31 >>>> [<ffffffff8025807f>] setup_irq+0x163/0x1a1 >>>> [<ffffffff80382b1b>] ide_intr+0x0/0x200 >>>> [<ffffffff8025814e>] request_irq+0x91/0xb5 >>>> [<ffffffff8038638d>] init_irq+0x283/0x50d >>>> [<ffffffff8038675f>] hwif_init+0x148/0x32b >>>> [<ffffffff80386abf>] probe_hwif_init_with_fixup+0x23/0x94 >>>> [<ffffffff80389184>] ide_setup_pci_device+0x80/0xbc >>>> [<ffffffff80592c3c>] ide_scan_pcidev+0x31/0x58 >>>> [<ffffffff80592c85>] ide_scan_pcibus+0x22/0xa5 >>>> [<ffffffff80592582>] ide_init+0x55/0x63 >>>> [<ffffffff805798c1>] kernel_init+0x163/0x2cd >>>> [<ffffffff80411166>] _spin_unlock_irq+0x15/0x30 >>>> [<ffffffff8020a2a8>] child_rip+0xa/0x12 >>>> [<ffffffff8032492c>] acpi_ds_init_one_object+0x0/0x7c >>>> [<ffffffff8057975e>] kernel_init+0x0/0x2cd >>>> [<ffffffff8020a29e>] child_rip+0x0/0x12 >>>> >>>>handlers: >>>>[<ffffffff80382b1b>] (ide_intr+0x0/0x200) >>>>Disabling IRQ #14 >>>>ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 >>>>=========== >>>> >>>>Using nolapic in the guest's kernel worked but seems the apic is >>>broken. >>>> >>>>Also, in Gregory's original code there was qemu cmdline option of >>>>setting the pic/apic position. >>>>It is required for debugging/comparing these source of problems. >>>>Thanks, Dor. >>>> >>>> >>>> >>>> >>>>----- >>>>In simplicity there is elegance. >>>>Dor Laor ;) >>>> >>>> >>>>--------------------------------------------------------------------- >-- >>>-- >>>>This SF.net email is sponsored by: Splunk Inc. >>>>Still grepping through log files to find problems? Stop. >>>>Now Search log events and configuration files using AJAX and a >browser. >>>>Download your FREE copy of Splunk now >> http://get.splunk.com/ >>>>_______________________________________________ >>>>kvm-devel mailing list >>>>kvm-devel@lists.sourceforge.net >>>>https://lists.sourceforge.net/lists/listinfo/kvm-devel ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
