If the operating system is no longer "operating the system"...
... but the hypervisor is doing it, isn't it about time it was given a new name? A Process Manager maybe?
I have wondered why Unix OS's get virtualised - haven't the sysadmins ever heard of chroot and LD_LIBRARY_PATH? All the hypervisor and the extra copy(s) of the OS are doing is sucking up CPU cycles that then can't be used by running processes. If you need to run 10 processes run them in the same OS instance, its not rocket science. I realise Windows is a toy OS and doesn't have anything equivalent to chroot but for Linux , BSD etc, there is no good reason to use a hypervisor·
