I believe there were fixes for this in 3.2
In 3.2+ the VM should start with the right timezone offset
anyway, a forceful "ntpdate"-like update of time should succeed. It probably is a problem inside the guest OS that the NTP client refuses to sync the clock because of too much difference
Are they planning to upgrade?