Does the STANDARD LE (not the virtualized image) support the virtio devices (especially virtio net)?

cosmos · July 7, 2025 at 10:49 AM

I'm tinkering with sky42 's special image for Intel N150-based rigs, as a virtualized proxmox instance.

The VM has internet access just fine, but when I'm yrying to enable WOL I receive an error.

External Content pastebin.com

Content embedded from external sources will not be displayed without your consent.

Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

~~Regardless of the image I'm currently using, any idea if the standard image LE12 image includes virtio* devices?~~

EDIT: Yes it does, see post #2.

Addendum: the latest official LE12 nightly produces a black screen, LE works though (can SSH):

External Content pastebin.com

Content embedded from external sources will not be displayed without your consent.

Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

From kodi.log:

Code

2025-07-07 13:15:01.426 T:9923    error <general>: DBus error: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower was not provided by any .service files
2025-07-07 13:15:01.426 T:9923     info <general>: LogindUPowerSyscall - UPower not found, battery information will not be available
2025-07-07 13:15:01.431 T:9923     info <general>: CKeyboardLayoutManager: loading keyboard layouts from special://xbmc/system/keyboardlayouts...
2025-07-07 13:15:01.509 T:9923    error <general>: [xkb] couldn't find a Compose file for locale "C" (mapped to "C")
2025-07-07 13:15:01.509 T:9923  warning <general>: CLibInputKeyboard: Failed to compile localized compose table, composed key support will be disabled
2025-07-07 13:15:01.512 T:9923     info <general>: RetroPlayer[RENDER]: Registering renderer factory for DMA
2025-07-07 13:15:01.512 T:9923     info <general>: RetroPlayer[RENDER]: Registering renderer factory for OpenGLES
2025-07-07 13:15:01.512 T:9923    error <general>: CDRMUtils::OpenDrm - no drm devices found: (No such file or directory)
2025-07-07 13:15:01.512 T:9923    error <general>: CWinSystemGbm::InitWindowSystem - failed to initialize Atomic DRM
2025-07-07 13:15:01.512 T:9923    error <general>: CDRMUtils::OpenDrm - no drm devices found: (No such file or directory)
2025-07-07 13:15:01.512 T:9923    error <general>: CWinSystemGbm::InitWindowSystem - failed to initialize Legacy DRM
2025-07-07 13:15:01.512 T:9923    error <general>: CDRMUtils::OpenDrm - no drm devices found: (No such file or directory)
2025-07-07 13:15:01.512 T:9923    error <general>: CWinSystemGbm::InitWindowSystem - failed to initialize off screen DRM
2025-07-07 13:15:02.132 T:9923  critical <general>: CApplication::CreateGUI - unable to init windowing system

Display More

cosmos · July 7, 2025 at 5:22 PM

Adding output of ethtool corresponding to the virtio-net provided card:

Code

# ethtool eth0
Settings for eth0:
       Supported ports: [  ]
       Supported link modes:   Not reported
       Supported pause frame use: No
       Supports auto-negotiation: No
       Supported FEC modes: Not reported
       Advertised link modes:  Not reported
       Advertised pause frame use: No
       Advertised auto-negotiation: No
       Advertised FEC modes: Not reported
       Speed: Unknown!
       Duplex: Unknown! (255)
       Auto-negotiation: off
       Port: Other
       PHYAD: 0
       Transceiver: internal
       Link detected: yes
 
 # ethtool -i eth0
driver: virtio_net
version: 1.0.0
firmware-version:
expansion-rom-version:
bus-info: 0000:00:12.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no

Display More

From the looks of it, the driver is correctly identified as virtio_net. For some reason though, there is a lot of information missing (like duplex or any wake-on-lan capabilities). IIRC, other VMs get this information just fine.

Could it be a kernel build issue?