Skip to content

Conversation

@AyushSriv06
Copy link

This PR adds support for Cloud Hypervisor as a new VMM option.

  • Added [cloud_hypervisor.go], implementing the VMM interface using CLI arguments
  • Registered Cloud Hypervisor in the VMM factory ([vmm.go]
  • Updated documentation in [hypervisor-support.md]
  • Added e2e test cases (skippable until images are available)
  • Added cpus to the spell dictionary

Fixes: #160

Signed-off-by: Ayush Srivastava <ayushsrisks@gmail.com>
@netlify
Copy link

netlify bot commented Jan 23, 2026

Deploy Preview for urunc ready!

Name Link
🔨 Latest commit 3d69997
🔍 Latest deploy log https://app.netlify.com/projects/urunc/deploys/6978cea1cf6f6400083c1105
😎 Deploy Preview https://deploy-preview-393--urunc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@cmainas
Copy link
Contributor

cmainas commented Jan 26, 2026

Hello @AyushSriv06 ,

thank you for this contribution. However, since this PR adds support for a new monitor, we kindly ask you to try it out first locally, creating the necessary images. After this is done, please update the test descriptions and we will start the review process.

@cmainas
Copy link
Contributor

cmainas commented Jan 26, 2026

Hello @AyushSriv06 , sure the kernel booted but it failed. A boot leading to panic is not successful.

@AyushSriv06
Copy link
Author

Hello @AyushSriv06 , sure the kernel booted but it failed. A boot leading to panic is not successful.

Since the official images aren't ready and my local 'hello world' app was incompatible (32-bit vs 64-bit), I used my computer's Linux kernel to test it.
The screenshot (showing the 'kernel panic') proves it worked because:

  • Cloud Hypervisor definitely started (otherwise nothing would happen).

  • It successfully booted the kernel (that's who printed the panic).

  • We captured those logs successfully.

Screenshot from 2026-01-26 15-24-16

am i missing something?

@cmainas
Copy link
Contributor

cmainas commented Jan 26, 2026

Hello @AyushSriv06 , the kernel panic message not syncing: VFS: unable to mount root fs indicates that the application never started inside the VM, because the Linux kernel could not mount the rootfs which most probably contains the application.

Unfortunately, you need to build a correct image with the correct Linux kernel and verify that the application starts inside the VM. In urunc's documentation you can find a tutorial on how to build images for Linux using existing container images https://urunc.io/tutorials/existing-container-linux/. You only need to either build or fetch a Linux kernel suitable for cloud-hypervisor. You can find such kernel images in:

Signed-off-by: Ayush <ayushsrisks@gmail.com>
@AyushSriv06
Copy link
Author

I have resolved all the issues and used Cloud Hypervisor optimized Linux kernel (v6.2).
All the tests are passing now.
Screenshot from 2026-01-27 20-04-18

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add support for Cloud hypervisor

2 participants