Comment 6 for bug 1747394

Hi Sosha,
the crash itself is in libxml2 so I add a bug task for that.

From the libvirt POV this seems to be in a stage where it initializes its state drivers.
virStateInitialize iterates on drivers and calls stateInitialize of the respective backend.

I can't see from your trace which that is, but I assume this triggers right when you start libvirtd?
If so did you register special backends?
The following is the list of drivers with such a function

0 bhyve_driver.c 1753 .stateInitialize = bhyveStateInitialize,
2 interface_backend_netcf.c 1139 .stateInitialize = netcfStateInitialize,
3 interface_backend_udev.c 1211 .stateInitialize = udevStateInitialize,
4 libxl_driver.c 6594 .stateInitialize = libxlStateInitialize,
5 lxc_driver.c 5590 .stateInitialize = lxcStateInitialize,
6 bridge_driver.c 4272 .stateInitialize = networkStateInitialize,
7 node_device_hal.c 778 .stateInitialize = nodeStateInitialize,
8 node_device_udev.c 2070 .stateInitialize = nodeStateInitialize,
9 nwfilter_driver.c 640 .stateInitialize = nwfilterStateInitialize,
a qemu_driver.c 21355 .stateInitialize = qemuStateInitialize,
b remote_driver.c 8648 .stateInitialize = remoteStateInitialize,
c secret_driver.c 578 .stateInitialize = secretStateInitialize,
d storage_driver.c 2743 .stateInitialize = storageStateInitialize,
0 uml_driver.c 3020 .stateInitialize = umlStateInitialize,
1 vz_driver.c 4171 .stateInitialize = vzStateInitialize,
2 xen_driver.c 269 .stateInitialize = xenUnifiedStateInitialize,

Since it has netcf entries down the stack trace I can only assume it is the init of netcf.
That would be in netcfStateInitialize

There is calls ncf_init and the lib also has libxml2 bindings.
I fail to derive more from the stack trace as-is, but that already meand we should also add a task for netcf.

I wonder:
1. is this reproducible on e.g. every restart of libvirtd?
2. do you have any non-default network configuration on the system or in libvirt that might be what we would need to reproduce that?