<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Command Line - Tag - Dimas Maulana</title>
    <link>https://dimasmaulana.pages.dev/tags/command-line/</link>
    <description>Dimas Maulana Website</description>
    <generator>Hugo 0.165.0 &amp; FixIt v0.4.5</generator>
    <language>en</language>
    <lastBuildDate>Thu, 07 May 2026 00:10:21 +0000</lastBuildDate>
    <atom:link href="https://dimasmaulana.pages.dev/tags/command-line/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>VMware Fusion Cannot Unlock a Virtual Machine from the CLI</title>
      <link>https://dimasmaulana.pages.dev/posts/software/vmware-fusion-cli-unlock-limitation/</link>
      <pubDate>Thu, 07 May 2026 00:10:21 +0000</pubDate>
      <guid>https://dimasmaulana.pages.dev/posts/software/vmware-fusion-cli-unlock-limitation/</guid>
      <category domain="https://dimasmaulana.pages.dev/categories/software/">Software</category>
      <category domain="https://dimasmaulana.pages.dev/categories/troubleshooting/">Troubleshooting</category>
      <description>&lt;p&gt;Unlocking a virtual machine from the command line was not reliable in VMware Fusion on macOS. The limitation was easy to misread as an incorrect command, a damaged virtual machine, or a stale lock file, because all three can produce similar-looking failures.&lt;/p&gt;&#xA;&lt;p&gt;The useful comparison was running the same task in VMware Workstation on Windows. Against a comparable virtual-machine setup, the command-line workflow worked there. That moved the focus away from the VM and toward the difference between the two VMware products.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
