Xendriverdomain.service Failed

While going through logs in one of my appvm, I noticed that xendriverdomain.service was loaded and had failed. In its template, I found these logs. This didn’t make any noticeable difference, however.

This is a debian-minimal template installed with additional software.

May 13 09:59:37 debian-11-office xl[703]: libxl: error: libxl_utils.c:820:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
May 13 09:59:37 debian-11-office xl[703]: libxl: error: libxl_utils.c:820:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
May 13 09:59:37 debian-11-office xl[703]: libxl: error: libxl_utils.c:820:libxl_cpu_bitmap_alloc: failed to retrieve the maximum number of cpus
May 13 09:59:37 debian-11-office xl[704]: xl: fatal error: xl_utils.c:273: No such file or directory: logfile = open(fullname, O_WRONLY|O_CREAT|O_APPEND, 0644)
May 13 09:59:37 debian-11-office xl[703]: libxl: error: libxl_exec.c:117:libxl_report_child_exitstatus: domain monitoring daemonizing child [704] exited with error status 1
May 13 09:59:37 debian-11-office systemd[1]: xendriverdomain.service: Control process exited, code=exited, status=253/n/a

This error only happens in this template and appvms that are based on this template. Other debian-minimal based templates are not affected.

You can try to clone the original debian-minimal template and install your additional software in it one by one to see which software is causing this error.