I've just got a reply from Veeam support:
I 'm a bit astonished that 9.2.x is still not supported by Veeam. However, I updated the plugin (one needs to uninstall the current one before) and will try if that fixes the problem. I will let you know!
like I said - this is a global problem the last few months (well, a bit longer now already I guess). anything with dynamic content that basically allows endless possibilities to query (like git forges, forums, ...) are hit particularly hard...
the behaviour is intentional and a security feature - each newly created snapshot is only allowed to re-use chunks of the previous snapshot, for other chunks it has to "prove" that it actually has that chunk by uploading it. PBS (as opposed to...
Yes, that is to be expected, the IPAM tab in Datacenter is what you pick when you choose `pve` as the IPAM option, otherwise the external plugin is used.
What's the exact sdn config?
cat /etc/pve/sdn/zones.cfg
cat /etc/pve/sdn/vnets.cfg
cat...
Thanks for the reply! I admit I hadn't investigated the agent due to it working with no errors for years...
root@redacted[~]# qemu-ga -V
QEMU Guest Agent 5.0.1
root@redacted[~]# qemu-ga -D
[general]
daemon=false
method=isa-serial...
Thanks for the reply! I admit I hadn't investigated the agent due to it working with no errors for years...
root@redacted[~]# qemu-ga -V
QEMU Guest Agent 5.0.1
root@redacted[~]# qemu-ga -D
[general]
daemon=false
method=isa-serial...
Die 5. HDD kannst Du als Reserve drin lassen und einen striped mirror aus den 4 Stück erstellen. RAIDZ/5/6 (parity) ist für VM Performance generell die schlechteste Wahl.
Hallo geordi,
leider gibt es keinen offiziellen Weg die Weboberfläche hier anzupassen. Du könntest CSS overrides über deinen Browser probieren, allerdings kann dies bei einem Update leicht kaputt gehen und andere unvorhersehbare Verhaltensweisen...
I can confirm similar behavior on a 4-node cluster running Proxmox VE 9.2.2.
Cluster hardware:
2x Intel Xeon E3-1220L v2
1x AMD EPYC 7551P
1x AMD EPYC 3251
Only the EPYC 3251 node is affected.
Symptoms:
Progressive performance degradation...
I can confirm similar behavior on a 4-node cluster running Proxmox VE 9.2.2.
Cluster hardware:
2x Intel Xeon E3-1220L v2
1x AMD EPYC 7551P
1x AMD EPYC 3251
Only the EPYC 3251 node is affected.
Symptoms:
Progressive performance degradation...
Hi,
I can't recall the actual message that prompted me to reapply the SDN config. I can remember it was show under SDN/Status for all my VLANs/VNets, while the Fabric just was showing the usual "ok". Also there was no error message during the...
Hi,
I wasn't able to reproduce this on my cluster.
A few questions from my side:
How did this look in the UI? Did you get an error on apply? Where there any pending changes? We didn't deprecate anything in the fabrics yet AFAIK.
You could try...
I've seen only parallel suspends which run into timeout, I use those most of the time.
Attached the log, interesting might be:
May 23 23:26:31 pve pveproxy[1089089]: got inotify poll request in wrong process - disabling inotify
...
May 23...
Example: I unplugged wrong OSD disk, how to reactivate it?
1. Stop OSD process ( systemctl stop ceph-osd@XX ) and unmount OSD dir ( umount /var/lib/ceph/osd/ceph-XX )
2. If OSD use encryption I need to close crypto mapper
cryptsetup close...
Hallo geordi,
leider gibt es keinen offiziellen Weg die Weboberfläche hier anzupassen. Du könntest CSS overrides über deinen Browser probieren, allerdings kann dies bei einem Update leicht kaputt gehen und andere unvorhersehbare Verhaltensweisen...
I'll try to reproduce the issue on my own server.
Aside from pveversion and VM config file, which commands shall I execute and which log files are required?
I remember that the logs, accessible from GUI are very short when hibernation fails...