libvirt and bhyve problems

[Craig Rodrigues]

On Thu, Jun 12, 2014 at 12:00 PM, Roman Bogorodskiy <novel at freebsd.org> wrote:
>
> Ah. Actually, libvirt manages bridges and taps on its own. So, the
> preferred flow is that libvirt starts its networks on startup
> automatically. By default it has a network with the 'virbr0' device
> which it creates on its own.
>
> Later on it creates vnet devices (which are tap devices) automatically
> as well on VM startup and plugs them to the bridge.
>
> The configuration you have probably confuses it, could you consider
> trying without that?

OK, I removed all autobridge and cloned_interfaces entries
from my rc.conf and rebooted.  I am still using your version of the
libvirt port.

I tried the steps again and got this:

2014-06-13 19:09:10.482+0000: 34485605376: info : libvirt version: 1.2.5
2014-06-13 19:09:10.482+0000: 34485605376: error :
dnsmasqCapsRefreshInternal:726 : Cannot check dnsmasq binary dnsmasq:
No such file or directory
2014-06-13 19:09:10.482+0000: 34485605376: info :
networkReloadFirewallRules:1750 : Reloading iptables rules
2014-06-13 19:09:10.482+0000: 34485605376: info :
networkRefreshDaemons:1722 : Refreshing network daemons
2014-06-13 19:09:10.593+0000: 34485605376: error : virExec:417 :
Cannot find 'pm-is-supported' in path: No such file or directory
2014-06-13 19:09:10.593+0000: 34485605376: warning :
virQEMUCapsInit:948 : Failed to get host power management capabilities
2014-06-13 19:09:10.615+0000: 34485605376: info :
virDomainObjListLoadAllConfigs:18249 : Scanning for configs in
/usr/local/var/run/libvirt/qemu
2014-06-13 19:09:10.615+0000: 34485605376: info :
virDomainObjListLoadAllConfigs:18249 : Scanning for configs in
/usr/local/etc/libvirt/qemu
2014-06-13 19:09:10.716+0000: 34485605376: info :
virDomainObjListLoadAllConfigs:18249 : Scanning for configs in
/usr/local/etc/libvirt/bhyve
2014-06-13 19:09:10.716+0000: 34485605376: info :
virDomainObjListLoadAllConfigs:18273 : Loading config file 'bhyve.xml'
2014-06-13 19:09:25.938+0000: 34485598208: error :
virNetDevTapCreate:385 : Unable to create tap device: Invalid argument
2014-06-13 19:09:26.063+0000: 34485598208: error : virCommandWait:2426
: internal error: Child process (/usr/sbin/bhyvectl --destroy
--vm=bhyve) unexpected exit status 255


If I do ifconfig, I have no bridge or tap devices.


>
> Also, do you have working 'net-list' command in virsh with my version of
> port?

I get this:
virsh # net-list
 Name                 State      Autostart     Persistent
----------------------------------------------------------




>
> PS If you're available for some real-time conversation such as on IRC, I
> think some kind of things would be faster to discuss there.


You can private mail me some times when you are available.  I am busy
the next few days,
but might have a few hours on Sunday.
--
Craig