Description of problem: If the CFME VHD actual VM is created with the Legacy Network adapter, the network does not respond externally. You can't SSH into it. Version-Release number of selected component (if applicable): I only tried with 5.5.0.11, but assume it's global. Will check 5.4.4 as well. How reproducible: Create the Hyper-V VM, when you configure the network selection, and you accidentally select the Legacy adapter, it works fine internally but you external access does not work. Steps to Reproduce: 1. Create Hyper-V VM with CFME VHD Image 2. Configure Network for Legacy Adapter 3. Try to SSH in externall. Actual results: Unable to connection. If you open the Console, everything works fine. Expected results: Additional info: I'm pretty certain we just need to document this. This history for this is when Hyper-V first started to work with Linux images, it couldn't handle to network stuff, so they just create a very basic network. It hasn't been an issue for any versions of Hyper-V we support. Here is a recent Tech Note from Microsoft encouraging people to not use this selection. https://technet.microsoft.com/en-us/library/ee941153.aspx
Moving back to the default assignee for now to be considered along with upcoming work.
Closing this bug with the addition of a known issue to the documentation.