Old unused vdi file on another drive generates VERR_FILE_NOT_FOUND error

English Virtualization
1

The following was posted on a VirtualBox forum, but since the VirtualBox files were downloaded from the SuSE repo via YaST, the comment of a moderator on the VirtualBox forum prompted me to post here as well.

I recently installed a new OS (SuSE Leap 42.1) and VirtualBox 5.0.18 on a new partition of an SSD. Another partition on the same drive has SuSE 13.2 and VirtualBox 4.3.26.

I copied the entire directory for a standalone, full clone in SuSE 13.2 to the new (42.1) system. Until now, I never received any errors in 13.2. Following the transfer of the virtual machine to 42.1 and registration of the .vdi file, the machine started and operated, again without error.

Two days ago (06/28/16), I accepted a SuSE update of VirtualBox from 5.0.18 to 5.0.22, which included the following files:


    virtualbox-qt-5.0.22-19.1.x86_64
    virtualbox-guest-x11-5.0.22-19.1.x86_64
    virtualbox-5.0.22-19.1.x86_64
    virtualbox-guest-tools-5.0.22-19.1.x86_64
    virtualbox-host-kmp-default-5.0.22_k4.1.26_21-19.1.x86_64
    virtualbox-guest-kmp-default-5.0.22_k4.1.26_21-19.1.x86_64

Although my recollection is not precise, shortly thereafter upon re-starting VirtualBox, I received the following error:


    ‘/z/linux13-1/root/VirtualBox VMs/WindowsXP Clone1/WindowsXP Clone1.vdi’
    VD:error VERR_FILE_NOT_FOUND opening image file

The Windows XP VM flagged in Virtual Media Manager is located on an entirely different drive (/sda vs. the SSD /sde). Moreover, it was used with the very first SuSE install, SuSE 13.1, in 2014, which has not been used or accessed in more than one year. The same error now also appears when I go back to the 13.2 installation on /sde. Although I have not done an exhaustive search, I am unaware of any errant snapshots on any of the systems. Everything functioned correctly when in use.

While the new system functions properly and I don’t believe that this will cause me any difficulties (although I may be wrong about that), I am puzzled as to the origin of this error. Mindful of the problems that may occur through the deletion of files, even those arguably not in use, I have not attempted to change or delete anything.

I welcome any advice and suggestions. I can provide more information and configuration files if that would be helpful.

Thanks.

2

One additional, possibly important piece of information. In view of comments in some VirtualBox forum posts, I realized that I needed to update the guest additions .iso from 5.0.18 to 5.0.22, but I did that after I received the error message. Perhaps that caused the error - but I can’t think of why the mismatch in the guest additions would have caused this.

3

Recommend you re-inspect your default location for virtual machines. I’ve seen your error in the past where a VBox upgrade doesn’t always preserve all custom settings, IIRC simply re-setting solves the problem

VM Virtualbox Manager > File > Preferences > General > Default Machine Folder.

And, as long as you have “Preferences” open, re-check every other setting.

And, you might also check the “remembered” locations of other things in each individual Guest, particularly the paths to the virtual disks, both the system disk and the virtual cdrom ISO files.

And, be aware that old versions of files can appear if your system “recovers” a file, eg if your system crashes and isn’t shut down gracefully.

TSU

4

tsu2 -

Thanks - you’ve helped me zero in on several anomalies that I’m not certain how to resolve.

As a preliminary matter, the Default Machine Folder is /root/VirtualBox VMs, the default location according the VirtualBox Manual sec. 10.1.1. SuSE placed the configuration files in /root/.config/VirtualBox. So that appears to be in order.

First, I discovered from Preferences that I had not updated the extension pack from the initial install of v. 5.0.18 (2 strikes! first the guest additions and now the extension pack). Preferences > extensions now displays Version 5.0.22r108108. And Manager > Settings > Storage > Controller:IDE shows VBoxGuestAdditions_5.0.22.iso.

