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

[Xen-users] Block devices stuck in dead domain?


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "John Hannfield" <hal9020@xxxxxxxxx>
  • Date: Tue, 10 Jun 2008 18:35:45 +0100
  • Delivery-date: Tue, 10 Jun 2008 10:36:17 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=H8vIHPArjaAaT4X2Y62t2wrjPKBfXhkT4w+OIMI/K4bcUXUwisO5koI+gKwunjHHx3 RmB1WKJZuVYcimtzX5Q4zf9oNW/uL2oG3FxDuLLPaymPIdYo41ciijL7QEmfLMq53YM+ VLhgDlfwed5jdhFJpQgg2JQIkhkoal3OOJ7wA=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello,

I'm running xen 3.1.0 on a AMD Opteron system.
Sometimes 'xm list' hangs forever, even though 'xm info' works straight away.
Usually this happens after a guest domain dies.

The only thing I can do, to get xm responsive again, is to stop and start
xend.

/etc/init.d/xend stop
/etc/init.d/xend start

This works fine, and the existing running VM's are OK.
But for the one that died, I can't restart it because xen sees the
file systems as still in use. I get the message.

Error: Device 769 (vbd) could not be connected.
Device /dev/vg1/www.abc.com_root is mounted in a guest domain,
and so cannot be mounted now.

Even though the guest domain is no longer in the 'xm list' output.
Any idea how to tell xen that it can use this LVM volume?

Thanks,
-- 

John

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


 


Rackspace

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