I think any Cloud hosting service / provider, offering a Proxmox VE instance setup, should offer a full suite of available & appropriate initial options covering storage, networking, firewalling & exposure in their setup. I do not consider a...
Joining in with the following observations; over a year since last driver refresh, there have been driver updates but no binaries released until now. Upstream changelogs minimal to say the least. This is Not the fault of Proxmox team. We know...
Hi,
ich würde auf jeden Fall vorher Backups machen. Durch das Umstellen vom OS-Typ ändern sich nämlich Teile der virtuellen Hardware und Windows ist da manchmal sehr pingelig. Hängt aber vom konkreten Fall ab. Vielleicht auch vorher bei einem...
Thanks for getting back to me! I set the endpoint URL to what it is in the post you linked, and rebooted just for good measure. The GC job now took 25 seconds as opposed to 5 seconds the first time I ran it, then it took 5 seconds again. Please...
That's basically where I got stuck...it had seemingly ignored the WARN entries up until that point, so an additional one line output about "cannot continue until all WARN issues are resolved" would be user friendly, especially for those doing it...
just went through the key migration this morning. it was a sudden unexpected surprise after doing a simple apt upgrade from 9.2.10 to 9.2.20 (which included the newer 19.2.6 ceph i think) after rebooting around half my cluster i saw the...
I read about rgw_sigv4_insecure but was not sure where to set it. Thanks.
I just finished fixing our S3 implementation about 10 minutes ago and found exactly this change being the culprit for 403 errors. The issue with our s3 client...
I would recommend the following (on ThreadReaper)
1. remove the systemd-boot package
2. fill in /etc/default/grub using the one from the working node, but adapt "GRUB_CMDLINE_LINUX_DEFAULT" to get the correct kernel cmdline
3. clear out...
In my case, I didn't have to modify any PMG config files on install, so it should survive PMG updates (and in fact has for almost a year). If you followed standard install, you should be in the same boat.
If you did modify a config file...
At least the extra file space is sparse, i.e. not actually consuming space on disk:
filename: vm-5130-disk-1.qcow2
file length: 421 GiB (452044718080 bytes)
337G /var/lib/vz/images/5130
Discarding as others suggested is of course worth a try.
We found GitHub issue #756. Our symptoms are very similar, especially:
Event ID 129
vioscsi/viostor
affected volume becomes unresponsive
VM reboot restores operation
Ceph-backed storage
However, the github issue is marked as resolved and we...
Hello,
this is a German blog from Dennis Schröder of the installing procedure "Proxmox VE auf dem Raspberry Pi 5: So läuft die ARM-Version..."
Please see:
#...
Resolved: GRUB rescue prompt after kernel update — root cause was multi-PV LVM boot
System: Proxmox VE 9.2, UEFI boot, pve VG originally spanning two physical volumes (/dev/sda3 + a second NVMe partition, added earlier via vgextend/lvextend to...
I would reinstall with LVM root on (1) disk, and create a separate LVM space for the 2nd disk. Restore LXCs/VMs from backups
It's generally not recommended to extend LVM over multiple PVs unless you have RAID underneath. Personally I would not...