Dear list, I have an openSUSE system running in 3.1.8. When I start this system at a certain time using Headless I can see in /var/log/messages in the VM the startup messages with their timestamp. This timestamp is ahead of the real time in the timezone. The host is having it hardware clock at UTC and its timezone is +0200. I configured the guest also with a UTC "hardware clock" and its timezone is also +0200. Below you see the timestamp change, these lines are adjacent in the log.
Jul 3 04:10:01 ktmhost kernel: bootsplash: status on console 0 changed to on Jul 3 02:23:37 ktmhost sshd[3956]: Invalid user jim from 114.247.18.8 The startvm command has been given at Jul 3 02:21:02 +0200, so the full boot time is about 2 minutes, after which the guest clock is OK. The problem is that I want to start shortly after the boot a cronjob. I know at what time the VM will be started so I want to start the cronjob 10 minutes after starting the VM. However this does not work. I can see some timestamps in the above log before the time the cronjob should start, however this job is not started. I think the problem is in the initial time that the clock is showing when the cron daemon is started which is after the time the cronjob should start. So I wonder why the initial time during boot and system start is having this odd relation with the real time. It is not UTC nor the time in the timezone. -- fr.gr. Freek de Kruijf ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
