Machine disconnects from network when starting VM

MrPlaceholder

New Member
Jan 5, 2025
2
0
1
Hello,

This is my first time posting here but not my first time reading so first of all thanks for all the help. I'm having an issue where I am trying to start a TruenasVM(TrueNAS-13.0-U6.2). When I start the VM the GUI freezes up and if I refresh the page I can no longer access the GUI. I can still access the shell with a monitor connected directly to the machine. Only once I reboot proxmox then I can connect to the GUI once it is up again. I'm also able to check that the TrueNas vm is running via qm list. Once this issue happens I also see that the light on the ethernet port turns off completely on the machine and switch side.

Edit:
For context I am trying to pass a HBA through to this truenas vm. I just learned that if I try to spin up the VM with the hba on the hardware list is when the issue happens. I've just been able to spin up and install truenas without the hba but when i go to reconnect it I have the same issue. I am eager to learn and thank you in advance to anyone willing to lend a hand.

Specs
Processor: Ryzen 7 3700x
Motherboard: MSI B550 Gaming Gen3

lspci | grep Broadcom
Code:
04:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

lspci | grep Ethernet
Code:
2a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)

/etc/network/interfaces
Code:
auto lo

iface lo inet loopback


iface enp42s0 inet manual


auto vmbr0

iface vmbr0 inet static

        address 192.168.1.229/24

        gateway 192.168.1.1

        bridge-ports enp42s0

        bridge-stp off

        bridge-fd 0



#source /etc/network/interfaces.d/*

ip link
Code:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp42s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP mode DEFAULT group default qlen 1000
    link/ether d8:43:ae:9f:cb:97 brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
    link/ether d8:43:ae:9f:cb:97 brd ff:ff:ff:ff:ff:ff
 
Hi,
Edit:
For context I am trying to pass a HBA through to this truenas vm. I just learned that if I try to spin up the VM with the hba on the hardware list is when the issue happens. I've just been able to spin up and install truenas without the hba but when i go to reconnect it I have the same issue. I am eager to learn and thank you in advance to anyone willing to lend a hand.
they might be in the same IOMMU group, meaning you can't passthrough only one of them, see also: https://pve.proxmox.com/wiki/PCI(e)_Passthrough
 
Maybe the pve os disk is on same hba where you do a passthrough on which cannot work.
 
Hi,

they might be in the same IOMMU group, meaning you can't passthrough only one of them, see also: https://pve.proxmox.com/wiki/PCI(e)_Passthrough
Thanks fiona,

I was also able to find more information on: https://pve.proxmox.com/wiki/PCI_Passthrough as well. I did pvesh get /nodes/{nodename}/hardware/pci --pci-class-blacklist "" and it showed the hba controller and a few other things including my ethernet controller share the IOMMU group 15. I assume this would be the root of my issue so I really appreciate the insight. The docs mention needing to have support for ACS (Access Control Services). That is something I am going to poke around my bios for to see if i have support and can enable that. I will also trying moving the hba to the only other available pcie slot. Unfortunately I don't have much time on my hands and with others using connected to the server I can't bring it down now. I will try that out when I can. Thanks again!