On Fri, Dec 01, Wei Liu wrote: > What information do you need? For a moment let's skip using the fuzzy > "Dom0" term and try to be precise. Like "I would like to know if that > domain has access to all hardware" or something else.
That depends on the .service files. This is the list of openSUSE Tumbleweed: dev-hugepages.mount:ConditionVirtualization=!private-users haveged.service:ConditionVirtualization=!container hv_fcopy_daemon.service:ConditionVirtualization=microsoft hv_kvp_daemon.service:ConditionVirtualization=microsoft hv_vss_daemon.service:ConditionVirtualization=microsoft irqd.service:ConditionVirtualization=!container ksm.service:ConditionVirtualization=no lxcfs.service:ConditionVirtualization=!container mcelog.service:ConditionVirtualization=false ntp-wait.service:ConditionVirtualization=!container ntpd.service:ConditionVirtualization=!container rng-tools.service:ConditionVirtualization=!container smartd.service:ConditionVirtualization=false sys-fs-fuse-connections.mount:ConditionVirtualization=!private-users systemd-random-seed.service:ConditionVirtualization=!container systemd-timesyncd.service:ConditionVirtualization=!container vgauthd.service:ConditionVirtualization=vmware vmblock-fuse.service:ConditionVirtualization=vmware vmtoolsd.service:ConditionVirtualization=vmware xendriverdomain.service:ConditionVirtualization=xen I think the relevant services are ksm,mcelog and smartd. Each one likely wants the "hardware domain" rather than the "toolstack domain". IMO what systemd today sees as "dom0" should be set based on "XENFEAT_dom0". Olaf
signature.asc
Description: PGP signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel