Hey all. Having issues with Time drifting on CentOS 5.3 x64 guests. CentOS 6 time is working great. Any ideas or input as to why this is happening?
Thanks,
Adam
Thanks,
Adam
Time Drift CentOS 5.3
- Thread starter adamb
- Start date
This seems to happen with ntp enabled and disabled. I can set the clock back to the correct time with NTP but it still drifts. I am guessing its something simple but can't seem to dig much information up.
Starting to think this has to do with the cpu type of the CentOS5 guests. Currently it is set to the default (qemu 64). Not sure what a Intel Xeon X5650 falls under.
Here is pveversion -v
root@proxmox1:~# pveversion -v
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
pve-kernel-2.6.32-7-pve: 2.6.32-60
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
Here is the config output
root@proxmox2:~# cat /etc/pve/nodes/proxmox1/qemu-server/104.conf
boot: dcn
bootdisk: ide0
cores: 3
ide0: drbd0:vm-104-disk-1
memory: 8000
name: Webmail
net0: e1000=F2:E7:A3:FC:F4:09,bridge=vmbr1
onboot: 1
ostype: l26
sockets: 1
I do not remember an issue with timekeeping in your version but you got a old one. update your box, especially KVM 1.1 has a lot of fixes. this is a general recommendation.
vmid.conf:
I see nothing related to timekeeping but using virtio for net and block is recommended for Linux. but I don't know if your kernel got the virtio drivers, 5.3 is pretty old. latest centos 5.x kernel got virtio. you will find an article describing the move to virtio on RHEL pages (e.g. on access.redhat.com)
vmid.conf:
I see nothing related to timekeeping but using virtio for net and block is recommended for Linux. but I don't know if your kernel got the virtio drivers, 5.3 is pretty old. latest centos 5.x kernel got virtio. you will find an article describing the move to virtio on RHEL pages (e.g. on access.redhat.com)
Tried a few different cpu types. Same issue, read quite a bit about the cpu type effecting system time.
Updating a production box scares me a bit. Anything I should look out for?
Correct me if I am wrong. I should be able to Migrate all VM's to node1, update node2, reboot. Migrate all VM's to node2, update node1, reboot.
Is this the correct command to update each node "aptitude update && aptitude full-upgrade"? I appreciate all the help and assistance!
Last edited:
Good point, but still need to get something like that setup.
Can you confirm for me that this is the correct method for updating?
"aptitude update && aptitude full-upgrade"
yes. We also provide update instruction for each release, see:
http://pve.proxmox.com/wiki/Proxmox_VE_News
Appreciate the input!, I added that to my notes.
The update fixed the time issues I was seeing in CentOS 5.3 x64 VM's.
The update fixed the time issues I was seeing in CentOS 5.3 x64 VM's.
Hi,
this is because centos 5.3 don't have kvm-clock (old kernel)
http://s19n.net/articles/2011/kvm_clock.html
But indeed,kvm 1.1 have a lot of bugfix in the differents timer.
this is because centos 5.3 don't have kvm-clock (old kernel)
http://s19n.net/articles/2011/kvm_clock.html
But indeed,kvm 1.1 have a lot of bugfix in the differents timer.