Justin Clift wrote: > On 23 Jan 2017, at 11:38, Daniel P. Berrange <berra...@redhat.com> wrote: > > On Wed, Dec 21, 2016 at 09:55:53AM +0000, Justin Clift wrote: > <snip> > > > > I'm looking at (what I hope is the correct) configuration file for the > > build: > > > > https://github.com/Homebrew/homebrew-core/blob/master/Formula/libvirt.rb > > Yep, that's the right one. > > > and see '--without-qemu' being passed - what is the reason for that ? It > > looks like you're building libvirtd, so enabling QEMU thereafter should > > not have any significantly difficulties. Certainly we expect the QEMU > > driver code to be platform agnostic - all the Linux specific bits are > > believed to be wrapped in conditionals. > > > > IOW if you see build errors with QEMU on OS-X could you tell us what they > > are. > > From memory (it's been a few years!), it was because the QEMU that builds > in Homebrew wouldn't talk to Libvirt anyway. So it was useless to add the > support in. > > That being said, I do remember someone mentioning they should probably > worth together ok these days. But, I'm not sure if anyone's checked > and/or really tried to make it work.
Well, at least it builds the qemu driver successfully, maybe later I'll check if it could actually run a VM. > > We'd really want to see the QEMU driver enabled > > Yep, it sounds like it'd be a useful combination. As would xhyve, if > that could somehow use the bhyve support (I have no idea). :) I think it won't work as is, but quite probably a fair amount of the bhyve code could be reused (probably with some refactoring). Roman Bogorodskiy
signature.asc
Description: PGP signature
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
