[Info-vax] clock problems with OpenVMS x86 on VirtualBox
Jan-Erik Söderholm
jan-erik.soderholm at telia.com
Fri May 12 03:52:47 EDT 2023
Den 2023-05-12 kl. 09:51, skrev Jan-Erik Söderholm:
> Den 2023-05-12 kl. 03:49, skrev gah4:
>> On Saturday, May 6, 2023 at 9:49:43 AM UTC-7, Craig A. Berry wrote:
>>> I am running OpenVMS x86_64 E9.2-1 under VirtualBox 7.0.8 on macOS
>>> Ventura 13.3.1 (a). The host is a 2019 MacBook Pro with 2.3 GHz 8-Core
>>> Intel Core i9. The clock isn't working right, most easily seen by the
>>> fact that the following two commands were typed exactly one minute apart:
>>
>>
>> If you Google for virtualbox clock, there are over 15 million hits.
>> (That is, for all guest OS.)
>>
>> I didn't follow all of them, but it does seem that the ones that work have
>> guest OS that know how to ask VB about the clock, instead of using
>> the usual one.
>>
>
> Actually, that was how I thought it worked. Since I observed that
> the clock in my VirtualBox VMS environment lagge a bit behind
> but each 10-20 sec, it jumpt ahead and skipped a second so that
> it become in sync with the host Windows environment again.
>
> I do not understand how VMS "knows" to jump a second ahead in
> any other way then to ask some other environment. No NNTP here...
Btw, and I might have missed some posts, but do we have more then one
report of the VMS clock showing the wrong time?
More information about the Info-vax
mailing list