The ESXi console is a window into your virtual machine, and like any window it has limits: a resolution stuck in 2005, a clipboard that does nothing, keys that arrive late. Most of it is fixable in minutes. The rest is about knowing when to stop fighting the console and use the right door instead.
Every Ubuntu-on-ESXi user meets the same three console complaints. The screen opens at a tiny fixed resolution. Copy-paste between your computer and the VM silently fails. And everything feels a half-second behind, as if the VM were on another continent. Each has a different cause - a missing package, a host policy, or the simple physics of a remote framebuffer - and this page separates them so you fix the right one.
ESXi gives you two ways in. The browser console runs in the web client: nothing to install, fine for installs and emergencies, but keyboard handling and screen updates are the weakest of any option. VMware Remote Console (VMRC) is a free standalone app from VMware/Broadcom: full-screen mode, better key handling (it can send combinations the browser traps), local device redirection, and a noticeably snappier picture.
Honest guidance: install Ubuntu through whichever console is open, then install VMRC on the machine you administer from. If you spend real hours in VM consoles, the difference is not subtle.
An Ubuntu Desktop VM that opens at a tiny resolution and refuses to offer bigger ones is almost always missing its display partner package:
sudo apt updatesudo apt install open-vm-tools-desktopIf sizes are still limited, check the VM's video settings: the default virtual graphics memory is sized for ordinary single-screen use; only raise it for genuinely large or multi-monitor console work. And remember the ceiling - the console renders what the virtual SVGA adapter can do, not what your physical graphics card can do. For a beautiful desktop experience, the answer is not a bigger console setting; it is a remote desktop protocol, covered below.
Clipboard sharing rides on the same desktop tools package, so install it and reboot first. If it still fails, the honest second cause: host policy. ESXi exposes per-VM isolation settings that control copy, paste and drag-and-drop, and in many environments they are deliberately switched off - a clipboard is a two-way data door, and security teams close it on purpose.
On your own lab host you can enable the isolation options in the VM's advanced settings. On an office host you do not control, accept the policy and use the grown-up alternative: transfer files over the network - a shared folder, scp, or the datastore browser for ISOs. Fighting a deliberate security policy with workarounds is how admins lose access entirely.
A remote console redraws the guest's framebuffer and ships you the picture. Text typing will feel close; anything graphical will trail. You can reduce it - VMRC instead of the browser, a wired network instead of congested Wi-Fi, a host that is not CPU-starved - but you cannot make it feel local.
So work like administrators actually do:
If even SSH feels laggy, stop blaming the console: the host is overloaded, and the sizing guide in this series is the real fix.
Black console, VM clearly running: usually Ubuntu's own screen blanking or lock, not a crash. Click into the console and press a key, wait a few seconds for the picture to return, and consider disabling screen blanking on a lab VM you administer through the console.
Keys landing wrong: the browser console maps your keyboard through the browser and your local layout; VMRC handles layouts more faithfully. For install-time emergencies, the console menus offer explicit "send key" options for combinations like Ctrl+Alt+Delete that your own OS would otherwise swallow.
Console freezes while the VM is under load: a saturating VM is a slow VM everywhere, console included. Cross-check with SSH or the host performance tab before concluding the console itself is broken.
The full process on a live ESXi host - creating the virtual machine, installing Ubuntu and fixing the common problems, exactly as they appear on screen.
Watch Full VideoTwo causes cover almost every case. First, the Ubuntu Desktop VM needs the open-vm-tools-desktop package installed and a reboot. Second, the host may block clipboard sharing through the VM's isolation settings - a deliberate security choice on many office hosts. On your own host you can enable it in the VM's advanced settings; on a managed host, move files over the network instead.
Yes, VMRC is a free download from VMware/Broadcom, and for anyone who administers VMs regularly it is absolutely worth it: full-screen mode, reliable special-key handling, better keyboard layouts and a visibly smoother picture than the browser console. The browser console remains handy for quick checks from any machine.
Because a console is a remote picture of the guest display, not a local one - every change is rendered, captured and shipped to you, so graphical work always trails your input a little. Reduce it with VMRC and a wired connection, but for daily work use the right protocol: SSH for Ubuntu Server, or a remote desktop service for Ubuntu Desktop. The console is the rescue door, not the front door.