Using vm workstation with almalinux 9.5 installation, and there’s a weird lag in the terminal window with I assume a bash shell (I didn’t check to see what shell is on by default).
Symptom: Each command line you type is mostly fine, but there’s a strange lag when you hit return, and when you’re in vim writing lines of code the same thing. Generally feels weird and unresponsive, not snappy, like typing through a laggy ssh network connection.
The size of the terminal window matters. If it’s small, like it is when you first run the terminal window, then it’s fine. But if you make it larger to take up most of the screen, or hit the button to make it full size and take up all of the screen, that’s when it gets laggy, so it must have something to do with the graphical environment.
Do not have this issue with CentOS/Stream.
Need to fix because I write a ****load of code, and every ms of response time in vim/typing matters.
Hello. I’m using VM Workstation Pro. I “see” the desktop on the desktop, inside of the VM Workstation Pro software, if that makes any sense.
Edit, I just verified it is totally related to how much screen real estate the terminal session takes up on the screen. What I mean is … the default “small” terminal is great. But I made the terminal window larger, in steps, until it took up the full screen, and each time I made it bigger it introduced more “lag”. I believe it is graphics lag, and not keyboard lag, … it just “feels like” keyboard lag.
That is VMware, I presume? (I haven’t used VMware.)
The “seeing” is that hypervisors may offer “Console” view, or one connects to remote directly via VNC, RDP, or something.
Anyway, what “graphics device” does the VMware give for the VM guest?
I’d start by checking that with ‘lspci’. For example:
[root@here ~]# lspci | grep -i vga
00:01.0 VGA compatible controller: Red Hat, Inc. Virtio 1.0 GPU (rev 01)
[root@here ~]# lspci -s 00:01.0 -nn -v
00:01.0 VGA compatible controller [0300]: Red Hat, Inc. Virtio 1.0 GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller])
Subsystem: Red Hat, Inc. Device [1af4:1100]
Flags: bus master, fast devsel, latency 0, IRQ 21
Memory at c0000000 (32-bit, prefetchable) [size=8M]
Memory at 800600000 (64-bit, prefetchable) [size=16K]
Memory at c204f000 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: [98] MSI-X: Enable- Count=3 Masked-
Capabilities: [84] Vendor Specific Information: VirtIO: <unknown>
Capabilities: [70] Vendor Specific Information: VirtIO: Notify
Capabilities: [60] Vendor Specific Information: VirtIO: DeviceCfg
Capabilities: [50] Vendor Specific Information: VirtIO: ISR
Capabilities: [40] Vendor Specific Information: VirtIO: CommonCfg
Kernel driver in use: virtio-pci
That is a VM on libvirt/KVM. The KVM is set to offer ‘Virtio’ device. That is not the only device option that libvirt/KVM has. Some may be more efficient than others.
Likewise, I’d expect the VMware to be able to emulate (or pass through) more that one “GPU” type.
I have to admit that my VM’s do not run GUI. I interact via ssh (CLI) sessions.