Some HVM systems don't pickup IP from DHCP

[Pete Howell]

I've noticed on several installs, that the system would not pickup an IP address and had to have one hardcoded.  Does anyone know why this happens?

[Henri KONSTAIN]

Wondering that as well.
MAC and IP are setup on DHCP server but the Qubes install did not 'take' it.

Had to enter manual entries in IPV4 Settings.

[Unman]

You should read the fine documentation on creating HVMs :
https://www.qubes-os.org/doc/hvm-create/

particularly the section on "Setting up networking for HVM domains".

[joev...@gmail.com]

"Even though we do have a small DHCP server that runs inside HVM untrusted stub domain to make the manual network configuration not necessary for many VMs, this won’t work for most modern Linux distributions which contain Xen networking PV drivers (but not Qubes tools) built in which bypass the stub-domain networking (their net frontends connect directly to the net backend in the netvm). In this instance our DHCP server is not useful."

Weird, I have an HVM running solely from a LiveCD built on Thinstation. It picks up DHCP just fine.

[yura...@gmail.com]

On Thursday, November 5, 2015 at 4:00:22 AM UTC, Pete Howell wrote:
> I've noticed on several installs, that the system would not pickup an IP address and had to have one hardcoded.  Does anyone know why this happens?

I had a similar issue when I installed Android 7.1 on Qubes OS, it did not pickup the ethernet connection, but rather kept seeking a wireless connection.
I tried to bind the template of which the Android 7.1 was installed on, to Sys-Net, instead of Sys-Firewall, and it instantly solved the issues.

I'm not too much into as to why and how this works, perhaps it just bypasses the Qubes internal DHCP? Though, if putting another firewall up next to the Qubes default firewall, it should be possible to maintain the overall security, however, without the ability to send files from/to Android 7.1, or whatever else is hosted with HVM. I suspect?