With the API server socket option, we want to support new UX patterns: 1) The CLI model: The user entirely configures a guest from the command line and does not expect to be able to control it dynamically through the API socket. This is the current model. 2) The API control model: The user does not configure anything from the command line, and calls the cloud-hypervisor binary with the API socket path command line option only. Everything will be done from the API socket, including the guest initial configuration and creation. 3) The hybrid model: The user wants to quickly create and start a guest and then asynchronously control it from the API socket. The initial configuration setup is done through the command line and further control go through the API socket. In this model, we need to make sure that the guest configuration is valid. We don't want to support invalid configurations that could implicitly be overwritten through the API socket. In order to support the new models (#2 and #3) we need to be able to tell if an empty guest configuration was passed through the command line or not. If it is empty, then we go with model #2. If it is not empty, we either go with #1 or #3. One way to check if a guest configuration is empty or not is by logically grouping the command line options into a VM config group and a VMM config one. If the VM config group is empty, then the user is not trying to configure a guest. Signed-off-by: Samuel Ortiz <sameo@linux.intel.com>

Add support for multiple disks #2

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions