Virtualbox Issues
-
@brandon220 said in Virtualbox Issues:
@jmoore Was virtualization enabled in the BIOS?
Yeah it was. I tried to check all the obvious things. Of course, both iso's worked perfectly using vmware player. So not sure what it going on with it but it has me feeling pretty dumb lol
-
@jmoore said in Virtualbox Issues:
So for context I usually use kvm for everything and I have no issues, ever. Today however I was on a Windows machine and wanted to load opensuse on it so thought I would try virtualbox for the heck of it. Could not get it to work. Played with every setting I could find. Then tried fedora32, still the same thing. Both just hang before it actually starts installing. So I tried the free vmware player and both work flawlessly with the defaults.
So does anyone get virtualbox to work after pointing it to an iso with the defaults?
I have, but I don't use virtual box often enough. There should be configs built for these in VBox though.
Are you using VBox 32 or 64 bit on what Windows version?
-
@DustinB3403 said in Virtualbox Issues:
@jmoore said in Virtualbox Issues:
So for context I usually use kvm for everything and I have no issues, ever. Today however I was on a Windows machine and wanted to load opensuse on it so thought I would try virtualbox for the heck of it. Could not get it to work. Played with every setting I could find. Then tried fedora32, still the same thing. Both just hang before it actually starts installing. So I tried the free vmware player and both work flawlessly with the defaults.
So does anyone get virtualbox to work after pointing it to an iso with the defaults?
I have, but I don't use virtual box often enough. There should be configs built for these in VBox though.
Are you using VBox 32 or 64 bit on what Windows version?
- Just downloaded today. Got both iso's today also. It is not a big deal but it is just weird. I assume I have to configure something within virtualbox because I tried the straight defaults first.
-
@jmoore said in Virtualbox Issues:
@DustinB3403 said in Virtualbox Issues:
@jmoore said in Virtualbox Issues:
So for context I usually use kvm for everything and I have no issues, ever. Today however I was on a Windows machine and wanted to load opensuse on it so thought I would try virtualbox for the heck of it. Could not get it to work. Played with every setting I could find. Then tried fedora32, still the same thing. Both just hang before it actually starts installing. So I tried the free vmware player and both work flawlessly with the defaults.
So does anyone get virtualbox to work after pointing it to an iso with the defaults?
I have, but I don't use virtual box often enough. There should be configs built for these in VBox though.
Are you using VBox 32 or 64 bit on what Windows version?
- Just downloaded today. Got both iso's today also. It is not a big deal but it is just weird. I assume I have to configure something within virtualbox because I tried the straight defaults first.
To ask a dumb question are you building these vms with the template or trying to configure it yourself?
-
@DustinB3403 said in Virtualbox Issues:
@jmoore said in Virtualbox Issues:
@DustinB3403 said in Virtualbox Issues:
@jmoore said in Virtualbox Issues:
So for context I usually use kvm for everything and I have no issues, ever. Today however I was on a Windows machine and wanted to load opensuse on it so thought I would try virtualbox for the heck of it. Could not get it to work. Played with every setting I could find. Then tried fedora32, still the same thing. Both just hang before it actually starts installing. So I tried the free vmware player and both work flawlessly with the defaults.
So does anyone get virtualbox to work after pointing it to an iso with the defaults?
I have, but I don't use virtual box often enough. There should be configs built for these in VBox though.
Are you using VBox 32 or 64 bit on what Windows version?
- Just downloaded today. Got both iso's today also. It is not a big deal but it is just weird. I assume I have to configure something within virtualbox because I tried the straight defaults first.
To ask a dumb question are you building these vms with the template or trying to configure it yourself?
Not a dumb question at all. I mostly followed the template (guided mode) I think it is called.
Type = Linux
Version = openSuse 64 bit
Selected to create virtual hard disk now
Changed the memory to 4096 mb (this machine has 16 gb)
Increased disk space to 20gb
Selected vdi for the type of image
Selected dynamically allocated
Changed video memory to 32 mb
Went to storage tab and added my iso to the virtual optical disk drive
Hit start>>>i see a splash screen and it looks like it tried to load the kernel. Then just stops completely without going to next step -
Try disabling Hyper-V.
I use virtualbox all the time. It's great and super-easy to use.
-
@Pete-S said in Virtualbox Issues:
Try disabling Hyper-V.
I use virtualbox all the time. It's great and super-easy to use.
I have never enabled it
-
@DustinB3403 Somehow my brain skipped the sentence with VMWare Player....
-
-
@jmoore said in Virtualbox Issues:
@Pete-S said in Virtualbox Issues:
Try disabling Hyper-V.
I use virtualbox all the time. It's great and super-easy to use.
I have never enabled it
I found out when installing Docker Desktop for users that Hyper-V gets enabled and Virtualbox stops working. I'd double-check Hyper-V.
-
@scottalanmiller said in Virtualbox Issues:
@jmoore said in Virtualbox Issues:
Selected vdi for the type of image
This is suspect.
That is the default that it uses for all their Linux
-
@Eric-Ross said in Virtualbox Issues:
@jmoore said in Virtualbox Issues:
@Pete-S said in Virtualbox Issues:
Try disabling Hyper-V.
I use virtualbox all the time. It's great and super-easy to use.
I have never enabled it
I found out when installing Docker Desktop for users that Hyper-V gets enabled and Virtualbox stops working. I'd double-check Hyper-V.
Thanks for the input, I did double check this and hyper-v was never enabled on that machine.
-
Ok so I duplicated things at home as best I could including installing virtualbox and the same iso's and it all works with the defaults like it should. So only thing I can think of is there is just something peculiar with the machine I was using at work for this. No idea what it could be. It was a precision tower 5810 with a standard windows install. Maybe it was just something with that particular piece of hardware but not going to worry about it further since its probably just that.
-
I would mark as solved but I do not see the option where it should be.
-
@jmoore said in Virtualbox Issues:
I would mark as solved but I do not see the option where it should be.
because it was never marked as a question first.. hit topic controls
-
@JaredBusch said in Virtualbox Issues:
@jmoore said in Virtualbox Issues:
I would mark as solved but I do not see the option where it should be.
because it was never marked as a question first.. hit topic controls
Got it thanks, I will remember that for next time.
-
What is the specific error?
Application Guard and Credential Guard will use hyper-v to sandbox without actually enabling hyper-v.
-
@stacksofplates said in Virtualbox Issues:
What is the specific error?
Application Guard and Credential Guard will use hyper-v to sandbox without actually enabling hyper-v.
There was no error. It looks like it loaded kernel but I can't be 100% sure that it did so completely. I would get the opensuse splash and it would just hang from there, never moving past that. I guess its just something with this machine at work because virtualbox worked perfectly on my workstation at home last night. They had identical settings so it was just weird and I was feeling like an idiot lol.
-
@jmoore said in Virtualbox Issues:
@stacksofplates said in Virtualbox Issues:
What is the specific error?
Application Guard and Credential Guard will use hyper-v to sandbox without actually enabling hyper-v.
There was no error. It looks like it loaded kernel but I can't be 100% sure that it did so completely. I would get the opensuse splash and it would just hang from there, never moving past that. I guess its just something with this machine at work because virtualbox worked perfectly on my workstation at home last night. They had identical settings so it was just weird and I was feeling like an idiot lol.
Yeah it could be the application guard stuff. From my experience you need to use bcdedit to disable that. And it's annoying.
-
@stacksofplates said in Virtualbox Issues:
@jmoore said in Virtualbox Issues:
@stacksofplates said in Virtualbox Issues:
What is the specific error?
Application Guard and Credential Guard will use hyper-v to sandbox without actually enabling hyper-v.
There was no error. It looks like it loaded kernel but I can't be 100% sure that it did so completely. I would get the opensuse splash and it would just hang from there, never moving past that. I guess its just something with this machine at work because virtualbox worked perfectly on my workstation at home last night. They had identical settings so it was just weird and I was feeling like an idiot lol.
Yeah it could be the application guard stuff. From my experience you need to use bcdedit to disable that. And it's annoying.
I guess it could be but this is a newly imaged machine and other machines (but different models) work with the defaults also. So I wonder if it does not have something to do with this specific model or something in its bios. I glanced at the virtualbox documentation page just enough to make sure these defaults are what is suggested and they were. so it cvould be related to hyper-v but I am not convinced as other machines with the same image work fine. Who knows lol, its just one of those things.
