Search results

2 Henon: are you sure that enables IOMMU in BIOS? On my Gigabyte G292-Z40 with Ryzen CPU I have same problem(intel_iommu=on) until enable the IOMMU in BIOS/UEFI

flotho, the problem was in "Max open files" on PM-host. We solve it with increasing DefaultLimitNOFILE upto 32768: cat /etc/systemd/system.conf.d/open-files.conf [Manager] DefaultLimitNOFILE=32768:524288 the problem is discussed here...

Hi, we have Proxmox cluster with 4 hosts proxmox-ve: 6.4-1 (running kernel: 5.4.128-1-pve) pve-manager: 6.4-13 (running version: 6.4-13/9f411e79) pve-kernel-5.4: 6.4-5 pve-kernel-helper: 6.4-5 pve-kernel-5.4.128-1-pve: 5.4.128-1 ...

hi all! Got this errors on 3 big(only big) VM in PVE 6.4 (128-256Gb RAM) with Ubuntu guest OS, storages: external CEPH cluster (RBD pools) May 31 09:31:13 pm-cal-56-02 pvestatd[3589]: VM 134 qmp command failed - VM 134 qmp command 'query-proxmox-support' failed - unable to connect to VM 134...

Same problem with 6.4: May 31 09:31:13 pm-cal-56-02 pvestatd[3589]: VM 134 qmp command failed - VM 134 qmp command 'query-proxmox-support' failed - unable to connect to VM 134 qmp socket - timeout after 31 retries May 31 09:31:16 pm-cal-56-02 pvestatd[3589]: VM 138 qmp command failed - VM 138...

OK, I found a way to solve this problem: usage "args:" in qm.conf and add line with params for "ens3" Net-card: args: -netdev type=tap,id=net0,ifname=tap100i0,script=/var/lib/qemu-server/pve-bridge,downscript=/var/lib/qemu-server/pve-bridgedown,vhost=on -device...

spirit, thanks for fast and detail answered ! , but the problem we don't have root(or console with sudo) access to many VMs, so we need tell VM owners how to change the adapter name or run a some script to change it... is it possible change PCI number of Net-card on "virtual hardware" level?

Hallo! I test migration from Ovirt to Proxmox with keep existing VM rbd images on CEPH storages. Problem: In oVirt all Centos VM have type of Netcard "VirtIO" - same as I set in Proxmox, but in oVirt it use default name for interface "ens3" but in Proxmox VM got name "ens18" So network is...

opsss.... I just noticed that I didn't remove part "ceph.client." from the keyring-file name !!! after fixing this pool connected!!! tuxis - thanks for help!

it is CEPH 12, but I think this not issue - 'rbd ls' from shell works fine

I tested this option too - and got error: rbd error: rbd: listing images failed: (95) Operation not supported (500)

Hi! I install my Proxmox 6.3 3-nodes test cluster (ceph version 14.2.16) and have a problem with external CEPH-pool connection: I put ceph.conf in '/etc/pve' next make symlink in '/etc/ceph' root@tentakel4:/etc/pve# ls -l /etc/ceph/ total 6 lrwxrwxrwx 1 root root 18 Feb 2 11:30 ceph.conf ->...