Did a stupid thing and looking for hel in resolving my issue.
I deleted a running remote (pve) in this file, /etc/proxmox-datacenter-manager/remotes.cfg and after a while wanted to re-add the same remote.
In the PDM gui i tried to create the same...
Hmm, early on we had one time where VMs stalled out but I thought it was user error and/or tied to using "nodown" at the time. Since then we've used noout, norebalance, norecover, and the two no-scrubs when doing maintenance. If we're rebooting...
A very small advice, before rebooting a Ceph node, stop OSDs manually, more info here(why):
https://bugzilla.proxmox.com/show_bug.cgi?id=7827
https://forum.proxmox.com/threads/vm-processes-stall-when-rebooting-adjacent-node.185178/#post-862294
Thank you, yes I have a RAID controller for the RAID 6 array. I thought proxmox might be able to utilitize an NVME for caching but sounds like I'm at the wrong layer my raid controller would utilize it. Thanks for pointing me in the right direction!
Of course, follow the guides for Ceph posted previously. But in general for PVE updates we:
1) in Ceph set checkboxes for:
(any node > Ceph > OSD > Manage Global Flags)
nodeep-scrub
noout
norebalance
norecover
noscrub
2) run ha-manager...
That did not make much difference but "pci=pcie_bus_perf" this. For future reference to others:
1- CPU Type: Host and NUMA enabled
2- Check the nvme afinity and put it in CPU Affinity under CPU settings (---for d in /sys/bus/pci/devices/*/nvme...
It is on q35 otherwise it dos not let me do pcie option on the passthrough. this last change did it.
Read Test:
Jobs: 32 (f=32): [R(32)][2.5%][r=9684MiB/s][r=2479k IOPS][eta 01m:57s]
Jobs: 32 (f=32): [R(32)][4.2%][r=9630MiB/s][r=2465k IOPS][eta...
you can also use the vmware pvscsi option to emulate there scsi controller to so the VM should not know its running on KVM in proxmox rather than VMware
Building on what Francois asked -- that error "unable to get monitor info from DNS SRV with service name: ceph-mon" is a DNS resolution issue. When you don't specify the cluster or monitors explicitly, the Ceph client library tries to...
@vociferous, I apologize for the tardy reply. This was indeed the culprit! Great find and thank you!
In the interim, I have switched to console mode to mitigate it however it would be great to have this addressed upstream, or, as you said, just...
Check your VM is on chipset Q35 if not change it to Q35.
Your lspci show your drive MaxPayload is 128 bytes at the moment but the drive supports 512. so lets add "pci=pcie_bus_perf" to the vm kernel command line
ASPM policy is default try...
Here is the ouput for the affinity:
root@test1:~# for d in /sys/bus/pci/devices/*/nvme; do echo "$(dirname $d): NUMA $(cat $(dirname $d)/numa_node)"; done
/sys/bus/pci/devices/0000:c1:00.0: NUMA 0
/sys/bus/pci/devices/0000:c3:00.0: NUMA 0
I am...
Can you post the actual Windows build numbers for the affected VMs? Run winver or check Settings > System > About inside the guest. The specific build matters because Microsoft changed how VBS and Hyper-V enlightenments behave in certain updates...