Hello,
I have a question. Where are the entries stored in the Virtual Media Manager Optical drive section? Are these iso file paths stored in an XML file. I don't see them in the VirtualBox.xml file.
Virtual Media Manager entries location ?
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Virtual Media Manager entries location ?
The virtual media manager shows you all of the media from all registered VMs.
There has been no global media registry stored in VirtualBox.xml since the VBox 3.x days - over four years ago now.
There has been no global media registry stored in VirtualBox.xml since the VBox 3.x days - over four years ago now.
Re: Virtual Media Manager entries location ?
That doesn't explain how the media manager knows that I once upon a time had an ISO attached, which is no longer attached to any virtual machines, and the ISO no longer exists. Every time I launch Virtualbox it complains that the ISO file doesn't exist. There are other ISOs in the list that do exist, and the "Attached to:" field clearly says "Not Attached".mpack wrote:The virtual media manager shows you all of the media from all registered VMs.
There has been no global media registry stored in VirtualBox.xml since the VBox 3.x days - over four years ago now.
The VM configuration files don't actually reference an ISO file name, they only reference a UUID, so there must be a data store mapping the UUID to a path.
-
mpack
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Mostly XP
Re: Virtual Media Manager entries location ?
I didn't "explain" anything except how VirtualBox works since v4 came out. I don't exactly know what you are seeing, but it doesn't change how VirtualBox works.
For example, if the VirtualBox.xml file was created in V3 days then it may contain a media register. You can easily open it in a text editor and look. But you said that you already did this.
It's also possible that you have missed that the media register in a .vbox file is separate from the controller section which references an image by UUID.
If VirtualBox shows you media in the media manager, then it hasn't just invented a filename out of thin air: the ISO is registered. Either in VirtualBox.xml, or in the .vbox file of a registered VM. On startup the VirtualBox GUI scans those files to build the list it shows you in media anager.
The only other place that stores a list of files is the recent files list, but you only see those in a file open dialog, not media manager.
For example, if the VirtualBox.xml file was created in V3 days then it may contain a media register. You can easily open it in a text editor and look. But you said that you already did this.
It's also possible that you have missed that the media register in a .vbox file is separate from the controller section which references an image by UUID.
If VirtualBox shows you media in the media manager, then it hasn't just invented a filename out of thin air: the ISO is registered. Either in VirtualBox.xml, or in the .vbox file of a registered VM. On startup the VirtualBox GUI scans those files to build the list it shows you in media anager.
The only other place that stores a list of files is the recent files list, but you only see those in a file open dialog, not media manager.