I am trying to install SLES 12 SP1 with OpenStack 6 on a Hyper-V environment based on Windows 2012R2 latest updates.

In order to expand the OpenStack configuration with nodes a network or PXE boot is inevitable. In Hyper-V this feature is only available using the Legacy Network Adapter.

Doing so everything runs fine (though some installation steps are executed 3 or more times before they are finished) and the Suse OpenStack Console shows that the cloud-admin, control-1 and compute-1 are ok until you stop them, change for example the memory settings to more, and then the Suse VM start but does no longer connect to the OpenStack admin LAN network on the required Legacy Network Adapter.

The message given on the console is net eth0: 21140 transmit timed out, status fc.... resetting.... And this goes on forever.

Because it is an automatic installation of OpenStack nodes root access can only be done by the root user on the cloud-admin node. Since there is no connection nothing can be done on the VM node itself to resolve the issue.

Strangely enough I do not experience these issues on a Dell server but only on a HP Enterprise server, which is very strange because the OpenStack Admin LAN is a internal Hyper-V LAN, thus not connected to a physical network card (Software Only). Both the network and the network card are created by Microsoft and Suse and Microsoft claim full support.

Having nowadays these kind of issues surprises me because MS and Suse have been in a relationship for so long.

Does anyone knows what to do?

Thanks in advance