ML310e Gen8 V2 with Server 2016 Hyper-V

[Tony1044]

This server, despite being on the Microsoft HCL as certified for Windows Server 2016 (see https://www.windowsservercatalog.com/item.aspx?idItem=5034ab7d-e864-6747-9e38-df974f397de7&bCatID=1282 ) )doesn't seem to support the Hyper-V role.

I have tried the following scenarios (note, all firmware is as up to date as possible):

Installed Windows Server 2016 using intelligent provisionsing;

Installed Windows Server 2016 without intelligent provisioning;

Installed bare metal Hyper-V 2016.

In all cases, I've tried using both the drivers shipped on the provisioning AND the latest drivers from the HPE supprot site.

In every case, the role will go through the initial add, will reboot, reboot again and hang at the Windows logo with a spinning wheel.

Safe boot works but removing the role from there results in it saying feature couldn't be completed at which point it reboots back into the same hung condition.

A logged boot shows the last file loaded to be FASTFAT.SYS. Renaming this in both the DLL cache and SYSTEM32\drivers folder just shows the same point with the exception that FASTFAT failed to load.

In a nutshell the server doesn't appear to be in any way comaptible with Hyper-V 2016 OR I just have a bad one.

Wouldn't mind if anyone else could test and let me know their results.

Oh it's the onboard BL210 Array Controller with a pair of 1TB SATA drives (all checks out in good condition). Same results whether using the very latest 2016 compatible driver or the older 2012 R2 driver.

This is just a lab machine but I'm now at the point of not wanting to risk 2016 on it, trashing my lab down the line if I added another role that turns out to screw the OS over. :(

[Tony1044 · Accepted solution]

I refused to give up on this and I've stumbled on the following from HPE in this document:  https://www.hpe.com/h20195/V2/getpdf.aspx/4AA5-5841ENW.pdf

Table 5. Known issues and workarounds.

Description of issue

ML310e Gen8 v2 will not boot after enabling the Hyper-V role.

Workaround/Solution

Ensure ROM settings are configured with VT enabled and VT-D disabled before enabling the Hyper-V role.

I am in the process of trying and will report back any success or otherwise.

[Tony1044]

Very happy to report that disabling VT-d has worked.

Anyone else having the issue, remember you need to power the server off when changing VT settings in the BIOS or the don't take - a reboot is not sufficient.

[chessome]

Funny, I also had this exact problem with the same server.

Thank you very much for your efforts, problem succesfully solved by disabling VT-D!

Btw, what is the drawback of disabling vt-d?

[skywardsolution]

Wow thank you, this worked like a charm. 

[Shayban]

worked for me. thanks.

[josemonteiro]

Worked for me =) 

[PegasoBlanco]

Perfecto !!!!, tuve ese problema durante algunos dias, sin contar que tuve que sufrir para llegar a este punto, porque el servidor no tenia instalado el Intelligent Provisioning, lo instalé y no funcionó, duré dando muchas vueltas, actualicé el firmware de ILO, BIOS y nada, hasta que tuve que pedir soporte a HPE, resultó que habia otro firmware más actualizado, funcionó y ahora con ese problema de Windows que no pasaba del logo con raid 1 para Hyper-V nooo!!, pero con este foro logré solucionar mi problema !!!!, muchas gracias a todos !!!

Perfect !!!!, I had this problem for a few days, without counting that I had to suffer to get to this point, because the server did not have Intelligent Provisioning installed, I installed it and it did not work, I spent many laps, I updated the firmware of ILO, BIOS and nothing, until I had to ask HPE for support, it turned out that there was another firmware more updated, it worked and now with that Windows problem that did not go beyond the logo with raid 1 for Hyper-V nooo !!, but with this forum I managed to solve my problem !!!!, thank you very much to all!

[Odirlei]

Thank you, my friend! I'm from Brazil and I went through this for Problems. Thank God we have the collaboration of dedicated people with you to help. I leave my reservation here to be more voluntary as our friend. Hugs, I'm from Cuiabá in the Brazilian Midwest. If I come here, I'll pay for the beer if I drink.

Att.

Odirlei Araujo

[RobertoAzon]

Hi, I can not find the VT-D option in the bios. Could you tell me where you are? you have posivilidad to send me a screenshot ??
thank you very much for being crazy trying to solve this issue

[RobertoAzon]

Hola, no encuentro la opcion que hay que deshabilitar en bios, no veo nada de VT ni VTD, he actualizado firmware a version 2018. he actualizado el inteligent y nada, cuando instalo el rol de hyper-v se reinicia y se queda colgado en el logo de windows hay que tener una version especifica de firwmare??

un saludo Gracias!

-----------------------------

Google Translation

Hello, I can not find the option to disable in bios, I do not see anything from VT or VTD, I have updated firmware to version 2018. I have updated the inteligent and nothing, when I install the role of hyper-v it restarts and hangs on the windows logo must have a specific version of firwmare ??

a greeting Thank you!

-----------------------------

[LeandroT]

Pude acceder al server nuevamente desactivando el VT-D

Primer punto, porque anda en 2008 R2 y no en 2016.

Segundo punto, el VT-D hace que uno pueda virtualizar un sistema operativo de 64 bits dentro de otro, por ende a virtualizar solo cosas de 32, ¿porque?, si el server lo compramos, si cobran contratos de mantenimiento, porque si desde el 2017 que se reporto van 2 años y nadie de HP hizo nada

La verdad me da mucha verguenza que den un soporte como el que dan y la verdad que no es barato, cada vez mas convencido de comprar menos HP.

Tercer punto, dan el tema como solucionado!!!!, no esta solucionado!, podemos hacer que ande pero no con toda la funcionalidad, de que solucion me hablan, de una para salir del paso, pero de solucion esta muy lejos de serlo.

Disculpen mi bronca, pase muchos dias peleando con esto, y la verdad es una verguenza la solucion.

[LeandroT]

I was able to access the server again by deactivating the VT-D

First point, because you walk in 2008 R2 and not in 2016.

Second point, the VT-D makes it possible to virtualize a 64-bit operating system inside another, therefore to virtualize only things of 32, why ?, If the server we buy it, if they charge maintenance contracts, because if from the 2017 that is reported go 2 years and nobody from HP did anything

The truth gives me a lot of embarrassment that give a support as they give and the truth that is not cheap, increasingly more convinced to buy less HP.

Third point, give the subject as solved !!!!, is not solved !, we can make it walk but not with all the functionality, what solution they talk to me, one to get out of step, but the solution is far from being so .

Excuse my anger, spend many days fighting with this, and the truth is a shame the solution.

[MarceloLinck]

This is tragic due to the lack of willingness in two years not to have a plausible solution with or without support.
Step by the same problem and I do not see how solved a pie solution.

[LawrenceH]

Thank you Tony.

Can confirm disabling VT-d AFTER installing HyperV role and no boot worked on Server 2016.

I now wonder if this would have worked on Server 2019 that I removed thinking it was the issue.

I had also tried updating BIOS, ILO, and RAID Drivers.

Thanks Again!

Lawrence

[ashwin pai]

We had the same issue on  Server 2019.  I even called MS and tech suggested to check with HP so I searched and found this article.  I can confirm that after  disabling VT-D  server camed up  with Hyper-V role installed.

Thank you!

[Daren Friday]

Worked here

Thank you

Daren

[Josias1]

worked for me too... Thanks