[Info-vax] clock problems with OpenVMS x86 on VirtualBox

[Jan-Erik Söderholm]

Den 2023-05-08 kl. 13:08, skrev Craig A. Berry:
> 
> On 5/8/23 1:45 AM, Jan-Erik Söderholm wrote:
>> Den 2023-05-08 kl. 00:44, skrev David Turner:
>>> Like I have always suspected.
>>> I think there is more of an emulator in the OpenVMS x86 code than has 
>>> been admitted.
>>> The faster the CPU on the virtualbox the faster your "native X86" code 
>>> is gonna run
>>> Anyone care to elaborate or prove this?
> 
> Prove what?  That nothing in this newsgroup stays on-topic?
>> I should not take the writing below as anything of a value.
> 
> It's of value to me if it helps anyone identify a solution to the
> problem I'm having.
> 
>> Just the line saying "it takes about >> 15 seconds for MONITOR
>> SYSTEM to initiate its display" says that something is really
>> wrong with that environment. On my laptop with VirtualBox,
>> MONITOR starts in around 1 sec. I cannot see any difference
>> between my VirtualBox environment and a real AlphaServer DS20e.
> 
> Right.  There is no reason to hijack my thread with a conspiracy theory.


Now, did *I* do that? You quoted me before your reply.
It was David T that dragged the "emulator" into this. And he was
of course completely of-track with this "emulator" talk.

I was just confirming that something must be weird in the
setup that was reported, and that was what I commented on. You are
correct that it migth now help you directly, but I thought it could
be of some use/interest anyway.

And I also found it interesting that the clock "ticked" a bit
slow and then jumped forward and skipped a second to catch-up.

But yes, if this had been a common VirtualBox issue, it would
have been know by now, of course.




> I have what must be an extremely common set-up, yet things are
> completely haywire.  Other people with VirtualBox do not see what I'm
> seeing.  There must be some combination of host OS / host hardware /
> hypervisor / settings that is not an agreeable combo.

Sure...

> Speculating
> without foundation that OpenVMS x86 runs on an emulator rather than a
> hypervisor does not get me any closer to figuring out what the actual
> problem is.

Again, *I* did not do added that "speculation"...