This bug was fixed in the package libvirt - 1.2.8-0ubuntu20
---
libvirt (1.2.8-0ubuntu20) vivid; urgency=medium
* debian/rules:
- use --with-esx (LP: #565771)
- specify restart-after-upgrade (LP: #1215617)
* debian/control: add libcurl4-gnutls-dev for esx support
--
It seems this only requires curl?
If so then this should be fine.
status: confirmed
** Changed in: libvirt (Ubuntu)
Importance: Low = Medium
** Changed in: libvirt (Ubuntu)
Status: Won't Fix = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Please see
http://lists.alioth.debian.org/pipermail/pkg-libvirt-discuss/2010-January/13.html
for an answer from the Debian package maintainer. It sounds like if you
volunteer to
maintain the ESX support, he may be open to enabling it by default.
--
Please stop disabling the VMware ESX
won't fix per hallyn
** Changed in: libvirt (Ubuntu)
Status: New = Won't Fix
--
Please stop disabling the VMware ESX driver
https://bugs.launchpad.net/bugs/565771
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in ubuntu.
Which version are you using?
Thanks
chuck
** Changed in: libvirt (Ubuntu)
Importance: Undecided = Low
** Changed in: libvirt (Ubuntu)
Status: New = Incomplete
--
Please stop disabling the VMware ESX driver
https://bugs.launchpad.net/bugs/565771
You received this bug notification
I don't know which software you're asking about... I'm using Ubuntu
Lucid with libvirt 0.7.5 to connect to an ESX 4 host.
** Changed in: libvirt (Ubuntu)
Status: Incomplete = New
--
Please stop disabling the VMware ESX driver
https://bugs.launchpad.net/bugs/565771
You received this bug
** Description changed:
libvirt ships with a limited but functional ESX driver. Ubuntu (and
Debian) disable this with --without-esx in debian/rules. I can't think
of any reason for Ubuntu to do this. Simply change it to --with-esx
- instead so people who are interested can use that driver.
