Man sieht eindeutig, dass du keine Ahnung hast. Fragen nach Details stellen? Unverschämt. Du könntest ja auch einfach mal die Lösung präsentieren. Würde uns allen das Leben erleichtern. :)
@antiager
Und nun nochmal ein wenig ernster:
Da du ja...
Klar, ist immer ein Gute Idee die KI zu fragen - Menschen brauchen ja auch keine Infos zur Hardware auf der das ganze läuft. Auch nicht wie das konfiguriert ist. ZFS, Sicher läuft.
Meine Glaskugel fragt, ob da vielleicht auch noch ein bischen...
That "Operation not supported (os error 95)" is EOPNOTSUPP, which is a useful clue. The restore daemon VM mounts the backup and the kernel refuses a specific operation on that file, so this looks less like corruption (verification passing...
Good question — this is one of the main safety concerns the plugin was designed around.
SharedLvmThin does not rely on multiple PVE nodes independently modifying LVM metadata at the same time.
All shared-LVM metadata mutations are serialized...
Haven't seen it mentioned in the kernel package Changelog, but the block device statistics regression indeed seems to be solved with 7.0.14-15-pve, at least on the system I tested it on for the past couple of days.
Thanks!
Ah, ha, this is funny. Looking at output from the script, next day/ now that I am reading it and not quite so sleep deprived, it tells me clearly,
"SKIP: NOTE: Expensive checks, like CT cgroupv2 compat, not performed without '--full' parameter"...
I took a look at the code again, and AFAIU (which might be wrong), pvestatd initiates the Balloon changes here:
https://git.proxmox.com/?p=pve-manager.git;a=blob;f=PVE/Service/pvestatd.pm;h=34f9da71fd05ee3c9c5cd1e09d25fe9832eb3364;hb=HEAD#l296...
I think "ask" is putting it too mildly. As I understand it: the memory is simply taken without negotiation or consideration, which can cause OoM-kills inside the VM (if the user sets the minimum memory too low or memory cannot be released quickly...
Once the threshold is reached, the host will ask the VMs to return memory to the host. The VMs need to be able to return that memory! That means, a way to communicate with the host via the Ballooning device, and free memory that can be returned...
Ultimately, although the memory limitation under 7.0 is annoying, running the VM with 10GB allocated is perfectly acceptable for my use case.
On the other hand, the aacraid unbinding issue that I raised initially is a clear regression from 6.17...
Das timeout beim Start kommt meistens daher, dass der alte qemu-Prozess noch nicht sauber weg ist und der scope deshalb blockiert. Deshalb hilft nur ein Host-Reboot. Das Problem ist das Hängen davor. Schau ins journal vom Host für den Zeitpunkt...
Could you please post the contents of frr.conf.local and the contents of the generated frr.conf as well as your /etc/pve/sdn/fabrics.cfg ?
Just to make sure: After editing frr.conf.local, the SDN configuration needs to be re-generated and...
I’ve not tried this here but in my experience with other firewalls, if a connection/state is open adding a drop rule will not close it as the allowed open state still exists. IOW end the ping then enable the rule.
I took a look at the code again, and AFAIU (which might be wrong), pvestatd initiates the Balloon changes here:
https://git.proxmox.com/?p=pve-manager.git;a=blob;f=PVE/Service/pvestatd.pm;h=34f9da71fd05ee3c9c5cd1e09d25fe9832eb3364;hb=HEAD#l296...