[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] domU's not coming back from reboots

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Brian Hays" <brian.hays@xxxxxxxxx>
  • Date: Thu, 23 Feb 2006 22:37:36 -0500
  • Delivery-date: Fri, 24 Feb 2006 03:38:07 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=bInziDzJ7Dw4xqAn1QgXk7bvI+piUmrTbhnS6Aa2HnDT3kOk924tBDE4L2i83FWr3whykieB43rI5lHS8tCVHGhbt8KDFg7NPC05UlflgC2leCCHm68wwGrZYyPN0ucIi5Oe/uY96yZp8lU0mhzNPbtc89Gf+lsQD0ZyPGMDlW0=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


It appears that after an upgrade to 3.0.1, reboots from within a domU result in the domU shutting down but not coming back up.

/var/log/xen-hotplug.log reports "xenstore-list: could not list path backend/vbd/40"

Attempts to manually start the domU up again via "xm create" fail until first running "xenstore-rm backend/vbd/40"

This has happened on several occasions within different domU's on different machines. Is there a known workaround... Is this already fixed in unstable?

Thank you,
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.