This is a bit of a cheeky hardware question and a long shot that somebody here has found the same problem.
Proxmox will boot just fine and so will Start9, I can look at Start9 via a terminal window within Proxmox or I can use the IP address that Proxmox gets from my router’s DHCP. All looks great, except I can not attach a volume to setup my Start9?
If I add a physical M.2 SSD to the machine the NIC falls over (I believe something to do with addresses). If I restart the machine and enter the BIOS during boot, I can see that the M.2 SSD is there and looks fine. It appears that conflicting physical addresses are generated on the machine when proxmox spins up Start9 and the NIC disappears. I can not see the device on my router and the Ethernet port on the PC is dead.
Anybody sharp with this sort of hardware/VE/VM conflict that can see a very obvious fix?
I don’t have THE answer, but I didn’t want to leave you hanging here all by your lonesome.
You might want to try following this guide, or at least reviewing it for clues as to other things you could try. It might be worth a shot to reset the BIOS to factory settings, to possibly resolve IRQ or I/O address conflicts.
It seems to be well described here on a Reddit thread. I will stick it on a monitor and keyboard and see if I can find the conflict in the network configuration.
I have been tinkering with Linux since the first Raspberry Pi so I can see what I am supposed to be doing. I will be dead chuffed if I can spin up a Start9 server in a VM in Proxmox.
Thanks again for the link, I had a good read over that just now