Old unused vdi file on another drive generates VERR_FILE_NOT_FOUND error

[w2tq]

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:

Code: Select all

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:

Code: Select all

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

This 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.

[Perryg]

Since the files you show above are not from the official version of VirtualBox can we assume you have the OpenSUSE version of VirtualBox ( fork ) ? If so you would need to ask them what needs to be done.

[w2tq]

Perryg -

Thanks for the reply.

Do you suspect that it's a glitch in the SuSE repo files and not something more general (perhaps something I did inadvertently)?

I did search the SuSE forum for virtualization and did not uncover anything, but I will post there as well.

Thanks.

[Perryg]

Don't know my friend, just that we have no idea how to help with their build since we don't use it.

[w2tq]

Thanks. Have you or any of your colleagues ever encountered anything of this sort before? It's very puzzling as the systems have always functioned quite well.

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.

[Perryg]

If I had to guess what might be the problem I would say it had to do with the upgrade to leap. That version is close to bleeding edge and does come with its own head scratchers.

[w2tq]

No, I don't believe that Leap is at fault here. The VM worked fine under 5.0.18. This occurred well after the install - and it was a new, clean install. Timing-wise, it appears to have occurred after the update to 5.0.22.

Is there a log of errors associated with the Virtual Media Manager? I have looked at every config and log file on the system, and there is no mention of this. A search of the forums and the web did not yield anything.

[mpack]

We do not support forks, so please ask your questions on the OpenSUSE site as Perry already said. Locking this.