| I just found that if you look at the sxp file, specifically;
on_xend_start ignore on_xend_stop ignore
change ignore to start and stop accordingly.
I found some tidits on converting the simpler domU config to the newer SXP style... I think.
May be I am reading this wrong but my Running Xen book states on page 183, paragraph 1, that most users will not need this type of functionality.
What are your thoughts?
On Oct 8, 2009, at 11:50 AM, Grant McWilliams wrote:
On Thu, Oct 8, 2009 at 11:37 AM, Brian Krusic <brian@xxxxxxxxxx> wrote: Hi all,
In the older format using Xen 3.0.3 (domains created via xm), I simply created a sym link from /etc/xen/domU config file to /etc/xen/auto.
I am now using virt-install (Xen 3.4.1) which creates the domU config in /var/lib/xend/domains/UUID_#_of_domU/config.sxp.
So I sym link this to a file in /etc/xen/auto/hostname_of_domU and noticed that no auto starting of the domU happens.
I've looked in both my Xen books and only find that /etc/xen/auto is the place to auto start domUs.
Any ideas on how to auto start gracefully while not writing a script in /etc/rc3.d every time a new domU comes on line?
And why are xm create and virt-install so diff in how they approach domU configs? This is confusing.
- Brian
I just updated to 3.4.1 and autostart stopped working. I copied the xen domU file into /etc/xen/auto and it started working again. Xendomains kept complaining that my domU file was not valid. Start there.
Grant McWilliams
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
