WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [BUG?] Non-privileged (1) attempt to map I/O space 00000

To: "Sven Köhler" <skoehler@xxxxxx>
Subject: Re: [Xen-devel] [BUG?] Non-privileged (1) attempt to map I/O space 000000f0
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Thu, 03 May 2007 08:48:02 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 03 May 2007 00:46:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <f1aq4k$u7e$1@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <f1aq4k$u7e$1@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Sven Köhler <skoehler@xxxxxx> 02.05.07 21:51 >>>
>i'm getting this error after i upgraded to xen 3.0.4-1.
>It seems, that it doesn't harm anything.
>
>Anyway: for any domU i start, i get this in "xm dmesg":
>(XEN) mm.c:566:d1 Non-privileged (1) attempt to map I/O space
000000f0
>(XEN) mm.c:566:d2 Non-privileged (2) attempt to map I/O space
000000f0
>(XEN) mm.c:566:d3 Non-privileged (3) attempt to map I/O space
000000f0
>(XEN) mm.c:566:d4 Non-privileged (4) attempt to map I/O space
000000f0
>(XEN) mm.c:566:d5 Non-privileged (5) attempt to map I/O space
000000f0

This is generally being caused by tools like hwinfo that try to map
BIOS space
(which is meaningless in DomU-s; only Dom0 is allowed to see the real
BIOS
space). Having looked at it quite a while back I thinks there's
nothing
reasonable we can do at the Xen or kernel side, it's the offending tool
that
needs fixing if this message is considered a problem.

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>