Hello,
I recently upgraded to Virtualbox 5.1.26. I brought up my Arch Linux guest and found that the clock was going very fast. I'm talking about 300 times fast!
I run date then ten seconds later I run it again. It says that three minutes have elapsed!
I tried creating a new guest and booting from ISO: archlinux-2017.06.01-x86_64. The same thing happens.
I have now downgraded to 5.1.24. I no longer have this issue.
Extremely fast clock with Windows host, Linux guest VirtualBox-5.1.26-117224-Win
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Extremely fast clock with Windows host, Linux guest VirtualBox-5.1.26-117224-Win
- Start the VM. Not from a saved or paused state. Clean start.
- Take the steps required to generate/observe the error.
- Shut down the VM. Not saved or paused. Completely shut down.
- Right-click on the VM in the VirtualBox Manager. Select "Show Log..."
- Save it (only the first VBox.log), ZIP it and attach it to your response (see the "Upload attachment" tab below the reply form).
- Right-click on the VM in the VirtualBox Manager. Select "Show in Finder/Explorer/Whatever".
- ZIP the selected ".vbox" file and attach it to your response.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
Re: Extremely fast clock with Windows host, Linux guest VirtualBox-5.1.26-117224-Win
I just upgraded back to 5.1.26 r117224 and no longer experience this issue.
Since I last posted I upgraded the Linux kernel from 4.12.3 to 4.12.6 and reinstalled the guest additions. Maybe that did it.
Since I last posted I upgraded the Linux kernel from 4.12.3 to 4.12.6 and reinstalled the guest additions. Maybe that did it.