linux as vmware guest: delayed sys time after sleep mode
in [General Linux]
|
Prev: +++ NFL Jerseys On Sale at www.ajerseys.com
Next: ===Christian Louboutin - www.vipchristianlouboutin.com
From: Hank M. on 4 Aug 2010 01:47 Hello, I use linux guest vms with vmware on a desktop pc. After putting the host to sleep and waking it up again the guests continue to run fine but have their system time way behind. ntpd does not help since the gap to the current time is too large. hw clock is correct, manually running hwclock -s is too awkward. has anyone solved or automated this? thanks, bye Hank
From: Kenny McCormack on 4 Aug 2010 08:06 In article <i3auu1$8mv$1(a)news.albasani.net>, Hank M. <nomail(a)nomail.com> wrote: >Hello, > >I use linux guest vms with vmware on a desktop pc. >After putting the host to sleep and waking it up again the guests >continue to run fine but have their system time way behind. >ntpd does not help since the gap to the current time is too large. >hw clock is correct, manually running hwclock -s is too awkward. > >has anyone solved or automated this? > >thanks, bye > >Hank The stock answer to this is: Install VMWare tools. So, assuming you've done that, then one must note that, contrary to VMWare's claims, the "VMWare Tools" are not perfect. A couple of comments from my own experience, neither of which directly address your question: 1) Although I haven't tested this in a long time, my experience was that you had to suspend the guest (using the VMWare console) before putting the host to sleep. If you didn't, then the guest would crash. Does this agree with your experience and practice? 2) I've never liked the VMWare Tools anyway, so I don't use them. I built my own system for (constant) time-sync between guest and host. I might be convinced to share it with you. Anyway... It sounds like you ought to be able to convince NTP to do this - probably just some setting somewhere. But I don't use NTP either (since I use my own system). -- Faced with the choice between changing one's mind and proving that there is no need to do so, almost everyone gets busy on the proof. - John Kenneth Galbraith -
From: Hank M. on 6 Aug 2010 07:04 On 04.08.2010 14:06, Kenny McCormack wrote: > In article <i3auu1$8mv$1(a)news.albasani.net>, Hank M. <nomail(a)nomail.com> wrote: > The stock answer to this is: Install VMWare tools. have them installed however not investigated deeply. > So, assuming you've done that, then one must note that, contrary to > VMWare's claims, the "VMWare Tools" are not perfect. > > A couple of comments from my own experience, neither of which directly > address your question: > 1) Although I haven't tested this in a long time, my experience was > that you had to suspend the guest (using the VMWare console) > before putting the host to sleep. If you didn't, then the guest > would crash. Does this agree with your experience and practice? no, in fact guests ran fine after wakeup. suspend and resume seems to solve my problem on quick judgement but is still clumsy to use. > 2) I've never liked the VMWare Tools anyway, so I don't use them. I > built my own system for (constant) time-sync between guest and > host. I might be convinced to share it with you. > would be interesting to read what you do. > Anyway... > > It sounds like you ought to be able to convince NTP to do this - > probably just some setting somewhere. But I don't use NTP either (since > I use my own system). thats very true. search led me to the "tinker panic 0" config option. seems to allow ntpd to quickly correct the time by large deltas. fine with me until further notice. thanks Hank
From: Kenny McCormack on 7 Aug 2010 09:16
In article <i3gq7b$136$1(a)news.albasani.net>, Hank M. <nomail(a)nomail.com> wrote: >On 04.08.2010 14:06, Kenny McCormack wrote: >> In article <i3auu1$8mv$1(a)news.albasani.net>, Hank M. ><nomail(a)nomail.com> wrote: > >> The stock answer to this is: Install VMWare tools. > >have them installed however not investigated deeply. If the tools are installed fully correctly, then it is supposed to do automatic "all-the-time" clock sync (between the guest and the host). >no, in fact guests ran fine after wakeup. suspend and resume seems to >solve my problem on quick judgement but is still clumsy to use. We may be talking at cross-purposes here - there may not be sufficient bandwidth on Usenet for me to explain what I meant. So, let's let it go... >> 2) I've never liked the VMWare Tools anyway, so I don't use them. I >> built my own system for (constant) time-sync between guest and >> host. I might be convinced to share it with you. >> > >would be interesting to read what you do. I may put it on a web site at some point (or I may not...) My system is basically a homebrew NTP (yeah, re-inventing the wheel, blah, blah, blah) >> Anyway... >> >> It sounds like you ought to be able to convince NTP to do this - >> probably just some setting somewhere. But I don't use NTP either (since >> I use my own system). > >thats very true. search led me to the "tinker panic 0" config option. >seems to allow ntpd to quickly correct the time by large deltas. fine >with me until further notice. A happy ending... -- "We should always be disposed to believe that which appears to us to be white is really black, if the hierarchy of the church so decides." - Saint Ignatius Loyola (1491-1556) Founder of the Jesuit Order - |