Search Criteria
Package Details: cloud-hypervisor 42.0-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/cloud-hypervisor.git (read-only, click to copy) |
---|---|
Package Base: | cloud-hypervisor |
Description: | A Virtual Machine Monitor for modern Cloud workloads |
Upstream URL: | https://github.com/cloud-hypervisor/cloud-hypervisor |
Licenses: | Apache:2.0 |
Submitter: | zer0def |
Maintainer: | gdamjan |
Last Packager: | gdamjan |
Votes: | 4 |
Popularity: | 0.000000 |
First Submitted: | 2019-12-18 23:57 (UTC) |
Last Updated: | 2024-10-30 19:49 (UTC) |
Dependencies (3)
- rust (rust-nightlyAUR, rustup-gitAUR, rust-nightly-binAUR, rust-gitAUR, rustup) (make)
- qemu-headless (qemu-gitAUR, qemu-headless-gitAUR) (optional) – for /usr/lib/qemu/virtiofsd
- virtiofsd (optional) – rust implementation of virtiofsd
Required by (3)
- flintlock (optional)
- kata-runtime (optional)
- kata-runtime-bin (optional)
Latest Comments
AveryFreeman commented on 2023-11-19 20:58 (UTC) (edited on 2023-11-26 18:39 (UTC) by AveryFreeman)
I'm trying to build the package with dbus API support, so I modified the
PKGBUILD
slightly:I noticed about half of the integration tests would fail without root access. Any recommendations for a more graceful solution than
sudo
?Here's a list of features in the
.toml
file:People with AMD processors should also comment-out the
tdx
feature inCargo.toml
if building with--all-features
, as it is Intel-only.zer0def commented on 2020-12-12 06:02 (UTC)
Sorry for the late bump, things have been rowdy and release note remarks on migrating off the
vhost-user-fs
backend to a separate project made me hesitate and want to double-check repercussions. It still may end up causing issues, but the hypervisor itself looks to be working just fine.gdamjan commented on 2020-11-03 01:43 (UTC)
The package should depend on qemu-headless (which is also provided by qemu).
And even then, it should probably be an optdepends, since the requirement is fully optional.
rageltman commented on 2020-10-27 00:01 (UTC)
This build is failing due to a missing revision in the vm-memory repo: