Bug 1386791 - [ESXi][RHEL6]Unable to set resolutions above 1280x1024 with vmwgfx update
Summary: [ESXi][RHEL6]Unable to set resolutions above 1280x1024 with vmwgfx update
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.8
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Bo Yang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-19 15:49 UTC by Deepu K S
Modified: 2021-03-11 14:45 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-10 15:20:20 UTC
Target Upstream Version:


Attachments (Terms of Use)
Xorg logs (55.26 KB, text/plain)
2016-10-19 15:52 UTC, Deepu K S
no flags Details
dmesg output with drm.debug=0xe (92.58 KB, text/plain)
2016-10-19 15:53 UTC, Deepu K S
no flags Details

Description Deepu K S 2016-10-19 15:49:55 UTC
Description of problem:
We are unable to set resolutions above 1280x1024 for VMWare graphics on RHEL 6.8
Higher resolutions are populated in xrandr output. But unable to set.

# xrandr
Screen 0: minimum 1 x 1, current 1024 x 768, maximum 8192 x 8192
Virtual1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   1280x768      60.00 +  59.87
   1920x1200     59.88
   1600x1200     60.00
   1680x1050     59.95
   1400x1050     59.98
   1280x1024     60.02
   1440x900      59.89
   1280x960      60.00
   1360x768      60.02
   1280x800      59.81
   1152x864      75.00
   1024x768      60.00*
   800x600       60.32
   640x480       59.94
Virtual2 disconnected (normal left inverted right x axis y axis)
Virtual3 disconnected (normal left inverted right x axis y axis)
Virtual4 disconnected (normal left inverted right x axis y axis)
Virtual5 disconnected (normal left inverted right x axis y axis)
Virtual6 disconnected (normal left inverted right x axis y axis)
Virtual7 disconnected (normal left inverted right x axis y axis)
Virtual8 disconnected (normal left inverted right x axis y axis)


Running the command for changing the resolution to 1600x1200 raises an error:

# xrandr --verbose --output Virtual1 --mode 1600x1200
    screen 0: 1600x1200 420x315 mm  96.57dpi
    crtc 0:    1600x1200  60.00 +0+0 "Virtual1"
    xrandr: Configure crtc 0 failed
    crtc 0: disable
    crtc 1: disable
    crtc 2: disable
    crtc 3: disable
    crtc 4: disable
    crtc 5: disable
    crtc 6: disable
    crtc 7: disable
    screen 0: revert
    crtc 0: revert
    crtc 1: revert
    crtc 2: revert
    crtc 3: revert
    crtc 4: revert
    crtc 5: revert
    crtc 6: revert
    crtc 7: revert

# xrandr --verbose --output Virtual1 --mode 1280x1024

changes the resolution of Virtual1 without a problem.

Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 6.8
kernel-2.6.32-642.4.2.el6.x86_64
xorg-x11-server-Xorg-1.17.4-9.5.el6_8.x86_64
xorg-x11-drv-vmware-13.1.0-2.el6.x86_64

# lspci | grep -i VGA
00:0f.0 VGA compatible controller: VMware SVGA II Adapter

How reproducible:
Always

Steps to Reproduce:
1. Update kernel to RHEL 6.8 version on a system on VMware.
2. Update xorg-x11-server-Xorg and xorg-x11-drv-vmware to latest
3. xrandr --output <output> --mode 1600x1200

Actual results:
Unable to set resolutions above 1280x1024

Expected results:
Should be able to set higher resolutions supported by driver.

Additional info:
It appears that vmgwgfx.ko module has been introduced with RHEL 6.8 for direct rendering. The issue is seen only on RHEL 6.8 kernels.

RHEL 6.7 and earlier kernels didn't have this problem. Below is a xrandr output which provides higher resolutions and user is able to set the resolutions.

# xrandr 
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 2560 x 1600
default connected 1680x1050+0+0 0mm x 0mm
   1280x768      60.00     0.00  
   2048x1536     85.00    75.00    60.00     0.00  
   1920x1440     85.00    75.00    60.00     0.00  
   1856x1392     75.00    60.00  
   1792x1344     75.00    60.00  
   1600x1200     85.00    75.00    70.00    65.00    60.00     0.00  
   1400x1050     75.00    60.00     0.00  
   1280x1024     85.00    75.00    60.00     0.00  
   1280x960      85.00    60.00     0.00  
   1152x864      75.00     0.00  
   1024x768      85.00    75.00    70.00    60.00     0.00  
   832x624       75.00  
   800x600       85.00    75.00    72.00    60.00    56.00     0.00  
   640x480       85.00    75.00    73.00    60.00     0.00  
   720x400       85.00  
   640x400       85.00     0.00  
   640x350       85.00  
   320x240        0.00  
   400x300        0.00  
   512x384        0.00  
   854x480        0.00  
   1280x720       0.00  
   1366x768       0.00  
   1920x1080      0.00  
   1280x800       0.00  
   1440x900       0.00  
   1680x1050      0.00* 
   1920x1200      0.00  
   2560x1600      0.00  
   720x480        0.00  
   720x576        0.00  
   320x200        0.00  
   800x480        0.00

Comment 1 Deepu K S 2016-10-19 15:52:29 UTC
Created attachment 1212191 [details]
Xorg logs

