Bug 798905

Summary: libvirt starts qemu with invalid spice tls port
Product: Red Hat Enterprise Linux 6 Reporter: Gerd Hoffmann <kraxel>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.3CC: acathrow
Target Milestone: rcKeywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-01 09:49:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Gerd Hoffmann 2012-03-01 08:38:01 UTC
Description of problem:
see $summary

Version-Release number of selected component (if applicable):
libvirt-0.9.10-3.el6.x86_64
qemu-kvm-0.12.1.2-2.234.el6.x86_64

How reproducible:
    <graphics type='spice' autoport='yes' listen='127.0.0.1'>
      <listen type='address' address='127.0.0.1'/>
    </graphics>

qemu is started with ... 

-spice port=5900,tls-port=4294967295,addr=127.0.0.1,disable-ticketing

... and complains ...

qemu-system-x86_64: spice tls-port is out of range

... which is obviously true.

Comment 1 Gerd Hoffmann 2012-03-01 08:40:11 UTC
qemu doesn't start, which makes this a regression.

Comment 2 Gerd Hoffmann 2012-03-01 08:48:45 UTC
Tried to workaround this by disabling autoport.  xml looks like this now:

    <graphics type='spice' port='5900' autoport='no' listen='127.0.0.1'>
      <listen type='address' address='127.0.0.1'/>
    </graphics>

Now libvirt complains:

[root@rincewind ~]# virsh start fedora-org-ahci
error: Failed to start domain fedora-org-ahci
error: unsupported configuration: spice TLS port set in XML configuration, but TLS is disabled in qemu.conf

Comment 5 Gerd Hoffmann 2012-03-01 09:49:04 UTC

*** This bug has been marked as a duplicate of bug 798220 ***