dbs-cli: support virtio-mem feature

We can use dbs-cli to simply hotplug memory in virtual machine. It
should use update action, and only parameter is size in mib.

Example:

./dbs-cli  --api-sock-path /tmp/api-sock --hotplug-memory 1024 update

Fixes: #23

Signed-off-by: Helin Guo <helinguo@linux.alibaba.com>

Author: HerlinCoder

Cargo.lock

@@ -10,8 +10,10 @@ dragonball = { git = "https://github.com/kata-containers/kata-containers", branc
     "virtio-blk",
     "virtio-vsock",
     "virtio-net",
+    "virtio-mem",
     "hotplug",
     "dbs-upcall",
+    "atomic-guest-memory"
 ] }
 clap = { version = "4.0.27", features = ["derive"] }
 serde = "1.0.27"

Cargo.toml

@@ -22,6 +22,11 @@ pub fn run_api_client(args: DBSArgs) -> Result<()> {
         let request = request_virtio_blk(&config);
         send_request(request, &args.api_sock_path)?;
     }
+    if let Some(size_mib) = args.update_args.hotplug_memory {
+        let request = request_hotplug_memory(size_mib);
+        send_request(request, &args.api_sock_path)?;
+    }
+
     Ok(())
 }
 
@@ -48,6 +53,13 @@ fn request_virtio_blk(virtio_blk_config: &str) -> Value {
     })
 }
 
+fn request_hotplug_memory(size_mib: usize) -> Value {
+    json!({
+        "action": "hotplug_memory",
+        "size_mib": size_mib,
+    })
+}
+
 fn send_request(request: Value, api_sock_path: &str) -> Result<()> {
     let mut unix_stream = UnixStream::connect(api_sock_path).context("Could not create stream")?;
 

src/api_client.rs

@@ -10,6 +10,7 @@ use std::os::unix::net::{UnixListener, UnixStream};
 
 use anyhow::{anyhow, Context, Result};
 use dragonball::device_manager::blk_dev_mgr::BlockDeviceConfigInfo;
+use dragonball::device_manager::mem_dev_mgr::MemDeviceConfigInfo;
 use dragonball::device_manager::virtio_net_dev_mgr::VirtioNetDeviceConfigInfo;
 
 use crate::vmm_comm_trait::VMMComm;
@@ -105,6 +106,21 @@ impl ApiServer {
                         .context("Insert a virtio-blk device to the Dragonball")?;
                 }
             }
+            Some("hotplug_memory") => {
+                let mem_cfg = MemDeviceConfigInfo {
+                    mem_id: "virtio-mem0".to_string(),
+                    capacity_mib: 0,
+                    size_mib: v["size_mib"]
+                        .as_u64()
+                        .context("Invalid virtio-mem size input")?,
+                    multi_region: true,
+                    host_numa_node_id: None,
+                    guest_numa_node_id: None,
+                    use_generic_irq: None,
+                    use_shared_irq: None,
+                };
+                return self.insert_mem_device(mem_cfg);
+            }
             _ => {
                 println!("Unknown Actions");
             }

src/api_server.rs

@@ -297,4 +297,12 @@ The type of it is an array of BlockDeviceConfigInfo, e.g.
         display_order = 2
     )]
     pub hotplug_virblks: Option<String>,
+
+    #[clap(
+        long,
+        value_parser,
+        help = "Hotplug memory (MiB) through connection with dbs-cli api server",
+        display_order = 2
+    )]
+    pub hotplug_memory: Option<usize>,
 }

src/parser/args.rs

@@ -9,6 +9,7 @@ use dragonball::{
         BlockDeviceConfigInfo, BootSourceConfig, VmmAction, VmmActionError, VmmData, VmmRequest,
         VmmResponse, VsockDeviceConfigInfo,
     },
+    device_manager::mem_dev_mgr::MemDeviceConfigInfo,
     device_manager::virtio_net_dev_mgr::VirtioNetDeviceConfigInfo,
     vcpu::VcpuResizeInfo,
     vm::VmConfigInfo,
@@ -145,4 +146,10 @@ pub trait VMMComm {
             .with_context(|| format!("Failed to insert virtio-blk device {:?}", blk_cfg))?;
         Ok(())
     }
+    
+    fn insert_mem_device(&self, mem_cfg: MemDeviceConfigInfo) -> Result<()> {
+        self.handle_request_with_retry(Request::Sync(VmmAction::InsertMemDevice(mem_cfg.clone())))
+            .with_context(|| format!("Failed to insert mem device {:?}", mem_cfg))?;
+        Ok(())
+    }
 }