Use less restrictive locking in VM.start()

[marmarek]

Reported by joanna on 9 Sep 2011 14:17 UTC
Currently we're waiting until qrexec connects (or fails) and during this all time we're not allowing any other VM.start() to proceed. This is ineffective because while qrexec waits for connection, we might be already loading another VM.

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

[marmarek]

Modified by joanna on 10 Sep 2011 08:15 UTC

[marmarek]

Modified by joanna on 10 Sep 2011 08:15 UTC

[marmarek]

Modified by joanna on 25 Sep 2011 10:53 UTC

[marmarek]

Modified by joanna on 25 Sep 2011 10:53 UTC

[marmarek]

Comment by marmarek on 10 Oct 2011 15:30 UTC
Starting 5 domains simultaneously takes more than 30s on my hardware, which results in killing domains because of qrexec_daemon timeout.

Anyway changed to allow starting more domain simultaneously.

[marmarek]

Comment by marmarek on 10 Oct 2011 15:30 UTC
Starting 5 domains simultaneously takes more than 30s on my hardware, which results in killing domains because of qrexec_daemon timeout.

Anyway changed to allow starting more domain simultaneously.

[marmarek]

Comment by marmarek on 10 Oct 2011 23:56 UTC
http://git.qubes-os.org/gitweb/?p=marmarek/core.git;a=commit;h=e1ccda362c53c6d18d8ab0fc42fdeda3f0d21e6b

[marmarek]

Comment by marmarek on 10 Oct 2011 23:56 UTC
http://git.qubes-os.org/gitweb/?p=marmarek/core.git;a=commit;h=e1ccda362c53c6d18d8ab0fc42fdeda3f0d21e6b