Virtualbox Issues
-
@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.
