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@lists.xensource.com http://lists.xensource.com/xen-users
Hi John, On Tue, Jun 10, 2008 at 1:35 PM, John Hannfield <hal9020@gmail.com> 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@lists.xensource.com http://lists.xensource.com/xen-users
Hi Todd, Thanks for the ideas.> did you try xm destroy <guest VM that crashed> ?Yes, I did that, but wasn''t sure it was destroyed, as ''xm list'' - it just hangs. But I assumed the domain was destroyed.> 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.Do you know how to remove the entry from xenstore? I had a look in /var/run/xenstored/ but couldn''t really make sense of anything there. Is there a guide to xenstore somewhere, or any other tips on learning about it? Cheers, -- John _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tue, Jun 10, 2008 at 5:58 PM, John Hannfield <hal9020@gmail.com> wrote:> Hi Todd, > > Thanks for the ideas. > > > did you try xm destroy <guest VM that crashed> ? > > Yes, I did that, but wasn''t sure it was destroyed, as ''xm list'' - it > just hangs. > But I assumed the domain was destroyed. > > > 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. > > Do you know how to remove the entry from xenstore? > I had a look in /var/run/xenstored/ but couldn''t really make > sense of anything there. Is there a guide to xenstore somewhere, > or any other tips on learning about it? >xenstore uses a backend tree database (tdb). There are xenstore-* commands used to access it (see below). This is a pretty good reference: http://wiki.xensource.com/xenwiki/XenStoreReference here are the commands that are available: xenstore-chmod xenstore-exists xenstore-read xenstore-control xenstore-list xenstore-rm xenstored xenstore-ls xenstore-write I suspect that it should be something like find the domain ID and getting rid of the vbd entry. xm list hanging is not a good sign though. Let us know if you run into problems in your efforts. Cheers, Todd _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Tuesday June 10 2008 01:35:45 pm John Hannfield wrote:> 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.As root, get the output of ''lsof|grep www.abc.com'', and kill any process that still has your root device open. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users