|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] Backend device in use after reboot
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
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] Backend device in use after reboot,
Steve Dobbelstein <=
|
|
|
|
|