changset 7048:c89485e939cc, Non-privileged attempt to map I/O, bridge odditiies, debug console

changset 7048:c89485e939cc, Non-privileged attempt to map I/O, bridge odditiies, debug console

[Ted Kaczmarek]

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

Happens every time I start an FC4 domU, not seeing this with Centos 4.1,
debian 3.1 or gentoo-2005 domu's.

Also seeing some strange behavior with the bridge setups as well.
Had one instance where network layer was toast, and llc was half
working. Also the bridge interfaces are not being cleaned up, if a domU
fails (sporadically seeing this) and I issue an xm destroy the bridge
interface for that domU is left behind.

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?


Also saw the OUCH timer gripe, but only a few entries.
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=257


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.

Regards,
Ted

Re: changset 7048:c89485e939cc, Non-privileged attempt to map I/O, bridge odditiies, debug console

[Keir Fraser]

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

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.

  -- Keir

Re: changset 7048:c89485e939cc, Non-privileged attempt to map I/O, bridge odditiies, debug console

[Ted Kaczmarek]

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