Files
systemd/src/basic
zhaoshuang 8b4055c5e2 virt: detect Alibaba Cloud ECS as KVM
Alibaba Cloud ECS instances expose "Alibaba Cloud ECS" in DMI
product_name/bios_vendor and "Alibaba Cloud" in sys_vendor. None of
these match dmi_vendor_table[], so systemd-detect-virt --vm reports
"none" on these machines, even though they run on a KVM-based
hypervisor. This is especially visible on ARM64 instances, where the
CPUID fallback does not exist (x86 only) and /proc/device-tree is
not populated.

Add "Alibaba Cloud ECS" to dmi_vendor_table[], mapping to
VIRTUALIZATION_KVM. The narrower prefix avoids matching the bare
"Alibaba Cloud" sys_vendor value, reducing the false-positive
surface for Alibaba's bare-metal (X-Dragon) instances compared to
the original broader prefix. bios_vendor also carries the same
string on ECS VMs though, so the protection is not complete —
fully resolving the VM-vs-bare-metal ambiguity would need the
SMBIOS BIOS-Characteristics bit check that the Amazon EC2 entry
uses.

The existing "back to DMI" fallback path in detect_vm() reports
"kvm" on both x86 and ARM64.

(cherry picked from commit abffa868a8)
2026-09-09 10:08:20 +01:00
..
…
2026-01-06 10:34:02 +01:00
2026-04-26 21:21:49 +02:00
2026-03-03 22:18:26 +01:00
2026-02-05 16:18:35 +01:00
2026-03-31 18:30:40 +02:00
2026-04-09 22:47:10 +02:00
2026-04-09 22:47:10 +02:00
2025-12-15 08:50:13 +09:00
…
…
…
2026-07-19 22:34:06 +01:00
2026-09-09 10:08:20 +01:00