[Info-vax] WHY IS VSI REQUIRING A HYPERVISOR FOR X86 OPENVMS?

Arne Vajhøj arne at vajhoej.dk
Thu Dec 31 20:01:02 EST 2020


On 12/31/2020 5:35 PM, Snowshoe wrote:
> On 12/31/2020 1:50 PM, D W wrote:
>> On Thursday, December 31, 2020 at 12:07:41 PM UTC-5, Andrew Brehm wrote:
>>> On 21/12/2020 02:03, Michael C wrote:
>>>> 2ND PROBLEM - JOINING THE LINUX PATCH OF THE DAY CLUB
>>>>
>>>> HERE IS THE OPENVMS CERT COUNTS AS OF 2018 COMPARE THEM WITH OTHER 
>>>> OSs - SEE THE PROBLEM?
>>>
>>> No, I don't see the problem. How would Linux patches affect OpenVMS
>>> running in a virtualised environment?
>>>
>>> I'm not sure you understand virtualisation correctly.
> 
> Is there such a thing as an OS-less VM hypervisor? More specifically, a 
> hypervisor which is its own OS in a way, you boot it directly (not 
> booting Linux/Windoze then starting the hypervisor) and pretty much the 
> only thing you can do once booted is starting virtual machines.

That is what a bare-metal hypervisor does.

> I suspect this is the case but I am not familiar with hypervisors.
> I also suspect that many/most/all are really Linux under the hood.

The most widely bare-metal hypervisor VMWare ESXi has its own
kernel, but it does come with a bunch of userland
Linux stuff and a compatibility layer that allow using
Linux device drivers besides native device drivers.

Arne



More information about the Info-vax mailing list