Koichi Shiraishi

@cbarratt Hmm... The cause of this issue does not seem to be a `docker-machine-driver-xhyve`. Do you have disabled the SIP (System Integrity Protection)? ``` bash sudo csrutil status ```

@cbarratt Oh, I checked now, I also was enable SIP :( Anyway, if the original `xhyve` does not start, strange something in your environment. I will cooperate in the improvement...

@cbarratt Sorry, I'm not good at English. > I can try disable SIP and see if that helps? Do you not know how to disable the SIP?

@cbarratt I understand. Thanks. I also debug xhyve now. `hv_vm_create` is src/vmm/intel/vmx.c +467. Why this error handle is executed... :(

@cbarratt FYI, I and your difference is this points. ``` bash ProductName: Mac OS X ProductVersion: 10.11.3 # Not beta BuildVersion: 15D13b ``` Did you update OS yesterday?

@cbarratt I was updated to 15E27e(beta) by mistake yesterday :scream_cat: It could not also be started. This would be a apple's bug.

@cbarratt I have prepared a bootable install OS X USB, and forcible downgrade. (Not delete HDD, overwrite install) Improved, but it is not recommended.

@vcarus Thanks issue :) I small fix your comment. sorry. and, I will investigate the cause from now. Please wait a little :)

@vcarus I think your displayed, ``` bash rdmsr to register 0x570 on vcpu 0 ``` This means that xhyve is launch properly. So the cause does not seem to match...

@vcarus FYI, normal `/var/db/dhcpd_leases` contents, ``` bash $ cat /var/db/dhcpd_leases { name=boot2docker ip_address=192.168.64.2 hw_address=1,de:5f:75:68:cf:32 identifier=1,de:5f:75:68:cf:32 lease=0x56ab0fb6 } { name=boot2docker ip_address=192.168.64.10 hw_address=1,da:bf:6a:77:cf:32 identifier=1,da:bf:6a:77:cf:32 lease=0x56aa386a } { name=boot2docker ip_address=192.168.64.9 hw_address=1,ea:2:b7:57:cf:32 identifier=1,ea:2:b7:57:cf:32 lease=0x56aa327c...