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.

Bug 1017217

Summary: Multiple devices of same type can share "resources"
Product: Red Hat Enterprise Linux 6 Reporter: Tomas Jamrisko <tjamrisk>
Component: qemu-kvmAssignee: Gerd Hoffmann <kraxel>
Status: CLOSED NOTABUG QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.5CC: acathrow, bsanford, bsarathy, chayang, codong, dyuan, juzhang, mazhang, michen, mkenneth, qzhang, tjamrisk, virt-maint, zpeng
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-10 14:45:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tomas Jamrisko 2013-10-09 12:58:04 UTC
Description of problem:
Using the same device multiple times can result in them sharing some "resources", such as I/O port, interrupt or DMA channel. Which can result in them not behaving properly. 

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.410.el6.x86_64
seabios-0.6.1.2-28.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Start a windows VM with 4 qxl devices: 
"-vga qxl -device qxl -device qxl -device qxl"
2. Look into Device Manager and Display adapters

Actual results:
One of those 4 adapters will have a yellow triangle with exclamation mark

Expected results:
it should work properly.

Additional info:
The error causing the warning is 'Code 12': This device cannot find enough free resources that it can use. 

http://technet.microsoft.com/en-us/library/cc732199%28v=ws.10%29.aspx

Comment 1 Tomas Jamrisko 2013-10-09 13:00:40 UTC
Adding regression as this previously worked properly. At least on qemu-kvm-rhev-0.12.1.2-2.355.el6_4.3.x86_64

Comment 4 Tomas Jamrisko 2013-10-09 15:57:51 UTC
*** Bug 1010422 has been marked as a duplicate of this bug. ***

Comment 5 Gerd Hoffmann 2013-10-10 12:26:02 UTC
Reproduces.  I see it with both 410 and 355 builds, thus no regression.

Most likely your guests are configured in different ways.  With four qxl devices you have to set the vram size to 32mb (instead of using the default of 64mb), otherwise the qxl pci bars do not fit into the pci i/o hole.  Please double-check.

Comment 6 Tomas Jamrisko 2013-10-10 14:45:25 UTC
Yes, you are right. For some reason the configuration between RHEV3.2 and RHEV3.3 got changed from 32 to 64. And now in the latest build changed it back to 32 again... Closing as NOTABUG, as this definitely wasn't an issue in qemu-kvm after all... (didn't know about the limit)