I have a test cluster of 3 VMs in virtualbox on my pc.
Their IPs changed as follows:
A: 172.16.0.150 > 192.168.100.1 (NOT a gateway)
A: 172.16.0.151 > 192.168.100.2
A: 172.16.0.152 > 192.168.100.2
Now I get the following message when i run 'service ceph-mon@local status':
Processor -- bind...
According to https://pve.proxmox.com/wiki/Roadmap.
intel_iommu defaulted to on in kernels 5.15 based kernels up to pve-kernel-5.15.35-3-pve with version 5.15.35-6. An enabled IOMMU can cause problems with older hardware - issues were reported with, for example, HP DL380 g8 servers, and Dell...
Oddly enough, it seems to have been one specific VM that triggered the crash for me. Granted it was a backup server. Yet, I have 2 other proxmox hosts that also have backup servers on them with no apparent issues.
The link above refers refers to the example below:
# download the image
# create a new VM with VirtIO SCSI controller
qm create 9000 --memory 2048 --net0...
Experienced a CPU softlock earlier today. Xeon E series
Gut feeling says it's perhaps a spike in IO that causes it? I say this because I started relatively large upload to a VM via SSH and the issue happened shortly after - however this could be a total coincidence.
Linux proxm 5.15.30-2-pve...
According to: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_remove_a_cluster_node
It states the following:
Important As mentioned above, it is critical to power off the node before removal, and make sure that it will not power on again (in the existing cluster network) with...
I tried restoring from the GUI. Proxmox version 7.1-7. But from the error message i assume the following command was run on the CLI:
restore vma archive: lzop -d -c /var/lib/vz/dump/vzdump-qemu-208-2022_11_19-16_44_47.vma.lzo | vma extract -v -r /var/tmp/vzdumptmp4009962.fifo -...
I am getting the following 'failed: storage 'backup' does not exist' error when trying to restore a vzdump from another server to my proxmox instance. Moved it from proxmox 6 to 7.
All i want to know is how can i change the storage name in the VMA file from 'backup' to 'local-lvm'?
When I look at the disks I have available on a particular node I see there is the option to initialize them with GPT.
I'm still new and not really clear on how this works. Usually we manually add the extra disks with LVM to the existing VG.
What exactly does the option do?