Sorry to post again, As I see the email I posted is "[Empty message]"
in mailling list.

The message from xen console through serial.

---------------------------------------------------------------------------------------------------
Connected to localhost.
Escape character is '^]'.
(XEN) Xen version 3.2-1 (Debian 3.2.1-2) ([email protected]) (gcc
version 4.3.1 (Debian 4.3.1-2) ) Sat Jun 28 09:32:18 UTC 2008
(XEN) Command line: console=com1
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN) Disc information:
(XEN)  Found 1 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009fc00 (usable)
(XEN)  000000000009fc00 - 00000000000a0000 (reserved)
(XEN)  00000000000e8000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 000000007fff0000 (usable)
(XEN)  000000007fff0000 - 0000000080000000 (ACPI data)
(XEN)  00000000fffbd000 - 0000000100000000 (reserved)
(XEN) System RAM: 2047MB (2096700kB)
(XEN) Xen heap: 14MB (15008kB)
(XEN) Domain heap initialised: DMA width 32 bits
(XEN) Processor #0 6:2 APIC version 20
(XEN) IOAPIC[0]: apic_id 1, version 17, address 0xfec00000, GSI 0-23
(XEN) Enabling APIC mode:  Flat.  Using 1 I/O APICs
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 2100.048 MHz processor.
(XEN) CPU0: AMD QEMU Virtual CPU version 0.9.1 stepping 03
(XEN) Total of 1 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) IO-APIC + timer doesn't work!  Boot with apic=debug and send a
report.  Then try booting with the 'noapic'
option****************************************
(XEN)
(XEN) Reboot in five seconds...
---------------------------------------------------------------------------------------------------

After I see the log, I tried with:
   root (hd0,0)
   kernel /xen-3.2-1-amd64.gz noapic
   modules /vmlinuz-2.6.26-1-xen-amd64 ....
   modules /initrd.img-2.6.26-1-xen-amd64 ...

This configuration as grub config works fine.

When try to pass apic=debug  to "kernel /xen-3.2-1-amd64.gz", There is
no debug message shown.
If you needs other info. Let me know please. :-)

Xinming

On Wed, Dec 17, 2008 at 8:07 PM, Avi Kivity <[email protected]> wrote:
> Yiyi Hu wrote:
>>
>> Host info:
>> h...@hs ~ $ uname -a
>> Linux Hs 2.6.27-gentoo-r6 #1 SMP Mon Dec 15 11:43:12 CST 2008 x86_64
>> AMD Athlon(tm) X2 Dual Core Processor BE-2350 AuthenticAMD GNU/Linux
>>
>> KVM is version 81. Installed from portage.
>>
>> The guest is 64bit debian lenny, Within guest, we install the xen system.
>> The xen-in-kvm won't boot fine after upgraded to kvm-81.
>>
>> After testing, I found:
>> With kvm-81 userspace util and kernel modules bundled with kernel
>> 2.6.27, xen-in-kvm boots fine..
>> If I try to use the kvm module bundled with kvm-81, The xen-in-kvm
>> doesn't boot, with guest screen messed up.
>>
>> For the combination of both kernel modules and userspace utils are from
>> kvm-81.
>> With either -no-kvm-irqchip or -no-kvm-pit option passed, xen-in-kvm boots
>> fine.
>> With both -no-kvm-irqchip and -no-kvm-pit options passed, xen-in-kvm
>> also boots fine.
>> Though, We can see the screen messed up when the kernel boots. But the
>> mess up will be cleared by newer kernel messages.
>>
>> The *problem* script used to start xen-in-kvm.
>>
>> TAPNAME=tap0
>> sudo /usr/bin/tunctl -u hyy -t $TAPNAME
>> sudo /sbin/ifconfig $TAPNAME up
>> sudo /sbin/brctl addif br0 $TAPNAME
>> kvm -k en-us -m 2048 \
>>    -daemonize \
>>    -vnc localhost:5 \
>>    -hda lenny-xen.img \
>>        -net nic,model=rtl8139,macaddr=DE:AD:B3:EF:27:A8 \
>>    -net tap,script=no,ifname=$TAPNAME \
>>    -serial mon:telnet::3333,server,nowait \
>>
>
> What does the Xen serial console show?
>
> --
> error compiling committee.c: too many arguments to function
>
>
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to