On Mon, 2009-11-02 at 16:44 +0100, Alain RICHARD wrote:
a) use_virsh = 1 per default
b) that if your resource have a path attribute, vm.sh automatically
revert to use_virsh=0, even if you hard code use_virsh=1 !
c) there is no option to indicate the xml file that virsh use to
create the vm. It always tries "virsh create name" where name is the
The point a) is a little bit silly because if you have a RHEL 5.3
cluster that is using xm configuration files, your vm will no longer
launch after upgrade because it tries to do a "virsh create name"
instead of "xm create name". It would have been probably cleaner to
have "use_virsh = 0" per default to keep compatibility.
Libvirt's Xen mode loads config files from /etc/xen. When you run
'virsh start foo' it will look for the config in /etc/xen which defines
the virtual machine named 'foo'.
So, effectively, either what you said above works for me or I don't
understand your problem. Both 'xm' and 'virsh' modes work on Xen
domains in 5.4 (assuming you don't have a path attribute set): http://pastebin.ca/1653460
Did you mix 5.3 libvirt with 5.4 rgmanager or something? If so, I'd
simply keep using the vm.sh from rgmanager in 5.3.