But an icon in Windows 7 curiously displays guest additions v. 4.3.26r98988. And in the registry, HKLM/SOFTWARE/Oracle/VirtualBox_Guest_Additions, the version and revision is similarly 4.3.26 and 98988, respectively. Lastly, the files in C\Program_Files\Oracle\VirtualBox_Guest_Additions all display the 2015 install date from 13.2 (and thus the old version), and not 2016. As mentioned previously, the VM was copied in its entirety from the 13.2 installation and then registered in the new machine in Leap 42.1, so that would explain the initial references to prior guest additions. Nonetheless, even I went through the guest additions install process twice (once with 5.0.18 and again with 5.0.22), they don’t seem to have carried through to Windows 7. I do recall the Wizard running (at least the first time). Attempts to run an update via Devices > Insert Guest Additions CD Image do not work, perhaps because VirtualBox senses that it has already installed the most current CD. There are 5.0.22 exe’s in the Windows CD folder which I suspect may start the wizard.

Second, the end of one of the logs from the configuration directory (VBoxSVC.log) lists a series of errors:

VirtualBox XPCOM Server 5.0.22_SUSE r108108 linux.amd64 (openSUSE Buildservice) release log
00:00:00.002355 main     Log opened 2016-07-01T18:21:13.505315000Z
00:00:00.002357 main     Build Type: release
00:00:00.002360 main     OS Product: Linux
00:00:00.002361 main     OS Release: 4.1.26-21-default
00:00:00.002362 main     OS Version: #1 SMP PREEMPT Mon Jun 13 13:32:30 UTC 2016 (294632f)
00:00:00.002383 main     DMI Product Name: System Product Name
00:00:00.002390 main     DMI Product Version: System Version
00:00:00.002463 main     Host RAM: 5957MB total, 5321MB available
00:00:00.002467 main     Executable: /usr/lib/virtualbox/VBoxSVC
00:00:00.002467 main     Process ID: 2274
00:00:00.002468 main     Package type: LINUX_64BITS_GENERIC (OSE)
00:00:00.112366 nspr-2   Home directory: '/root/.config/VirtualBox'
00:00:00.112579 nspr-2   Loading settings file "/root/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:00.113291 nspr-2   Successfully initialised host USB using sysfs
00:00:00.119407 nspr-2   NAT: resolv.conf: nameserver 192.168.1.1
00:00:00.119456 nspr-2   HostDnsMonitor: old information
00:00:00.119466 nspr-2     no server entries
00:00:00.119475 nspr-2     no domain set
00:00:00.119481 nspr-2     no search string entries
00:00:00.119487 nspr-2   HostDnsMonitor: new information
00:00:00.119493 nspr-2     server 1: 192.168.1.1
00:00:00.119499 nspr-2     domain: home
00:00:00.119505 nspr-2     search string 1: home
00:00:00.119517 nspr-2   HostDnsMonitorProxy::notify
00:00:00.123813 nspr-2   VD: VDInit finished
00:00:00.123877 nspr-2   ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={0eb668d2-495e-5a36-8890-29999b5f030c} aComponent={SystemPropertiesWrap} aText={Cannot determine default Guest Additions ISO location. Most likely they are not available}, preserve=false aResultDetail=0
00:00:00.127147 nspr-2   Loading settings file "/root/VirtualBox VMs/m5-vm2/m5-vm2.vbox" with version "1.14-linux"
00:00:15.174085 nspr-2   Load [/usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxHostWebcam.so] rc VINF_SUCCESS
00:00:15.387514 nspr-3   ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={f30138d4-e5ea-4b3a-8858-a059de4c93fd} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0
00:00:15.413872 nspr-3   ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={f30138d4-e5ea-4b3a-8858-a059de4c93fd} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0
00:01:00.928327 nspr-4   ERROR [COM]: aRC=NS_ERROR_NOT_IMPLEMENTED (0x80004001) aIID={0eb668d2-495e-5a36-8890-29999b5f030c} aComponent={SystemPropertiesWrap} aText={Method setDefaultAdditionsISO is not implemented}, preserve=false aResultDetail=0
00:01:26.700897 nspr-2   ERROR [COM]: aRC=NS_ERROR_NOT_IMPLEMENTED (0x80004001) aIID={0eb668d2-495e-5a36-8890-29999b5f030c} aComponent={SystemPropertiesWrap} aText={Method setDefaultAdditionsISO is not implemented}, preserve=false aResultDetail=0
00:01:35.225551 nspr-4   ERROR [COM]: aRC=NS_ERROR_NOT_IMPLEMENTED (0x80004001) aIID={0eb668d2-495e-5a36-8890-29999b5f030c} aComponent={SystemPropertiesWrap} aText={Method setDefaultAdditionsISO is not implemented}, preserve=false aResultDetail=0
00:05:26.413329 nspr-3   Load [/usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxHostWebcam.so] rc VINF_SUCCESS
00:05:28.194091 nspr-2   ERROR [COM]: aRC=NS_ERROR_NOT_IMPLEMENTED (0x80004001) aIID={0eb668d2-495e-5a36-8890-29999b5f030c} aComponent={SystemPropertiesWrap} aText={Method setDefaultAdditionsISO is not implemented}, preserve=false aResultDetail=0
00:05:43.993854 nspr-4   ERROR [COM]: aRC=NS_ERROR_NOT_IMPLEMENTED (0x80004001) aIID={0eb668d2-495e-5a36-8890-29999b5f030c} aComponent={SystemPropertiesWrap} aText={Method setDefaultAdditionsISO is not implemented}, preserve=false aResultDetail=0
00:08:28.824683 nspr-2   ERROR [COM]: aRC=NS_ERROR_NOT_IMPLEMENTED (0x80004001) aIID={0eb668d2-495e-5a36-8890-29999b5f030c} aComponent={SystemPropertiesWrap} aText={Method setDefaultAdditionsISO is not implemented}, preserve=false aResultDetail=0
00:18:35.331291 nspr-4   ERROR [COM]: aRC=NS_ERROR_NOT_IMPLEMENTED (0x80004001) aIID={0eb668d2-495e-5a36-8890-29999b5f030c} aComponent={SystemPropertiesWrap} aText={Method setDefaultAdditionsISO is not implemented}, preserve=false aResultDetail=0

