This went smoothly for me with the exception of one OSD showing an old lockbox key, i think it is a bug - removing the OSD in ceph config fixed it
https://forum.proxmox.com/threads/cehpx-disabled-ceph-key-migration-removing-an-auth-entry.186359/
Kurzer Zwischenstand von mir: Bis Dienstag kein "Rückfall", an dem Tag habe ich dann Updates gefahren und deswegen rebootet. Nu dauert es wieder ein paar Tage. Melde mich, wenn mein Server nächstes Mal spinnt.
I'd recommend trying to reproduce this directly on the PVE host, bypassing the VM. Allocate a raw volume with pvesm alloc and test against the block device directly (or mkfs and mount it).
My suspicion is that LVM doesn't clear extents on...
Hello,
I'm confused.
So I can/must/should (?) use
proxmox-auto-install-assistant prepare-iso... --on-first-boot blub.sh
But I also have to provide it in the answer file?
Also
Does not seem to be correct. You can just use DHCP option or DNS...
I'm a recent convert to Proxmox and have been up and running for about a month. I've noticed over time, that moving a VM to a new node almost always causes the next backup to do a full disk read, and with multiple VMs having multiple TBs of...
That would certainly work I suppose, but this is just a test for a bigger cluster that gets deployed later in which I do not necessarily have that liberty
not sure if we have different script versions but only the final 'confirm' step gave me the next command to run. up until that point during 'dryrun', if anything remained undone on that step, the output would tell you to 'review plan and run this...
On both FSLogix VMs, line up the Event 129 timestamps with Ceph latency on the host for the same minutes. Run ceph osd perf, check the RBD image latency in the Proxmox graphs, and look for slow ops warnings in the Ceph log. If the resets match...
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...
This is what I am currently testing now, leaving all other LXCs and VMs powered off, reducing the allocated memory on the problematic VM
EDIT:
Confirmed, I did in fact, over commit my memory. Decreasing the allocated RAM on the problematic VM...
Sep 24 23:14:15 CMDC01 systemd-journald[544]: Under memory pressure, flushing caches.
That doesn't look good either. What else is running on the machine? The one VM alone shouldn't cause memory pressure.
Here's a theory: You have over committed...
Hi @eatonjb, welcome to the forum.
The first thing I would check is the system log:journalctl. There may be some clues there.
If the customer has to manually power-cycle the server, that may indicate that there are messages on the console. If a...
Tried lowering the allocated vCPU from 12 to 4 to this VM and re-added the GPU on the VM. Still getting the same issue. Currently trying to generate journalctl via an active ssh connection but it's taking a while, vm is still also "starting"...