From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [BUG?] Non-privileged (1) attempt to map I/O space 000000f0 Date: Thu, 03 May 2007 08:48:02 +0100 Message-ID: <4639AFD2.76E4.0078.0@novell.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-15?Q?Sven=20K=F6hler?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >>> Sven K=F6hler 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