Bug 1035134
Summary: | Stable guest ABI doesn't check ram value of video | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | tingting zheng <tzheng> |
Component: | libvirt | Assignee: | Ján Tomko <jtomko> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.5 | CC: | dyuan, lcui, mzhan, rbalakri, tzheng, xuzhang |
Target Milestone: | rc | Keywords: | Upstream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | libvirt-0.10.2-31.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1035123 | Environment: | |
Last Closed: | 2014-10-14 04:18:45 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: | |||
Bug Depends On: | 1035123 | ||
Bug Blocks: |
Comment 1
Ján Tomko
2013-12-06 14:23:32 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. 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 |