you stole my username
here is something i said on reddit:
if the distro has xen drivers installed but no qubes packages, you need to use manual ip config.
if the distro doesnt have xen drivers installed you can use dhcp config.
if you use dhcp config for the hvm since it does not have xen drivers, but you will connect to sys-whonix, you will need a new netvm(proxyvm) in between the hvm and sys-whonix
windows probly works because #2
ubuntu probly doesnt work because #1. ubuntu has xen drivers which disable emulated nics…and that breaks dhcp. you have to manually assign ips that qubes tells you to if you dont have the qubes networking packages
basicaly if you use a hvm that doesnt have xen (windows), you can use dhcp BUT you need another proxyvm in between if you want to connect to sys-whonix.
i havent figured out why yet. but when a hvm uses dhcp it always receives a def gateway of 10.137.0.1 from the dm domain. when it tried to do internet it looks for 10.137.0.1. qubes is configured that the netvm always responds with ‘hey im 10.137.0.1’ even when its not because they all have mac addr fe:ff:ff:…:ff. for some reason that doesnt work with sys-whonix directly. so you have to create another qube that provides net and is cofigure with sys-whonix for upstream.
…or just use manual config which tells windows who the real gw is (sys-whonix) so it doesnt have to ‘search’ for it with imagniary addresses like 10.137.0.1 (qubes never assigns a netvm this ip)
edit: qubes os likes to make qubes believe they are the only host on the network by assigning netmask 255.255.255.255. this is fine when you have a qube that has qubes pkgs. but for a hvm like windows, just give it a 24 bit 255.255.255.0 to keep stuff simple