No subject

tools, causing the time time to ping-pong. I need to investigate further.

It appears to be the kernel time module itself which causes the reset. There
are three available. My kernel was using tsc, and then after the last reset
to 1986 it changed the module to acpi_pm, and since then it appears to not
be doing anything drastic. I can specify the module as a kernel parameter,
so will look into doing that.

Add to the mix various comments about Ubuntu having upgraded to a "tickless"
kernel which may be incompatible with VMWare - and I have to look at doing a
custom kernel compile as well.

But I've had a good weekend which didn't involve anything work related, and
so long as the server is maintaining a rough idea of what day-or-the-week it
is, this can wait will Monday!

Kind regards
Simon

------=_Part_11698_11898206.1204484206173
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Jonathan,<br><br><div><span class="gmail_quote">On 01/03/2008, <b class="gmail_sendername">Jonathan Carter (highvoltage)</b> &lt;<a href="mailto:jonathan at ubuntu.com">jonathan at ubuntu.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I&#39;m not sure if I mentioned this before, but perhaps just to keep things<br> a little sane under those conditions, have you installed an ntp client<br> in the virtual machine?</blockquote><div><br>I did install ntpd (which is both a server and a client, and is recommended to have a better handle on things than putting ntpdate into a cron entry).<br>
<br>From what I&#39;ve read, ntpd can actually have a conflict with the VMWare tools, causing the time time to ping-pong. I need to investigate further.<br><br>It appears to be the kernel time module itself which causes the reset. There are three available. My kernel was using tsc, and then after the last reset to 1986 it changed the module to acpi_pm, and since then it appears to not be doing anything drastic. I can specify the module as a kernel parameter, so will look into doing that.<br>
<br>Add to the mix various comments about Ubuntu having upgraded to a &quot;tickless&quot; kernel which may be incompatible with VMWare - and I have to look at doing a custom kernel compile as well.<br><br>But I&#39;ve had a good weekend which didn&#39;t involve anything work related, and so long as the server is maintaining a rough idea of what day-or-the-week it is, this can wait will Monday!<br>
<br>Kind regards<br>Simon<br></div></div><br>

------=_Part_11698_11898206.1204484206173--