Search results

So you also cant snapshot like in iSCSI?

Hello Community, Does Proxmox VE and Proxmox (subscription wise) support NVMe over TCP Storages? Are there any prerequisites to meet? I dont have any experience in nvme over tcp yet. As far as I know NVMe over TCP requires "nvme-cli" and some manual configuration right? Thanks Jonas

Is there any information about FIPS 140-2 and PVE and if PVE is compliant to that?

Hello. I made a bugreport for this. This error happens, if you were on squid-no-subscription before, updated the pve host BEFORE installing ceph. This causes the pve-base packages of ceph (librados, ceph-common) etc be upgraded to ceph 19.x (squid). If you then switch back to...

Can someone tell why a clipboard is a "local" ressource? Is it something that will be actuall stored on the node in a file? Its really unfortunate that we cant migrate those vms that have clipboard enabled.

What about: rbd -p {pool} ls -l and if theres a image left (at my side there was still a cloud init image for example): rbd -p {pool} rm {image} do you have krbd = 1 (enabled?)

I would go for zfs mirrors, make sure you setup monitoring or at least install zfs-zed after setting up zfs, so you get basic zfs monitoring to @root. Please dont install proxmox on a usb-drive, those will fail very soon, as proxmox is very write intensive on boot-medium.

Hello the attachment is empty (at least on my side). Please post the error and the config of the vm with qm config VMID

Can you check to try to delete the vm again after the first deletion and post the error here? I had something similiar last week and Im in contact with proxmox. Your logs and insights might help fixing this problem.

Try to disable lldp engine: for i in $(lshw -c network -businfo | grep X710 | awk '{print $2}') do ethtool --set-priv-flags $i disable-fw-lldp on done whats the output from: ethtool -m enp2s0f1np1

Thanks! Already updating, keep up the great work! Thanks for the pre-christmas present!

Done: https://bugzilla.proxmox.com/show_bug.cgi?id=5895 had the same issue on a system today.

Seems like your network cards get new names, because you got a new pcie-device. Can you check if you got new names for your nics when placing the new pcie2nvme card init? If so, try to fix them by mac adress: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#network_override_device_names

The vm needs to be running.

Try to use the opt-in 6.11 kernel, in our case, the errors with the broadcom nics disappeared (at least no blacklisting needed anymore). Might be worth a try for you. You might need to fix your fw first, contact your hw vendor for that.

When I compare this to my homeserver. This is different: # You dont have /boot/efi root@pveneo:~# lsblk -o +FSTYPE NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS FSTYPE sda 8:0 0 447.1G 0 disk ├─sda1...

Thanks! Seems like your not booting from an efi system. What is the output of: findmnt /and lsblk -o +FSTYPE

Hello Jona, Whats the output of proxmox-boot-tool status? What about efibootmgr -v? Greetings Jonas

Hi Aaron! Thanks! It did help! Steps: Recover PVE-Quorum, edit Monmap on last node, delete old osds, add 2 new nodes, create mon, create osds, recover.

Can you post your system your configuration and what command you have used? It looks OK, but If your unsure check 'ceph osd perf' while benchmarking to see if one of your nvme is peforming bad. Ceph tell is also useful to see if one nvme is not working as the others regarding performance. But I...