These would appear to confirm some of the problems I have identified, but not the reference to the old clone in 13.1.

I have done some searching in both the VirtualBox and SuSE virtualization forums to see how to address this, but I haven’t found anything concrete and I am reluctant to do anything until I receive more guidance. One possible strategy would be to unmount the guest additions iso from the system and then attempt to reload it. Perhaps I would also need to delete files from the program files directory and keys in the registry.

Ironically, despite all of this, the system works and works well! Nevertheless, I believe that it would be prudent to clean this up.

Thanks again for your assistance.

5

Are you running it under root??? Those files should be in your home folder. root should have nothing to do with it.

6

To update the Guest Additions (Which has to be done in each Guest individually),

“Run” the VM
In the Guest Window,
Devices > Insert Guest Additions CD image…

If your VirtualCD was automatically mounted during boot, you will be prompted that it will need to be unmounted before remounted with the Guest Additions ISO. Agree to the notification.

Now, you can open your File Manager to the mounted CDROM and find the Guest Additions install for your particular OS.

These steps automatically access the new Guest Additions ISO that is pre-packaged with your Virtualbox installation, so should be consistent with your new latest version of Virtualbox.

TSU

7

Yes, I am running root. I am fully cognizant of the risks and potential downsides, but due to somewhat unique circumstances here, that is how this machine is configured.

Please, I do not wish to get into a discussion about this - I can easily present both sides. Rather, I would prefer to solve the guest additions update question and the original error, as well as anything associated with this.

Thank you.

8

tsu2 -

Thanks for your response.

