I dont know how to explain this other than to say on my windows 7 guest, it takes about 10 seconds for the clock to advance 1 second.  I have been dealing with this for a while, but now I want to run some scheduled tasks based on time, and that is obviously impossible.  Eventually the clock will be off by DAYS.  Has anyone else seen this?

Yep. It was worse with some builds of virtualbox than others. I've had the best luck so far with 4.0.10, and I haven't upgraded past that version to test, because everything I need to work pretty much does. Every once in a while I'll have a write failure to a mapped unraid share from my xp guest due to a timeout, but this version is much better than previous versions in that regard as well as the system clock issue. You do have the appropriate guest additions drivers loaded in the guest, and the closed source extension pack loaded on the server, right?

Where might I find those?

 

 

Thanks

Oh, one other thing. Server load had a lot to do with it in my case, I could actually watch the guest clock slow down if I started working the server too hard. The version I'm on right now is much less sensitive to load, but I can still see the effects slightly.

 

The guest additions are included in the base download, the extension pack is a separate download and installed via the command line, typically you add the line to the same set of commands you use to install / start vbox, or if you manually compiled your own package like I did, you can install it before you compress the package and it stays installed when you do the installpkg.

I Created a custom script that will update the time every 1min which, since its slow, probably happens every 5mins.  That will work enough for me.

 

thanks