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.
Description of problem:
The issue here is that qemu started with "-vnc none,..." reports invalid authentication method to VNC clients like virt-manager or virt-viewer and they are forced to tell qemu to skip authentication via libvirt.
See Bug 1434551 how virt-manager needs to workaround this issue.
Version-Release number of selected component (if applicable):
all versions of qemu
Comment 2Marc-Andre Lureau
2017-03-28 16:07:22 UTC
Sent to QEMU list:
[PATCH] vnc: allow to connect with add_client when -vnc none
Comment 3Marc-Andre Lureau
2017-06-06 09:07:50 UTC
The bug does not seem to happen with qemu-kvm-1.5.3-139.el7, I suppose it's a regression of a later version refactoring (the code change significantly there).
Pavel, could you confirm? I suggest to close this bug if it doesn't happen.
This bug is valid also for qemu-kvm, I've just tested it with qemu-kvm-1.5.3-140.el7. The code is significantly different but the same issue is there:
vnc.c:2996
...
if (strcmp(display, "none") == 0)
return;
...
To test it you can comment these lines in /usr/share/virt-manager/virtManager/domain.py:1198
graphics = self.get_graphics_devices()[0]
if (graphics.type == "vnc" and
graphics.get_first_listen_type() == "none"):
flags = libvirt.VIR_DOMAIN_OPEN_GRAPHICS_SKIPAUTH
and create a guest with VNC and listen type set to "none". If the workaround in virt-manager is commented you get a message "Viewer was disconnected".
Comment 6Marc-Andre Lureau
2017-06-09 14:24:13 UTC
Sent patch "[RHEL-7.4 qemu-kvm PATCH] vnc: allow to connect with add_client when -vnc none" on rhvirt-list.
Comment 8Miroslav Rezanina
2017-09-20 12:28:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2018:0816