Comment 2 Deepu K S 2016-10-19 15:53:02 UTC
Created attachment 1212192 [details]
dmesg output with drm.debug=0xe

Comment 3 Deepu K S 2016-10-19 15:54:00 UTC
The workaround found was to boot with kernel-2.6.32-573.26.1.el6.x86_64 kernel.

Comment 6 Sinclair Yeh 2017-03-13 17:20:57 UTC
We will try to reproduce this at VMWare and update this issue.

Comment 7 Bo Yang 2017-03-15 11:08:00 UTC
Update WW11.3

Summary:
Reproduced this issue in RHEL6.8 with kernel-2.6.32-642.4.2.el6.x86_64 based on above steps. 

ENV:
Host: ESX6.0
Guest: kernel-2.6.32-642.4.2.el6.x86_64
xorg-x11-server-Xorg-1.17.4-16.el6_8.x86_64
xorg-x11-drv-vmware-13.1.0-2.el6.x86_64
00:0f.0 VGA compatible controller: VMware SVGA II Adapter

Reproduced Steps:
1. Install Desktop and xorg-x11-drv-vmware
2. "# startx" to boot Desktop
3. "# xrandx" Virtual1 connected 1280x768
4. "# xrandr --verbose --output Virtual1 --mode 1600x1200", reproduced issue

Comment 8 Deepak 2017-03-17 00:16:03 UTC
Could you please attach output of glxinfo and vmware.log file. Thanks

Comment 9 Deepak Rawat 2017-03-18 01:15:34 UTC
It seems max vram size is the limiting factor here to increase the resolution. From logs we can observe:

Maximum display memory size is 9024 kiB

This KB article can be helpful in increasing the resolution of guest OS:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003

[drm] Initialized drm 1.1.0 20060810
vmwgfx 0000:00:0f.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[drm] DMA map mode: Using physical TTM page addresses.
[drm] Capabilities:
[drm]   Rect copy.
[drm]   Cursor.
[drm]   Cursor bypass.
[drm]   Cursor bypass 2.
[drm]   8bit emulation.
[drm]   Alpha cursor.
[drm]   Extended Fifo.
[drm]   Multimon.
[drm]   Pitchlock.
[drm]   Irq mask.
[drm]   Display Topology.
[drm]   GMR.
[drm]   Traces.
[drm]   GMR2.
[drm]   Screen Object 2.
[drm] Max GMR ids is 64
[drm] Max number of GMR pages is 65536
[drm] Max dedicated hypervisor surface memory is 163840 kiB
[drm] Maximum display memory size is 9024 kiB
[drm] VRAM at 0xec000000 size is 9024 kiB
[drm] MMIO at 0xfe000000 size is 256 kiB
[drm] global init.

Comment 10 Deepak Rawat 2017-03-21 18:53:37 UTC
Could you please also make sure the below patch is applied to kernel for VRAM issue:

https://cgit.freedesktop.org/mesa/vmwgfx/commit/?id=40ed03e115bbfb7dea28447166e3e02635abbdbd

Comment 11 Deepak Rawat 2017-03-22 18:17:26 UTC
Commit ID from Linux kernel for previous mentioned patch - d5f1a291e32309324a8c481ed84b5c118d1360ea

Comment 13 Bo Yang 2017-03-28 05:40:59 UTC
(In reply to Deepak from comment #10)
> Could you please also make sure the below patch is applied to kernel for
> VRAM issue:
> 
> https://cgit.freedesktop.org/mesa/vmwgfx/commit/
> ?id=40ed03e115bbfb7dea28447166e3e02635abbdbd

Update WW13.2

As RHEL7.3 build had above patch, retested with all resolutions, it worked.
Retested in RHEL6.9 with kernel 2.6.32-696, also reproduced this issue.

So can we make a rhel6.8 or rhel6.9 build with this patch? and i can verify it again.

Comment 14 Yaju Cao 2017-03-28 05:51:48 UTC
CC Rob Clark who used to deal with vmwgfx related fix

Comment 15 Yaju Cao 2017-03-29 09:52:31 UTC
Hi,

Update from QE side.

We have confirmed RHEL 7.3 has fixed this issue, and the patch for the fix is probably as VMware's mention in Comment 11. As our test result is: The kernel build kernel-3.10.0-499.el7 can reproduce this issue, and kernel-3.10.0-500.el7 has no this issue.

So I suggest that either recommend customer to upgrade to RHEL 7.3.
Or if customer insist to stay on RHEL 6, then we may need developer and PM decide whether the fix can be back-ported. In this case, we QE are pleased to verify the fix. 

Thanks!

Comment 20 Chris Williams 2017-06-07 22:25:01 UTC
Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017.  During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification.  Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com

Comment 21 Bo Yang 2017-06-12 01:53:21 UTC
WW24.1 Update:

The workaround has been documented here:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003

Steps for workaround:
1. Power off target VM
2. Modify VM's vmx file:
        svga.vramSize = "20971520"
        svga.maxWidth = "2560"
        svga.maxHeight = "2048"
3. Power on target VM
4. Set your larger resolution with xrandx

Comment 22 Yaju Cao 2017-06-12 03:21:09 UTC
Hi, Deepu K S

As shown in comment 21, we have confirmed the VMware workaround works for this issue. It seems that this bug can not be fixed in RHEL 6 anymore, but I think you can tell customer to use this workaround.


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