[systemd-devel] [PATCH] systemd-detect-s390-virt: add virtualization detection on s390x

[Lennart Poettering]

On Mon, 07.07.14 12:18, Thomas Blume (Thomas.Blume at suse.com) wrote:

> 
> On Fri, 4 Jul 2014, Lennart Poettering wrote:
> 
> >>+        _id = "PR/SM";
> >>+        r = 1;
> >
> >Well, this is not useful, this is about detecting whether the OS we run
> >in is the closest to the hardware of the system or is is removed from it
> >via some virtualization layer.
> >
> >This definition means that on Xen dom0 is not considered virtualization,
> >but domU is.
> >
> >It appears to be that it's similar here, and hence the above makes
> >little sense.
> 
> 
> Actually it is like there is no dom0 on s390(x).
> Direct hardware access is done on a level where the operating system doesn't
> have any influence.
> For example, unlike Xen dom0, the disks are never physical devices, they are
> only shares of a storage pool.
> Same is true for e.g. the CPUs or the main memory. It is all virtualized.
> Some functions, like e.g. SMART for the disks, just doesn't make sense here.
> Even if PR/SM is closer to the hardware than z/VM or KVM, the
> e behaviour is the same. There is no useful SMART information.

If everything is virtualized on s390, what's the difference between the
two virtualizations you wanted to distuingish then?

Lennart

-- 
Lennart Poettering, Red Hat