<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Varda Ali</title>
    <description>The latest articles on DEV Community by Varda Ali (@vardaali).</description>
    <link>https://dev.to/vardaali</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4061074%2Fb6948322-18c4-43ce-804f-01260b4e1b57.jpg</url>
      <title>DEV Community: Varda Ali</title>
      <link>https://dev.to/vardaali</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vardaali"/>
    <language>en</language>
    <item>
      <title>Kali Linux Mouse Cursor Invisible in VMware Workstation — Fixed with SWcursor Config</title>
      <dc:creator>Varda Ali</dc:creator>
      <pubDate>Mon, 03 Aug 2026 17:16:46 +0000</pubDate>
      <link>https://dev.to/vardaali/kali-linux-mouse-cursor-invisible-in-vmware-workstation-fixed-with-swcursor-config-4f74</link>
      <guid>https://dev.to/vardaali/kali-linux-mouse-cursor-invisible-in-vmware-workstation-fixed-with-swcursor-config-4f74</guid>
      <description>&lt;h2&gt;
  
  
  Problem
&lt;/h2&gt;

&lt;p&gt;Running Kali Linux (2025.4, Xfce, X11) as a VM in VMware Workstation on a Windows host. The mouse cursor was completely invisible inside the VM window — the mouse still moved and clicks still worked, but no cursor icon rendered anywhere on screen. It worked fine everywhere on the Windows host, just not inside the Kali VM.&lt;/p&gt;

&lt;p&gt;If you're building a home lab for penetration testing/SOC practice and hit this, it's more common than you'd think — and most of the fixes floating around online don't actually target the real cause.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I tried that didn't fix it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Reinstalled &lt;code&gt;open-vm-tools-desktop&lt;/code&gt; and &lt;code&gt;fuse3&lt;/code&gt;, rebooted&lt;/li&gt;
&lt;li&gt;Toggled VMware's "Accelerate 3D graphics" setting on and off&lt;/li&gt;
&lt;li&gt;Switched Xfce's cursor theme away and back (including explicitly to DMZ-White)&lt;/li&gt;
&lt;li&gt;Manually forced a cursor refresh: &lt;code&gt;xsetroot -cursor_name left_ptr&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Fixed Windows display scaling (was at 125%, tested at 100%)&lt;/li&gt;
&lt;li&gt;Enabled "Override high DPI scaling" in VMware's compatibility settings&lt;/li&gt;
&lt;li&gt;Fully uninstalled VMware Workstation Player (EOL) and installed the new free VMware Workstation Pro&lt;/li&gt;
&lt;li&gt;Ruled out an external mouse driver conflict by testing with it fully unplugged&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of these touched the actual problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  The actual cause
&lt;/h2&gt;

&lt;p&gt;Checking the Xorg log pointed at the real issue:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;cat&lt;/span&gt; /var/log/Xorg.0.log | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-i&lt;/span&gt; cursor
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This showed:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;(WW) modeset(0): Option "HWcursor" is not used ```



Kali was using the generic `modesetting` X11 driver (not a VMware-specific one), and its **hardware cursor** wasn't rendering correctly inside the VM. 
Note: don't bother trying to install `xserver-xorg-video-vmware` — it's not available in current Kali repos, because Kali doesn't use that driver anymore.

## What actually fixed it

Force a **software cursor** instead of the broken hardware one:



```bash
sudo mkdir -p /etc/X11/xorg.conf.d
sudo nano /etc/X11/xorg.conf.d/20-swcursor.conf
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Paste this into the file:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;Section &lt;span class="s2"&gt;"Device"&lt;/span&gt;
    Identifier &lt;span class="s2"&gt;"Configured Video Device"&lt;/span&gt;
    Driver &lt;span class="s2"&gt;"modesetting"&lt;/span&gt;
    Option &lt;span class="s2"&gt;"SWcursor"&lt;/span&gt; &lt;span class="s2"&gt;"true"&lt;/span&gt;
EndSection
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Save, exit, then reboot:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nb"&gt;sudo &lt;/span&gt;reboot
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Cursor showed up immediately after reboot.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this happens
&lt;/h2&gt;

&lt;p&gt;VMware's virtual display adapter and the Linux &lt;code&gt;modesetting&lt;/code&gt; driver don't always agree on how to composite the hardware cursor layer - especially on certain host GPU/driver combinations. Forcing software cursor rendering sidesteps the compositing bug entirely by having Xorg draw the cursor itself instead of relying on hardware acceleration for it.&lt;/p&gt;




&lt;p&gt;If you're setting up a Kali lab and hit this exact symptom (mouse moves, no cursor visible), skip the theme-switching and DPI settings — check your Xorg log first, then go straight to the SWcursor fix.&lt;/p&gt;

</description>
      <category>kalil</category>
      <category>vmware</category>
      <category>cybersecurity</category>
      <category>linux</category>
    </item>
  </channel>
</rss>
