Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Avoid kernel panic: Detect if other processes are using vmx #9

Closed
tiborvass opened this issue Jun 10, 2015 · 8 comments
Closed

Avoid kernel panic: Detect if other processes are using vmx #9

tiborvass opened this issue Jun 10, 2015 · 8 comments

Comments

@tiborvass
Copy link

@tiborvass tiborvass commented Jun 10, 2015

Currently, if you have virtualbox running already, xhyve will kernel panic.

Is there a way we could detect if something is already using vmx and error out cleanly?

@xez
Copy link
Collaborator

@xez xez commented Jun 10, 2015

I can reproduce the panic with VirtualBox + xhyve but not VMware + xhyve. Maybe only an issue with VirtualBox?

@tiborvass
Copy link
Author

@tiborvass tiborvass commented Jun 10, 2015

@xez I am no expert on VMX but I think I read that there are two modes: one that lets other processes use VMX, and one that doesn't and I believe Virtualbox uses the latter. I believe Parallels also does that, however it has some error handling code, and will prompt to close Virtualbox.

I am not sure if folks at Parallels added virtualbox-specific code (i.e. check if Virtualbox is running) or if there is a proper way to check if we can access vmx before actually using it.

@mist64
Copy link
Collaborator

@mist64 mist64 commented Jun 10, 2015

Duplicate of #9 - there is nothing xhyve can do, we're user mode, and this is a kernel panic. :( VirtualBox has to be fixed to play nicely with Hypervisor.framework.

@mist64 mist64 closed this Jun 10, 2015
@mdaniel
Copy link

@mdaniel mdaniel commented Jun 10, 2015

I think you mean dupe of #5 and since you are well versed in Hypervisor.framework, could we implore you to search or file an issue with VirtualBox? Just saying they need to here in a GH comment does not help them achieve that goal.

@tiborvass
Copy link
Author

@tiborvass tiborvass commented Jun 10, 2015

@mist64 FWIW, Parallels can detect that something incompatible is using vmx (here: it's xhyve).
Parallels detecting xhyve

AntonioMeireles added a commit to AntonioMeireles/xhyve that referenced this issue Jun 11, 2015
…gets surprised.

Signed-off-by: António Meireles <antonio.meireles@reformi.st>
AntonioMeireles added a commit to AntonioMeireles/xhyve that referenced this issue Jun 11, 2015
…gets surprised.

Signed-off-by: António Meireles <antonio.meireles@reformi.st>
mist64 added a commit that referenced this issue Jun 11, 2015
add a pointer in the README about #5/#9 so that no one gets surprised.
@il-demone-guardiano
Copy link

@il-demone-guardiano il-demone-guardiano commented Jul 11, 2015

Does not happen anymore with VirtualBox 5.0.
You can even run VirtualBox and xhyve side by side.

@paulp
Copy link

@paulp paulp commented Jul 11, 2015

Confirming @il-demone-guardiano's experience.

screen shot 2015-07-11 at 08 11 13

@AntonioMeireles
Copy link
Member

@AntonioMeireles AntonioMeireles commented Jul 11, 2015

#39 updates docs regarding this 😄

erikolofsson pushed a commit to erikolofsson/xhyve that referenced this issue May 8, 2019
get proper size for raw block devices.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
7 participants
You can’t perform that action at this time.