Marek Marczykowski
|
109cdf7935
|
dom0: use qubes-prefs in scripts (#421)
Instead of qvm-set-* and qvm-get-*
|
2012-02-07 03:07:43 +01:00 |
|
Marek Marczykowski
|
2483409f53
|
dom0/pm-utils: sync clock based on dom0, and then try to sync from network (#435)
|
2012-02-01 18:23:17 +01:00 |
|
Marek Marczykowski
|
59e7041554
|
dom0/pm-utils,dom0-update: sync clock using new qvm-sync-clock tool (#435)
|
2012-02-01 17:39:21 +01:00 |
|
Joanna Rutkowska
|
bb70eb270f
|
dom0: pm-utils: 01qubes-sync-vms-clock: exclude clockvm when syncing clocks on resume
|
2012-02-01 17:39:21 +01:00 |
|
Joanna Rutkowska
|
ddd71a6490
|
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-02-01 17:39:21 +01:00 |
|
Joanna Rutkowska
|
8c4ac4326f
|
pm-utils: 01qubes-sync-vms-clock: cosmetic fix for nicer output
|
2010-07-08 12:45:33 +02:00 |
|
Joanna Rutkowska
|
115df6f1af
|
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:32:50 +02:00 |
|