Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionJean-Pierre Pitout
2011-06-13 09:39:12 UTC
Description of problem:
Version-Release number of selected component (if applicable):
When you configure a VNC server in /etc/sysconfig/vncservers and specify the "-nolisten tcp" as an argument for vncserver it will cause qemu-kvm to ignore the <graphics type='vnc' port='1' autoport='no' listen='0.0.0.0'> in /etc/libvirt/qemu/vm-server.xml
How reproducible:
Always.
Steps to Reproduce:
1. Configure a vnc connection with "-nolisten tcp" in /etc/sysconfig/vncservers
2. Configure /etc/libvirt/qemu/<your-vm>.xml with <graphics type='vnc' port='5901' autoport='no' listen='0.0.0.0'>
3. Restart VM.
4. netstat -ntlp | grep qemu-kvm
Actual results:
qemu-kvm ignores <graphics type='vnc' port='5901' autoport='no' listen='0.0.0.0'>
Expected results:
qemu-kvm adheres to <graphics type='vnc' port='5901' autoport='no' listen='0.0.0.0'>
Additional info:
Let me start by saying I am aware that the default/correct way of connecting to a VNC server.
Which would be via a ssh tunnel to localhost. (ie vncviewer -via root@blah localhost:1).
I speculate that this bug may be by design, but I have 2 issues with this:
1. I haven't been able to find any documentation about this behavior, which causes a lot of time to be wasted doing troubleshooting.
2. You cannot get granular with the configuration. Say you want to allow X connections to qemu-kvm, but not to vncserver, you cannot. You are forced into a one-size-fits-all scenario.
Please attach a copy of /etc/sysconfig/vncservers
What is the output of the netstat command in step (4)?
What is the output you expect to see?
What is the output of "netstat -ntlp | grep 590" ?
Comment 3Jean-Pierre Pitout
2011-06-18 08:42:08 UTC
I do apologize, I must have been mistaken as I cannot replicate this anymore.
I suspect I was editig /var/run/libvirt/qemu/vm-server.xml instead of /etc/libvirt/qemu/vm-server.xml, probably a lack of coffee.
Please ignore this bug until further notice.
Kind regards and apologies,
Jean-Pierre Pitout