|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] libxl: xl create segfaults
On Tue, 28 Sep 2010, Christoph Egger wrote:
> Attached patch fixes the hang. The issue is that 'xl create' tries to
> start qemu-dm from a directory it isn't installed in.
>
thanks for the patch, I have applied it.
>
> Now I can start a guest with 'xl create' but xl is still not there.
> I can spot yet another bugs:
>
> 1) I can't see the full boot loader output on the guest's serial console.
> The output starts when the bootloader invokes a timer.
> The output coming before that is sort of skipped.
>
> When I start the guest with 'xm' all is fine.
>
>
> 2) The guest crashes:
>
> Booting "Xen-in-Xen" ends with:
> (XEN) ENABLING IO-APIC IRQs
> (XEN) -> Using new ACK method
> (XEN) ..TIMER: vector=0xF0 apic1=0 pin1=2 apic2=0 pin2=0
> (XEN) ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> (XEN) ...trying to set up timer (IRQ0) through the 8259A ...
> (XEN) ..... (found pin 0) ... failed.
> (XEN) ...trying to set up timer as Virtual Wire IRQ... failed.
> (XEN) ...trying to set up timer as ExtINT IRQ... failed :(.
> (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...
>
> Booting a Linux guest ends with:
> [ 0.004000] Setting APIC routing to physical flat
> [ 0.004000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=0 pin2=0
> [ 0.004000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC
> [ 0.004000] ...trying to set up timer (IRQ0) through the 8259A ...
> [ 0.004000] ..... (found apic 0 pin 0) ...
> [ 0.004000] ....... failed.
> [ 0.004000] ...trying to set up timer as Virtual Wire IRQ...
> [ 0.004000] ..... failed.
> [ 0.004000] ...trying to set up timer as ExtINT IRQ...
> [ 0.004000] ..... failed :(.
> [ 0.004000] Kernel panic - not syncing: IO-APIC + timer doesn't work!
> Boot
> with apic=debug and send a report. Then try booting with the 'noapic'
> option.
> [ 0.004000]
> [ 0.004000] Pid: 1, comm: swapper Not tainted 2.6.34 #2
> [ 0.004000] Call Trace:
> [ 0.004000] [<ffffffff816055ad>] panic+0xa3/0x11e
> [ 0.004000] [<ffffffff81028db4>] ? default_spin_lock_flags+0x9/0xd
> [ 0.004000] [<ffffffff81028db4>] ? default_spin_lock_flags+0x9/0xd
> [ 0.004000] [<ffffffff812303d5>] ? __const_udelay+0x42/0x44
> [ 0.004000] [<ffffffff81df9a14>] setup_IO_APIC+0x9e8/0xa3d
> [ 0.004000] [<ffffffff81028d26>] ? native_patch+0x1b9/0x1cb
> [ 0.004000] [<ffffffff81df52b0>] native_smp_prepare_cpus+0x2fd/0x38c
> [ 0.004000] [<ffffffff81de9606>] kernel_init+0x71/0x1de
> [ 0.004000] [<ffffffff8100ab24>] kernel_thread_helper+0x4/0x10
> [ 0.004000] [<ffffffff81de9595>] ? kernel_init+0x0/0x1de
> [ 0.004000] [<ffffffff8100ab20>] ? kernel_thread_helper+0x0/0x10
>
> The guests boot fine when I start them with 'xm create'.
>
Could you attach the VM config file here?
Does that config file work fine with xl in a normal Xen environment?
My guess is that it is due to a difference in default values between xl
and xend (for example timer_mode).
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- Re: [Xen-devel] libxl: xl create segfaults,
Stefano Stabellini <=
|
|
|
|
|