core-admin/dom0/pm-utils/01qubes-sync-vms-clock

#!/bin/sh

. "${PM_FUNCTIONS}"

sync_qubes_vms_wallclock()
{
/usr/bin/qvm-sync-dom0-clock
DATE=$(date)
echo
echo "Syncing VMs clock to: $DATE"
qvm-run --all --exclude=`qvm-get-clockvm` -u root "date -s \"$DATE\""
}

case "$1" in
        thaw|resume) sync_qubes_vms_wallclock ;;
        *) exit 0 ;;
esac
Dom0: sync wallclocks in all vms upon resume from S3 sleep This is really a workaround, until Xen implements proper suspend/resume mechanism for notfying DomUs about system-wide S3 sleep. See this thread for more details: http://lists.xensource.com/archives/html/xen-devel/2010-07/msg00037.html 2010-07-06 16:22:34 +02:00			`#!/bin/sh`

			`. "${PM_FUNCTIONS}"`

			`sync_qubes_vms_wallclock()`
			`{`
dom0: pm-utils: 01qubes-sync-vms-clock: run qvm-sync-dom0-clock before syncing clocks on other VMs (#433) ... instead of just $(date), which caused problems when Dom0 clock got desynced somehow. 2012-01-30 11:00:35 +01:00			`/usr/bin/qvm-sync-dom0-clock`
Dom0: sync wallclocks in all vms upon resume from S3 sleep This is really a workaround, until Xen implements proper suspend/resume mechanism for notfying DomUs about system-wide S3 sleep. See this thread for more details: http://lists.xensource.com/archives/html/xen-devel/2010-07/msg00037.html 2010-07-06 16:22:34 +02:00			`DATE=$(date)`
pm-utils: 01qubes-sync-vms-clock: cosmetic fix for nicer output 2010-07-08 12:45:33 +02:00			`echo`
Dom0: sync wallclocks in all vms upon resume from S3 sleep This is really a workaround, until Xen implements proper suspend/resume mechanism for notfying DomUs about system-wide S3 sleep. See this thread for more details: http://lists.xensource.com/archives/html/xen-devel/2010-07/msg00037.html 2010-07-06 16:22:34 +02:00			`echo "Syncing VMs clock to: $DATE"`
dom0: pm-utils: 01qubes-sync-vms-clock: exclude clockvm when syncing clocks on resume 2012-01-30 13:09:20 +01:00			qvm-run --all --exclude=`qvm-get-clockvm` -u root "date -s \"$DATE\""
Dom0: sync wallclocks in all vms upon resume from S3 sleep This is really a workaround, until Xen implements proper suspend/resume mechanism for notfying DomUs about system-wide S3 sleep. See this thread for more details: http://lists.xensource.com/archives/html/xen-devel/2010-07/msg00037.html 2010-07-06 16:22:34 +02:00			`}`

			`case "$1" in`
			`thaw\|resume) sync_qubes_vms_wallclock ;;`
			`*) exit 0 ;;`
			`esac`