In my response to you (post #4), just before the code box with the log, I stated that “[a]ttempts to run an update via Devices > Insert Guest Additions CD Image do not work, perhaps because VirtualBox senses that it has already installed the most current CD.” I also mentioned that the VirtualBox manager displays “VBoxGuestAdditions_5.0.22.iso.” See http://susepaste.org/60337424. Please let me know if that is different from you are suggesting.

Additional clarification: nothing happens when I click on the “Insert Guest Additions CD Image” option - no dialog, no wizard.

If I did follow the correct procedure, should I now power down the VM, remove the iso, perhaps delete something on the Windows side as well, and then start the process anew?

One additional point - I am using the Yast repo version of VirtualBox, not the download from the Oracle site. When I first ran the “Insert Guest Additions CD Image” process, the iso was downloaded after a prompt from the dialog in VirtualBox. Thus, I’m a little uncertain by the reference to “the new Guest Additions ISO that is pre-packaged with your Virtualbox installation.” There was no iso with the install - I needed to get it either from Oracle’s website, the dialog, or some other source.

Thanks again.

9

On Thu 30 Jun 2016 08:06:01 PM CDT, w2tq wrote:

Two days ago (06/28/16), I accepted a SuSE update of VirtualBox from
5.0.18 to 5.0.22, which included the following files:

Hi
If you updated to version 5.0.22 then this came from a non-standard
repo?

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.26-21-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

10

malcolmlewis -

No, it came from the YaST update: https://lists.opensuse.org/opensuse-updates/2016-06/msg00111.html

In the past, I tended to avoid all but the most critical updates (starting with SuSE v. 9.x), but I have had Leap 42.1 on two other machines for some time and I accepted updates on those with no ill effects. So I decided to accept updates on this machine (the one I trying to fix).

As can be seen from the list archive item, this was a maintenance update rated moderate. What I didn’t realize at the time was the need to update both the extension pack and the guest additions at the same time. But as explained earlier in post #4, the original install of the guest additions (v. 5.0.18) never carried through to the Windows guest, even though the iso was mounted.

To be clear, I used the YaST repo version to install VirtualBox after installing Leap 42.1, which I’ve done in the past and it’s worked fine.

11

Hi
OK, my bad, web UI showed 5.0.8, patch info pointed at 5.0.22, but wondered as there are other repos…

12

malcolmlewis -

On the contrary, your question was very good, as there are at least two or three sources from which to obtain the VirtualBox files (from the VirtualBox website, YaST, and SuSE repos, the last two possibly being the same) and it is easy to commingle files from tow or more of them and then create a corrupt installation due to file incompatibility.

I was advised in this forum a few years ago to use the files from YaST, as they would then track the updates from YaST and to the kernel, avoiding any need to refresh or recompile, etc. Further, the YaST version was arguably tailored to work well with SuSE. I haven’t done any research since then but my guess is that advice still holds.

Again, your question is an excellent one. To be precise, while the basic files came from YaST (and thus ultimately a SuSE repo), VirtualBox reaches out, most likely to a repo associated with Oracle or perhaps SuSE) to obtain the guest additions iso. See Manual, sec. 4.2.1.1. Installation (“In the “Devices” menu in the virtual machine’s menu bar, VirtualBox has a handy menu item named “Insert Guest Additions CD image”, which mounts the Guest Additions ISO file inside your virtual machine. A Windows guest should then automatically start the Guest Additions installer, which installs the Guest Additions into your Windows guest. Other guest operating systems (or if automatic start of software on CD is disabled) need manual start of the installer.”).

I obtained the extension pack directly from the Oracle website: https://www.virtualbox.org/wiki/Download_Old_Builds_5_0. I was unable to identify another source.
Hopefully, these are compatible. But I must have something to generate these errors.

Thanks for asking.

13

Although I run my VBox on Windows, it’s very unlikely that internally, the VBox application itself should be any different no matter the HostOS.

The Guest Additions source (an ISO file) should always be installed as part of the overall Virtualbox application, so the two should always be matched, there is no reason why there might be a mis-match using the described way to install Guest Additions unless someone dug into the app and modified it (ie Manually replaced the iso file). The other way that is subject to error is to manually point the virtual CDROM to a Guest Additions iso file which may not be the correct file.

The Virtualbox Extensions are not distributed with the Virtualbox application.
When upgrading, the Virtualbox application <may> detect Extensions need to be upgraded but it’s unreliable… I don’t always see this.
If Virtualbox has been upgraded to the latest release (Today, that’s 5.24), then you can download the file from the Virtualbox website, then “Add” a new extension in Virtualbox > File > Preferences. When you “Add” this Extension file, Virtualbox will detect its type and offer to replace the older existing Extensions.

