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/
Home Products Support Community News


[Xen-bugs] [Bug 1247] Cascade failure when creating multiple domU's requ

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1247] Cascade failure when creating multiple domU's requires dom0 reboot
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Fri, 9 May 2008 07:15:54 -0700
Delivery-date: Fri, 09 May 2008 07:16:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1247-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Comment #3 from jpeacock@xxxxxxxxxxxxxxxxxx  2008-05-09 07:15 -------
(In reply to comment #1)
> or you already know of it - but in my experience, when I get that problem
> trying to 'xm create', it means that my udev daemon (on dom0) has gone AWOL.
> Simply doing an '/etc/init.d/udev start' to bring udev back up always seems to
> fix the problem for me.

Centos does not have a udev service handler; it is run via /etc/rc.sysinit. 
udev was running during the entire following process, so that isn't it.

I just shut down a domain and then tried to restart it, but it hung.   I did
note that xenstore-ls shows that the original backend/tap entry was not cleaned
up properly (so there are now two entries with different indexes pointing at
the same disk image.  In fact there are stale entries under both backend/tap
and backend/vif.  I know from past experience that trying to clear these keys
using xenstore-rm is not effective; only rebooting will allow me to start
another domU.

Based on one suggestion I found on the 'Net, I added a hardlink from
/etc/udev/rules.d/xen-backend.rules to /etc/udev/rules.d/92-xen-backend.rules,
in the hope that the udev cleanup stuff would work, but this apparently isn't
sufficient.  I've turned up the udev logging to DEBUG so we'll see if I can
even see the xen events firing in the syslog.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list