On a Monday in 2020, Mathieu Tarral wrote:
Hi,
I'm facing an issue with libvirt and the LIBXL driver, failing when searching for DMI
data in /sys.
info : libvirt version: 5.0.0, package: 4+deb10u1 (Guido Günther <agx(a)sigxcpu.org>
Thu, 05 Dec 2019 00:22:14 +0100)
error : udevGetDMIData:1719 : internal error: Failed to get udev device for syspath
'/sys/devices/virtual/dmi/id' or '/sys/class/dmi/id'
This error is set and logged in a void fuction - it is not the one
blocking the driver initialization.
error : libxlDriverConfigNew:1803 : Unable to configure libxl's
memory management parameters
This is the important error, calling libxl_get_free_memory failed for
some reason:
https://gitlab.com/libvirt/libvirt/-/blob/v5.0.0/src/libxl/libxl_conf.c#L...
Unfortunately, I'm not actually familiar enough with Xen to offer
further suggestions.
error : virStateInitialize:662 : Initialization of LIBXL state driver
failed: internal error: Failed to get udev device for syspath
'/sys/devices/virtual/dmi/id' or '/sys/class/dmi/id'
Here the caller is picking up the first error instead of the second
because the second one was logged via a different API.
Jano
error : daemonRunStateInit:799 : Driver state initialization failed
The relevant function udevGetDMIData in libvirt:
https://github.com/libvirt/libvirt/blob/cb09344a2cccc0cc9bcefa3cb53d7af45...
I don't understand what's happening, as this initialization failure only happens
when I boot on the Xen kernel.
Also, the /sys/class/dmi* paths are not exposed on Xen.
Note: Running on Xen 4.12.1
Any ideas ?
Thanks !