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.
Bug 1292394 - Vnc server should failed to start when specifying -vnc :a in qemu start option
Summary: Vnc server should failed to start when specifying -vnc :a in qemu start option
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.8
Hardware: x86_64
OS: Windows
low
low
Target Milestone: rc
: ---
Assignee: Gerd Hoffmann
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-17 10:15 UTC by Guo, Zhiyi
Modified: 2016-01-15 16:16 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-15 16:16:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Guo, Zhiyi 2015-12-17 10:15:13 UTC
Description of problem:
Vnc server should failed to start when specifying -vnc :a in qemu start option

Version-Release number of selected component (if applicable):
kernel: 2.6.32-593.el6.x86_64
qemu:qemu-kvm-0.12.1.2-2.482.el6.x86_64
virt-viewer:virt-viewer-2.0-6.el7.x86_64
qxlwddm: qxlwddm-0.1-12

How reproducible:


Steps to Reproduce:
1.Launch vm with command:
qemu-kvm -name win10x64 -m 8G -machine pc,accel=kvm\
        -cpu SandyBridge\
        -smp 8 \
        -name win10 \
        -uuid 990ea161-6b67-47b2-b803-19fb01d30d12 \
        -device virtio-serial -chardev spicevmc,id=vdagent,debug=0,name=vdagent \
        -vnc :a \
        -serial unix:/tmp/m,server,nowait \
        -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 \
        -vga qxl \
        -cdrom /usr/share/virtio-win/virtio-win-1.7.5.iso \
        -drive file=/home/storage/win10-1.qcow2,if=none,id=drive-scsi-disk0,format=qcow2,cache=none,werror=stop,rerror=stop -device virtio-scsi-pci,id=scsi0 -device scsi-hd,drive=drive-scsi-disk0,bus=scsi0.0,scsi-id=0,lun=0,id=scsi-disk0,bootindex=1 \
        -monitor stdio \

Actual results:
Guest launch successfully. Info vnc from monitor:
QEMU 0.12.1 monitor - type 'help' for more information
(qemu) info vnc
Server:
     address: 0.0.0.0:5900
        auth: none
Client: none


Expected results:
Guest should failed to launch and kindly error info should prompt like:
Failed to start VNC server on `:a': can't convert to a number: a

Additional info:
vnc option should only accept none negative integer and should not over 59635.

Comment 2 Gerd Hoffmann 2016-01-04 12:52:19 UTC
Does this happen on RHEL-7 too?

Comment 3 Guo, Zhiyi 2016-01-06 02:56:42 UTC
No such issue happen on RHEL 7.2, qemu version: qemu-kvm-rhev-2.3.0-31.el7.x86_64
On qemu-kvm-rhev:
If specify 'vnc :a',qemu-kvm-rhev will prompt: Failed to start VNC server on `:a': can't convert to a number: a
And if specify 'vnc :65535', qemu-kvm-rhev will prompt: Failed to start VNC server on `:65535': port 65535 out of range.
On qemu-kvm-0.12.1.2-2.482.el6.x86_64:
Both 'vnc :a' and 'vnc :65535' accepted by qemu-kvm.
[root@dhcp-11-59 clustering]# qemu-kvm -vnc :a -monitor stdio
QEMU 0.12.1 monitor - type 'help' for more information
(qemu) info vnc
Server:
     address: 0.0.0.0:5900
        auth: none
Client: none
[root@dhcp-11-59 clustering]# qemu-kvm -vnc :65535 -monitor stdio
QEMU 0.12.1 monitor - type 'help' for more information
(qemu) info vnc
Server:
     address: 0.0.0.0:5899
        auth: none
Client: none

Comment 4 Gerd Hoffmann 2016-01-06 07:16:07 UTC
> No such issue happen on RHEL 7.2, qemu version:

Good.

Usually we don't backport that kind of minor issues, it just gets fixed upstream and picked up on new releases (and by rebasing too).  The later happened already (RHEL-7 not affected).  Setting low prio for now.  WONTFIX candidate.

Comment 5 Ademar Reis 2016-01-15 16:16:17 UTC
(In reply to Gerd Hoffmann from comment #4)
> > No such issue happen on RHEL 7.2, qemu version:
> 
> Good.
> 
> Usually we don't backport that kind of minor issues, it just gets fixed
> upstream and picked up on new releases (and by rebasing too).  The later
> happened already (RHEL-7 not affected).  Setting low prio for now.  WONTFIX
> candidate.

Agree


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