Temporarily disable balloon device in crosvm
Currently the balloon device is already forcibly disabled within
crosvm itself, for protected VMs. This is because the balloon protocol
cannot possibly work without forthcoming kernel and hypervisor
modifications.
Disabling here in virtualizationservice allows the disablement to be
removed in upstream crosvm without breaking our tests when that is
merged into Android.
We disable balloon device even for non-protected VMs for now, because
the balloon protocol currently doesn't work for those either, when
running on pKVM hypervisor.
Bug: 238931615
Test: run a vm, confirm no balloon capability
Change-Id: Ie514cff903267d5e18229632b25b4ebf97c78dcf
diff --git a/virtualizationservice/src/crosvm.rs b/virtualizationservice/src/crosvm.rs
index 82a9e78..4a9df46 100644
--- a/virtualizationservice/src/crosvm.rs
+++ b/virtualizationservice/src/crosvm.rs
@@ -434,6 +434,7 @@
.arg("--extended-status")
.arg("run")
.arg("--disable-sandbox")
+ .arg("--no-balloon")
.arg("--cid")
.arg(config.cid.to_string());