All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Kaczmarek <tedkaz@optonline.net>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: Open up bugs  for these?
Date: Thu, 20 Oct 2005 08:21:06 -0400	[thread overview]
Message-ID: <1129810866.30682.87.camel@pluto.linsolutions.com> (raw)

xen_changeset          : Wed Oct 19 06:53:00 2005 +0100
7425:7c951e3eb5ab

Tyan 2446 SMP, FC4 dom0

1st boot, start xend
Unable to read memory/target

start 10 domU's
(XEN) DOM1: (file=mm.c, line=460) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM1: (file=mm.c, line=460) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM2: (file=mm.c, line=460) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM2: (file=mm.c, line=460) Non-privileged attempt to map I/O
space 00000000

2nd boot, start xend
Unable to read memory/target

Start 10 domU's
(XEN) DOM2: (file=mm.c, line=460) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM2: (file=mm.c, line=460) Non-privileged attempt to map I/O
space 00000000

3rb boot, start xend
Unable to read memory/target

Start 10 domU's
(XEN) DOM2: (file=mm.c, line=460) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM2: (file=mm.c, line=460) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM1: (file=mm.c, line=460) Non-privileged attempt to map I/O
space 00000000
(XEN) DOM1: (file=mm.c, line=460) Non-privileged attempt to map I/O
space 00000000




I am only seeing the Non-privileged attempt  error on FC4 guests from
what I can tell with this changeset and from the above three attempts 
the second time only 1 domU error was logged.

Things also melt down after running over 12 hours or so, after a reboot
guests are created no problems, shut down no problems, with no zombies.
After I ran over night I started seeing issues with every domU being
zombied on shutdown, and recreating they all hung at

IP-Config: Unable to guess netmask for address 238.0.0.0



Regards,
Ted

             reply	other threads:[~2005-10-20 12:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-20 12:21 Ted Kaczmarek [this message]
2005-10-20 13:53 ` Open up bugs for these? Ted Kaczmarek

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=1129810866.30682.87.camel@pluto.linsolutions.com \
    --to=tedkaz@optonline.net \
    --cc=xen-devel@lists.xensource.com \
    /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.