This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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


Yes, its the same script and they call the same thing which is diff on each system.

So my conventional Centos 5 system has virt-manager 0.5.3-10 and libvirt 0.3.3-1, found at the Centos repos.

Where as my Gitco-ized Centos 5 system has virt-manager 0.7.0-1 and libvirt 0.7.0-6. These packages were updated using the Gitco 3.4.1 repo so I know they are in the Xensource domain.

I think Xensource fundamentally changed domU config methodology and I can see the advantages of setting startup behavior within a domU config file because sym links are too easy to blow away.

Its too bad the SXP format is like pig latin and looks more like code.

- 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?


Xen-users mailing list

Xen-users mailing list