Re: [Xen-devel] Backend device in use after reboot

[Adam Heath <doogie@xxxxxxxxxxxxx>]

On Fri, 11 Nov 2005, Mark Williamson wrote:

> > > 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.
>
> OK, I jumped into this thread a bit late but here goes.
>
> 1) I'm not sure why the device should still be in use after reboot
> 2) xendomains used to allow all running domains to be shutdown, not just the
> ones in /etc/xen/auto - this might have become configurable with the recent
> enhancements, did you check for this?
>
> > The better fix is to have xm learn about /etc/xen/auto, and get rid of the
> > xendomains init script.
> >
> > xm create -a
>
> I'm not clear what the advantage in having the looping code within xm, rather
> than within the init script?

xm create foodomain

This would create the state files saying foodomain is active.

xm shutdown -a

This would handle all domains started with xm create -a, and started
individually.

It also would mean one command to do everything, instead of several.


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