### System details

Omarchy 4.0.0, Hyprland 0.56.2, running as a VMware guest (Workstation/Player) with the **VMware SVGA II Adapter** (`vmwgfx` kernel driver), no 3D acceleration.

(`omarchy-debug` requires sudo + an interactive TTY, so its output could not be attached here; the relevant Hyprland log excerpts are included inline below.)

### What's wrong?

**Invisible mouse cursor on VMware SVGA II (vmwgfx).**

After login, once the Hyprland desktop finishes loading, the mouse pointer is invisible anywhere on the desktop. During early boot / the display-manager phase (before the compositor takes over) the cursor is still visible. Pointer events are delivered — windows can be focused blindly — but there is no visible pointer.

**Root cause** (from `/run/user/$UID/hypr/$HYPRLAND_INSTANCE_SIGNATURE/hyprland.log`):

The vmwgfx hardware cursor plane fails to commit, hundreds of times per session:

```
DEBUG from aquamarine ]: legacy drm: cursor fb: 26 with bo handle 53039 from fd 52, size [Vector2D: x: 64, y: 64]
ERR from aquamarine ]: legacy drm: drmCloseBufferHandle in cursor failed
... (1700+ occurrences over a few hours)
ERR from aquamarine ]: drm: Cannot commit when a page-flip is awaiting
```

Hyprland pushes the cursor onto the DRM cursor plane, the commit fails on vmwgfx (which is also why `AQ_NO_ATOMIC=1` is needed on this driver — atomic modesetting hangs page-flips), and the pointer never shows up.

**Verified fix**:

Append to `~/.config/hypr/looknfeel.lua`:

```lua
-- VMware SVGA II (vmwgfx) does not display the hardware cursor plane;
-- render the cursor in software.
hl.config({
  cursor = {
    no_hardware_cursors = true,
  },
})
```

After `hyprctl reload`, `hyprctl getoption cursor:no_hardware_cursors` reports `set: true`, the cursor-fb commit errors stop completely, and the pointer is visible. Persists across reboots.

Two things that do NOT work, worth noting in the docs:
- `WLR_NO_HARDWARE_CURSORS=1` as an env var is deprecated and ignored by current Hyprland.
- A `cursor { no_hardware_cursors = true }` block in a legacy `hyprland.conf` is ignored when a `hyprland.lua` config exists (as in Omarchy 4.x).

**Suggestion**: Omarchy already ships `install/user/hardware/fix-nouveau-cursor.sh`, which applies exactly this `no_hardware_cursors` fix when nouveau is detected. The same treatment should cover VMware guests: detect `vmwgfx` (e.g. `lspci -k | grep -q 'Kernel driver in use: vmwgfx'` or `lspci | grep -qi 'VMware SVGA II'`) and append the same block to `looknfeel.lua`. Many people first try Omarchy in a VMware VM, so this is a common first-run failure that silently leaves users with an invisible pointer.

Happy to send a PR if the maintainers agree. Related (different symptom, same environment): #7835.