[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] config.sxp pain - auto start?



Hi,

I just noticed something diff between the 2 systems, the plain Centos 5 system that is completely up to date and the Centos 5 system having the Gitco repo.

The virt-install on the Centos system is 566 lines and the Gitco one is 937.

Since they both have RHEL as the author I assume they both came from Redhat but why is the Gitco system diff?

I did an update on my plain Centos system and it didn't suck down a newer version of the script.

Any ideas?  Am I looking at this completely wrong?

- Brian

On Oct 8, 2009, at 3:26 PM, Fajar A. Nugraha wrote:

On Fri, Oct 9, 2009 at 3:29 AM, Brian Krusic <brian@xxxxxxxxxx> wrote:
One big problem I see is consistency.
Wether GUI or CLI, in 3.4.1, SXP is the default.

Last time I check virt-install is not part of Xen. It's a separate
project by Redhat.

And I personally have to assume others will need to manage this Xen
infrastructure I've sold management on and have created.

I do it the old-fashioned way : create old-style config files and
symlinks manually :D

So I must conform to the way of SXP unfortunately.
 It does make things more
complicated at first glance.
Just my thoughts.

Ask Redhat to have "on_xend_start/stop" parameter configurable when
creating new guests?
Also ask Xen developers to have a new "xm" command that can change the
value of "on_xend_start/stop" without having to delete - edit -
recreate domU?

--
Fajar

_______________________________________________
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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.