Problem starting libvirtd in WSL-2

[mwoodpatrick]

Windows Version

Microsoft Windows [Version 10.0.22635.2850]

WSL Version

2.0.14.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.133.1-1

Distro Version

Debian GNU/Linux 12 (bookworm)

Other Software

qemu & virt-manager

Repro Steps

sudo apt -y install libguestfs-tools libosinfo-bin qemu-system virt-manager
sudo systemctl enable --now virtlogd # Virtual machine log manager
sudo systemctl enable --now libvirtd # Virtualization daemon

Expected Behavior

service libvirtd should be running

Actual Behavior

systemctl status libvirtd

* libvirtd.service - Virtualization daemon
     Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; preset: enabled)
     Active: inactive (dead)
TriggeredBy: * libvirtd.socket
             * libvirtd-admin.socket
             * libvirtd-ro.socket
       Docs: man:libvirtd(8)
             https://libvirt.org

Dec 09 02:40:12 mlwphpenvy360 systemd[1]: Starting libvirtd.service - Virtualization daemon...
Dec 09 02:40:12 mlwphpenvy360 systemd[1]: Started libvirtd.service - Virtualization daemon.
Dec 09 02:40:12 mlwphpenvy360 libvirtd[244]: libvirt version: 9.0.0, package: 9.0.0-4 (Debian)
Dec 09 02:40:12 mlwphpenvy360 libvirtd[244]: hostname: mlwphpenvy360
Dec 09 02:40:12 mlwphpenvy360 libvirtd[244]: internal error: Failed to get udev device for syspath '/sys/devices/virtua>
Dec 09 02:42:12 mlwphpenvy360 systemd[1]: libvirtd.service: Deactivated successfully.

Diagnostic Logs

No response

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• WSL2 not starting despite Hyper-V and virtualization being enabled (#4930), similarity score: 0.79

Closed similar issues:

• WSL2 fails to start with Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/HNS/0x80070424 (#10755), similarity score: 0.77
• Unable to Start WSL2 (#4216), similarity score: 0.77
• Unable to start WSL2 (#9171), similarity score: 0.77
• wsl: Nested virtualization is not supported on this machine. -- Then starts anyway (#10041), similarity score: 0.77
• Unable to start linux environment using wsl (#7679), similarity score: 0.77
• WSL2 ERROR: The virtual machine or container with the specified identifier is not running. (#5095), similarity score: 0.77
• WSL fails to start with error code Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x800700b7 (#10435), similarity score: 0.77
• WSL2 fails to start (#10536), similarity score: 0.77
• Error on first start: Error code: Wsl/Service/CreateInstance/CreateVm/ConfigureNetworking/0x800706bf (#8841), similarity score: 0.76

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[elsaco]

@mwoodpatrick libvirtd service is starting and stopping okay. Notice last entry libvirtd.service: Deactivated successfully. libvirtd is split in separate daemons now. Try running virsh nodeinfo or another command and see if it works. Or try virt-install and create a vm. It works, but you're limited to qemu as there's no kvm support in the WSL default kernel. You'll get a friendly WARNING KVM acceleration not available, using 'qemu'

The Failed to get udev device for syspath '/sys/devices/virtual/dmi/id' can be safely ignored. You're doing nested virtualization and there's no dmi info available. If you run dmidecode in a WSL container you'll get No SMBIOS nor DMI entry point found, sorry.

On a real system this is the output in /sys/devices/virtual/dmi/id:

/sys/devices/virtual/dmi/id/
├── bios_date
├── bios_release
├── bios_vendor
├── bios_version
├── board_asset_tag
├── board_name
├── board_serial
├── board_vendor
├── board_version
├── chassis_asset_tag
├── chassis_serial
├── chassis_type
├── chassis_vendor
├── chassis_version
├── modalias
├── power
├── product_family
├── product_name
├── product_serial
├── product_sku
├── product_uuid
├── product_version
├── subsystem -> ../../../../class/dmi
├── sys_vendor
└── uevent

[microsoft-github-policy-service]

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-open it.

Thank you!