Libvirt SPICE direct consoles
This specification proposes modifications to Nova's libvirt driver to support "direct" SPICE VDI consoles. These consoles are "direct" in that they are not intended to use a HTML5 transcoding proxy to access, and instead the user would use a native SPICE client like `remote-viewer`.
Blueprint information
- Status:
- Complete
- Approver:
- Sylvain Bauza
- Priority:
- Undefined
- Drafter:
- Michael Still
- Direction:
- Approved
- Assignee:
- Michael Still
- Definition:
- Approved
- Series goal:
- Accepted for 2025.1
- Implementation:
-
Implemented
- Milestone target:
- None
- Started by
- Sylvain Bauza
- Completed by
- Sylvain Bauza
Related branches
Related bugs
Sprints
Whiteboard
Proposed spec: https:/
[20240719 bauzas] Spec approved for the Dalmatian cycle
Gerrit topic: https:/
Addressed by: https:/
libvirt: Add config option to require secure SPICE.
Addressed by: https:/
WIP: libvirt: allow concurrent access to SPICE consoles.
Addressed by: https:/
WIP: libvirt: Add guest devices to support SPICE USB.
Addressed by: https:/
WIP: libvirt: Optionally enable SPICE debug logging.
Addressed by: https:/
WIP: libvirt: Optionally support sound when using SPICE.
Addressed by: https:/
libvirt: allow direct SPICE connections to qemu
Addressed by: https:/
libvirt: Add extra spec for sound device.
Addressed by: https:/
libvirt: direct SPICE console object changes
Addressed by: https:/
libvirt: direct SPICE console database changes
Addressed by: https:/
libvirt: Add extra specs for USB redirection.
[20241119 bauzas] Spec reapproved for the Epoxy timeframe
[20250306 bauzas] Marking the blueprint as Implemented since we merged the new API microversion but as we have the 2nd stage series still open, we will need to create another blueprint (eg. libivrt-spice-2) for Flamingo.
