Opened 14 years ago
Closed 8 years ago
#7517 closed defect (obsolete)
W2k3 guest time sync problems (VbglR3GetHostTime failed; rc2=VERR_IO_GEN_FAILURE)
| Reported by: | virtboxguy | Owned by: | |
|---|---|---|---|
| Component: | guest additions | Version: | VirtualBox 3.2.8 |
| Keywords: | timesync | Cc: | |
| Guest type: | Windows | Host type: | Windows |
Description (last modified by )
Virtualbox 3.2.8 running on Windows Server 2003 (32Bit) Guest: Windows Server 2003 (32Bit) GuestAdditions: 3.2.8
The time of the guest isn't synchronized. Especially after a savestate and resume the guest clock is far far away from the host clock. In the Log files I found:
00:01:32.296 Guest Log: VBoxService.exe: Error: VbglR3GetHostTime failed; rc2=VERR_IO_GEN_FAILURE
I've checked this with an earlier version of VIrtualbox (3.1.8, also GuestAdditions downgrades) but observe the same error. An test on Windows 7 host didn't show this behaviour, so I suggest it's an Server 2003 host issue.
Even with "VboxService -vvv" I didn't get more information about the timesync problem.
Attached the vbox.log
The issue is rather critical, cause the clock is so fast out of time, that an workaround with a very shot poll interval of the windows w32time daemon is necessary.
Attachments (4)
Change History (8)
by , 14 years ago
comment:2 by , 14 years ago
Not reproducible. Please attach a VBox.log file taken from a 3.2.10 session.
by , 14 years ago
| Attachment: | VBox_start_guest_than_savestate.log added |
|---|
by , 14 years ago
| Attachment: | VBox_after_resume.log added |
|---|
by , 14 years ago
| Attachment: | Clock_mismatch_after_savestate_and_resume.png added |
|---|
comment:3 by , 14 years ago
Attached the log files for version 3.2.10.
Test: Boot guest with vbocheadless than savestate Wait approx 20 min. and resume
Also attached is the screen shot of the clocks (guest left, host right)
comment:4 by , 8 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → obsolete |
| Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
vbox.log