[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [Xen-devel] Upstream QEMU and Xen unstable not working
From: |
Wei Liu |
Subject: |
Re: [Qemu-devel] [Xen-devel] Upstream QEMU and Xen unstable not working |
Date: |
Tue, 19 Jul 2011 10:53:27 +0800 |
On Mon, 2011-07-18 at 11:03 +0100, Ian Campbell wrote:
> On Mon, 2011-07-18 at 10:51 +0100, Wei Liu wrote:
> > Bug resend.
> >
> > This bug was reported about one month ago. QEMU fails to start with
> > Xen unstable. I found that it has not been fix with latest Xen
> > unstable. BIOS is Seabios (with Xen patch).
>
> Please use current mainline seabios.git -- it does not require any
> additional patches.
>
> http://wiki.xensource.com/xenwiki/QEMUUpstream also includes an updated
> SeaBIOS .config which you might try.
>
> Ian.
>
Thanks Ian. This bug is fixed. But I spot new bug with Stefano's
xen-next QEMU.
------mainline seabios with xen-next------
(XEN) HVM7: HVM Loader
(XEN) HVM7: Detected Xen v4.2-unstable
(XEN) HVM7: Xenbus rings @0xfeffc000, event channel 2
(XEN) HVM7: System requested SeaBIOS
(XEN) HVM7: CPU speed is 2993 MHz
(XEN) irq.c:264: Dom7 PCI link 0 changed 0 -> 5
(XEN) HVM7: PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:264: Dom7 PCI link 1 changed 0 -> 10
(XEN) HVM7: PCI-ISA link 1 routed to IRQ10
(XEN) irq.c:264: Dom7 PCI link 2 changed 0 -> 11
(XEN) HVM7: PCI-ISA link 2 routed to IRQ11
(XEN) irq.c:264: Dom7 PCI link 3 changed 0 -> 5
(XEN) HVM7: PCI-ISA link 3 routed to IRQ5
(XEN) HVM7: *** HVMLoader assertion '(devfn != PCI_ISA_DEVFN) ||
((vendor_id == 0x8086) &&
(XEN) HVM7: (device_id == 0x7000))' failed at pci.c:78
(XEN) HVM7: *** HVMLoader crashed.
If I use Anthony's old QEMU tree, qemu-dm-15, HVM boots up. But there
are issues with irq binding.
------mainline seabios with qemu-dm-15------
(XEN) irq.c:344: Dom6 callback via changed to Direct Vector 0xf3
(XEN) irq.c:1979: dom6: pirq 16 or emuirq 8 already mapped
(XEN) irq.c:1979: dom6: pirq 16 or emuirq 12 already mapped
(XEN) irq.c:1979: dom6: pirq 16 or emuirq 1 already mapped
(XEN) irq.c:1979: dom6: pirq 16 or emuirq 6 already mapped
(XEN) irq.c:1979: dom6: pirq 16 or emuirq 4 already mapped
(XEN) irq.c:1979: dom6: pirq 16 or emuirq 7 already mapped
(XEN) event_channel.c:341:d6 EVTCHNOP failure: error -17
(XEN) event_channel.c:341:d6 EVTCHNOP failure: error -17
(XEN) event_channel.c:341:d6 EVTCHNOP failure: error -17
(XEN) event_channel.c:341:d6 EVTCHNOP failure: error -17
Wei.
- [Qemu-devel] Upstream QEMU and Xen unstable not working, Wei Liu, 2011/07/18
- Re: [Qemu-devel] [Xen-devel] Upstream QEMU and Xen unstable not working, Ian Campbell, 2011/07/18
- Re: [Qemu-devel] [Xen-devel] Upstream QEMU and Xen unstable not working,
Wei Liu <=
- Re: [Qemu-devel] [Xen-devel] Upstream QEMU and Xen unstable not working, Ian Campbell, 2011/07/19
- Re: [Qemu-devel] [Xen-devel] Upstream QEMU and Xen unstable not working, Wei Liu, 2011/07/19
- Re: [Qemu-devel] [Xen-devel] Upstream QEMU and Xen unstable not working, Stefano Stabellini, 2011/07/19
- Re: [Qemu-devel] [Xen-devel] Upstream QEMU and Xen unstable not working, Wei Liu, 2011/07/19
- Re: [Qemu-devel] [Xen-devel] Upstream QEMU and Xen unstable not working, Stefano Stabellini, 2011/07/19
Re: [Qemu-devel] Upstream QEMU and Xen unstable not working, Stefano Stabellini, 2011/07/18