problems with ntp on VMwareServer
- Thread starter thsuniki
- Start date
thsuniki said:
hi,
this is a known problem in vmware with linux kernels 2.6 and no ntp problem.
we had this also with vmware workstation but now it works.
please give me more information:
- vmware server version (exact build number)
- vmware server installed on windows or linux?
- on which hardware? dual cpu?
- do you use one or two cpu for proxmox?
- do you suspended/resume the proxmox?
- version of proxmox? kernel?: type
cat /proc/version
regards,
Martin
VMware Server 1.0.0 build-24927
installed on Windows 2003 Enterprise 5.2.3790 SP1
hardware: Dell Poweredge sc 850 one CPU Xeon 2,8 GHz Dualcore 2,5 GByte RAM
I use 1 cpu for proxmox.
Suspend and Resume don't help only restart helps.
I use proxmox 1.4 original.
Thanks Thomas Fuhrmann
installed on Windows 2003 Enterprise 5.2.3790 SP1
hardware: Dell Poweredge sc 850 one CPU Xeon 2,8 GHz Dualcore 2,5 GByte RAM
I use 1 cpu for proxmox.
Suspend and Resume don't help only restart helps.
I use proxmox 1.4 original.
Thanks Thomas Fuhrmann
thsuniki said:
hi thomas,
thanks for the update.
one comment for suspend and resume: if you suspend and resume you will run into problems - this was an old workaround, but now do not use this. if you suspend and resume, the time is wrong and you will get these errors. for manual synchronize please go to the web configuration (configuration/system/time) and click on "save" to sync. time. reboot is not necessary.
are there other virtual machines running on this server? how many?
Maybe when the server is unser load this will cause the problem. We know this also from virtual server/virtual pc - we have to find workarounds for the problems of vmware and microsoft with linux kernels 2.6.
I will try to reproduce the behaviour with a similar setup, please keep in mind that vmware is still beta.
regards,
martin
Hi,
we have the same Problem with VMware ESX 2.5.2. The Suspend/Resume trick doesn 't work for us, too.
- vmware server version: ESX 2.5.2, build-21059
- hardware: IBM X366, 4 CPU (8 with Hyperthreading), 32 GB-RAM, 16 VMs p
- CPUs for Proxmox: 1 CPU
- Suspend/Resume: doesn't work
- Proxmox version: 1.5 with Hotfix 1.5-1340
As a workaround: can't i use a cronjob (maybe every 5 minutes) to synchronize the time with ntp?
I've tried a "/etc/init.d/ntpdate reload/restart", but it doesn't seems to work.
Any Idea??
we have the same Problem with VMware ESX 2.5.2. The Suspend/Resume trick doesn 't work for us, too.
- vmware server version: ESX 2.5.2, build-21059
- hardware: IBM X366, 4 CPU (8 with Hyperthreading), 32 GB-RAM, 16 VMs p
- CPUs for Proxmox: 1 CPU
- Suspend/Resume: doesn't work
- Proxmox version: 1.5 with Hotfix 1.5-1340
As a workaround: can't i use a cronjob (maybe every 5 minutes) to synchronize the time with ntp?
I've tried a "/etc/init.d/ntpdate reload/restart", but it doesn't seems to work.
Any Idea??
netdate
Hello,
we have currently esx 2.1.2 running and are investigating a upgrade to 3.0.
Our specialist doesn´t currently agree to a upgrade concerning problems with all of our linux based systems. There are several threads in VMWare forums regarding timer and network problems.
so it seams, that we wait along until the situation is rock solif again.
Regarding your timer problem. It should have been fixes in 2.5.2 (according the mails from VMWare), in Fact, they have still problems.
We are running Proxmox on a VMWare-maschine and the suspend/resume trick was investigated by our WMWare specialist
If this dowsn´t help, or if a maschine restarts automatically and can´t be suspended by hand, we have a line in the proxmox /etc/crontab:
55 * * * * root /sbin/netdate tcp 172.29.0.18 > /dev/null
The programm netdate is not delivered by proxmox standard, instead it is pulled out from a old Suse-Linux and placed on proxmox.
The 172.29.0.18 is our timeserver, you can fill in a linux-maschine running ntp-packet as server.
As sugestion to proxmox; if possilbe, compile and deliver the simple netdate-command as standard, as long as the Timerproblems at vmware exist.
I can provide you with the currently running version out of our Proxmox if needed.
Kind regards
-mm-
Hello,
we have currently esx 2.1.2 running and are investigating a upgrade to 3.0.
Our specialist doesn´t currently agree to a upgrade concerning problems with all of our linux based systems. There are several threads in VMWare forums regarding timer and network problems.
so it seams, that we wait along until the situation is rock solif again.
Regarding your timer problem. It should have been fixes in 2.5.2 (according the mails from VMWare), in Fact, they have still problems.
We are running Proxmox on a VMWare-maschine and the suspend/resume trick was investigated by our WMWare specialist
If this dowsn´t help, or if a maschine restarts automatically and can´t be suspended by hand, we have a line in the proxmox /etc/crontab:
55 * * * * root /sbin/netdate tcp 172.29.0.18 > /dev/null
The programm netdate is not delivered by proxmox standard, instead it is pulled out from a old Suse-Linux
and placed on proxmox.The 172.29.0.18 is our timeserver, you can fill in a linux-maschine running ntp-packet as server.
As sugestion to proxmox; if possilbe, compile and deliver the simple netdate-command as standard, as long as the Timerproblems at vmware exist.
I can provide you with the currently running version out of our Proxmox if needed.
Kind regards
-mm-