Black Screen Flashing Underscore after install promt CentOS
Posted: 30. Jul 2020, 10:56
I am new to virtual box (v6.1.12), I am trying to create a new virtual pc running centOS 8.2.2004. I set up the machine in an acceptable manner, creating a virtual HDD 20GB, 4GB ram and selecting my CentOS ISO file. I then boot my machine and it makes it to the install promt. As soon as I select install my screen goes black and all I have is a flashing underscore (_) in the top left of the screen. I cannot get beyond this point. Checking my logs I have noticed an error:
Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8e
Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8f
Not really sure what it means, can it not find the virtual hard disk to install to? I will attach full logs. I am running windows 10 which I upgraded from 7, Don't know if that is relevant. Sorry if this is a repeat question but I can't find someone with my exact situation and problem. Virtualisation is enabled and Microsoft hyper V is disabled. Although I have managed to run a kali machine previously on Microsoft hyper v, I just cannot get virtual box to work. I need to use it to participate in my class, so any advice or help would be greatly appreciated.
Guest Log: int13_harddisk: function 02, unmapped device for ELDL=8e
Guest Log: int13_harddisk_ext: function 41, unmapped device for ELDL=8f
Not really sure what it means, can it not find the virtual hard disk to install to? I will attach full logs. I am running windows 10 which I upgraded from 7, Don't know if that is relevant. Sorry if this is a repeat question but I can't find someone with my exact situation and problem. Virtualisation is enabled and Microsoft hyper V is disabled. Although I have managed to run a kali machine previously on Microsoft hyper v, I just cannot get virtual box to work. I need to use it to participate in my class, so any advice or help would be greatly appreciated.
The choice of animal is appropriate: Your guest is running, just really slow. Or it might guru-meditate or crash. This is because a service that uses Microsoft Hyper-V is running on your host PC. Normally Hyper-V blocks Virtualbox. But your PC is of the type and OS where Virtualbox can attempt to run the guest using the Hyper-V engine. This arrangement is still being developed and isn't 100% yet.
) will be seen in the Status Bar.