Opened 21 months ago
Closed 20 months ago
#344 closed enhancement (fixed)
Use less restrictive locking in VM.start()
| Reported by: | joanna | Owned by: | joanna |
|---|---|---|---|
| Priority: | minor | Milestone: | Release 1 Beta 3 |
| Component: | core | Keywords: | |
| Cc: |
Description
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.
Change History (4)
comment:1 Changed 21 months ago by joanna
- Milestone changed from Release 1 Beta 2 to Release 1 Beta 3
comment:2 Changed 20 months ago by joanna
- Priority changed from major to minor
comment:3 Changed 20 months ago by marmarek
comment:4 Changed 20 months ago by marmarek
- Resolution set to fixed
- Status changed from new to closed

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.