libvirt and bhyve problems

Craig Rodrigues rodrigc at FreeBSD.org
Tue Jun 10 19:25:24 UTC 2014


On Tue, Jun 10, 2014 at 12:15 PM, Roman Bogorodskiy <novel at freebsd.org> wrote:
>
> This last line also sounds strange.
>
> I'm wondering if you execute 'net-list --all' will you see the 'default'
> network? And if it's there, will 'net-show default' should that
> Autostart is enabled for it?


If I do:
# virsh -c 'bhyve:///system'
Welcome to virsh, the virtualization interactive terminal.

Type:  'help' for help with commands
       'quit' to quit

virsh # net-list --all
error: Failed to get the number of active networks
error: this function is not supported by the connection driver:
virConnectNumOfNetworks


The past few times, I have been compiling the port using WITH_DEBUG=yes.

However, I am not getting useful stacktraces:

/usr/ports/devel/libvirt/work/libvirt-1.2.5]# file /usr/local/sbin/libvirtd
/usr/local/sbin/libvirtd: ELF 64-bit LSB shared object, x86-64,
version 1 (FreeBSD), dynamically linked (uses shared libs), for
FreeBSD 11.0 (1100022), not stripped


# gdb /usr/local/sbin/libvirtd libvirtd.core
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "amd64-marcel-freebsd"...
Core was generated by `libvirtd'.
Program terminated with signal 11, Segmentation fault.
#0  0x0000000801aa8513 in ?? ()
(gdb) where
#0  0x0000000801aa8513 in ?? ()
#1  0x0000001800000008 in ?? ()
#2  0x00007fffff3f9330 in ?? ()
#3  0x0000000809e5510c in ?? ()
#4  0x0000000000000007 in ?? ()
#5  0x0000000809e5531b in ?? ()
#6  0x0000000000000000 in ?? ()


BTW, can you give me:
  (1)  exact git command to checkout libvirt
  (2)  configure command you typed
  (3)  make command you typed

I want to get a working setup like you have.  It looks like the port
needs some fixing before
it can be used fully.
--
Craig


More information about the freebsd-testing mailing list