Recent content by sumsum

thanx for this hint. My old ProLiant DL360p Gen8 Lab Server did not came up after the upgrade to Proxmox 8. It just got stuck during the booting process. Booting in Recovery Mode worked, but no network. After removing the ntpsec package as you commented, did the trick. I dont know why ntpsec...

We run KVM vm‘s with icecast Streaming servers since years and serve several 1000‘s of listeners. No issues with network

Das kann ich nur bestätigen, die Backups via CIFS funktionieren tadellos. Bei NFS muss wirklich irgendwo ein Bug drin sein.

Just to sum up what we've tested right now Backup on Local Storage works more or less. we have no high cpu spikes but sometimes interrupts NFS Target with nfs vers=4.2 high CPU spikes and issues as described NFS Targets with nfs vers=4.1high CPU spikes and issues as described we played with...

We experience here the same issue on 6.1-2 (running kernel: 5.3.13-1-pve), pve-manager: 6.1-5 (running version: 6.1-5/9bf06119) disabling the guest agent or/and limiting I/O does not help. The Backup Storage used is nfs4 The Spike in Windows & Linux VM's goes up to 100% for several seconds...

I‘m Aware that the following won‘t delivers the answer. But in Debian Terms : „As always, it will be released when it’s ready” ;)

It May be a OVH Issue and Not related to Proxmox. A while back I experienced the Same Problem. 4 out 8 Linux VM‘s lost Connection. Before they were Running over month w/o problems. My Solution, regenerate new MAC addresses for those failing VM‘s. The OVH Network/Switch just lost the MAC address...

We are Running a few Proliant G7 Servers with the same NIC and PVE 5.3. so far w/o any issues. Have you tried to Check/replace the network cables? Or Even change the Switch Port.

und nach der "Name Resolution..." Meldung kam etwas ähnliches wie : "Das Schließen einer UDP-Socket mit der lokalen Portnummer "56327" im Prozess "888" dauert länger als erwartet. Die lokale Portnummer ist möglicherweise erst nach Abschluss dieses Vorgangs wieder verfügbar. Der Grund hierfür...

Wie sieht das Ereignis Protokoll der Windows Vm zum Zeitpunkt des Crash aus ?

Happy Birthday ! All the best for another decade. By the way, where‘s the Cake? Post a picture of the cake for evidence

Do they realy Shut down or just disconnect the Network ?

for my part, the Windows10 VM is running on Default (kvm64)

Same situation here on a Lab Installation. A Mix of Debian, Centos VM's and one Windows 10 VM. while the Linux VM's run stable, the Win 10 VM get regular CRITICAL_STRUCTURE_CORRUPTION Blue Screen Error (0x00000109) after a few hours in operation. Before running PVE 4 and upgraded to PVE 5. the...

We run several HPE ProLiant DL360 G9 with RAID Controller P440ar/2 GB FBWC on Proxmox 5. No issues so far.