HTH,
TSU

14

tsu2 -

Thank you for the reply and the background on VirtualBox guest additions and extension pack. With your advice to check preferences, I did learn of and then correct extension pack mismatch. That one was straightforward.

Two issues remain. First, and most immediately, how to I direct VirtualBox or Windows 7 to load the correct guest additions (5.0.22). As I mentioned, the VirtualBox Manager shows that the correct iso (5.0.22) is mounted, but nothing happens when I select the VirtualBox guest install command (Device > Insert, etc.). I can see from Windows Explorer that although the exe’s for 5.0.22 were loaded, the guest additions installed in program files are those from v. 4.3.26 (carried over when I copied the VM). Even though I initiated the iso installation with the original 5.0.18 VirtualBox implementation, it apparently did not properly install in Windows 7.

I am tempted to run the VBoxWindowsAdditions.exe in the Windows CD drive folder (v. 5.0.22r108108 - the same as the current VirtualBox install), unless you or someone recommends something different.

Secondly, there is the VERR_FILE_NOT_FOUND error, but getting the correct guest additions installed may resolve that. And, as mentioned several times, the system works despite the warnings.

Thanks. I look forward to further advice and suggestions.

15

Further update - making some progress.

In VirtualBox manual, sec. 4.2.1.1, about two-thirds of the way through the section, the manual states that one may “. . . choose VBoxWindowsAdditions.exe from the CD/DVD drive inside the guest to start the installer.” So I did that and now the files in C\program_files\Oracle etc. have been updated to the matching version (5.0.22r108108). So that worked and didn’t blow up the system.

Now the logs read slightly differently. VBoxSVC.log:

VirtualBox XPCOM Server 5.0.22_SUSE r108108 linux.amd64 (openSUSE Buildservice) release log
00:00:00.001507 main     Log opened 2016-07-02T22:56:44.267290000Z
00:00:00.001509 main     Build Type: release
00:00:00.001513 main     OS Product: Linux
00:00:00.001514 main     OS Release: 4.1.26-21-default
00:00:00.001515 main     OS Version: #1 SMP PREEMPT Mon Jun 13 13:32:30 UTC 2016 (294632f)
00:00:00.001537 main     DMI Product Name: System Product Name
00:00:00.001543 main     DMI Product Version: System Version
00:00:00.001642 main     Host RAM: 5957MB total, 5431MB available
00:00:00.001646 main     Executable: /usr/lib/virtualbox/VBoxSVC
00:00:00.001647 main     Process ID: 3441
00:00:00.001647 main     Package type: LINUX_64BITS_GENERIC (OSE)
00:00:00.106867 nspr-2   Home directory: '/root/.config/VirtualBox'
00:00:00.107049 nspr-2   Loading settings file "/root/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:00.107904 nspr-2   Successfully initialised host USB using sysfs
00:00:00.111918 nspr-2   NAT: resolv.conf: nameserver 192.168.1.1
00:00:00.111985 nspr-2   HostDnsMonitor: old information
00:00:00.111994 nspr-2     no server entries
00:00:00.112000 nspr-2     no domain set
00:00:00.112003 nspr-2     no search string entries
00:00:00.112007 nspr-2   HostDnsMonitor: new information
00:00:00.112010 nspr-2     server 1: 192.168.1.1
00:00:00.112014 nspr-2     domain: home
00:00:00.112018 nspr-2     search string 1: home
00:00:00.112025 nspr-2   HostDnsMonitorProxy::notify
00:00:00.114023 nspr-2   VD: VDInit finished
00:00:00.114120 nspr-2   ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={0eb668d2-495e-5a36-8890-29999b5f030c} aComponent={SystemPropertiesWrap} aText={Cannot determine default Guest Additions ISO location. Most likely they are not available}, preserve=false aResultDetail=0
00:00:00.117962 nspr-2   Loading settings file "/root/VirtualBox VMs/m5-vm2/m5-vm2.vbox" with version "1.14-linux"
00:00:11.976818 nspr-2   Load [/usr/lib/virtualbox/ExtensionPacks/Oracle_VM_VirtualBox_Extension_Pack/linux.amd64/VBoxHostWebcam.so] rc VINF_SUCCESS
00:00:12.200486 nspr-3   ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={f30138d4-e5ea-4b3a-8858-a059de4c93fd} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0
00:00:12.227276 nspr-2   ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={f30138d4-e5ea-4b3a-8858-a059de4c93fd} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false aResultDetail=0

