From 30ebd272d69c64e691054f31d75b324ad20ec905 Mon Sep 17 00:00:00 2001 From: Rob Bradford Date: Tue, 13 Feb 2018 14:54:09 +0000 Subject: [PATCH] crosvm: allow control of running VM via socket Remove control_sockets definition that shadows earlier one which contains the opened socket for receiving messages for controlling the running VM. This shadowing meant that the messages sent over the socket were not handled. TEST="crosvm run -s" with socket and then subsequent "crosvm stop" causes the running VM to be shutdown BUG=811749 Signed-off-by: Rob Bradford Change-Id: If5a82ec10c29ab037cbedcf7acea23a49b4cfeb6 Reviewed-on: https://chromium-review.googlesource.com/916264 Commit-Ready: Dylan Reid Tested-by: Dylan Reid Reviewed-by: Zach Reizner Reviewed-by: Dylan Reid --- src/linux.rs | 1 - 1 file changed, 1 deletion(-) diff --git a/src/linux.rs b/src/linux.rs index 158723929e..789c2de712 100644 --- a/src/linux.rs +++ b/src/linux.rs @@ -733,7 +733,6 @@ pub fn run_config(cfg: Config) -> Result<()> { .unwrap(); let mut next_dev_pfn = BASE_DEV_MEMORY_PFN; - let mut control_sockets = Vec::new(); let (io_bus, stdio_serial) = setup_io_bus(&mut vm, exit_evt.try_clone().map_err(Error::CloneEventFd)?)?;