2
So I've tried the trick from Virtual PC 2007, adding the following section to the vmc configuration file:
<components>
<host_time_sync>
<enabled type="boolean">false</enabled>
</host_time_sync>
</components>
Later someone suggested VPC doesn't want the components level so added this instead:
<host_time_sync>
<enabled type="boolean">false</enabled>
<frequency type="integer">15</frequency>
<threshold type="integer">10</threshold>
</host_time_sync>
When I start up XP Mode (Microsoft Virtual PC) it completely ignores any of these two configuration changes and if I change the clock it's instantly reset to the host time again. I've also obviously disabled the Windows Time service but as it's not joined to a domain or set up with a source it shouldn't be involved anyway.
I need to test an application over a few midnight passes and thought the XP Mode machine would be perfect, so I didn't have to mess with my workstation clock... is there any way to get the VPC guest to not sync time with the host? This is easy in Hyper-V ;p
Yes I tried that first, didn't work - then in some MSDN forum thread someone suggested removing the components part for VPC. Which did no difference. – Oskar Duveborn – 2009-10-02T14:38:59.680