From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MSFd5-0003k2-1K for garchives@archives.gentoo.org; Sat, 18 Jul 2009 19:31:31 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A89F0E030B; Sat, 18 Jul 2009 19:31:29 +0000 (UTC) Received: from smtpout.karoo.kcom.com (smtpout.karoo.kcom.com [212.50.160.34]) by pigeon.gentoo.org (Postfix) with ESMTP id 6BBECE030B for ; Sat, 18 Jul 2009 19:31:29 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.43,227,1246834800"; d="scan'208";a="112505143" Received: from unknown (HELO compaq.stroller.uk.eu.org) ([213.152.39.90]) by smtpout.karoo.kcom.com with ESMTP; 18 Jul 2009 20:31:28 +0100 Received: from [192.168.1.71] (unknown [192.168.1.71]) by compaq.stroller.uk.eu.org (Postfix) with ESMTP id BA15A137D40 for ; Sat, 18 Jul 2009 20:31:24 +0100 (BST) Message-Id: From: Stroller To: gentoo-user@lists.gentoo.org In-Reply-To: <1247906999.224777@rumba> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 (Apple Message framework v935.3) Subject: Re: [gentoo-user] wakeup in virtualbox vm? Date: Sat, 18 Jul 2009 20:31:20 +0100 References: <1247906999.224777@rumba> X-Mailer: Apple Mail (2.935.3) X-Archives-Salt: beb435da-69e7-4c40-a977-aa37ebfd3c4f X-Archives-Hash: c12b6b40a5b55b4a9bf69fb63f286098 On 18 Jul 2009, at 09:49, Konstantinos Agouros wrote: > ... Is there a > way that the guest recognizes the wakeup and than sets the time > using ntpdate > or based on the clock of the host-os which is ntp-synchronized? I doubt it. I know little about virtualisation, so am ready to be proved wrong on that one. I can only think to make a cron job to call an ntp pool on a regular basis. I think there may be a switch to ntp which allows it to make larger jumps. The problem with this is that etiquette would tend to dictate not syncing with the upstream ntp server more than once per hour, so each time you wake it up your clock is going to be wrong for an average of 45 minutes (allowing for Sod's Law). Solution that occurs to me is to run your own local ntp server on another machine which doesn't sleep (or on the host Mac itself) and sync with that; thus your cron job can run every minute to update the clock, and the time it takes to correct after waking will be insignificant. Or sleep or hibernate the guest o/s before sleeping the host. Stroller. PS: shouldn't the correct virtualisation terminology be "host o/s" and "parasite o/s"? Methinks the marketing department were allowed to write the docs on this one.