Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1567709 - Need an error msg when try to change the heads in cirrus and vga video xml snippet
Summary: Need an error msg when try to change the heads in cirrus and vga video xml sn...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux Advanced Virtualization
Classification: Red Hat
Component: libvirt
Version: 8.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Lili Zhu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-16 03:17 UTC by Lili Zhu
Modified: 2021-02-15 07:38 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-15 07:38:25 UTC
Type: Bug
Target Upstream Version:


Attachments (Terms of Use)

Description Lili Zhu 2018-04-16 03:17:31 UTC
Description of problem:
 Need an error msg when try to change the heads in cirrus and vga video xml snippet

Version-Release number of selected component (if applicable):
libvirt-3.9.0-14.el7_5.2.x86_64

How reproducible:
100%

Steps to Reproduce:
Now it seems that the attribute heads can be set in the xml of cirrus and vga video.
1. prepare a guest with cirrus or vga video
2. edit the number of screen
# virsh dumpxml vm1
......
   <video>
      <model type='cirrus' vram='16384' heads='3' primary='yes'/>
    </video>
......

3. check the number of screen using virt-viewer

Actual results:
There is only 1 screen.

Expected result:
Generate an error message if the heads can not be changed in cirrus and vga video xml

Additional info:

Comment 5 RHEL Program Management 2021-02-15 07:38:25 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


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