[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Backend device in use after reboot
- To: Mark Williamson <mark.williamson@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
- From: Wensheng Wang <wenshengwang@xxxxxxxxx>
- Date: Fri, 11 Nov 2005 11:58:13 -0600
- Delivery-date: Fri, 11 Nov 2005 17:58:20 +0000
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Qn1Ivwv0tFUt+0SLGVAhxVuUFzg8QldPEZgC3ID93eOX5pxeayeZ1MlP7p8Uo2kVPD8iua6sGEMBPPMNq7IPpNaqG0WvULHWr0eS82sE9PMpCPFd2+JKrQPIUJ5MD6aQ3Z4817KEWg1OeeygzNvNrST7V6rjUUTr4bA6oYOirCk=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
I just looked at my /etc/init.d/xendomains, in stop(), it test a env
variable called XENDOMAINS_AUTO_ONLY, If it true, it shutdown only
those in /etc/xen/auto
And in my /etc/sysconfig/xendomains, this variable is indeed set false.
Then it try to "xm save" followed by "xm shutdown" if "xm save" failed.
In my /etc/sysocnfig/xendomains, XENDOMAINS_SAVE is set to
I don't have this directory. So it should proceed to shutting-down.
It all look good to me. I don't understand why I had this problem.
I will try reboot again and see what happens. I only saw it once.
On 11/11/05, Mark Williamson <mark.williamson@xxxxxxxxxxxx> 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?
Xen-devel mailing list