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

["Todd Deshane" <deshantm@xxxxxxxxx>]

Hi John,

On Tue, Jun 10, 2008 at 1:35 PM, John Hannfield <hal9020@xxxxxxxxx> wrote:

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?

did you try xm destroy <guest VM that crashed> ?
 
If that doesn't work you may be able to use xm block-detach
or if that doesn't work, you could try to remove the entry from xenstore manually.

If that doesn't work the last resort might be to reboot. (If that is not an option, then
there may be more tricks, things to delete or detach).

Hope that helps,
Cheers,
Todd

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