Hello Everyone,
Been using VB on windows for some years and been great up to ver 5.2.28 which vb always detected changes in my vmdk file and release&remove the old one in order for the newly created to be effective, However; since upgrading to 6.1.12 3 days ago... things are so different and one of them is I don't know what to do to access my vmdk file as VB constantly opens up a Hard Disk Selector folder which contains none of my vmdk files, I must have done something wrong during the straight forward installation, what must I do to rectify it?
Deeply appreciate your help & thanks in advance.
vmdk issues with VB 6.1.12
-
- Volunteer
- Posts: 841
- Joined: 14. Sep 2019, 16:51
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: WIN11,10, 7, Linux (various)
- Location: United Kingdom
Re: vmdk issues with VB 6.1.12
Long time since I used a 5.2. version but many interface changes were introduced in the transition from 5 to 6, so have a look at Section 5.3 of the the VirtualBox User Manual for the version you've installed (The Virtual Media Manager) to see if you can spot the difference. If you launch 'Virtual Media Manager...' from the VirtualBox Menu you should be able to see whether your 'vmdk' file is known and accessible; and it will show the current file path.
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: vmdk issues with VB 6.1.12
In addition to MultiOS's thoughts, please describe more about what you're seeing, perhaps some screenshots (posted with the forum's Upload Attachment tab not on a 3rd-party site, please).
Finally, please explain exactly what you're trying to do, a nice short statement of your overall intent. Something like this:
"I'm trying to clone my disk file so I can compact it and use the compacted disk file."
I have never seen Virtualbox automatically detect a change in a disk file then automatically release a disk file. How exactly did this happen?JxT2020 wrote:up to ver 5.2.28 which vb always detected changes in my vmdk file and release&remove the old one in order for the newly created to be effective,
Please explain the steps you take to get to this place, and a screenshot of what this "Hard Disk Selector" is.JxT2020 wrote:VB constantly opens up a Hard Disk Selector folder which contains none of my vmdk files
Finally, please explain exactly what you're trying to do, a nice short statement of your overall intent. Something like this:
"I'm trying to clone my disk file so I can compact it and use the compacted disk file."
Re: vmdk issues with VB 6.1.12
Thanks for pointing it out & definitely missed it completely, will reinstall the latest of ver 6, thanks so much.multiOS wrote:Long time since I used a 5.2. version but many interface changes were introduced in the transition from 5 to 6, so have a look at Section 5.3 of the the VirtualBox User Manual for the version you've installed (The Virtual Media Manager) to see if you can spot the difference. If you launch 'Virtual Media Manager...' from the VirtualBox Menu you should be able to see whether your 'vmdk' file is known and accessible; and it will show the current file path.
Sorry it was poorly explained, below is the screenshot I come up with whenever there is a new vmdk file created out of the disk file, then I click on Check which takes me to the options of Release & Remove (VB doesn't do it automatically), once released&removed I choose Add New Disk (Storage Setting) then VB goes to the directory where the newly created vmdk file is. hope it's clearer now... thanks so much again to both of you.scottgus1 wrote:I have never seen Virtualbox automatically detect a change in a disk file then automatically release a disk file. How exactly did this happen?
- Attachments
-
- VB_NewVMDK.png (33.11 KiB) Viewed 18468 times
-
- Volunteer
- Posts: 841
- Joined: 14. Sep 2019, 16:51
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: WIN11,10, 7, Linux (various)
- Location: United Kingdom
Re: vmdk issues with VB 6.1.12
Sorry if this is already obvious to you, but using the the 'new' Virtual Media Manager feature as a base, my understanding is:
- 'Add' puts the existence of a 'new/unlisted' Virtual Disk in to VirtualBox's 'knowledge bank' and then lists it as available, but doesn't attach/mount it to any virtual machine.
- 'Release' unmounts a Virtual Disk, but retain's VirtualBox's knowledge of its existence - It should still be listed as available unless the physical file has been moved/deleted, when it will will still be listed, but with a warning that it is not accessible.
- 'Remove' entirely delists/removes the Virtual Disk from the VirtualBox knowledge base, but doesn't delete the actual disk file (so can still be added back).
- 'Add' puts the existence of a 'new/unlisted' Virtual Disk in to VirtualBox's 'knowledge bank' and then lists it as available, but doesn't attach/mount it to any virtual machine.
- 'Release' unmounts a Virtual Disk, but retain's VirtualBox's knowledge of its existence - It should still be listed as available unless the physical file has been moved/deleted, when it will will still be listed, but with a warning that it is not accessible.
- 'Remove' entirely delists/removes the Virtual Disk from the VirtualBox knowledge base, but doesn't delete the actual disk file (so can still be added back).
-
- Volunteer
- Posts: 5677
- Joined: 14. Feb 2019, 03:06
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Linux, Windows 10, ...
- Location: Germany
Re: vmdk issues with VB 6.1.12
Using 'Remove' provides you with a second dialog where you can select between 'Keep' and 'Delete' the actual disk file.multiOS wrote:- 'Remove' entirely delists/removes the Virtual Disk from the VirtualBox knowledge base, but doesn't delete the actual disk file (so can still be added back).
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: vmdk issues with VB 6.1.12
OK, I see where you are now. Is there anything else you need, or are you good now?JxT2020 wrote:whenever there is a new vmdk file created out of the disk file, then I click on Check which takes me to the options of Release & Remove (VB doesn't do it automatically), once released&removed I choose Add New Disk (Storage Setting) then VB goes to the directory where the newly created vmdk file is. hope it's clearer now... thanks so much again to both of you.
Re: vmdk issues with VB 6.1.12
Yes everything is back to normal now, thanks to you & multiOSscottgus1 wrote:OK, I see where you are now. Is there anything else you need, or are you good now?
Cheers
-
- Site Moderator
- Posts: 20945
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: vmdk issues with VB 6.1.12
Great! Glad you're up and running.