README 2.2 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667
  1. CloudHv is a port of OVMF for the Cloud Hypervisor project.
  2. The Cloud Hypervisor project
  3. ----------------------------
  4. Cloud Hypervisor is a Virtual Machine Monitor that runs on top of KVM. The
  5. project focuses on exclusively running modern, cloud workloads, on top of a
  6. limited set of hardware architectures and platforms. Cloud workloads refers to
  7. those that are usually run by customers inside a cloud provider. This means
  8. modern operating systems with most I/O handled by paravirtualised devices
  9. (i.e. virtio), no requirement for legacy devices, and 64-bit CPUs.
  10. https://github.com/cloud-hypervisor/cloud-hypervisor
  11. Design
  12. ------
  13. Based on Cloud Hypervisor's motto to reduce the emulation as much as possible,
  14. the project logically decided to support the PVH boot specification as the only
  15. way of booting virtual machines. That includes both direct kernel boot and OVMF
  16. firmware which must be generated as PVH ELF binaries.
  17. PVH allows information like location of ACPI tables and location of guest RAM
  18. ranges to be shared without the need of an extra emulated device like a CMOS.
  19. Features
  20. --------
  21. * Serial console
  22. * EFI shell
  23. * virtio-pci
  24. Build
  25. -----
  26. The way to build the CloudHv target is as follows:
  27. OvmfPkg/build.sh -p OvmfPkg/CloudHv/CloudHvX64.dsc -a X64 -b DEBUG
  28. Usage
  29. -----
  30. Assuming Cloud Hypervisor is already built, one can start a virtual machine as
  31. follows:
  32. ./cloud-hypervisor \
  33. --cpus boot=1 \
  34. --memory size=1G \
  35. --kernel Build/CloudHvX64/DEBUG_GCC5/FV/CLOUDHV.fd \
  36. --disk path=/path/to/disk.raw
  37. Releases
  38. --------
  39. In edk2-stable202202, CloudHv is generated as data-only binary.
  40. Starting with edk2-stable202205, CloudHv is generated as a PVH ELF binary to
  41. reduce the amount of emulation needed from Cloud Hypervisor.
  42. For TDX, things are handled differently and PVH is not used, which is why the
  43. firmware is always generated as a data-only binary.
  44. +-------------------+----------------+
  45. | | CloudHv |
  46. +-------------------+----------------+
  47. | edk2-stable202202 | Data binary |
  48. +-------------------+----------------+
  49. | edk2-stable202205 | PVH ELF binary |
  50. +-------------------+----------------+