Craig Rodrigues wrote:

> On Thu, Jun 12, 2014 at 12:00 PM, Roman Bogorodskiy <no...@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
> ----------------------------------------------------------
> 

I have updated the port:

http://people.freebsd.org/~novel/misc/libvirt_port2.tgz

Changes are:

 * added RUN_DEPENDS on dnsmasq (required for networking)
 * added installation on network definition files

Hopefully this will allow to bring up network on start. When the daemon
starts, virsh should show the following:

virsh # net-list
 Name                 State      Autostart     Persistent
 ----------------------------------------------------------
  default              active     yes           yes

virsh # 

If that's not the case, then something is still going wrong.

And yes, qemu support should be enabled (networks defs seem to be
installed with qemu support).

Even if it doesn't work, and 'net-list --all' is empty, we could try to
do it manually (but still, if it's the case, then it's something wrong
with the port that needs to be fixed):

in virsh

# net-define /usr/local/etc/libvirt/qemu/networks/default.xml
# net-start default

Roman Bogorodskiy

Attachment: pgpZGtuqlk5zW.pgp
Description: PGP signature

Reply via email to