Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-bugs

[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: Thu, 8 May 2008 14:02:37 -0700
Delivery-date: Thu, 08 May 2008 14:02:58 -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
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1247





------- Comment #1 from jeff@xxxxxxxxxxxxxxx  2008-05-08 14:02 -------
(In reply to comment #0)
> For the last 10 days or so, I have been having problems where I get the
> dreaded:
> 
>   Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
> 
> and once that happens, I must reboot the machine before I can start a domU
> again.

I'm not intimately familiar with the other bugs currently filed for the
'hotplug scripts not working' issue, so please excuse me if this doesn't apply
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.

I suspect the same thing afflicts you given your mention of rebooting fixing
the problem. While this is obviously not a great state of affairs, running the
udev init script to restart udev is clearly a better solution than a physical
restart.

I have not noticed any issues with currently-running domUs when this issue
comes up, FWIW: they don't hiccup or have any other problems. The problem seems
isolated to the creation of new domU processes only.

Hope this helps somewhat...


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs