[Info-vax] %SYSTEM-F-ACCVIO again

[Simon Clubley]

On 2024-04-07, motk <yep at yep.yep> wrote:
> On 4/8/24 12:20, Arne Vajhøj wrote:
>
>> I consider it more likely that VMS and the CPU/virtual memory
>> environment your VM provide disagree on something causing
>> random sporadic memory related errors.
>
> It seems odd, I agree. This was running on an intel nuc with a 12th gen 
> i5 cpu, and I wonder if openvms doesn't like straddling P/E cores.
>
> I've previously done some memory burn-in on that node without issues.
>
> I've migrated it over to a plain 6th gen node with 4 boring cores; lets 
> see if that improves things.
>

It's still a VMS bug (even if VMS is being _way_ too fragile) IMHO.

IIRC, motk is using proxmox, which many other people are using just fine
to run other operating systems.

If there's something VMS needs or a configuration it doesn't support,
then that should be probed at boot time and VMS should refuse to continue
booting with the reason why been made clear. The bug in this case is that
this check is missing from VMS.

The other possibility is that VMS is _supposed_ to work OK in this
configuration, but this specific VM setup has been untested by VSI until
now. That means there is a bug in the VMS code itself which needs fixing.

Simon.

-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Walking destinations on a map are further away than they appear.