qm monitor vmId show mem and qm monitor show vmId tlb timeout / freeze

[uriel]

Hi,

By testing all qm monitor function I find that:
show mem, lead to a timeout, a make all qm monitor call failed for a few minutes.
and
show tlb make my VM freeze

the Host is an AMD Ryzen based PC running an up to date Proxmox 6.2.11.

Note: the VM have a passthrough gpu.

Uriel.

 

[wolfgang]

Hi,

AFIK there is no "show" command in the current version of pve 6.2-11.
did you mean "info"?

 

[uriel]

oups, yes you are right it's a info command.

 

[wolfgang]

We can't reproduce this here with Ryzen Gen1 - Gen3.
How large is your VM memory?

 

[uriel]

my QEMU config: /etc/pve/nodes/node/qemu-server/2000.conf

agent: 1
balloon: 0
bios: ovmf
bootdisk: virtio0
cores: 16
cpu: host
efidisk0: local-lvm:vm-2000-disk-1,size=4M
hostpci0: 09:00,x-vga=on,pcie=on,romfile=current.rom
machine: q35
memory: 16096
name: win10
net0: virtio=E2:58:8C:C5:36:A4,bridge=vmbr0,firewall=1
numa: 0
ostype: win10
scsihw: virtio-scsi-single
smbios1: uuid=46991989-aeb1-4f32-a658-b2cd2cd8442e
sockets: 1
tablet: 0
vga: none
virtio0: local-lvm:vm-2000-disk-0,cache=writethrough,size=70G
virtio1: SATA:vm-2000-disk-0,cache=writethrough,size=200G
vmgenid: 776f7fe5-7fb2-4b2e-831d-5fcbff93556c

I remove a [setup] block and parent: setup line
I do not know why proxmox gui add some parent parameter in my config each time I use the GUI.

Storage info of the host:
-1 nvme SSD
-1 SATA SSD
-1 CIF mount from my NAS for template / iso

df -h extract:

/dev/mapper/pve-root 94G 57G 33G 64% /
SATA 57G 5.7G 52G 10% /SATA

 

[wolfgang]

I guess the problem is the PCI passthrough.
You have memory regions on HW so this memory is not meant to be dumped.

 

[uriel]

I guess the problem is the PCI passthrough.
You have memory regions on HW so this memory is not meant to be dumped.

Thx for this answer, but as I sayed in my initial question, I do not need this feature, I just see that It make the guest vm crash.

I fix the issue on my side by not allowing this call. (in all case)

In the best scenario this call should be deny in this case. But I'm sure there is a lot of more useful change to make before.

So, have a nice day