Reporting for launched xhyve

[zchee]

This thread is not issue thread. Post a report only.
See also Would you do me a favor?

OK, Running, Good, etc...
Anything will do.

[johanneswuerbach]

Hey, I would like to try the driver, but it seems to have a lot of dependencies https://github.com/zchee/docker-machine-xhyve#libguestfs (OSX Fuse, etc.). Mind uploading a binary?

[zchee]

@johanneswuerbach Thanks issue!

I can upload the binary, but the binary requests a libguestfs.dylib as a dynamic linking.
The reason, OS X does not support static build.
If remove the libguestfs, there are several problems.

• Needs way to copy the userdata.tar to disk image before launch the xhyve
• Give up use extfs Docker Backing Filesystem (will be using tmpfs. bad performance)

I know how to solve these without libguestfs, but I felt that pretty way used libguestfs.

If you are satisfied with tmpfs, I will make use tmpfs version binary from now.

BTW, I also have a problem in many of dependency.
I'm looking for a better way to make ext.4 disk image without a libguestfs.

Sorry terrible English :(

[johanneswuerbach]

I definitely see why you used libguestfs, but can't b2d auto-format the disk when it discovers an unformatted one? https://github.com/boot2docker/boot2docker/blob/master/rootfs/rootfs/etc/rc.d/automount#L13-L16

[zchee]

@johanneswuerbach I tried before. I don't remember so much...

But, docker-machine can not first connect the vm use ssh in that case.
docker-machine core implementation is create id_rsa, id_rsa, *.pem based on $HOME/.docker/machine/certs/* before launch any vm.

And, docker also docker-machine is doing a secure remote connection use *.pem.

So, need to copy the locally created userdata.tar in the first.

[zchee]

@johanneswuerbach
But, not accurate, I will check by gdb from now.

[johanneswuerbach]

Looks like b2d is just dd-ing a tar on that specific partition containing the certs: https://github.com/boot2docker/boot2docker/blob/master/rootfs/rootfs/etc/rc.d/automount#L22

Maybe the xhyve driver could create the same using hdiutil and dd.

[zchee]

@johanneswuerbach I remembered.

Yes. The method was previously used.

docker-machine boot2docker provisioner requires ssh login to some of the setting.
e.g. https://github.com/docker/machine/blob/master/libmachine/provision/boot2docker.go#L117-L127

If not exist /var/lib/boot2docker/userdata.tar, boot2dokcer is automatically formatted own disk, and create *.pem.
and, did not write hostid_rsa.pub data into authorized_keys.
In that case, It means for ssh login is needs tcuser password.

create blank disk image use dd
    |
boot2docker automatically create some files
    |
ssh login use tcuser password
    |
delete *.pem, and copy the local pem to img. and edit authorized_keys

I knew this way, but I feel it's pushy.

Hmm...
Let me think about it.

[johanneswuerbach]

Works like a charm now! :-)

[zchee]

@johanneswuerbach Oh! Thanks :)

[aybabtme]

I've been trying for a while to get this working, but it fails to find the -F flag (introduced in an unmerged PR against xhyve):

$ docker-machine -D create -d xhyve xhyve-dev
...
(xhyve-dev) DBG | operation not supported by device
(xhyve-dev) DBG | xhyve: illegal option -- F
(xhyve-dev) DBG | Usage: xhyve [-behuwxMACHPWY] [-c vcpus] [-g <gdb port>] [-l <lpc>]
(xhyve-dev) DBG |              [-m mem] [-p vcpu:hostcpu] [-s <pci>] [-U uuid] -f <fw>
...

The full output: debug.txt

[zchee]

@aybabtme Thanks issue :)

Could you create a new issue thread?

[aybabtme]

@zchee cool, just opened #59

[rothomp3]

It's working for me! Only thing was for some reason it didn't set up the boot script for the XHYVE_EXPERIMENTAL_NFS_SHARE, so I had to manually ssh in and mount the NFS share. After doing that, it's cranking away on building Swift from source now!