You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi folks,
I am trying to get MigTD-MigTD communication set up using vmcall-vsock interface. The hypervisor used does not support virtio-serial/virtio-vsock and hence we need to exercise the vmcall-vsock interface to set up the TLS handshake.
MigTD-s sends a payload of size 275 to MigTD-d. This is the hello packet initiated by MigTD-s. In response to that, MigTD-d is generating a response packet of size 46823 down to destination VMM. This does not seem to be correct.
According to the TLS spec, the response "hello" from server side should be shorter in length.
We are building the main branch tip "(build(deps): bump KyleMayes/install-llvm-action from 2.0.5 to 2.0.6)", with "vsock: pop all the received packets" patch reverted.
MigTD is built with command: cargo image --no-default-features --features=vmcall-vsock
Thanks!
The text was updated successfully, but these errors were encountered:
Hi folks,
I am trying to get MigTD-MigTD communication set up using vmcall-vsock interface. The hypervisor used does not support virtio-serial/virtio-vsock and hence we need to exercise the vmcall-vsock interface to set up the TLS handshake.
MigTD-s sends a payload of size 275 to MigTD-d. This is the hello packet initiated by MigTD-s. In response to that, MigTD-d is generating a response packet of size 46823 down to destination VMM. This does not seem to be correct.
According to the TLS spec, the response "hello" from server side should be shorter in length.
The payload dump shared here: tls_hello_handshake_payload.txt
We are building the main branch tip "(build(deps): bump KyleMayes/install-llvm-action from 2.0.5 to 2.0.6)", with "vsock: pop all the received packets" patch reverted.
MigTD is built with command: cargo image --no-default-features --features=vmcall-vsock
Thanks!
The text was updated successfully, but these errors were encountered: