From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "Hoyer, David" <David.Hoyer@netapp.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Xen supported LAPIC features
Date: Tue, 8 Oct 2013 21:33:20 +0100 [thread overview]
Message-ID: <52546C10.8020503@citrix.com> (raw)
In-Reply-To: <6777CD901FD53644B082307CD745FB83269D8A2C@SACEXCMBX02-PRD.hq.netapp.com>
On 08/10/13 20:37, Hoyer, David wrote:
> Output from xl dmesg: Note that I have modified Xen to partition off some of my DRAM as RAID CACHE in my E820 tables due to a specific need that we have. This is under early development by us.
>
>
> (XEN) Freed 264kB init memory.
> (XEN) traps.c:2600:d0 Domain attempted WRMSR 00000000000001fc from 0x000000002504005b to 0x0000000025040059.
> (XEN) traps.c:2600:d0 Domain attempted WRMSR 00000000000001fc from 0x000000002504005b to 0x0000000025040059.
> (XEN) traps.c:2600:d0 Domain attempted WRMSR 00000000000001fc from 0x000000002504005b to 0x0000000025040059.
> (XEN) traps.c:2600:d0 Domain attempted WRMSR 00000000000001fc from 0x000000002504005b to 0x0000000025040059.
> (XEN) traps.c:2600:d0 Domain attempted WRMSR 00000000000001fc from 0x000000002504005b to 0x0000000025040059.
> (XEN) traps.c:2600:d0 Domain attempted WRMSR 00000000000001fc from 0x000000002504005b to 0x0000000025040059.
> (XEN) traps.c:2600:d0 Domain attempted WRMSR 00000000000001fc from 0x000000002504005b to 0x0000000025040059.
> (XEN) traps.c:2600:d0 Domain attempted WRMSR 00000000000001fc from 0x000000002504005b to 0x0000000025040059.
> (XEN) domctl.c:1581: E820 RAID CACHE from Domain-1
> (XEN) domctl.c:1597: E820 RAID CACHE Addr=0x0000000300000000 Size=0x0000000080000000
> (XEN) physdev.c:178: dom1: 17:-1 already mapped to 17
> (XEN) physdev.c:178: dom1: 31:-1 already mapped to 21
> (XEN) physdev.c:178: dom1: 39:-1 already mapped to 22
> (XEN) physdev.c:178: dom1: 31:-1 already mapped to 21
> (XEN) physdev.c:178: dom1: 39:-1 already mapped to 22
> (XEN) physdev.c:178: dom1: 31:-1 already mapped to 21
> (XEN) physdev.c:178: dom1: 39:-1 already mapped to 22
> (XEN) vioapic.c:197:d1 vioapic_write_indirect error register 3
Without seeing the changes you have made for the raid cache, I cant tell
whether you have broken something in Xen.
However, this final error message from vioapic.c proves that you have a
buggy IOAPIC driver dom1 (which I presume is your domU); It is
attempting to read IOAPIC register 0x3 which doesn't exist in real
hardware (or certainly not in any spec I have encountered).
The errors from physdev.c are from physdev_map_pirq(). Given the number
of PCI devices you are trying to pass through, you might have run out of
pirqs for domU, although I would expect a rather more direct error
message. Try booting xen with "extra_guest_irqs=64" or so. The default
is for a limit of 32.
~Andrew
next prev parent reply other threads:[~2013-10-08 20:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 19:03 Xen supported LAPIC features Hoyer, David
2013-10-08 19:12 ` Andrew Cooper
2013-10-08 19:37 ` Hoyer, David
2013-10-08 20:33 ` Andrew Cooper [this message]
2013-10-09 14:04 ` Hoyer, David
2013-10-09 14:11 ` Andrew Cooper
2013-10-09 15:55 ` Hoyer, David
2013-10-25 19:45 ` Hoyer, David
2013-10-26 0:19 ` Andrew Cooper
2013-10-26 14:36 ` Hoyer, David
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=52546C10.8020503@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=David.Hoyer@netapp.com \
--cc=xen-devel@lists.xen.org \
/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.