So apparently "linux,dummy-virt" is a devicetree in popular use by various hypervisors, including crosvm: https://github.com/google/crosvm/blob/e5d7a64d377d00b9b96bc026548769ab59cf216b/aarch64/src/fdt.rs#L692 and qemu: https://github.com/qemu/qemu/blob/98c7362b1efe651327385a25874a73e008c6549e/hw/arm/virt.c#L283 and that's because the kernel ships support for that natively: https://www.kernel.org/doc/Documentation/devicetree/bindings/arm/linux%2Cdummy-virt.yaml It's explicitly for using in virtualization. Hence it's suitable for detecting it as generic fallback. This hence adds the check, similar to how we already look for one other qemu-specific devicetree. I ran into this while playing around with the new Pixel "Linux Terminal" app from google which runs a Debian in a crosvm apparently. So far systemd didn't recognize execution in it at all. Let's at least recognize it as VM at all, even if this doesn't recognize it as crosvm.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS
