I am new to the Forum and I’ve got a Problem thats stressing me out since yesterday.
I recently discovered OpenSuse and Virtualbox. I want to learn ABAP and for that I need a SAP-System.
So the main Problem I got is with the Virtualbox. At first it had conflicts with Hyper-V and missing Vt-x. After deactivating the feature Hyper-V it worked.
I started the OpenSuse Leap 15.0 Iso and finally got to the Menu:
I don’t know what the problem is. I have never experienced that. However, here’s what I would try in that situation.
On the initial boot screen (with the menu), when you move the cursor down to “Installation”, a box should show up (toward the bottom of the screen) for “Boot Options”. I would enter “edd=off” into that box, and see if that helps.
I haven’t used VirtualBox (I use KVM for virtualization). But I assume that there is some way that you can force the virtual machine to the Off state, so that you can start again to try this.
Your screenshot displaying “Probing EDD…” suggests that you’re somehow booting your HostOS or your system is still accessing your raw disk drives because there is no such thing when accessing only virtualized disk files.
Are you sure your screenshots are only when you start the Virtualbox installation process, click on the button with the green triangular arrow?
The other issue may be when you have more than one virtualization enabled, and this applies no matter if you are on Windows or Linux, or any combination of virtualization technologies… Only Virtualbox does not start services on boot, all others (AFAIK) do start services which have to be manually stopped before you can launch a different virtualization. In MSWindows, I would generally recommend opening the Services applet and going down the entire list looking for any service that might have anything to do with virtualization. I don’t know what services might apply specifically to Hyper-V, but this is what I do to disable VMware when running Virtualbox.
The alternative of course and probably more certain is to simply uninstall Hyper-V by going into your “Control Panel > Programs and Features > Turn Windows Features on or off” – And if you decide to run Hyper-V later, re-enable at that time.
Thank you for your reply. Excuse my late response, I wasn’t at work at that point anymore.
I tested it with Ubuntu and Kali Linux and its the same Problem there. It gets stuck at the blinking Cursor and thats it.
I turned off Hyper-V in the Windows Features and all its Sub-Features. I had two Issues before I even got into the Installation.
The first one was “VT-x not found” and after I checked everything in my BIOS and have not found VT-x but Virtualization on ENABLED and VT-d ENABLED. Afterwards I went into my Settings and turned Off VT-x in my VirtualBox settings. That erased the Problem with VT-x but made appear another one.
“Raw-mode is unavailable courtesy of Hyper-V in VirtualBox”
I solved this Problem by going into the Windows Features and turning off the Hyper-V Services. This didnt do the trick because after a long time of googling I figured out, that I need to activate a Features called “Windows Hypervisor Platform”.
After that I was able to reset all Settings in VirtualBox including VT-x because now it was working. The ISO booted properly and I got to the Menu you saw on the screenshots and there I am still right now…
I feel like its a simple Fix but I cant figure it out. I try to do this on my Workplace Laptop which is a little restriced for Installations. I cant just install everything from the scratch again because that would need a Ticketreuqest for Adminrights and so on.
I set the RAM on 2000 and 8000 …
Graphics Memory on 128…
Virtual Storage to 100GB…
I enabled and disabled everything possible in the settings and still no success…
I hope you can somehow help me with those information I gave you.
Tsu I think you were right. I suppose, that my VirtualBox got no writing rights on my Work-Laptop. It is restricted via the System and therefore Virtualbox stucks there, because it got no right to write altough its a Virtual Disk.
I will try it with Adminrights and then we will see what happens.
As I suspected but in a different way, you haven’t disabled Hyper-V.
Apparently a new feature has been added to Virtualbox, which is to not just emulate but actually use the SystemOS’ native hypervisor, and MSWindows Hyper-V is the first with VMware likely to follow sometime in the future.
So, you actually have two options how to proceed… to either work out your EDD problem (But I see you’ve already tried to turn off EDD support in your boot options although I don’t know if you’re doing it correctly) or re-inspecting why Virtualbox is still detecting Hyper-V if you think you’ve disabled or uninstalled it.
Although this integration with Hyper-V is “alpha” since a year ago, there has been enough attention that it might be a little more stable now… But note that if Hyper-V is detected, there isn’t likely any way to disable to run the Virtualbox hypervisor… Using the Hyper-V hypervisor is supposed to be automatic, and you should see the icon as described (Hey, maybe try clicking on the icon to see if it can be disabled that way?)
Otherwise, you may want to post your problem to the Oracle Virtualbox forums since your EDD problem is likely something they would want to know about and address…
Doublechecking what you’re doing to disable Hyper-V, the entry should look like the following encircled in red… the box should be unchecked. And, if you just checked or unchecked the box, I’m sure you’ll have to reboot to apply changes regardless whether you’re prompted or not.
