The key thing is that you must use a "machine"id of "pc-1.3" or it will say your hardware is not supported. Additionally you MUST use a virtio disk or you will get a ks_pre.sh error as soon as the install starts (a look at logs will show it can't find a disk). This is funny because even though the OS finds the disk and an fdisk -l shows it, it looks like the script looks for a /dev/vda device (virtio) and nothing else, so if you didn't use Virtio as you........

Idid a systemctl restart networking and it broke Proxmox VM connectivity! #proxmox is the problem after restarting the network the tap devices go to disabled state [2230884.919905] vmbr0: port 7(tap118i0) entered disabled state [2230884.948864] vmbr0: port 8(tap122i0) entered disabled state [2230884.972748] vmbr0: port 6(tap119i0) entered disabled state [2230885.004745] vmbr0: port 5(tap117i0) entered disabled state [2230885.03673........

You can find many ways to specify the VLANin your network configuration but Ifind this is the simplest and quickest. In this case we are talking about a bridged adapter "vmbr0" but it works even if you just had a normal non-bridged interface. The key here is that in vmbr0 you'll notice there is no IP address. We just specify "manual". Below it is a similar stanza for "vmbr0.58" in this case 58 represents the VLAN (change........