[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v1] core: mount xenfs, ignore proc-xen.mount (#6442, #6662)

On Fri, Dec 01, 2017 at 04:49:01PM +0100, Olaf Hering wrote:
> 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".

Thanks. This is much clearer. And I agree with your conclusion here.

> IMO what
> systemd today sees as "dom0" should be set based on "XENFEAT_dom0".

I'm fine with this. Keeping the semantics the same as Xen's is good.
We don't want to create more confusion.

To summarise:

1. You need XENFEAT_dom0 for hardware domain;
2. You need something else (missing atm?) for control domain.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.