It requires that you copy the vmlinuz64 and initrd.img files from the B2D ISO to a local filesystem location. As of right now enabling networking requires root privileges. Not sure if the Hypervisor framework has user-level accommodations for that.
Not to mention they're paid solutions, closed source and are horrible for battery life. Their only advantage is nice set of GUI tools and tight OS X integration.
This is great, is it possible to make it work with Docker?
Edit: Yes, it is.
Edit2: It is possible, but whether is it worth it or not is still a question. xhyve is a supervisor after all, you still need to boot a vm to use Docker. So if you like me, thought for a second that this can make containers in OSX a reality, don't get excited too early.
If you want a better solution on OSX than you already have, try https://github.com/codekitchen/dinghy - it does a really great job of wrapping Vagrant and taking care of setting up NFS instead of the incredibly slow default vboxfs.
Alternatively I've used Parallels + NFS with Vagrant for boot2docker but it's a real pain to get set up correctly. Dinghy just did it automatically, and also set up DNS and NTP for me. Can't recommend it enough.
Definitely time to add Hypervisor.framework to the list of interesting things on OS X to check out. Related: I'd love to see a Vagrant provider for Xhyve, may have to hack on that a bit later.
Fair warning, this may cause a Kernel panic. I've contributed to the bug with my trace, but it's definitely something to keep in mind when checking it out.
I really want this to work, though. It would be a great replacement for VirtualBox.
I wrote a quick set of scripts to get CoreOS booting under xhyve as a container host. The defaults will expose SSH and a docker client port and drop you directly into a shell. Some quick getting started info here:
Lots of GitHub issues filed for next steps in exploring this technology. Really exciting to see a simple CLI driven virtualization option on OSX. Patches accepted. :)
This project is awesome. No more vmware fusion for me. Props to netapp for funding and driving the bhyve project. FreeBSD was desperately in need of native virtualization capabilities.
I'm curious why there is a restriction of 2010 or newer mac. Is it something in the CPU that's needed? I've 10.10.3 installed on a non supported mac and wanted to use this, but getting errors when I try the test Linux
You need a CPU that supports Intel's virtualization instruction set. Specifically VT-x. You can check if your CPU supports it with:
sysctl machdep.cpu.features
You're looking for VMX. Here's an example from mine (highlighted the flag you're looking for):
That's really great! I had to rebuy VMware at work and Parallels at home when Yosemite came out because of the new hypervisor framework modifications that these two needed under Yosemite (I presume).
I don't really use the OSX integration of both systems, other than file mapping/sharing (I run Linux and Windows VMs).
I don't know about Parallels but VMWare Fusion 6 runs just fine on Yosemite – there's almost no reason to upgrade unless you want new icons.
That said, I'm completely with you on the value of Hypervisor.framework for people who are e.g. running Linux test instances and not really seeing much benefit from the UI integration but who still want to avoid the performance / stability problems caused by using virtualbox.
[+] [-] bruienne|10 years ago|reply
It requires that you copy the vmlinuz64 and initrd.img files from the B2D ISO to a local filesystem location. As of right now enabling networking requires root privileges. Not sure if the Hypervisor framework has user-level accommodations for that.
[+] [-] bruienne|10 years ago|reply
[+] [-] simonvdv|10 years ago|reply
I've also done some quick benchmarks, they are at the bottom of the post. Virtualbox had about 50% higher disk IO performance in my measurements.
Regarding the root permissions for networking: As far as I know it shouldn't be necessary if you sign the xhyve binary, haven't tried that though.
[+] [-] Osmium|10 years ago|reply
[+] [-] tachion|10 years ago|reply
[+] [-] alisnic|10 years ago|reply
Edit: Yes, it is.
Edit2: It is possible, but whether is it worth it or not is still a question. xhyve is a supervisor after all, you still need to boot a vm to use Docker. So if you like me, thought for a second that this can make containers in OSX a reality, don't get excited too early.
[+] [-] piranha|10 years ago|reply
[+] [-] DoubleMalt|10 years ago|reply
[+] [-] STRML|10 years ago|reply
Alternatively I've used Parallels + NFS with Vagrant for boot2docker but it's a real pain to get set up correctly. Dinghy just did it automatically, and also set up DNS and NTP for me. Can't recommend it enough.
[+] [-] therealmarv|10 years ago|reply
[+] [-] mendocino|10 years ago|reply
[+] [-] saidajigumi|10 years ago|reply
[+] [-] sudioStudio64|10 years ago|reply
[+] [-] ionforce|10 years ago|reply
Initially I thought it was "zive" and "bive", like "bive" was a foreign word from somewhere. Bhyve, the muse of unit tests!
[+] [-] floatboth|10 years ago|reply
[+] [-] falcolas|10 years ago|reply
I really want this to work, though. It would be a great replacement for VirtualBox.
[+] [-] techdragon|10 years ago|reply
[+] [-] bstx|10 years ago|reply
[+] [-] philips|10 years ago|reply
https://github.com/coreos/coreos-xhyve#coreos--xhyve
Lots of GitHub issues filed for next steps in exploring this technology. Really exciting to see a simple CLI driven virtualization option on OSX. Patches accepted. :)
[+] [-] tw04|10 years ago|reply
[+] [-] 4ad|10 years ago|reply
[+] [-] jkyle|10 years ago|reply
But, compiled clean, test vm started fast. Will look at again.
[+] [-] mendocino|10 years ago|reply
[+] [-] mateuszf|10 years ago|reply
[+] [-] jkyle|10 years ago|reply
I'd rather see it supported by vagrant, which would seem an appropriate tool to manage them with.
[+] [-] walterbell|10 years ago|reply
[+] [-] osxrand|10 years ago|reply
[+] [-] tw04|10 years ago|reply
You're looking for VMX. Here's an example from mine (highlighted the flag you're looking for):
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL * VMX * SMX EST TM2 SSSE3 FMA CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C
[+] [-] stephenr|10 years ago|reply
[+] [-] 72deluxe|10 years ago|reply
I don't really use the OSX integration of both systems, other than file mapping/sharing (I run Linux and Windows VMs).
Glad to see this, many thanks!
[+] [-] acdha|10 years ago|reply
That said, I'm completely with you on the value of Hypervisor.framework for people who are e.g. running Linux test instances and not really seeing much benefit from the UI integration but who still want to avoid the performance / stability problems caused by using virtualbox.
[+] [-] tachion|10 years ago|reply
[+] [-] pyvpx|10 years ago|reply