Ubuntu stuck asking to remove installation medium on Hyper V install

Question

I'm trying to install 16.04 on a virtual machine on my Windows 10 laptop. Everything goes fine with the install with the only variance from defaults is the usage of third party video drivers. I click ok to reboot and it then tells me to remove the installation medium and press enter. It's a virtual machine install, how do I do that without removing my keyboard?

Solution 1

Here is the latest update... I'm going to conclude that there is something amiss with 16.04. Noting what user542100 commented: ( Running on a Surface Pro 4. Ubuntu 14.04 works fine, but 16.04 just sits there after entering my password. Hyper-V manager shows this taking around 24% of the CPU, so something is going on. ) I decided to download the 14.04 ISO and create a VM using that one.

Not only did it respond when I hit "Enter" when prompted, but when it restarted and I logged in, the desktop loaded (in the 16.04 build, "turning off" the VM and then starting it got me to the login screen, but once I logged in, the desktop never appeared and a crash report started flashing so quickly I couldn't read it.

The only problem that remains is that there is no network connection even after I entered the static IP information that is required for my network (a unique IP address, not that assigned to the physical NIC). I will start a new thread for that one... also, going to full screen doesn't fill the screen, but, again, a new thread for that one.

So it appears to me, the ball is in Ubuntu's court.

Solution 2

Taken from https://www.eightforums.com/tutorials/5078-hyper-v-create-linux-virtual-machine-windows-8-a.html:

When Ubuntu reboots and stops telling Please remove installation media, click Stop to stop and close vm. This ejects the installation media

and now Restart vm, and you will be able to log in

Solution 3

After installing GnomeUbuntu 16.04 iso on Hyper-v went to the Hyper-v/ Configuration Settings/Bios and moved IDE to 1st boot position. It worked for me.

Comments

[CogitoErgoBibo]

Thanks! I did try that... it booted to the login screen and then just hung after I logged in. Eventually it starts flashing this error report, but it comes and goes so quick I can't read it.

[CogitoErgoBibo]

I am trying this now.. Delete the VM then recreate. Before starting it, I clicked on settings and pushed IDE up in the bios boot order above "CD". That should solve the reboot problem, however, I'm thinking my "hang" problem has to do with the fact that I'm running on this machine which has high-end NVidia graphics: dell.com/us/p/alienware-17-r3/pd

[CogitoErgoBibo]

"When Ubuntu reboots and stops telling Please remove installation media, click Stop to stop and close vm. " this doesn't happen. It just sits there at "Please remove.." and the attempt to solve the problem using the steps above did nothing.

[CogitoErgoBibo]

Sorry... it didn't. This: "When Ubuntu reboots and stops telling Please remove installation media"... never happens. It never "stops telling Please remove installation media". The only thing I can do is to click stop... this isn't a solution.

[Sinscary]

Click stop than close hyper-v and restart again.

[CogitoErgoBibo]

The problem I have with this is that it's not a "fix"... it's a workaround at best. The "Fix" would be what I stated above... "Click Settings and move IDE above CD before starting the VM". However, even that doesn't "Fix" the problem. The OS should allow the user to click enter... if the medium wasn't removed, it should prompt the user "Run from installation medium or boot to hard disk", or something like that. Ubuntu needs to address this. I'll start another thread about the hang after reboot.

[CogitoErgoBibo]

Update: I left the VM window open and after about 20 minutes it actually rebooted. (crazy timeout! :) ) I saw some error message "intel_rapl: no valid rapl domains found in package..." and waited another 5 minutes, then I saw a login screen. I am sorry Nitesh, but "Click stop than close hyper-v and restart again" isn't a fix. I think this forum should add a state: "mark as workaround". I do appreciate the info and time... but I am a diehard user advocate and a "Fix" is something that makes things work as expected, a workaround is a way to make what should happen, happen, when it doesn't

[Sinscary]

Well i am glad atleast things "workedaround".

[Sinscary]

Try to uncheck enable dynamic memory option

[Mike Fourie]

This may help askubuntu.com/questions/759987/…

[Pieter De Bie]

Fyi, I have the same problem on an actual laptop.