Update RpcServer::new_vsock calls for new return
Returns the assigned port along with the server now.
We do not take advantage of it yet.
Test: atest vm_accessor_test
Bug: 372381104
Change-Id: Ia32c5ca4a19cd6e39c3fc94c2d3a1f43a4a32bb5
diff --git a/android/virtmgr/src/aidl.rs b/android/virtmgr/src/aidl.rs
index 23652d2..c587df9 100644
--- a/android/virtmgr/src/aidl.rs
+++ b/android/virtmgr/src/aidl.rs
@@ -447,7 +447,7 @@
// Start VM service listening for connections from the new CID on port=CID.
let port = cid;
- let vm_server = RpcServer::new_vsock(service, cid, port)
+ let (vm_server, _) = RpcServer::new_vsock(service, cid, port)
.context(format!("Could not start RpcServer on port {port}"))
.or_service_specific_exception(-1)?;
vm_server.start();
@@ -469,7 +469,7 @@
// Start VM service listening for connections from the new CID on port=CID.
let port = cid;
match RpcServer::new_vsock(service, cid, port) {
- Ok(vm_server) => {
+ Ok((vm_server, _)) => {
vm_server.start();
return Ok((VmContext::new(vm_context, vm_server), cid, temp_dir));
}