[Info-vax] VSI has a new CEO

[calliet gérard]

Le 05/08/2021 à 10:49, John Dallman a écrit :
> In article <seg6ci$rdq$1 at gioia.aioe.org>, helbig at asclothestro.multivax.de
> (Phillip Helbig (undress to reply)) wrote:
>> In article <sef7om$i74$1 at dont-email.me>, Dave Froble
>> <davef at tsoft-inc.com> writes:
>>> Now that is just plain wrong.  VMS is VMS, regardless if running
>>> in a VM instance, or not.  Actually, VM instances will be better
>>> for porting work.  One doesn't need a production level computer
>>> to do porting work.
>> Sure, but do you expect people with no previous VM experience to
>> learn about VMs just to port VMS so that they have a head start on
>> the time when VMS doesn't need a VM on x86?
> 
> VMs aren't actually difficult to use. Just about everyone who works as a
> system administrator knows how to set up VMs from supplied images and
> start them. This is probably easier than installing an OS onto unfamiliar
> bare metal.
> 
> You may well want to do some configuration of the VMS instance inside
> your VM, but that's normal VMS sysadmin.
> 
> John
> 
Just today:

I had installed on my laptop an eak 9.0 on a virtual box. It worked.

Today I tried it: VMS said your CPU has not the XSAVE feature, I cannot 
boot.

Going in a cmd window, pythoning the vmscheck.py

It says: you have the XSAVE feature

Googling: "it's because you have the Hyper-V feature enabled, disable it 
and virtual box will have the XSAVE feature" (bcdedit /set 
hypervisorlaunchtype off)

Yes: now I have the XSAVE feature in my Oracle VM

Why? You know it: because there has been in between a windows update 
which switched the hypervisorlaunchtype

Summary: learning curve for VMs is not trivial, stability with VMs has 
to be inspected

It's a brave new world. And I do like that, anyway. But don't say it's 
the panacea.

-- 
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast.
https://www.avast.com/antivirus