Hi Patrice, First of all, thanks a lot for this great feedback!! This helps in building support for vSphere 5 in OpenNebula.
I've opened a ticket [1] in order to provide help with the "virsh" (and potentially other tools) selection issue. Regards, -Tino [1] http://dev.opennebula.org/issues/935 -- Constantino Vázquez Blanco, MSc OpenNebula Project Engineer www.OpenNebula.org | @tinova79 On Fri, Oct 21, 2011 at 8:07 AM, Patrice LACHANCE <[email protected]>wrote: > Hello > > For those interested in using OpenNebula to manage vSphere 5, please note > that you need to recompile libvirt after applying this patch ( > http://www.redhat.com/archives/libvir-list/2011-October/msg01027.html). > > If you install your brand new libvirt in /usr/local, you also need to > - 1/ lasy way > => replace /usr/bin/virsh with a link to your newly installed one > - 2/ better > => insert the path of your newly installed libvirt binaries in the > following scripts > ./var/remotes/scripts_common.sh > ./lib/sh/scripts_common.sh > > Since this problem might be recurrent, I suggest to add an option in > opennebula to specify with libvirt/virsh use. > > Patrice > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > >
_______________________________________________ Users mailing list [email protected] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
