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?

On Wed, Sep 8, 2010 at 10:22 AM, Daniel P. Berrange <berrange@redhat.com> wrote:

On Wed, Sep 08, 2010 at 09:56:51AM -0700, Mitchell Hashimoto wrote:
> Hello,
>
> I've done some research prior to this and the answer is clear that libvirtd
> doesn't compile on BSD or OSX, but I'd like to know more details about this,
> if I can have a bit of your time:
>
> * Are there any current efforts to get libvirtd running on BSD?
> * What are the blockers to getting it running?
> * My main goal is really to, at first only control VirtualBox, so
> KVM/Xen/etc is not an issue.
>
> I realize that KVM and some other hypervisors obviously can't be supported
> on BSD, but if I could just start by compiling libvirtd for VirtualBox on
> BSD that would be a big win in and of itself.

NB, virtualbox does not require libvirtd if you only care about local
access. If you want remote access, then obviously it would be needed.

There isn't any particular reason why libvirtd shouldn't work on any
UNIX based OS. If there are any Linux-isms in there, they're purely
accidental. The only platform where porting libvirtd will be hard
is Windows. Best to just enable libvirtd and then post details of the
compilation errors you get to the libvir-list mailing list

Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|