WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Backend device in use after reboot

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Backend device in use after reboot
From: Steve Dobbelstein <steved@xxxxxxxxxx>
Date: Thu, 10 Nov 2005 13:35:04 -0600
Delivery-date: Thu, 10 Nov 2005 19:35:26 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Our test setup uses LVM logical volumes as backend devices for the domUs.
For example, the configuration file for the first domU says:
disk = ['phy:/dev/virt-blkdev-backend/dom1,sda1,w',
'phy:/dev/virt-blkdev-backend/usr,sda2,r']

The configuration files for the domUs also have:
on_poweroff = 'destroy'
on_reboot   = 'destroy'
on_crash    = 'destroy'

The testing framework typically destroys and recreates the LVM volumes for
the domUs for a run of tests.

However, when the system hangs (domU down, dom0 down, network down, can
reboot from Xen console, but that's another problem) and the system is
rebooted, I cannot destroy the LVM volumes because they are in use.  No
domUs are started after the reboot.

What is holding onto the LVM volumes?  Is there a way to get them released?
Am I missing something?  Or is this a bug?

Thanks for any help.

Steve D.


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