David Scott

@aemengo thanks for your report. I think I've seen this error a few times too and I think it's harmless. It comes from an [exception handler around a connection callback](https://github.com/moby/vpnkit/blob/ae22283b503090803481dfa5e7bf1f431905dc11/src/hostnet/host.ml#L771)....

I think the cause of the problem is the compiler version: ``` - sha.1.9 is not available because your system doesn't comply with ocaml-version < "4.06.0". ``` The CI configuration...

Thanks for your reports. In order to make progress with this issue I need some reproduction steps. Could you provide a `docker-compose.yml` (or similar) and instructions to reproduce the problem?

@laarmen thanks for the update. Could you trigger the bug and then upload a diagnostic report? I'd like to take a look at the logs.

On Windows there should be a whale-shaped icon in the system tray. After right clicking on it there should be a menu item called something like "Diagnose and Feedback". Clicking...

`hyperkit` and `qcow-tool` share the [same implementation of qcow2](https://github.com/mirage/ocaml-qcow) and so are 100% compatible with each other. Since the majority of our testing focuses on qcow2 files created by `qcow-tool`...

I think this one is a leak in the 9P server end (inside the `vpnkit` process itself). Too many leaks :/

I'm not sure but I recommend running the following to capture a packet trace from the VM: ``` docker run -it -v /tmp:/out --net=host djs55/tcpdump -n -i eth0 -s 0...

It looks like `mirage-dns` cannot cope with responses larger than 4096 bytes: ``` 2019-04-05 16:02:59.149108+0100 localhost com.docker.vpnkit[27974]: XXX returning 420 answers 2019-04-05 16:02:59.149380+0100 localhost com.docker.vpnkit[27974]: Lwt.async failure (Invalid_argument "Cstruct.blit_from_string src=[7]...

Not sure. I think what I need to do is create a convincing test case to check.