Installer related changes for R4.0

[marmarek]

This is tracking ticket for problems blocking Qubes 4.0 installation.

• qubes-create not called
• template(s) not added to qubes.xml (qvm-add-template called from RPM post-installation script do not exists)
• root.img not migrated to LVM thin pool (if enabled)
• installation should choose LVM thin provisioning by default (now is just LVM)
• default storage pool is set to file-based, even when LVM thin pool was chosen during installation
• default lvm pool assumes qubes_dom0/pool00 name - it should automatically detect pool name based on selected installation (probably look at pool where root filesystem is placed)
• qubes-prefs and qvm-prefs have changed options (no longer accept --set or --get option, properties have underscores) (*)
• qubes-prefs requires --force-root to even get property value (qubes-netvm.service)
• qvm-start do not accept --no-guid option (was renamed to --no-start-guid) (*)

Generally, lets not break things just for the sake of breaking - there is no point in renaming options if their meaning is exactly the same. This applies to points marked with (*). Even when introducing new version (like qvm-prefs without --set/--get), lets still accept the old one. Especially when it's trivial to achieve.

[marmarek]

• qvm-run --all have changed meaning: previously it was about all running domains. This breaks qvm-run --all true used to start missing GUI daemons after user login

While for this particular case, it may be better to start GUI daemon some other way, generally qvm-run --all for all domains, including not currently running, makes very little sense.

[marmarek]

• qvm-run --all have changed meaning: previously it was about all running domains. This breaks qvm-run --all true used to start missing GUI daemons after user login

While for this particular case, it may be better to start GUI daemon some other way, generally qvm-run --all for all domains, including not currently running, makes very little sense.