Hyper-V support: it works but..

[ghost]

There are at least two issues (tested on Hyper-V, Windows 10):

1. When the machine starts (regardless of before or after the OS installation), it shows an IDE warning and hangs for 10-20 minutes then continues normally. This happens 8 out of 10 times. Rarely, it promptly continues. I am not sure what to make of it..
2. When it continues and I login successfully, the network card configuration fails me. I read at least 5 blogs and all the networking related documentation, but failed to configure Hyper-V's virtual switch (both legacy and "modern?"). A tip or two from network ninjas to configure Internet access via Hyper-V switch in SmartOS docs would save some time for rookies like me. :)

@rgardler, @jhowardmsft, @thomas1206, can we get any support/tips from @microsoft or @MSOpenTech here to get SmartOS functional via Hyper-V and Azure (related feedback for Azure: http://feedback.azure.com/forums/216843/suggestions/9341607)?

[rmustacc]

@jasonwilliams200OK what's the warning that the IDE controller is issuing? What device is Hyper-V emulating in this case? Regarding the networking level issues, is that a hyper-v level issue or is it a configuration issue in SmartOS?

[ghost]

@rmustacc,

what's the warning that the IDE controller is issuing?

Here it is:

What device is Hyper-V emulating in this case?

It is something called IDE Controller 0 in Hyper-V jargon. Here is the screenshot of my settings window:

Regarding the networking level issues, is that a hyper-v level issue or is it a configuration issue in SmartOS?

I am not sure. I have FreeBSD 10.2 (configured like this) and Ubuntu 14.0.4 running fine with similar configuration. In the aforementioned screenshot, I have not changed any setting (using defaults) under Hardware > Legacy Network Adapter > Advanced Features.

[backerman]

I get that warning, but my VM boots just fine. Other than adding the legacy network adapter, you also need to enable nested virtualization: (replacing foo with the VM's name)

Set-VMProcessor -VMName foo -ExposeVirtualizationExtensions $true

[ghost]

Also, in the virtual machine's network advanced settings, check Enable MAC address spoofing, so the sub-zones (nested virtualization) also get the internet.

Read it https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/nested-virtualization#networking-options and spent many hours to "figure it out".

Rest of the steps are same as VMWare guide by @AndreasMadsen, https://gist.github.com/AndreasMadsen/3732950#create-nodejs-image. After this, i can ssh from PowerShell (git-posh) on Windows 10 directly to the SmartMachine (or any "sub") zone created from SmartOS hypervisor with key authentication (no password; see other sections of Andreas' gist). Ofcourse we can SSH to global zone (SmartOS hypervisor) with root password as well.