I always use /etc/xen/auto, so that is the equivalent of an xm
create or xm restore at bootup (depending on whether or not there was a save
at shutdown). At shutdown, it is like an xm save or xm shutdown depending
on the config elsewhere. Mine shuts down because of how I have xendomains
configured (excerpt from /etc/sysconfig/xendomains in my case):
## Type: string
## Default: /var/lib/xen/save
#
# Directory to save running domains to when the system (dom0) is
# shut down. Will also be used to restore domains from if #
XENDOMAINS_RESTORE
# is set (see below). Leave empty to disable domain saving on shutdown
# (e.g. because you rather shut domains down).
# If domain saving does succeed, SHUTDOWN will not be executed.
#
XENDOMAINS_SAVE=""
There are several other settings that control how xendomains behaves in this
file, and they all have good explanations like the one above. I don't know
where this file would be in a source installation.
It may be that xendomains will always save all domains on xendomains stop
and restore all domains on xendomains start (or at least restore any that it
saved), either way, this behavior shouldn't change between reboots, but it
will only create them if they are in /etc/xen/auto, " Starting auto Xen
domains: news(skip)" is where it would have created domU news if said domU
hadn't already been restored. Hope this helps clear it up and get it set
how you want it,
Dustin
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Kai Schaetzl
Sent: Tuesday, August 05, 2008 07:32
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] dom0 and domU shutdown behavior
Dustin Henning wrote on Mon, 4 Aug 2008 16:01:25 -0400:
> I run F8 with the F8 Xen, and when I shut down, a python
> error/incompatibility (I think) causes the xendomains service to stop
> without shutting down the domUs (when xendomains is stopped on a properly
> functioning system, it will shut them down or kill them one at a time
based
> on the config).
I didn't think about xendomains. I just restarted it on a machine with one
guest, result:
service xendomains restart
Shutting down Xen domains: news(save)../etc/init.d/xendomains: line 280:
2455 Terminated watchdog_xm save
/etc/init.d/xendomains: line 318: 2455 Terminated watchdog_xm
save
Restoring Xen domains: news.
Starting auto Xen domains: news(skip)
- domU didn't go down, that's actually not so bad.
service xendomains stop
Shutting down Xen domains: news(save)../etc/init.d/xendomains: line 280:
2927 Terminated watchdog_xm save
/etc/init.d/xendomains: line 318: 2927 Terminated watchdog_xm
save
Xendomains seems to save and restore the domain. It does that no matter of
the domain in in /etc/xen/auto or not. At least if there is no reboot of the
machine in-between. I'm not so sure about what happens if the machine gets
rebooted. In the past (without a /etc/xen/auto link) sometimes I found it
got
started, sometimes not.
I would rather prefer that it shuts down completely and gracefully, but that
it at least saves the VM is better than nothing.
This is without the domain being "xen managed". Is there any difference if
it
is "xen managed" (you start with "xm start" instead of "create")?
Kai
--
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home