Unify terminology for service vm/user vm

NanlinXie commented 3 years ago

From DX view, we hope we could keep consistency for all these terminologies throughout our document and code, after discussion we are aligned:

1.User VM: A VM where user-defined environments and applications run. User VMs can run different OSes based on their needs, including for example, Ubuntu for an AI application, Android or Windows for a Human-Machine Interface, or a hard real-time control OS such as Zephyr, VxWorks, or RT-Linux for soft or hard real-time control. There are three types of User VMs: pre-launched, post-launched Standard and post-launched Real-Time User VMs.

2.Service VM: a special Virtual Machine (VM), directly launched by the hypervisor. The Service VM can access hardware resources directly by running native drivers and provides device sharing services to post-launched User VMs through the ACRN Device Model (DM). Hardware resources include CPUs, memory, graphics memory, USB devices, disk, and network mediation.

3.Guest: a generic term for any Virtual Machine (VM) that runs on top of the hypervisor. Both Service and User VMs are Guest VMs from the hypervisor’s perspective, albeit with different properties. This term can be found in the names of functions and variables in the ACRN source code.

Doc Impact Analysis:

[ ] New feature -> new HLD and usage guide
[ ] HLDs
[ ] Configuration data
[ ] Kernel module parameters
[ ] Device Model (acrn-dm) parameters
[ ] Hypervisor shell commands
[ ] ACRN tools (debug and/or service)
[ ] Build system
[x] Other documents (e.g. tutorials)

NanlinXie commented 3 years ago

Need go through all the documentation to align with code

NanlinXie commented 2 years ago

Doc PR : https://github.com/projectacrn/acrn-hypervisor/pull/6911

projectacrn / acrn-hypervisor

Unify terminology for service vm/user vm #6559