[one-users] OpenNebula 3.8.1 and VMware ESXI 5.0.0 using shared VMware and SSH transfer drivers

[Qiubo Su (David Su)]

Dear OpenNebula Community,

I have been using virt-manager *(KVM, QEMU and Libvirtd-0.9.8 installed for
managing VMs)* to manage VMs in the physical server installed OpenNebula
platform. But to experiment "OpenNebula 3.8.1 and VMware ESXI 5.0.0 using
shared VMware and SSH transfer drivers", I configured this OpenNebula front
end server to support VMware ESXI 5.0.0 as below:

*Configure Virsh with ESX*

1) root at apt-get install libgnutls-dev libdevmapper-dev libcurl4-gnutls-dev
python-dev libnl-dev libapparmor-dev libxml2

2) Download Libvirt-0.9.10 so that we configure it for ESX support. Untar
it post download and change folder to tarred one.
root at wget http://libvirt.org/sources/libvirt-0.9.10.tar.gz
root at tar xvzf libvirt-0.9.10.tar.gz
root at cd libvirt-0.9.10

3) Configure Libvirt for ESX support with the following commands:
root@ ./configure --with-esx --with-apparmor --sysconfdir=/etc
--libdir=/usr/lib --sbindir=/usr/sbin --datarootdir=/usr/share
--localstatedir=/var --libexecdir=/usr/lib/libvirt
root@ make
root@ make install
root at cp -a examples/apparmor/usr.* /etc/apparmor.d/
root at cp -a examples/apparmor/TEMPLATE /etc/apparmor.d/libvirt/
root at cp -a examples/apparmor/libvirt-qemu /etc/apparmor.d/abstractions/
root@ cat /etc/apparmor.d/usr.sbin.libvirtd
root at cat /etc/apparmor.d/usr.sbin.libvirtd | grep owner
root@/etc/init.d/apparmor restart

After configure Libvirt (libvirtd-0.9.10) for ESX support , can't use
virt-manager anymore (no /var/run/libvirt/libvirt-sock file exists). If
want to use virt-manager again, it seems need to uninstall/clean
libvirtd-0.9.10 and reinstall libvritd-0.9.8 (the one used before install
libvirtd-0.9.10).

 But under /libvirtd-0.9.10 directory, run “make clean/uninstall” and then
run “sudo apt-get install –reinstall qemu-kvm libvirt-bin ubuntu-vm-builder
bridge-utils ruby”, can't get libvirtd-0.9.8 back, can't see
/var/run/libvirt/libvirt-sock file either, even worse, can't find
libvirtd.conf and qemu.conf under /etc/libvirt/ as well. I didn't update
the ~/etc/oned.conf file (after updated it for supporting VMware esxi), is
it necessary to update it?

In this circumstance, how to make the virt-manager available to be used
again as before in this OpenNebula front end server? It will be good to
configure the front end server in a way that support both KVM and VMware
hypervisors at the same time, is this possible?

Thank you very much for your help and Have a great weekend !

Kind regards,
Q.D.S
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20140124/b37f5a4a/attachment.htm>