Closed gvancuts closed 2 years ago
UUIDs are also associated with macros such as POST_STANDARD_VM_UUID1
, POST_STANDARD_VM_UUID2
, .., POST_RTVM_UUID1
and others. See in hypervisor/include/common/vm_uuids.h for all the UUIDs and macros currently defined.
These macros imply some type of VM but what that really does is not clear. It is possible for example to run an RTVM re-using the UUIDs of standard post-launched VMs with no impact on the performance, i.e. it will have the same performance than the VM using the "official" UUID for RTVM.
Use of UUIDs: should the user use them, if so how? I actually cannot think of a reason we’d want those to be exposed to the user at all.
--rtvm
implies we use a specific UUID in the launch script. This is redundant and error-prone. We should be able to leave the UUID out of the picture and letacrn-dm
figure out which to use or throw an error if none is available.