Recent content by casalicomputers

Hello everyone I was wondering what is the proper way to setup the hardware controller. We usually setup Proxmox on Dell servers with the PERC H755 Hardware Raid controller which can be configured with different read/write policies, Usually we configure our storage on raid 5 or raid 10 virtual...

Update: after a bit of research I think that the error in the dmesg logs has little if anything to do with the issue I described. Thats related to a bug (?) of the i40e driver, as I understand it: at first the interface tries to filter the vlan tag of the packets instead of just passing it on to...

Hello everyone, Currently I've got my networking setup like this: The machine running PVE has two NICs: one is the default embedded NIC that came with the motherboard, a Broadcom NetXtreme Gigabit Ethernet (BCM5720), which is a RJ-45 dual-port, 1 Gigabit Ethernet Controller, the other is an...

Hello I'm posting a bit late, but I was having the same issue, the machine worked fine, but the system dropped the noVNC console connection during the init process, right when mounting /. So the DSM Virt Manager noVNC console kept getting stuck at the stage posted in the screenshot above. At...

Hello, welcome to the forums! I dont think there is any issue with proxmox, in my case the issue was that the cards had an unsupported sfp+ module. I've used the card on two different pve installations now, in the first case the issue was that we simply plugged the card in the pcie slot of an...

Hello everyone! I can confirm that this was also the issue for us... The colleague that installed the card didn't put it in the right slot :rolleyes: So the issue was on our side and not with the proxmox or the card, Sorry but I'm taking over for the colleague that started the thread, do I...

Unfortunately no, we tried to install intel updated ixgbe (5.18), but it is still not detected. Look like that card is just incompatible. We will update the thread if we found a solution.

Goodmorning, we are installing Promxox with ZFS on an old server to use it as replica on the main one. To be precise the server is a Dell R730 with an Intel(R) 10G 2P X520 Adapter installed and detected on the IDRAC, but not on Proxmox. Reading on the internet, look like this card is managed...

We applied the change, we do not get that warning anymore, but problem still persist, all the vms become unresponsive while moving large files into the vm, even tho when we stop the transfer the system started working again after some time, so look like there is still an improvement. We applied...

qm config 100: agent: 1,fstrim_cloned_disks=1 boot: order=scsi0;ide2;net0 cores: 4 ide2: none,media=cdrom memory: 4096 meta: creation-qemu=7.0.0,ctime=1680183385 name: dc01 net0: virtio=72:01:F6:5C:1B:5A,bridge=vmbr0 numa: 0 onboot: 1 ostype: l26 parent: pre_update scsi0...

We just discovered this that could be helpful, while the vm was hanging, ALL the Linux vms inside the same node logged this in the dmesg: [ 2055.223604] INFO: task btrfs-transacti:399 blocked for more than 120 seconds. [ 2055.224006] Not tainted 6.1.0-9-amd64 #1 Debian 6.1.27-1 [...

Hi, we have a Proxmox server built with ZFS that hosts various vms, including one that is a Debian Bookworm with a Samba domain controller. We experienced a weird problem where if we transfer data greater than 5GB, the vm could completely hang and become unresponsive, even from the built-in...

We did a lot of cold boot for testing and the problem didn't appear anymore, so i think it's pretty safe to say we solved the problem. Thanks for the support! Have a nice day.

We are still testing, but we think we got the problem. While gathering the info through "smartctl" we noticed some disks didn't match the disks they are supposed to be. Look like during cold boot, the system indexes the disks in a different order. I have created the HDD pool using devices as...

We tried to disconnect-reconnect a disk to get the log pattern into the dmesg and we found what happened before the disk failed during the boot phase. Just before the disk disconnection we have this in the dmesg output: [ 178.579018] x86/split lock detection: #AC: CPU 0/KVM/61253 took a...