Replies: 2 comments
-
|
I got around this by using the API to add a vsock, which also worked via ch-remote, I couldn't get it to work when using arguments passed to the cloud-hypervisor binary. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Wouldn't work because you didn't create a VM with this command - just started the VMM on the API socket. A VM is only created if |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I'm implementing an agent to measure usage consumption within a VM, it runs within the guest listening on vsock and is accessed via the host.
With Firecracker, this is working as expected. Firecracker opens a UNIX socket at the specified location when the process starts up, the host can read from that location by sending
CONNECT PORT_NUMBER\n.https://github.com/firecracker-microvm/firecracker/blob/main/docs/vsock.md
The agent can then dump its state.
With cloud-hypervisor, no socket is created despite the CLI flag being passed as directed in the docs:
I've also tried booting up a VM with existing code, and the additional argument populated, it made no difference.
VSOCK is enabled on the guest Kernel for Firecracker, and for cloud-hypervisor. The latest version of cloud-hypervisor is being used from the GitHub Releases page (42). The same host is being used to launch either f/c or c/h.
Please could someone advise on whether this feature is supported? The documentation states that it has parity with or pays homage to Firecracker.
Beta Was this translation helpful? Give feedback.
All reactions