Note that the third event from the end (00:00:00.11.976818) states that the extension pack loaded successfully. But there are three errors.

The last two seem to have something to do with a screenshot that’s not available. I’m going to put those aside for now, as I don’t believe they will preclude or degrade the VM’s operation.

The first one is puzzling, because the iso is in what I believe to be the default location for the configuration files: /$user/.config/VirtualBox. And the machine’s .vbox xml file shows this address(see ):

<?xml version="1.0"?>
<!-- ** DO NOT EDIT THIS FILE. etc. 
. . .
-->
<VirtualBox xmlns="http://www.innotek.de/VirtualBox-settings" version="1.14-linux">
  <Machine uuid="{cab7b222-509b-417b-bb03-5b5bb38234bb}" name="m5-vm2" OSType="Windows7_64" snapshotFolder="Snapshots" lastStateChange="2016-07-02T22:56:57Z">
    <MediaRegistry>
      <HardDisks>
        <HardDisk uuid="{3790b482-03fa-42e9-bf2a-f01852a19721}" location="win7 Clone1-disk1.vdi" format="VDI" type="Normal"/>
        <HardDisk uuid="{45fbe6ed-99e6-4384-8bab-7fb614ecb27a}" location="/z/linux13-1/root/VirtualBox VMs/WindowsXP Clone1/WindowsXP Clone1.vdi" format="VDI" type="Normal"/>
      </HardDisks>
      <DVDImages>
        <Image uuid="{11962368-06c0-4e9d-9f35-bf4448741447}" location="/root/.config/VirtualBox/VBoxGuestAdditions_5.0.22.iso"/>
      </DVDImages>
      <FloppyImages/>
    </MediaRegistry>
    <ExtraData>
      <ExtraDataItem name="GUI/LastCloseAction" value="PowerOff"/>
      <ExtraDataItem name="GUI/LastGuestSizeHint" value="1657,1078"/>
      <ExtraDataItem name="GUI/LastGuestSizeHint1" value="1689,1114"/>
      <ExtraDataItem name="GUI/LastNormalWindowPosition" value="133,29,1657,1131"/>
      <ExtraDataItem name="GUI/LastNormalWindowPosition1" value="2006,29,1689,1171"/>
      <ExtraDataItem name="GUI/LastScaleWindowPosition" value="2,23,1596,1128"/>
      <ExtraDataItem name="GUI/LastVisibilityStatusForGuestScreen1" value="true"/>
      <ExtraDataItem name="GUI/RestrictedRuntimeDevicesMenuActions" value="HardDrives"/>
      <ExtraDataItem name="GUI/RestrictedRuntimeMachineMenuActions" value="SaveState,PowerOff"/>
      <ExtraDataItem name="GUI/SaveMountedAtRuntime" value="yes"/>
      <ExtraDataItem name="GUI/ScaleFactor" value="1"/>
      <ExtraDataItem name="GUI/StatusBar/IndicatorOrder" value="HardDisks,OpticalDisks,FloppyDisks,Network,USB,SharedFolders,Display,VideoCapture,Features,Mouse,Keyboard"/>
    </ExtraData>
    <Hardware version="2">
      <CPU count="1" hotplug="false">
        <HardwareVirtEx enabled="true"/>
        <HardwareVirtExNestedPaging enabled="true"/>
        <HardwareVirtExVPID enabled="true"/>
        <HardwareVirtExUX enabled="true"/>
        <PAE enabled="false"/>
        <LongMode enabled="true"/>
        <HardwareVirtExLargePages enabled="false"/>
        <HardwareVirtForce enabled="false"/>
      </CPU>
      <Memory RAMSize="512" PageFusion="false"/>
      <HID Pointing="USBTablet" Keyboard="PS2Keyboard"/>
      <HPET enabled="false"/>
      <Chipset type="PIIX3"/>
      <Boot>
        . . .
      </Boot>
      <Display VRAMSize="128" monitorCount="2" accelerate3D="true" accelerate2DVideo="false"/>
      <VideoCapture enabled="false" screens="18446744073709551613" horzRes="1024" vertRes="768" rate="512" fps="25" maxTime="0" maxSize="0"/>
      <RemoteDisplay enabled="false" authType="Null" authTimeout="5000">
        <VRDEProperties>
          <Property name="TCP/Ports" value="3389"/>
        </VRDEProperties>
      </RemoteDisplay>
      <BIOS>
        <ACPI enabled="true"/>
        <IOAPIC enabled="true"/>
        <Logo fadeIn="true" fadeOut="true" displayTime="0"/>
        <BootMenu mode="MessageAndMenu"/>
        <TimeOffset value="0"/>
        <PXEDebug enabled="false"/>
      </BIOS>
      <USB>
        . . .
      </USB>
      <Network>
        . . .
      </Network>
      <UART/>
      <LPT>
        <Port slot="1" enabled="false" IOBase="0x378" IRQ="7"/>
      </LPT>
      <AudioAdapter controller="HDA" driver="ALSA" enabled="true"/>
      <RTC localOrUTC="local"/>
      <SharedFolders>
        <SharedFolder name="D" hostPath="/z/D" writable="true" autoMount="true"/>
        <SharedFolder name="F" hostPath="/z/F" writable="true" autoMount="true"/>
      </SharedFolders>
      <Clipboard mode="Bidirectional"/>
      <DragAndDrop mode="Bidirectional"/>
      <IO>
        <IoCache enabled="true" size="5"/>
        <BandwidthGroups/>
      </IO>
      <HostPci>
        <Devices/>
      </HostPci>
      <EmulatedUSB>
        <CardReader enabled="false"/>
      </EmulatedUSB>
      <Guest memoryBalloonSize="0"/>
      <GuestProperties>
        . . .
      </GuestProperties>
    </Hardware>
    <StorageControllers>
      <StorageController name="IDE" type="PIIX4" PortCount="2" useHostIOCache="true" Bootable="true">
        <AttachedDevice passthrough="true" type="DVD" port="0" device="0">
          <Image uuid="{11962368-06c0-4e9d-9f35-bf4448741447}"/>
        </AttachedDevice>
        <AttachedDevice passthrough="true" type="DVD" port="0" device="1">
          <HostDrive src="/dev/sr0"/>
        </AttachedDevice>
      </StorageController>
      <StorageController name="SATA" type="AHCI" PortCount="2" useHostIOCache="false" Bootable="true" IDE0MasterEmulationPort="0" IDE0SlaveEmulationPort="1" IDE1MasterEmulationPort="2" IDE1SlaveEmulationPort="3">
        <AttachedDevice nonrotational="true" type="HardDisk" port="0" device="0">
          <Image uuid="{3790b482-03fa-42e9-bf2a-f01852a19721}"/>
        </AttachedDevice>
      </StorageController>
    </StorageControllers>
  </Machine>
