On Tue, Apr 15, 2008 at 12:47 PM, Nix <[EMAIL PROTECTED]> wrote: > > The problem is NTP adjusting the multiplier part of the clock-provided > > cycles-to-ns conversion function. UML pretended to have a ns clock, > > with a multiplier of 1. When NTP adjusted that down in order to slow > > down the clock, that became 0, and time stopped. > > ... hang on, wouldn't this only happen if you had NTP running on your > guest? (I don't. For that matter, *why* would you have NTP running on > your guest? The guest just gets the time of day from the host anyway!)
Yes, ntpd would be required to trigger (or anything that adjusts mult, but I can't think of anything other than ntpd that would. (Anyway, this would be my doing; I was the only who reported the hanging a few weeks ago, and Jeff had been banging on on my test server, where with a dozen or so guests running concurrently, at least one of them would trigger within an hour. And the reason I have ntpd running on UML guests is I use the same deployment script for both UML guests and physical dedicated servers.) RF ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
