From: Wei Liu <liuw@liuw.name>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [Xen-devel] Upstream QEMU and Xen unstable not working
Date: Tue, 19 Jul 2011 10:53:27 +0800 [thread overview]
Message-ID: <1311044007.5933.3.camel@limbo> (raw)
In-Reply-To: <1310983409.20648.42.camel@zakaz.uk.xensource.com>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Wei Liu <liuw@liuw.name>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: Upstream QEMU and Xen unstable not working
Date: Tue, 19 Jul 2011 10:53:27 +0800 [thread overview]
Message-ID: <1311044007.5933.3.camel@limbo> (raw)
In-Reply-To: <1310983409.20648.42.camel@zakaz.uk.xensource.com>
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.
next prev parent reply other threads:[~2011-07-19 2:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 9:51 [Qemu-devel] Upstream QEMU and Xen unstable not working Wei Liu
2011-07-18 9:51 ` Wei Liu
2011-07-18 10:03 ` [Qemu-devel] [Xen-devel] " Ian Campbell
2011-07-18 10:03 ` Ian Campbell
2011-07-19 2:53 ` Wei Liu [this message]
2011-07-19 2:53 ` Wei Liu
2011-07-19 7:14 ` [Qemu-devel] [Xen-devel] " Ian Campbell
2011-07-19 7:14 ` Ian Campbell
2011-07-19 8:45 ` [Qemu-devel] [Xen-devel] " Wei Liu
2011-07-19 8:45 ` Wei Liu
2011-07-19 11:09 ` [Qemu-devel] " Stefano Stabellini
2011-07-19 11:09 ` Stefano Stabellini
2011-07-19 11:25 ` [Qemu-devel] [Xen-devel] " Wei Liu
2011-07-19 11:25 ` Wei Liu
2011-07-19 12:04 ` [Qemu-devel] [Xen-devel] " Stefano Stabellini
2011-07-19 12:04 ` Stefano Stabellini
2011-07-18 16:17 ` [Qemu-devel] " Stefano Stabellini
2011-07-18 16:17 ` Stefano Stabellini
2011-07-19 10:44 ` [Qemu-devel] [Xen-devel] " Ian Campbell
2011-07-19 10:44 ` Ian Campbell
2011-07-19 11:11 ` [Qemu-devel] " Stefano Stabellini
2011-07-19 11:11 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1311044007.5933.3.camel@limbo \
--to=liuw@liuw.name \
--cc=Ian.Campbell@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=anthony.perard@citrix.com \
--cc=qemu-devel@nongnu.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.