Bug 797769

Summary: Use vga as the default display adapter
Product: Red Hat Enterprise Linux 6 Reporter: Marko Myllynen <myllynen>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2CC: acathrow, dallan, dyuan, eblake, juzhang, mzhan, rjones, rwu, ydu, yupzhang
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 795688 Environment:
Last Closed: 2012-02-28 17:37:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Marko Myllynen 2012-02-27 09:32:37 UTC
+++ This bug was initially created as a clone of Bug #795688 +++

Description of problem:
Libvirt leaves the policy of the default display adapter hardware up to the hypervisor meaning that with QEMU one gets Cirrus instead of vga. However, as can be shown with glxgears vga provides much better FPS rate than Cirrus (these numbers are from RHEL 6.2 host/guest on a Lenovo laptop):

cirrus : 78 FPS
vga    : 260 FPS

Please make vga as the default display adapter in libvirt when using QEMU.

Version-Release number of selected component (if applicable):
RHEL 6.2

Additional info:
With the proposed optimizations in the bugs below the difference is even greater to vga's advantage:

https://bugzilla.redhat.com/show_bug.cgi?id=795685
https://bugzilla.redhat.com/show_bug.cgi?id=795686

--- Additional comment from dallan on 2012-02-22 18:57:24 EET ---

Marko, I understand what you're saying, but libvirt explicitly leaves this kind of decision up to either qemu or to management applications using libvirt (e.g., ovirt, virt-manager), so I have to close this as NOTABUG.  I'm sure that there are places where we've failed to follow that rule, but in general we try to honor it.

--- Additional comment from eblake on 2012-02-22 19:38:44 EET ---

(In reply to comment #3)
> Marko, I understand what you're saying, but libvirt explicitly leaves this kind
> of decision up to either qemu or to management applications using libvirt
> (e.g., ovirt, virt-manager), so I have to close this as NOTABUG.  I'm sure that
> there are places where we've failed to follow that rule, but in general we try
> to honor it.

That said, we should probably open bugs against virt-install and virt-manager so that default creation of new guests prefers vga where appropriate, rather than deferring to hypervisor defaults.

--- Additional comment from myllynen on 2012-02-27 11:31:08 EET ---

(In reply to comment #4)
> (In reply to comment #3)
> > Marko, I understand what you're saying, but libvirt explicitly leaves this kind
> > of decision up to either qemu or to management applications using libvirt
> > (e.g., ovirt, virt-manager), so I have to close this as NOTABUG.  I'm sure that
> > there are places where we've failed to follow that rule, but in general we try
> > to honor it.
> 
> That said, we should probably open bugs against virt-install and virt-manager
> so that default creation of new guests prefers vga where appropriate, rather
> than deferring to hypervisor defaults.

I've now proposed this change in the upstream mailing list:

http://lists.nongnu.org/archive/html/qemu-devel/2012-02/msg03274.html

Per Eric's suggestion I'll clone this bug against virt-install and virt-manager.

Thanks.

Comment 2 Dave Allan 2012-02-27 14:03:55 UTC
Cole, what do you think?

Comment 3 Cole Robinson 2012-02-28 17:37:03 UTC
This change would only exist in python-virtinst (which virt-manager uses) so duping to that bug

*** This bug has been marked as a duplicate of bug 797772 ***