question

MichaelGagnon-4003 avatar image
0 Votes"
MichaelGagnon-4003 asked DaveBarnum-9853 answered

Windows Server 2016 Hyper-V - Boot Error w/ Virtual Switch

I apologize if this question has been asked and/or answered elsewhere, but I cannot find a solution to this issue. When setting up a Debian based system within Hyper-V, it is unable to proceed past the GRUB menu if the VM has a virtual switch enabled. Upon making my selection within GRUB the VM seems to restart and proceed back to the GRUB menu. If the virtual switch is disabled, the VM boots with no issues and then the switch can be enabled after it proceeds past the GRUB menu. Strangely enough if I were to keep attempting to boot past the GRUB menu with the switch enabled it will eventually boot after 10+ attempts at doing so. I have run into this particular issue across two 2016 servers, as well as with various versions of Debian based distros. It is more of an annoyance than anything, however I would like to see if anyone has input on this particular issue. Thanks for any help or input on this situation!

windows-serverwindows-server-2016windows-server-hyper-v
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I have not seen this exact behavior, although I've never had good luck long term with Debian-based distros in Hyper-V.
Since you seem to specifically have problems with the virtual NIC (you keep saying virtual 'switch' but I'm guessing you mean 'adapter', right?), Linux distros usually get upset when the vNIC's MAC changes, which can happen any time that the hypervisor creates the VM's partition. The worst symptom I've ever seen is that the VM won't connect to the network, not this reboot cycle that you're witnessing. The fix is to tell the VM to use a static MAC address, which shouldn't hurt anything even if it doesn't address your problem.
I would dive into the guest system's logs, though. I can't imagine that a maintenance or management process would reboot the system without recording why.

0 Votes 0 ·
DSPatrick avatar image
0 Votes"
DSPatrick answered DSPatrick commented

Might check the build is supported.
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/supported-debian-virtual-machines-on-hyper-v

--please don't forget to upvote and Accept as answer if the reply is helpful--



· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--



0 Votes 0 ·
LimitlessTechnology-2700 avatar image
0 Votes"
LimitlessTechnology-2700 answered

Hello Michael G,

Thank you for your question.

1) Check VM boot method, in BIOS, set first boot order

2) Then start the VM and type F8 and select "safe mode", in safe mode select "Repair your computer"

3) Check if this can help to repair the system.

simple suggestion to fix this: Create a new VM and select generation 2.

If the answer was helpful, please don't forget to vote up or accept as an answer, thank you.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DaveBarnum-9853 avatar image
0 Votes"
DaveBarnum-9853 answered

There are many of us having the same issue, as described here: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1918265

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.