H
henrik.beckman
Guest
[EDIT] corrected verion numbers to the correct ones [/EDIT]
Hi,
We have serious issues after upgrading from 2.4 to 2.5, roughly a week after the upgrade we started getting clock source unstable error messages and performance tanked.
We are running our gateway in vmware 4.0 single CPU and 8GB RAM, the hardware beneath the hypervisor is plenty enough.
We have experimented with various clocksources apart from TSC but to no avail, latest has been the paravirtualizer but we still loose all performance shortly after boot.
Typical boot is normal until proxmox loads, the machine then gets slow and stays that way for atleast a few hours before it usualy gets unresponsive, a reboot in this state takes 45 minutes.
Please advice ASAP, We can provide our customer ID if needed.
For obvious reasons we can communicate through our normal email channel.
Sincerly
/Henrik
Hi,
We have serious issues after upgrading from 2.4 to 2.5, roughly a week after the upgrade we started getting clock source unstable error messages and performance tanked.
We are running our gateway in vmware 4.0 single CPU and 8GB RAM, the hardware beneath the hypervisor is plenty enough.
We have experimented with various clocksources apart from TSC but to no avail, latest has been the paravirtualizer but we still loose all performance shortly after boot.
Typical boot is normal until proxmox loads, the machine then gets slow and stays that way for atleast a few hours before it usualy gets unresponsive, a reboot in this state takes 45 minutes.
Please advice ASAP, We can provide our customer ID if needed.
For obvious reasons we can communicate through our normal email channel.
Sincerly
/Henrik
Last edited by a moderator: