Search results

Hmm... This is the only one issue with Proxmox until now, so I would really like to continue using it :) Why are you so unhappy with Proxmox? Any other problems? cu Peter

Hi, I also get this error on my cluster after upgrading it from Proxmox 1.x to 2.0 The only workaround to re-enable the NFS shares (at least for some days) is to restart the nfs server on my NAS (Synology). How ever, after the time the error comes back, the nfs shares seams to be offline again...

Ok, I will try an update during any weekend. OK, I see... This may reduce the CPU usage, but will not fix the problem with the Nahelem CPU bug... I will be back as soon as I have any news. Thanks + regards, Peter

Hi Tom, please find the details below: > 1. pveversion -v pve1:~# pveversion -v pve-manager: 1.9-24 (pve-manager/1.9/6542) running kernel: 2.6.32-6-pve proxmox-ve-2.6.32: 1.9-43 pve-kernel-2.6.32-6-pve: 2.6.32-43 qemu-server: 1.1-32 pve-firmware: 1.0-13 libpve-storage-perl: 1.0-19 vncterm...

Hi, I'm running a Windows SBS 2011 (Windows Server 2008R2 64 Bit) as a KVM-VM on a Proxmox 1.9 server. Mainly the system works fine but from time to time the VM runns into a Bluescreen with stop code 0x00000101. The Bluesreen usually happens during the daily vzdump backup job. After...