On Tue, Jun 10, 2014 at 4:43 AM, Roman Bogorodskiy <no...@freebsd.org> wrote:
> Hi Craig,
>
> It's a little unfortunate that there's no stacktrace, though we can try
> to see what's going on without it.
>
> Could you please edit libvirtd.conf (should be something like
> /usr/local/etc/libvirtd.conf if installed from port) to add:
>
> log_level = 2
>
> then run libvirtd by hand in foreground:

OK, I added log_level = 2 to /usr/local/etc/libvirt/libvirtd.conf
and ran libvirtd in the foreground:

2014-06-10 15:53:26.846+0000: 34485593088: info : libvirt version: 1.2.5
2014-06-10 15:53:26.846+0000: 34485593088: warning :
virDriverLoadModule:63 : Module
/usr/local/lib/libvirt/connection-driver/libvirt_driver_uml.so not
accessible
2014-06-10 15:53:27.023+0000: 34485605376: error : virExec:417 :
Cannot find 'pm-is-supported' in path: No such file or directory
2014-06-10 15:53:27.023+0000: 34485605376: warning :
virQEMUCapsInit:948 : Failed to get host power management capabilities
2014-06-10 15:53:27.034+0000: 34485605376: info :
virDomainObjListLoadAllConfigs:18249 : Scanning for configs in
/usr/local/var/run/libvirt/qemu
2014-06-10 15:53:27.034+0000: 34485605376: info :
virDomainObjListLoadAllConfigs:18249 : Scanning for configs in
/usr/local/etc/libvirt/qemu
2014-06-10 15:53:27.130+0000: 34485605376: info :
virDomainObjListLoadAllConfigs:18249 : Scanning for configs in
/usr/local/etc/libvirt/bhyve
2014-06-10 15:53:53.668+0000: 34485598208: error : virNetDevGetMTU:404
: Cannot get interface MTU on 'virbr0': Device not configured
Segmentation fault (core dumped)



I got that coredump after doing:

virsh -c 'bhyve:///system'
virsh # define /tmp/bhyve.xml
virsh # start bhyve
_______________________________________________
freebsd-virtualization@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
To unsubscribe, send any mail to 
"freebsd-virtualization-unsubscr...@freebsd.org"

Reply via email to