Kei Kamikawa

For now, it seems that the virtualization framework needs to make it clear that it is using unix sockets (vsock over unix socket).

Yes, but virtualization framework users cannot touch the vsock connection directly. So It was not a good to make`VirtioSocketConnection.LocalAddr()` and `VirtioSocketConnection.RemoteAddr()` look like vsock. > They do not mention it...

This is incorrect. Quote [this comment (2.](https://github.com/Code-Hex/vz/issues/61#issuecomment-1290150478), the guest CID that wants to be the `RemoteAddr` gets a different value with the current returning `RemoteAddr`. As commented, this CID can...

Ports can still be obtained using two methods `DestinationPort` and `SourcePort`. I just don't see the need to provide false `RemoteAddr`, and `LocalAddr`.

I don't know what you are trying to solve, but I am going to return `LocalAddr`, `RemoteAddr` in unnamed unix socket format, as I have mentioned from the beginning. I...

This is understandable, but the current implementation is already different. I've said this many times. Apple (`VZVirtioSocketConnection`) provides three members 1. fileDescripter 2. destinationPort 3. sourcePort Of these, vsock information...

Yes. It is undocumented about an unnamed unix socket. However, in Objective-C (Go is OK too), if you only return a fileDescripter, how would you make read/write to a bi-directional...

@cfergeau Thanks. I'm researching other options.

I'm trying [toybox](http://landley.net/toybox/index.html) but I can't boot (maybe this is successful but not shown on the console) on this library but I can be confirmed by qemu. ```make .PHONY: initrd...

I'm working on making too tiny Linux for testing them https://github.com/Code-Hex/puipui-linux