Implement "offline mode" in R4.0

[marmarek]

The idea of "offline mode" is to only manipulate qubes.xml, without talking to libvirt or other system components. This is useful for:

• tests
• installation
• recovery situations

Of course things like starting VM should fail. But listing or setting some properties should work.

[woju]

There is something, but it currently raises exception almost instantly.
https://github.com/woju/qubes-core-admin/blob/core3-devel/qubes/app.py#L135-146⎋

pozdrawiam / best regards .-.
Wojtek Porczyk .-^' '^-.
Invisible Things Lab |'-.-^-.-'|
| | | |
I do not fear computers, | '-.-' |
I fear lack of them. '-._ : ,-'
-- Isaac Asimov `^-^-_>

[woju]

There is something, but it currently raises exception almost instantly.
https://github.com/woju/qubes-core-admin/blob/core3-devel/qubes/app.py#L135-146⎋

pozdrawiam / best regards .-.
Wojtek Porczyk .-^' '^-.
Invisible Things Lab |'-.-^-.-'|
| | | |
I do not fear computers, | '-.-' |
I fear lack of them. '-._ : ,-'
-- Isaac Asimov `^-^-_>

[marmarek]

Take a look at linked commit (marmarek/qubes-core-admin@7de2e64)

[marmarek]

Take a look at linked commit (marmarek/qubes-core-admin@7de2e64)

[woju]

On Sat, May 21, 2016 at 02:37:03PM -0700, Marek Marczykowski-Górecki wrote:

Take a look at linked commit (marmarek/qubes-core-admin@7de2e64)

Won't hurt, but I can't tell from a glance if it is enough for some
weird cases. OK for patching through VMMConnection.init and
Qubes.init.

Will probably need some --argument for various cli tools as it is in
core2. Possibly even for all tools, though likely not supported in all
combinations, especially with some weird interactions of events.
For example QubesVM.name property disallows changing name if domain is
running. If done naively, qvm-prefs --offline-mode would be unsafe.

pozdrawiam / best regards .-.
Wojtek Porczyk .-^' '^-.
Invisible Things Lab |'-.-^-.-'|
| | | |
I do not fear computers, | '-.-' |
I fear lack of them. '-._ : ,-'
-- Isaac Asimov `^-^-_>

[woju]

On Sat, May 21, 2016 at 02:37:03PM -0700, Marek Marczykowski-Górecki wrote:

Take a look at linked commit (marmarek/qubes-core-admin@7de2e64)

Won't hurt, but I can't tell from a glance if it is enough for some
weird cases. OK for patching through VMMConnection.init and
Qubes.init.

Will probably need some --argument for various cli tools as it is in
core2. Possibly even for all tools, though likely not supported in all
combinations, especially with some weird interactions of events.
For example QubesVM.name property disallows changing name if domain is
running. If done naively, qvm-prefs --offline-mode would be unsafe.

pozdrawiam / best regards .-.
Wojtek Porczyk .-^' '^-.
Invisible Things Lab |'-.-^-.-'|
| | | |
I do not fear computers, | '-.-' |
I fear lack of them. '-._ : ,-'
-- Isaac Asimov `^-^-_>