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 1035134 - Stable guest ABI doesn't check ram value of video
Summary: Stable guest ABI doesn't check ram value of video
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Ján Tomko
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 1035123
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-27 07:06 UTC by tingting zheng
Modified: 2014-10-14 04:18 UTC (History)
6 users (show)

Fixed In Version: libvirt-0.10.2-31.el6
Doc Type: Bug Fix
Doc Text:
Clone Of: 1035123
Environment:
Last Closed: 2014-10-14 04:18:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1374 0 normal SHIPPED_LIVE libvirt bug fix and enhancement update 2014-10-14 08:11:54 UTC

Comment 1 Ján Tomko 2013-12-06 14:23:32 UTC 
Fixed upstream:
commit 952ab4c993b88a324c5910346efa4e75a72293b7
Author:     Ján Tomko <jtomko>
CommitDate: 2013-12-06 15:00:16 +0100

    Add qxl ram size to ABI stability check
    
    55bfd02 added a 'ram' attribute for qxl video devices
    but didn't update the ABI check.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1035123

git describe: v1.2.0-63-g952ab4c
Comment 5 tingting zheng 2014-04-14 09:36:13 UTC 
Tested pass with:
libvirt-0.10.2-32.el6.x86_64

Steps:
1.Prepare a guest,set the Display as "Spice" and Video as "QXL".
2.Boot the guest.
3.Use virsh dumpxml to get the xml of the guest.
# virsh dumpxml mig > mig.xml

4.Change the ram value of video:eg:change ram from '65536' to '65535'
change xml from:
      <model type='qxl' ram='65536' vram='65536' heads='1'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
to:
      <model type='qxl' ram='65535' vram='65536' heads='1'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>

5.Do migrate,error shows:
# virsh migrate --live mig qemu+ssh://$ip/system --xml mig.xml
error: unsupported configuration: Target video card ram 65535 does not match source 65536

Refer to the above comments,move the bug to VERIFIED.
Comment 7 errata-xmlrpc 2014-10-14 04:18:45 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.

http://rhn.redhat.com/errata/RHBA-2014-1374.html
Note You need to log in before you can comment on or make changes to this bug.