| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
RE: [Xen-devel] Backend device in use after reboot
On Thu, 10 Nov 2005, Wensheng Wang wrote:
> > 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.
The better fix is to have xm learn about /etc/xen/auto, and get rid of the
xendomains init script.
xm create -a
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home