update to 6.1.16 and lost my config

Discussions related to using VirtualBox on Linux hosts.
Post Reply
JerryG
Posts: 1
Joined: 17. Nov 2020, 16:39

update to 6.1.16 and lost my config

Post by JerryG »

I only have 1 VM on my linux host. in the update process to 6.1.16 my config was lost. When I run Virtualbox my VM does not show. So I desire to add it back.

My structure is this.
ls -l /home/silentm/vmware/CentOS\ 64-bit\ LSI/
-rw------- 1 silentm silentm 8684 Aug 13 08:31 CentOS 64-bit LSI.nvram
-rw-r--r-- 1 silentm silentm 0 Feb 27 2017 CentOS 64-bit LSI.vmsd
-rwxr-xr-x 1 silentm silentm 2735 Aug 13 08:31 CentOS 64-bit LSI.vmx
-rw-r--r-- 1 silentm silentm 272 Feb 27 2017 CentOS 64-bit LSI.vmxf
-rw-r--r-- 1 silentm silentm 32796639232 Nov 17 08:34 CentOS 7-64bit LSI.vmdk
-rw-r--r-- 1 silentm silentm 107382571008 Aug 13 09:05 CentOS 7.vhdx
-rw-r--r-- 1 silentm silentm 323155 Aug 5 08:39 vmware-0.log
-rw-r--r-- 1 silentm silentm 323085 Jun 30 14:14 vmware-1.log
-rw-r--r-- 1 silentm silentm 256013 May 31 10:09 vmware-2.log
-rw-r--r-- 1 silentm silentm 322239 Aug 13 08:31 vmware.log

When I click add and goto the directory above - IT ONLY wants to add *.xml and *.vbox. So that is no good.
When I click New and Enter my name, and use existing disk - it does not like that either.

How can I get this same VM to be in my menu and run again ?
Thanks,
Jerry
scottgus1
Site Moderator
Posts: 20945
Joined: 30. Dec 2009, 20:14
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Windows, Linux

Re: update to 6.1.16 and lost my config

Post by scottgus1 »

JerryG wrote:in the update process to 6.1.16 my config was lost.
An up/down/grade to Virtualbox does not kill the VM list and configuration files, just like updating Word does not delete all the .doc's. Having to completely rebuild everything would be a non-starter.

Virtualbox keeps its configuration files in the logged-on user's home folder. Are you sure you logged onto the same account you were using before?
JerryG wrote:IT ONLY wants to add *.xml and *.vbox.
This is because Virtualbox does not grok VMware's .vmx's, only .vbox's. And Virtualbox stores its logs in a Logs subfolder, not in the VM's main folder as shown.

This is a VMware VM, not a Virtualbox VM. There are no Virtualbox configuration files in this VM's folder. Are you sure you are starting the correct program?
Post Reply