crosvm: support passing command line arguments to plugin process

This uses the same command line mechanism as the kernel command line
option. As a consequence, the Config field for the params is now a
vector of strings to accommodate potential whitespace in the individual
params.

TEST=cargo build --features plugin; ./build_test
BUG=chromium:800626

Change-Id: Ief20a55bf7ced23f64e5112e184dd714f050120a
Reviewed-on: https://chromium-review.googlesource.com/895415
Commit-Ready: Zach Reizner <zachr@chromium.org>
Tested-by: Zach Reizner <zachr@chromium.org>
Reviewed-by: Dylan Reid <dgreid@chromium.org>

1 files changed, 2 insertions, 2 deletions

diff --git a/src/linux.rs b/src/linux.rs
index 1d0a311..1587239 100644
--- a/src/linux.rs
+++ b/src/linux.rs
@@ -746,8 +746,8 @@ pub fn run_config(cfg: Config) -> Result<()> {
                                   &mut control_sockets,
                                   balloon_device_socket)?;
 
-    if !cfg.params.is_empty() {
-        cmdline.insert_str(&cfg.params).map_err(Error::Cmdline)?;
+    for param in &cfg.params {
+        cmdline.insert_str(&param).map_err(Error::Cmdline)?;
     }
 
     let vcpu_count = cfg.vcpu_count.unwrap_or(1);