VMware Communities
wuairen
Contributor
Contributor

Cannot run linux(centos7) guest with resolution 1920*1080 under runlevel 3 console mode in host win10.

Hi,

I am running linux(centos7) guest with runlevel 3 console mode ( multi-user mode, which should be without X-server) under host win10, with Workstation 15 player.

I am not how to set it to run with resolution 1920x1080 mode, although it runs normally for runlevel 5, with X-server and Gnome.

When it boots up, it runs with default 800x600, then it seems not be able to change this resolution with full screen mode, unlike the runlevel 5, with X-server and Gnome, which will maximize the linux window with 1920x1080 under full screen mode.

My hardware is Dell notepad Latitude 5480 with Intel core i5.

For the vm hardware display setting, I tried options with/without 3D acceleration,  using host setting for monitors, and specific monitor setting(1920x1080)/

From the grub2 boot and run 'vbeinfo' from grub2, it seems there is no 1920x1080 mode supported by bios. It shows max mode is 1152x864.

Attempted to set the below in grub2, but it failed.

  GRUB_GFXMODE=1920x1080

GRUB_GFXPAYLOAD_LINUX=keep

I also attempted to change the  default resolution to 1920x1080 from the driver vmwgfx, but failed.

  • vmwgfx_drv.c

https://osdn.net/projects/android-x86/scm/git/kernel/blobs/c2b2fbc1a33e67826d264d5568d82b1491fc2bf9/...

From the below dmesg after with vga mode (1152x864), it seems that drm vmwgfx driver initialized from this grub set resolution.

If BIOS cannot support 1920x1080, then can we change the resolution during vmwgfx initialized?

[   20.648379] [drm] DMA map mode: Using physical TTM page addresses.

[   20.649877] [drm] Capabilities:

[   20.652662] [drm]   Rect copy.

[   20.653815] [drm]   Cursor.

[   20.654718] [drm]   Cursor bypass.

[   20.655635] [drm]   Cursor bypass 2.

[   20.656538] [drm]   8bit emulation.

[   20.657746] [drm]   Alpha cursor.

[   20.659128] [drm]   3D.

[   20.660012] [drm]   Extended Fifo.

[   20.661534] [drm]   Multimon.

[   20.663520] [drm]   Pitchlock.

[   20.664353] [drm]   Irq mask.

[   20.665139] [drm]   Display Topology.

[   20.666009] [drm]   GMR.

[   20.667656] [drm]   Traces.

[   20.668921] [drm]   GMR2.

[   20.669932] [drm]   Screen Object 2.

[   20.670871] [drm]   Command Buffers.

[   20.672784] [drm]   Command Buffers 2.

[   20.674149] [drm]   Guest Backed Resources.

[   20.674773] [drm]   DX Features.

[   20.675398] [drm] Max GMR ids is 64

[   20.676017] [drm] Max number of GMR pages is 65536

[   20.676642] [drm] Max dedicated hypervisor surface memory is 0 kiB

[   20.677250] [drm] Maximum display memory size is 131072 kiB

[   20.677871] [drm] VRAM at 0xe8000000 size is 4096 kiB

[   20.678491] [drm] MMIO at 0xfe000000 size is 256 kiB

[   20.679517] [drm] global init.

[   20.684090] [TTM] Zone  kernel: Available graphics memory: 2995720 kiB

[   20.686497] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB

[   20.687137] [TTM] Initializing pool allocator

[   20.687754] [TTM] Initializing DMA pool allocator

[   20.688435] vmwgfx 0000:00:0f.0: BAR 1: can't reserve [mem 0xe8000000-0xefffffff pref]

[   20.689040] [drm] It appears like vesafb is loaded. Ignore above error if any.

[   20.690205] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).

[   20.690798] [drm] No driver support for vblank timestamp query.

[   20.695720] [drm] Screen Target Display device initialized

[   20.698090] [drm] width 1152

[   20.698992] [drm] height 864

[   20.700310] [drm] bpp 32

[   20.706967] [drm] Fifo max 0x00040000 min 0x00001000 cap 0x0000077f

[   20.710895] [drm] Using command buffers with DMA pool.

[   20.711721] [drm] DX: yes.

[   20.712435] [drm] Atomic: yes

[   20.727048] checking generic (e8000000 400000) vs hw (e8000000 400000)

[   20.727062] fb: conflicting fb hw usage svgadrmfb vs VESA VGA - removing generic driver

[   20.727831] Console: switching to colour dummy device 80x25

[   20.729772] fbcon: svgadrmfb (fb0) is primary device

[   20.735793] Console: switching to colour frame buffer device 144x54

[   20.741865] [drm] Initialized vmwgfx 2.14.0 20170612 for 0000:00:0f.0 on minor 0

Any suggestions were appreciated.

0 Kudos
6 Replies
wila
Immortal
Immortal

Hi,

As you can see in your log, vmwgfx isn't initialized until later.

At that time you run with the framebuffer driver.

I don't think it is possible what you want to do with VMware Workstation Player.

Did the 1152x864 resolution work for you?

On VMware Workstation Professional you can set the display to resize to max and you get the "higher" screen resolution by that means.

This however is not an option with Player as it is a feature for the Professional version only.

Hope this helps,

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
0 Kudos
wuairen
Contributor
Contributor

Hi Wil,

Thanks for your answer.

So it should be that workstation player cannot support this.

0 Kudos
wila
Immortal
Immortal

Hi,

Yes I think so, not supported.

What you can do is use a terminal in your host and connect via SSH, then you can use the resolution provided by the host.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
0 Kudos
rpc_scandinavia
Contributor
Contributor

I don't know if this helps, but I run Debian Linux on a virtual machine under ESXi.

I add the following to "/etc/default/grub":

GRUB_GFXMODE=1920x1080x32,1680x1050x32,1600x900x32,1280x800x32,1024x768x32,auto

GRUB_GFXPAYLOAD_LINUX=keep

And then "update-grub".

When I boot, it does not change the resolution to 1920x1080.

To do this, I have to edit my virtual machine VMX file and change the hardware version to "10", then it boots in 1920x1080 from start (grub and forward).

Somehow the 1920x1080 mode is not available on virtual hardware version greater then ten.

kasper
Enthusiast
Enthusiast

I use VMWare workstation 16.1 as a WIndows 10 host and Centos 8 as a guest.   I have installed several variations of Centos (workstation, server, server with gui, etc) and can change the resolution up to 2560x1600.    It  makes the change and I apply and save.    However when I reboot it goes back to the default resolution.   I have tried several XRANDR changes and those did not work.   Will look at the GRUB reply.     Thank you for the post.

0 Kudos
rpc_scandinavia
Contributor
Contributor

Later I discovered that I also must set this value in the VMX file, for the GRUB stuff to work:

 

svga.guestBackedPrimaryAware = "FALSE"

 

This enables 1920 * 1080 from boot.

Please note that this is reset to "TRUE", when the VM is powered off and on again  😞