From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ted Kaczmarek Subject: Re: changset 7048:c89485e939cc, Non-privileged attempt to map I/O, bridge odditiies, debug console Date: Sat, 24 Sep 2005 13:12:00 -0400 Message-ID: <1127581920.3612.139.camel@pluto.linsolutions.com> References: <1127572957.3612.135.camel@pluto.linsolutions.com> <83a327a5047249aa731b363f810ef0e6@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7BIT Return-path: In-reply-to: <83a327a5047249aa731b363f810ef0e6@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Sat, 2005-09-24 at 17:25 +0100, Keir Fraser wrote: > On 24 Sep 2005, at 15:42, Ted Kaczmarek wrote: > > > With changset 7048:c89485e939cc I have two FC4 domU,s that generates > > these messages on startup. > > > > (XEN) DOM11: (file=mm.c, line=461) Non-privileged attempt to map I/O > > space 00000000 > > (XEN) DOM11: (file=mm.c, line=461) Non-privileged attempt to map I/O > > space 00000000 Just with my latest spin of this changeset. > > How recently has this started happening? A few of these printing out is > probably harmless. > > > My xen console also vanished, when I first connected I hit "h" and > > output was humming along, then it just stopped. Still not sure if I am > > using it properly. Is their some disable key stroke? > > The xen debug key 'h'? Input gets automatically redirected to domain0 > when it boots. You can switch back to Xen by hitting CTRL-a three > times. > > > Also saw the OUCH timer gripe, but only a few entries. > > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=257 > > I don;t know much about the scheduler. It sounds like it gets easily > upset. Someone probably needs to spend some time debugging it and > getting to understand it. > > > Question? > > Is it better for me to reboot and startup clean after I see this types > > of issues, or keep things running and test more. > > You are probably okay ignoring most of these. When domain don't die > properly I sometimes find that new domains don;t work properly either > but ymmv. Great good to know. Also, domU's are starting up much faster for me :-). > > -- Keir Regards, Ted