[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Xen-devel] Backend device in use after reboot
- To: xen-devel@xxxxxxxxxxxxxxxxxxx
- From: Wensheng Wang <wenshengwang@xxxxxxxxx>
- Date: Thu, 10 Nov 2005 17:23:01 -0600
- Cc: steved@xxxxxxxxxx
- Delivery-date: Thu, 10 Nov 2005 23:23:10 +0000
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition; b=uQH2rUXFn73++gDEoNeqNki2ePhw91sTI3LrueqCNlLrFilXS8OkiMOsp57otuv7QJXtp9eV9M7i9Npi7az5Rw8GqdDQrugYzSEu9y3hGoAHVYY1IkYuKwAhn+hQ9XT9SPofg/TDAtyGyEowhkJQH8NCGUG5umNUniMupGTRpbc=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
> 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.
I actually saw this too.
The domains that by xendomains (that have config file in /etc/xen/auto
at boot when xendomains started) will be shutdown (gracefully as
appose to poweroff/destroy) during domain-0 shutdown, and will come up
normally when server rebooted.
However if I add a new config file to /etc/xen/auto and xm create a
new domain, this domain will not be shutdown by xendomains during
server shutdown, and when server come back it has trouble start this
domain because it device in use( will shown can not connect to device
in xend.log). Do a xm list showing this domain in r or p state. I
have to xm destroy it before I can xm create it again.
I say it's bug and should be fixed. xendomains should shutdown all
running domainU instead of just ones it started.
Xen-devel mailing list