[UX] should config values related to the VM (disk-size, cpu, memory) be reflective of actual state of the VM?

[anjannath]

The usual way to find out the disk-size, cpu, memory of the CRC instance is to look at their respective config values, but these values only. give information about the desired config and not the actual config in the VM. crc status command shows the actual information but only when the instance is running.

/cc @gbraad

[cfergeau]

Both values are useful to know, so we need a way to get both. Imo it's good that config reflects what the user requested. If we also want the actual config of the VM to be in crc config, I'd add a --live, --actual flag for this. Imo it's fine to have this in crc status. I don't think actual cpu/memory will make a lot of sense when the VM is not running/will be possible to know, so this leaves only disk size?

[gbraad]

the api should be able to return requested and actual, so in that case the UI can decide what to show around this; actual is the most important as this is the truth...

Might become more relevant again when the CRC extension is more mature.