Skip to content

Conversation

@phip1611
Copy link
Member

@phip1611 phip1611 commented Dec 17, 2025

Since PR #7525 (Dec 2025)[0], Cloud Hypervisor uses a virtual Cargo manifest and the main package was moved to the ./cloud-hypervisor subdirectory. This change is effective since v50. As our v49-based CHV version backported these changes already, we need to adapt the Nix build of CHV.

[0] cloud-hypervisor/cloud-hypervisor#7525

This is blocked on cyberus-technology/cloud-hypervisor#40.

Since PR #7525 (Dec 2025)[0], Cloud Hypervisor uses a virtual Cargo manifest and
the main package was moved to the `./cloud-hypervisor` subdirectory. This change
is effective since v50. As our v49-based CHV version backported these changes
already, we need to adapt the Nix build of CHV.

[0] cloud-hypervisor/cloud-hypervisor#7525

Signed-off-by: Philipp Schuster <philipp.schuster@cyberus-technology.de>
On-behalf-of: SAP philipp.schuster@sap.com
@phip1611 phip1611 force-pushed the chv-virtual-manifest branch from bef0ed2 to 20201cc Compare December 17, 2025 10:47
@phip1611 phip1611 self-assigned this Dec 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant