libvirt and bhyve problems

[Craig Rodrigues]

On Wed, Jun 11, 2014 at 12:25 PM, Roman Bogorodskiy <novel at freebsd.org> wrote:
> I've attached a patch which should fix the segfault. Could you please
> let me know if it fixes the problem?

I have incorporated your patch into the libvirt port, and provided a tarball
of the port here:

http://people.freebsd.org/~rodrigc/libvirt_port.tgz

I can confirm that your patch eliminates the coredump for me.

So now I can do the following:

(1)  Start libvirtd:
                /usr/local/sbin/libvirtd

(2)  Start virsh:
                virsh -c "bhyve:///system"

(3)  Execute following inside virsh:
           define bhyve.xml
           start bhyve

           ( using bhyve.xml file from
http://lists.freebsd.org/pipermail/freebsd-virtualization/2014-June/002588.html
)

In the libvirtd console, I see this:

2014-06-11 22:47:16.357+0000: 34485605376: info : libvirt version: 1.2.5
2014-06-11 22:47:16.357+0000: 34485605376: error : virExec:417 :
Cannot find 'pm-is-supported' in path: No such file or directory
2014-06-11 22:47:16.357+0000: 34485605376: warning :
virQEMUCapsInit:948 : Failed to get host power management capabilities
2014-06-11 22:47:21.050+0000: 34485605376: info :
virDomainObjListLoadAllConfigs:18249 : Scanning for configs in
/usr/local/var/run/libvirt/qemu
2014-06-11 22:47:21.063+0000: 34485605376: info :
virDomainObjListLoadAllConfigs:18249 : Scanning for configs in
/usr/local/etc/libvirt/qemu
2014-06-11 22:47:21.168+0000: 34485605376: info :
virDomainObjListLoadAllConfigs:18249 : Scanning for configs in
/usr/local/etc/libvirt/bhyve
2014-06-11 22:47:21.168+0000: 34485605376: info :
virDomainObjListLoadAllConfigs:18273 : Loading config file 'bhyve.xml'
2014-06-11 22:47:43.469+0000: 34485598208: error :
virNetDevBridgeAddPort:399 : Unable to add bridge tap0 port vnet18:
Invalid argument
2014-06-11 22:47:43.573+0000: 34485598208: error : virCommandWait:2426
: internal error: Child process (/usr/sbin/bhyvectl --destroy
--vm=bhyve) unexpected exit status 255



For the last line, it looks like it is trying to do bhyvectl --destroy
--vm=bhyve
on a VM which doesn't exist, i.e. there is no entry in /dev/vmm/bhyve

It should ignore the error at this point and try to spawn the VM, but it fails.

--
Craig