Interesting MP Server Hosting Bug/Issue

[Velusion]

Oh yea... I spent hours going through the white papers, etc. Most of the timekeeping issues involve the clock going slower... only a few talk about it going faster, and I tried those fixes. After lots of research I came upon the AMD dual-core windows patch - and that fixed it with the OS.

I don't know what Dom3 is looking at when it keeps time, so I'm not sure whose fault it is really. Probably VMwares or AMD... unless Dom3 keeps track of time in some non-standard way. It certianly doesn't sync up with the OS (which makes sense).

[lch]

Just checking, so you have tried to finetune your settings manually like described in point 3 in that web page?

Edit config.ini, adding the lines described below.

The example presented here assumes that the host computer has a maximum speed of 1700MHz. The first line is the most important one. It should be your host computer's maximum speed in KHz—that is, its speed in MHz times 1000, or its speed in GHz times 1000000.

host.cpukHz = "1700000"

host.noTSC = "TRUE"

ptsc.noTSC = "TRUE"

The second and third lines enable a mechanism that tries to keep the guest clock accurate even when the time stamp counter (TSC) is slow.

[Velusion]

lch said:
Just checking, so you have tried to finetune your settings manually like described in point 3 in that web page?

Yep, using those switches now. I'm probably going to remove them now that the AMD patch seemed to fix the OS just to see if it makes a difference.

[alexti]

Velusion, I'm not sure how relevant it is, but there's a problem in VMWare that borks the timer functions on Linux on 64-bit AMD (dual core). The patch you have mentioned doesn't solve this problem. As of couple of months ago, there wasn't any solution to that.