Bug 479792 - Limited resolution in KVM guest
Limited resolution in KVM guest
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: xorg-x11 (Show other bugs)
rawhide
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: X/OpenGL Maintenance List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-12 23:58 EST by Jerry James
Modified: 2009-01-13 18:34 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-01-13 18:34:14 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
X server log from the guest (23.19 KB, text/plain)
2009-01-12 23:58 EST, Jerry James
no flags Details

  None (edit)
Description Jerry James 2009-01-12 23:58:04 EST
Created attachment 328834 [details]
X server log from the guest

Description of problem:
I created a Rawhide virtual machine on a Fedora 10 host (both x86-64).  I cannot get a display resolution of higher than 800x600 in the guest.  Xorg.0.log shows complaints about both bad modes and insufficient memory for modes.  (I allocated 1 GB of RAM to the guest, but I have no idea how video memory is allocated.)

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.5.99.3-9.fc11.x86_^4

How reproducible:
Always

Steps to Reproduce:
1. Start up my Rawhide guest
  
Actual results:
The display is 800x600, with higher resolutions marked unusable.

Expected results:
I would like to get something a little higher, maybe 1024x768.

Additional info:
Comment 1 Matěj Cepl 2009-01-13 18:34:14 EST
Currently we just emulate curris chip which is not able to do anything better. Adam Jackson advised me at least on workaround:

[00:31:07] ajax: only workaround for now is to run kvm with -std-vga and configure vesa for whatever resolution you want by hand.

Otherwise, this is NOTABUG. We will emulate some better chip eventually.

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