Bug 875403 - UI provides no way to choose an explicit SPICE port without configuring TLS
Summary: UI provides no way to choose an explicit SPICE port without configuring TLS
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virt-manager
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Cole Robinson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-11 01:20 UTC by Tristan Schmelcher
Modified: 2014-01-29 14:24 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-01-29 14:24:18 UTC
Embargoed:


Attachments (Terms of Use)

Description Tristan Schmelcher 2012-11-11 01:20:27 UTC
Description of problem:

When adding a SPICE display in the virt-manager UI, if the user disables automatic port allocation, then they are forced to enter a TLS port. This causes QEMU VMs to fail to run if TLS is not configured in qemu.conf. Thus, if TLS is not configured, then there is no way for the user to choose an explicit SPICE port through the UI.

Version-Release number of selected component (if applicable):

0.9.3

How reproducible:

100%

Steps to Reproduce:
1. On a system without TLS configured in QEMU, open virt-manager.
2. Open the Details for a working QEMU VM.
3. Add Hardware -> Graphics -> Spice server.
4. Disable automatic port allocation.
5. Choose a non-TLS port.
6. Attempt to remove the suggested TLS port number. Observe that the UI won't let you.
7. Click Finish.
8. Try to run the VM.

Actual results:

The user is forced to choose a TLS port and the VM fails to start, saying error "unsupported configuration: spice TLS port set in XML configuration, but TLS is disabled in qemu.conf".

Expected results:

The user should be able to set an explicit non-TLS port without having to set a TLS port, e.g. by specifying the TLS port as 0 or empty.

Additional info:

On Ubuntu 12.10, package version 0.9.3-1ubuntu2.

Workaround:

Hand-modify the XML to remove the tlsPort attribute.

Comment 1 Cole Robinson 2014-01-29 14:24:18 UTC
Thanks for the report, fixed upstream now


Note You need to log in before you can comment on or make changes to this bug.