Merge pull request #39 from AntonioMeireles/vbox5+
update warning regarding VirtualBox now that vbox 5.0 is out.
This commit is contained in:
commit
ed137cf752
1 changed files with 11 additions and 5 deletions
16
README.md
16
README.md
|
@ -158,11 +158,17 @@ If you want the same IP address across VM reboots, assign a UUID to a particular
|
|||
|
||||
Issues
|
||||
------
|
||||
Right now, if you have (any version of) VirtualBox running and attempt to run
|
||||
xhyve it will immediately crash your system as it triggers a kernel panic.
|
||||
This is not a xhyve issue *per se*, since it runs in userspace, but a
|
||||
VirtualBox one which just doesn't play nice with Hypervisor.framework.
|
||||
(see issues [#5](https://github.com/mist64/xhyve/issues/5) and [#9](https://github.com/mist64/xhyve/issues/9) for the full context)
|
||||
If you are, or were, running any version of VirtualBox, prior to 5.0, and
|
||||
attempt to run xhyve your system will immediately crash as a kernel panic is
|
||||
triggered. This is due to a VirtualBox bug (that got fixed in VirtualBox 5.0)
|
||||
as VirtualBox wasn't playing nice with OSX's Hypervisor.framework used by
|
||||
xhyve.
|
||||
|
||||
To get around this you either have to update to VirtualBox 5 (which got this
|
||||
fixed definitively) or, if you for some reason are unable to update, to reboot
|
||||
your Mac after using VirtualBox and before attempting to use xhyve.
|
||||
(see issues [#5](https://github.com/mist64/xhyve/issues/5) and
|
||||
[#9](https://github.com/mist64/xhyve/issues/9) for the full context)
|
||||
|
||||
TODO
|
||||
----
|
||||
|
|
Loading…
Add table
Reference in a new issue