</VirtualBox>

But the file also identifies the Windows XP clone that shows up the as the VERR_FILE_NOT_FOUND error that triggered this inquiry (see HardDisk uuid="{45fb,etc., the entry immediately above the guest additions iso).

I suspect it is simply a matter of deleting the image, but from where?

16

And one further thought. In an ideal world, all of the reported errors would be resolved and then not appear in the logs. Nevertheless, since I have now installed the guest additions in Windows 7 (and assuming that the installation was executed fully and properly), perhaps the error concerning the guest additions iso location doesn’t matter for now.

That would leave just the original VERR_FILE_NOT_FOUND error as the remaining item to fix.

17

They are install but the system still can’t find the additions iso because it is not where it expects it.

18

The guest additions are now installed because I installed them manually. Having done so, I am guessing that the system will not need to access the .iso again, unless I were to modify the system in such a manner that required a reloading of the guest additions. Someone please correct me if I am wrong on this.

I have not been able to find a designated location for the guest addition .iso, other than the one I mentioned in the .vbox file. What is the default location for the guest additions .iso? Or, what determines the default location for the .iso?

Now, more progress. I commented out the reference to the Windows XP guest in the .vbox xml file and now the original VERR_FILE_NOT_FOUND error does not occur when I open the VirtualBox manager. And the VBoxSVC.log generated thereafter lost the screenshot errors in the previous log.

VirtualBox XPCOM Server 5.0.22_SUSE r108108 linux.amd64 (openSUSE Buildservice) release log
00:00:00.001192 main     Log opened 2016-07-03T10:32:38.381108000Z
00:00:00.001194 main     Build Type: release
00:00:00.001199 main     OS Product: Linux
00:00:00.001200 main     OS Release: 4.1.26-21-default
00:00:00.001200 main     OS Version: #1 SMP PREEMPT Mon Jun 13 13:32:30 UTC 2016 (294632f)
00:00:00.001229 main     DMI Product Name: System Product Name
00:00:00.001234 main     DMI Product Version: System Version
00:00:00.001377 main     Host RAM: 5957MB total, 4270MB available
00:00:00.001380 main     Executable: /usr/lib/virtualbox/VBoxSVC
00:00:00.001381 main     Process ID: 4622
00:00:00.001381 main     Package type: LINUX_64BITS_GENERIC (OSE)
00:00:00.105370 nspr-2   Home directory: '/root/.config/VirtualBox'
00:00:00.105577 nspr-2   Loading settings file "/root/.config/VirtualBox/VirtualBox.xml" with version "1.12-linux"
00:00:00.106438 nspr-2   Successfully initialised host USB using sysfs
00:00:00.112569 nspr-2   NAT: resolv.conf: nameserver 192.168.1.1
00:00:00.112619 nspr-2   HostDnsMonitor: old information
00:00:00.112624 nspr-2     no server entries
00:00:00.112629 nspr-2     no domain set
00:00:00.112632 nspr-2     no search string entries
00:00:00.112634 nspr-2   HostDnsMonitor: new information
00:00:00.112637 nspr-2     server 1: 192.168.1.1
00:00:00.112640 nspr-2     domain: home
00:00:00.112643 nspr-2     search string 1: home
00:00:00.112650 nspr-2   HostDnsMonitorProxy::notify
00:00:00.116426 nspr-2   VD: VDInit finished
00:00:00.116519 nspr-2   ERROR [COM]: aRC=NS_ERROR_FAILURE (0x80004005) aIID={0eb668d2-495e-5a36-8890-29999b5f030c} aComponent={SystemPropertiesWrap} aText={Cannot determine default Guest Additions ISO location. Most likely they are not available}, preserve=false aResultDetail=0
00:00:00.123163 nspr-2   Loading settings file "/root/VirtualBox VMs/m5-vm2/m5-vm2.vbox" with version "1.14-linux"

All that remains is the guest additions .iso location error.

19

If DKMS is installed in your Guest, then your VBox Guest Additions kernel modules should be updated automatically when you update your kernel, otherwise the Guest Additions will need to be re-compiled and re-installed. You can do a simple search like the following to determine if DKMS is installed

zypper se dkms

The Guest Additions iso most likely is in the root of your VBox app file tree. You can run find or install and run locate (mlocate package) to find any file you wish on your system.

TSU

20

tsu2 -

Thanks. I have never installed dkms, as it is not part of the default installation. Should I install dkms? I’m not aware of any other package I now use that would benefit from dkms and, as explained below, updating Guest Additions is fairly simple.

Regarding the .iso, in my experience so far, that always ends up in Windows Explorer as a drive. I just right-click on the VBoxWindowsAdditions.exe, and it updates. The correct version of Guest Additions then shows up in Virtual Box Manager under storage.