Home » Questions » Computers [ Ask a new question ]

Rename vm (files) on vmware workstation

Rename vm (files) on vmware workstation

When I rename a virtual machine in vmware workstation, the old file names (e.g.: the hard drive file name) remains.

Asked by: Guest | Views: 314
Total answers/comments: 2
Guest [Entry]

I use the import option to do this. This way I can keep a base VM on a share someplace called base-XP or whatever, then when I need a new test VM, I do an import and the disks are named according to the setting I specify when going through the import wizard.
Guest [Entry]

"I have used this procedure on both Windows 10 and Ubuntu 21.04 hosts with an Ubuntu guest. These instructions begin by copying the VM, so as to preserve a backup. These instructions use VMware Player, not Workstation, but I believe the steps are largely the same.

Make sure VMware is not running.
Copy the VM's entire folder. To copy in Ubuntu, I ran sudo nautilus (replace nautilus with your own file manager) to open Files with administrator privileges.
When the copying was done, I named the new folder UbuWb.
Inside that folder, I renamed Ubuntu.vmx to be UbuWb.vmx, and deleted all .log, .vmsd, and .vmxf files.
I double-clicked on UbuWb.vmx. This opened VMware Player and produced a dialog that began, ""This virtual machine might have been moved or copied."" Since I was renaming it, I chose ""I Moved It.""
When the VM booted inside Player, I clicked on the VM's top bar > Ctrl-D (or I could have used top bar > Player > Manage > Virtual Machine Settings) > Options tab > General > Virtual machine name > rename as UbuWb > OK (in Windows host) or Save (in Linux host).
I closed down the VM and took a look in the file manager (e.g., Windows File Explorer). The Ubuntu.vmdk and Ubuntu.nvram files hadn't been renamed. I renamed them manually.
I restarted the VM (again, by double-clicking on UbuWb.vmx). In the Ubuntu host, that produced an error: ""File not found: Ubuntu.vmdk."" I clicked Browse > select UbuWb.vmdk > Open, and then restarted the VM.
There was a long minute of just sitting there with a black screen and a dead cursor, but then (in both hosts) the VM started.

I have blogged some additional remarks. My source of guidance was Rasor (2012)."