time drift back in Windows 2008 R2 VM

tincboy

Renowned Member
Apr 13, 2010
466
4
83
I've a six cpu core VM with Windows 2008 R2,
It's time drift back about 10 minutes every 2 hours,
pveversion -v:
Code:
pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-15
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

vm config:
Code:
args: -rtc-td-hack
args: -no-kvm-pit-reinjection
boot: cd
bootdisk: ide0
cores: 6
ide0: local:5150/vm-5150-disk-1.raw
ide2: local:iso/Windows_2008_r2.iso,media=cdrom
memory: 6144
name: vmname
net0: rtl8139=BE:4E:88:90:EE:16,bridge=vmbr980
ostype: other
unused0: local:5150/vm-5150-disk-2.raw
 
update to latest, you can also try the packages from pvetest (including KVM 1.1 stable).

and remove these two lines:

args: -rtc-td-hack
args: -no-kvm-pit-reinjection
 
I've update the server with below commands, are these enough or I should restart the server or stop and start the VM?
Code:
apt-get update
apt-get upgrade
 aptitude full-upgrade
 
Last edited:
I've upgrade the proxmox, but the qemu version didnt change
Code:
pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.1-68
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-12-pve: 2.6.32-68
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-16
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

Is this enough?
 
/etc/apt/sources.list
# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian squeeze pvetest



# pveversion -v
pve-manager: 2.1-12 (pve-manager/2.1/be112d89)
running kernel: 2.6.32-12-pve
proxmox-ve-2.6.32: 2.1-71
pve-kernel-2.6.32-11-pve: 2.6.32-66
pve-kernel-2.6.32-13-pve: 2.6.32-71
pve-kernel-2.6.32-12-pve: 2.6.32-68
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.92-2
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.8-1
pve-cluster: 1.0-27
qemu-server: 2.0-45
pve-firmware: 1.0-17
libpve-common-perl: 1.0-28
libpve-access-control: 1.0-24
libpve-storage-perl: 2.0-21
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.1-4
ksm-control-daemon: 1.1-1
 
I dont want to use unstable packages on my production server but I need to solve the time drift back issue,
I this issue gone by
pve-qemu-kvm: 1.0-9 ?
 
Just follow the suggestions - pvetest is not needed to resolved this issue.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!