time in OpenVMS X86-64
-
Topic author - Valued Contributor
- Posts: 93
- Joined: Thu Aug 27, 2020 5:50 am
- Reputation: 0
- Status: Offline
time in OpenVMS X86-64
Hi all,
I run X86-64 using Qemu/KVM on a Fedora-linux system. Every time I reboot the machine the time is set to UTC (although I configured it as CET (Europe/Amsterdam). It is logical because the internal clock of Fedora runs UTC (which is in Fedora translated to CET). Qemu just picks up UTC.
It is annoying to set the time correct every time by hand. How is this to be solved?
regards
Jouk
I run X86-64 using Qemu/KVM on a Fedora-linux system. Every time I reboot the machine the time is set to UTC (although I configured it as CET (Europe/Amsterdam). It is logical because the internal clock of Fedora runs UTC (which is in Fedora translated to CET). Qemu just picks up UTC.
It is annoying to set the time correct every time by hand. How is this to be solved?
regards
Jouk
Re: time in OpenVMS X86-64
There is probably a in your xml file. I changed that to
and that works for me. You probably want to edit the xml file with
Code: Select all
<clock offset='utc'>
Code: Select all
<clock offset='timezone' timezone='Europe/Berlin'>
Code: Select all
virsh edit <your-domain>
-
- Valued Contributor
- Posts: 60
- Joined: Tue Mar 22, 2022 6:47 pm
- Reputation: 0
- Location: England
- Status: Offline
Re: time in OpenVMS X86-64
I checked that on my machine (AlmaLinux 8.8, QEMU/KVM) and it was also showing GMT instead of BST. The fix above works beautifully, many thanks.
Last edited by martin on Mon Jun 05, 2023 7:15 am, edited 1 time in total.
Martin
- Retired System Manager: VMS/UNIX/UNICOS/Linux.
- Started on a VAX 11/782 in 1984 with VMS 3.6.
-
Topic author - Valued Contributor
- Posts: 93
- Joined: Thu Aug 27, 2020 5:50 am
- Reputation: 0
- Status: Offline
Re: time in OpenVMS X86-64
virsh does not work for me. Seems to find no domains. I created the virtual macine using "Virtual Machine Manager". However I located the xml file in /etc/libvirt/qemu. I made the change and now the system time is CET.
Last edited by joukj on Mon Jun 05, 2023 5:36 am, edited 1 time in total.
-
- Valued Contributor
- Posts: 60
- Joined: Tue Mar 22, 2022 6:47 pm
- Reputation: 0
- Location: England
- Status: Offline
Re: time in OpenVMS X86-64
Then there may be something odd in your setup. I created my VMS machine via VMM though I usually launch it via cockpit. To edit the XML file I used:
Code: Select all
# virsh edit gemini
Just a thought, try
Code: Select all
# command -v virsh
/bin/virsh
Code: Select all
# virsh list
Id Name State
--------------------
# virsh list --all
Id Name State
-------------------------
- XXXXXX shut off
- XXXXXX shut off
- XXXXXX shut off
- gemini shut off
- XXXXXX shut off
- XXXXXX shut off
- XXXXXX shut off
Last edited by martin on Mon Jun 05, 2023 7:36 am, edited 1 time in total.
Martin
- Retired System Manager: VMS/UNIX/UNICOS/Linux.
- Started on a VAX 11/782 in 1984 with VMS 3.6.
-
- Valued Contributor
- Posts: 71
- Joined: Sat Aug 15, 2020 9:00 am
- Reputation: 0
- Location: Cambridge, UK
- Status: Offline
Re: time in OpenVMS X86-64
Interesting. Just checked mine, and found the same.
@Martin - what did you out in for England?
I have:
<clock offset='utc'>
<timer name='rtc' tickpolicy='catchup'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='no'/>
</clock>
Are you running NTP?
Chris
@Martin - what did you out in for England?
I have:
<clock offset='utc'>
<timer name='rtc' tickpolicy='catchup'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='no'/>
</clock>
Are you running NTP?
Chris
-
- Valued Contributor
- Posts: 60
- Joined: Tue Mar 22, 2022 6:47 pm
- Reputation: 0
- Location: England
- Status: Offline
Re: time in OpenVMS X86-64
I changed the UTC to timezone Europe/London:
I'm running chrony on the server (a sort of windows-like replacement for NTP that RH impose) but nothing specific on the VMS VM, unless it has been installed by default. Since this is a hobbyist set up I usually shut down at night, so any drift of the clock on the VM would only be over at most 16 hours.
Code: Select all
<clock offset='timezone' timezone='Europe/London'>
<timer name='rtc' tickpolicy='catchup'/>
<timer name='pit' tickpolicy='delay'/>
<timer name='hpet' present='no'/>
</clock>
Martin
- Retired System Manager: VMS/UNIX/UNICOS/Linux.
- Started on a VAX 11/782 in 1984 with VMS 3.6.
-
- Valued Contributor
- Posts: 71
- Joined: Sat Aug 15, 2020 9:00 am
- Reputation: 0
- Location: Cambridge, UK
- Status: Offline
Re: time in OpenVMS X86-64
Thanks, updated and will see how it goes.
I have set up NTP as a client linked to my router, which offers an NTP service, but as yet it is failing. Need to dig further
Sadly I now have to reboot the VMS guest after an uptime of nearly 33 days! I still remember when they had to extend the field in a show system to allows for > 999 days! We hit that a few times...
Chris
I have set up NTP as a client linked to my router, which offers an NTP service, but as yet it is failing. Need to dig further
Sadly I now have to reboot the VMS guest after an uptime of nearly 33 days! I still remember when they had to extend the field in a show system to allows for > 999 days! We hit that a few times...
Chris
-
- Valued Contributor
- Posts: 60
- Joined: Tue Mar 22, 2022 6:47 pm
- Reputation: 0
- Location: England
- Status: Offline
Re: time in OpenVMS X86-64
I remember getting close to that on an IRIX system (Silicon Graphics' version of UNIX). 998 days as I recall, then the sparkies insisted on some down time for tests of the HV ring. grr, two more days - if only!
Martin
- Retired System Manager: VMS/UNIX/UNICOS/Linux.
- Started on a VAX 11/782 in 1984 with VMS 3.6.
-
- Contributor
- Posts: 21
- Joined: Sat Apr 22, 2023 3:56 am
- Reputation: 0
- Status: Offline
Re: time in OpenVMS X86-64
I had a UPS battery failure (I forgot to swap out on schedule....) take out a switch after 5 years of uptime. (Don't worry, totally secure, it was on the latest firmware version!)

Last edited by gdwnldsksc on Sun Jun 11, 2023 2:46 am, edited 1 time in total.