feat: implement virtio based host-guest communication #4024
andreiltdValidatePullRequest.yml
on: pull_request
docs-pr
3s
update-guest-locks
/
update-guest-locks
Matrix: build-guests
code-checks
/
linux-checks
11m 51s
code-checks
/
windows-checks
8m 53s
Matrix: build-test
Matrix: fuzzing / fuzz
Matrix: run-examples
report-ci-status
2s
Annotations
60 errors and 14 warnings
|
run-examples (mshv3, intel, debug) / run-examples
Process completed with exit code 101.
|
|
run-examples (hyperv-ws2025, amd, release) / run-examples
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
run-examples (hyperv-ws2025, intel, debug) / run-examples
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
run-examples (hyperv-ws2025, amd, debug) / run-examples
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
run-examples (kvm, amd, debug) / run-examples
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
run-examples (kvm, intel, release) / run-examples
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
run-examples (kvm, intel, debug) / run-examples
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
run-examples (mshv3, amd, debug) / run-examples
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
run-examples (kvm, amd, release) / run-examples
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
run-examples (mshv3, intel, release) / run-examples
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
build-test (hyperv-ws2025, amd, debug) / build-and-test
Process completed with exit code 1.
|
|
build-test (mshv3, amd, debug) / build-and-test
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
build-test (hyperv-ws2025, intel, release) / build-and-test
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
build-test (mshv3, intel, release) / build-and-test
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
build-test (mshv3, amd, release) / build-and-test
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
build-test (hyperv-ws2025, amd, release) / build-and-test
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
build-test (kvm, amd, release) / build-and-test
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
build-test (kvm, intel, release) / build-and-test
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
build-test (hyperv-ws2025, intel, debug) / build-and-test
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
build-test (kvm, amd, debug) / build-and-test
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
build-test (mshv3, intel, debug) / build-and-test
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
run-examples (hyperv-ws2025, intel, release) / run-examples
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
run-examples (hyperv-ws2025, intel, release) / run-examples
The operation was canceled.
|
|
run-examples (mshv3, amd, release) / run-examples
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
run-examples (mshv3, amd, release) / run-examples
The operation was canceled.
|
|
build-test (kvm, intel, debug) / build-and-test
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
build-test (kvm, intel, debug) / build-and-test
The operation was canceled.
|
|
fuzzing / fuzz (fuzz_host_print)
Process completed with exit code 1.
|
|
fuzzing / fuzz (fuzz_host_call)
The strategy configuration was canceled because "fuzzing.fuzz.fuzz_host_print" failed
|
|
fuzzing / fuzz (fuzz_host_call)
Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run
|
|
fuzzing / fuzz (fuzz_host_call)
Process completed with exit code 1.
|
|
fuzzing / fuzz (fuzz_guest_estimate_trace_event)
The strategy configuration was canceled because "fuzzing.fuzz.fuzz_host_print" failed
|
|
fuzzing / fuzz (fuzz_guest_estimate_trace_event)
The operation was canceled.
|
|
fuzzing / fuzz (fuzz_guest_trace)
The strategy configuration was canceled because "fuzzing.fuzz.fuzz_host_print" failed
|
|
fuzzing / fuzz (fuzz_guest_trace)
The operation was canceled.
|
|
fuzzing / fuzz (fuzz_guest_call)
The strategy configuration was canceled because "fuzzing.fuzz.fuzz_host_print" failed
|
|
fuzzing / fuzz (fuzz_guest_call)
The operation was canceled.
|
|
report-ci-status
Process completed with exit code 1.
|
|
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "build-test.hyperv-ws2025_amd_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
Validate Pull Request
The strategy configuration was canceled because "run-examples.mshv3_intel_debug" failed
|
|
build-guests (release) / build-guests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
code-checks / windows-checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
code-checks / linux-checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-guests (debug) / build-guests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-examples (mshv3, intel, debug) / run-examples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-test (hyperv-ws2025, amd, debug) / build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-examples (hyperv-ws2025, intel, release) / run-examples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
run-examples (mshv3, amd, release) / run-examples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
build-test (kvm, intel, debug) / build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
fuzzing / fuzz (fuzz_host_print)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
fuzzing / fuzz (fuzz_host_call)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
fuzzing / fuzz (fuzz_guest_estimate_trace_event)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
fuzzing / fuzz (fuzz_guest_trace)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
fuzzing / fuzz (fuzz_guest_call)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: extractions/setup-crate@4993624604c307fbca528d28a3c8b60fa5ecc859. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
c-guests-debug
Expired
|
2.65 MB |
sha256:1466c0a7c848a9eeac1b472fa21ebbf9086d2c7d9c49fb12ab66737a81b63578
|
|
|
c-guests-release
Expired
|
513 KB |
sha256:18547397bd291636034c8d354ee6ff250aa229ff19fc44bea9a7713f13e77041
|
|
|
fuzz-crash-artifacts
|
240 Bytes |
sha256:305007d685f93fd4d97599f8066cc98b35e4f360dbff7656a9ec93f5ebe7c4d4
|
|
|
interface-wasm
Expired
|
1.19 KB |
sha256:afdffacd695a0fea6473c7a90164c76d66a4c5b4e187ac359ee1de61455b900d
|
|
|
rust-guests-debug
Expired
|
4.15 MB |
sha256:7a566f664b04cacd89dcdae3c5d96b1c0af72a07c3100507666808ec701ee5dc
|
|
|
rust-guests-release
Expired
|
362 KB |
sha256:e5a2be6968eae4ee3726fec2e1a9c0151221dc826159d1e17958d5e609e10835
|
|
|
twoworlds-wasm
Expired
|
363 Bytes |
sha256:a2114ab3c71f1958315bde72d5383d22c615ccc045a6b4c6048811f73053caba
|
|