Re: Status of libvirtd on BSD/OSX?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2010/9/8 Daniel P. Berrange <berrange@xxxxxxxxxx>:
> On Wed, Sep 08, 2010 at 10:25:27AM -0700, Mitchell Hashimoto wrote:
>> Daniel,
>>
>> Thank you very much. Ah, I was under the impression that libvirtd was
>> required to control any hypervisors (local or remote). I'm purely interested
>> in local access to hypervisors right now. I'm sorry I admit that my next
>> question is not well researched, but I figured it would be a quick answer
>> from someone knowledgeable: Do you know the "./configure" flags off the top
>> of your head to disable libvirtd and only enable VirtualBox drivers?
>
> At the very least
>
>   configure
>    --without-xen \
>    --without-qemu \
>    --without-lxc \
>    --without-uml \
>    --without-esx \
>    --without-openvz \
>    --without-one \
>    --without-phyp \
>    --without-netcf \
>    --without-libvirtd
>
> Daniel

You should add --with-vbox, otherwise configure will disable the
VirtualBox driver if it can't find the VirtualBox XPCOMC library.

Matthias


[Index of Archives]     [Virt Tools]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]

  Powered by Linux