Core doesn't start qrexec daemon when starting dependent VMs

[marmarek]

Reported by joanna on 29 Mar 2011 12:43 UTC
This can be easily seen when we have a firewallvm and netvm and firewallvm is set as default netvm in the system (and it depends on netvm). In that case the init.d/qubes_netvm start script starts the defeault netvm (so the firewallvm), which it turn requires it to start the dependent vms (so netvm), but doesn't start qrexec for the latter. As a result the user cannot use qvm-run to execute commands on the netvm (starting manually /usr/lib/qrexec_daemon fixes the problem).

Migrated-From: https://wiki.qubes-os.org/ticket/160

[marmarek]

Comment by rafal on 31 Mar 2011 09:27 UTC
Fixed in http://git.qubes-os.org/?p=rafal/core.git;a=commit;h=d6bdb85883d858dbc942543a2ae2b5b11f37140d
Its descendant, http://git.qubes-os.org/?p=rafal/core.git;a=commit;h=b7698de251828d6391f63f28d454d6de5fbfeca6, is nice to have.

Now qrexec_daemon is started in vm.start(). Note that now we need to revert #128, reopened.

[marmarek]

Comment by rafal on 31 Mar 2011 09:27 UTC
Fixed in http://git.qubes-os.org/?p=rafal/core.git;a=commit;h=d6bdb85883d858dbc942543a2ae2b5b11f37140d
Its descendant, http://git.qubes-os.org/?p=rafal/core.git;a=commit;h=b7698de251828d6391f63f28d454d6de5fbfeca6, is nice to have.

Now qrexec_daemon is started in vm.start(). Note that now we need to revert #128, reopened.

[marmarek]

Modified by rafal on 31 Mar 2011 09:27 UTC

[marmarek]

Modified by rafal on 31 Mar 2011 09:27 UTC