Bo Chen

> but you must update your comments about the way we're gonna perform `state()`, `set_state()` and `transit_device_state()` as they will follow the updated spec here: https://github.com/tmakatos/muser/blob/migration-v2/docs/vfio-user.rst @sboeuf Just pushed a...

I wonder how do we regularly check security fixes for all our dependencies? Is there an "easy" way to do it automatically?

I wonder what's the plan for supporting live-upgrade across different versions? Are we looking at across two stable releases or even across two LTS releases?

> For the datapath, that means the virtqueues are handled through DMA directly between the hardware and the guest, while the control path goes through the vDPA framework. Sounds like...

For the existing integration tests, they are all testing live-migration between the same CH version, covering NUMA, vhost-user (OVS-DPDK), and local-migration. Do you think it would be enough to have...

@tmakatos @jlevon Do you know whether there are any available vfio-user device/server that implements the counterpart of `VFIO_USER_DEVICE_GET_REGION_IO_FDS`? IIUC, I don't think the latest SPDK/NVMe vfio-user supports this feature (as...

@liuw Thanks for starting this issue. Can you please elaborate more on what are the benefits of following libvirt's behavior, e.g. sending the updated config (instead of initial config) to...

@rbradford @sboeuf I just finished the experiments of live migration on a single Azure VM (both 'bare-metal' and 'nested'), and submitted a PR to document the steps https://github.com/cloud-hypervisor/cloud-hypervisor/pull/2726. I will...

VM-NODE Output: > leaving: NextTest entering: Testing +++++++++++++++++++++++++++++++++++++ Exception Caught: /home/chenbo/crete/crete-dev/lib/cluster/vm_node_fsm.cpp(1026): Throw in function bool crete::cluster::node::vm::fsm::QemuFSM_::is_finished::operator()(const EVT &, FSM &, SourceState &, TargetState &) [EVT = crete::cluster::node::vm::ev::poll, FSM = boost::msm::back::state_machine,...

Two running thread of vm-node: Thread 1 (main thread): it returned from node_driver.h:79 (run_node()) and is blocking at "node_driver.h:80", waiting for thread 2 to finish. Thread 2 (communication thread with...