feat(hypervisors): add Cloud Hypervisor VMM support

[AyushSriv06]

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

[netlify]

✅ Deploy Preview for urunc ready!

Name	Link
🔨 Latest commit	e668637
🔍 Latest deploy log	https://app.netlify.com/projects/urunc/deploys/69861f3c6cd8b300081a8f24
😎 Deploy Preview	https://deploy-preview-393--urunc.netlify.app
📱 Preview on mobile	Toggle 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]

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]

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

[AyushSriv06]

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.

am i missing something?

[cmainas]

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:

• The firecracker repository https://github.com/firecracker-microvm/firecracker/blob/main/docs/getting-started.md#getting-a-rootfs-and-guest-kernel-image
• From Kata containers releases https://github.com/kata-containers/kata-containers/releases/tag/3.25.0
• Build one using the instructions in the cloud hypervisor repository https://github.com/cloud-hypervisor/cloud-hypervisor?tab=readme-ov-file#building-your-kernel

[AyushSriv06]

I have resolved all the issues and used Cloud Hypervisor optimized Linux kernel (v6.2).
All the tests are passing now.

[AyushSriv06]

Hello @cmainas, could you review this?
Let me know if you need any test descriptions.

[cmainas]

Hello @AyushSriv06 ,

thank you for the changes. I have verified that cloud hypervisor can boot! Very nice. However, I have added some comments that need to be addressed. Please avoid changes which are unrelated to the cloud-hypervisor PR. You can open a new PR with the changes that are correct.

[AyushSriv06]

Hello, @cmainas i have resolved all the comments. may you review them once!