5.1.12 destroys images

[Craig P.]

Host: Windows 10 Guest: Ubuntu 16.04

Extensions Pack.

Existing Ubuntu image originally created with 5.1.8 and updated to 5.1.10, as run from Windows 10 host.

Procedure:

• create a snapshot
• exit virtual box
• relaunch virtual box
• All snapshots no longer exist
• Cannot boot guest (ubuntu 16.04)
• No disk image found is the error message.

Luckily, I had an original clone from 5.1.10.

I downgraded Virtual Box (and extensions pack) to 5.1.10 and everything is just fine.

Thus, I am avoiding Virtual Box 5.1.12.

Note to self / note to all - if you are contemplating upgrading virtual box, then make clones of all your images first. That way, such as in this case, where 5.1.12 destroyed my images, there is a backup / original starting point, for situations where the only resolution is to downgrade Virtual box.

[Socratis]

Data loss can be one of the worst bugs, duplication and verification are required. Can you repeat the experiment? But this time you need to gather some evidence, because the description alone isn't enough I'm afraid.

• Quit VirtualBox and wait for 1 minute.
• Run: "C:\Program Files\Oracle\VirtualBox\VBoxBugReport" "<VM_Name>". That's report #1.
• Re-create the problem:
  • Create a snapshot.
  • Quit VirtualBox and wait for 1 minute.
  • Run: "C:\Program Files\Oracle\VirtualBox\VBoxBugReport" "<VM_Name>". That's report #2.
  • Relaunch VirtualBox. Anything missing?
  • Quit VirtualBox and wait for 1 minute.
  • Run: "C:\Program Files\Oracle\VirtualBox\VBoxBugReport" "<VM_Name>". That's report #3.

Now, gather all three generated reports and attach them here. If you get a write-error, make sure that you issue the "VBoxBugReport" commands from a directory that you have write access to.

[Frank Mehnert]

I'm not able to reproduce this problem with the steps provided in the original description.

[Craig P.]

Replying to frank:

I'm not able to reproduce this problem with the steps provided in the original description.

I can not afford the luxury of attempting to following the debugging / diagnosis steps outlined above. Sorry. If I'm the only person experiencing this problem (doubtful), then this ticket is a non-priority.

As far as attempting to reproduce the problem, I guess I should point out that there are multiple builds of Microsoft Windows 10 (as I'm sure you all are aware, but not necessarily addressing). I am not on the absolute latest Windows 10 build, which in and of itself is a very long story and yet another testament to how Microsoft Windows 10, and Microsoft in general, is still not ready for prime time nor probably ever will be, since reliability and stability are not a priority as compared to their steady income profit agenda, but I digress.

I highly suspect that my problem with virtual box on 5.1.12 is related to changes in virtual box that were tested on the latest Windows 10 build versus virtual box 5.1.10, which came from 5.1.8, and historical versions thereof which were developed on and compatible with older builds of Windows 10.

To make a long story short, using 'winver', I am running Windows 10 version 1511 build 10586.713

[Craig P.]

While I'm here, I wish I could figure out how to upgrade my Windows 10 build, but I probably can not afford the luxury to do that either (since it did not work on my brand new HP laptop). In the end, I will probably figure out how to install ubuntu in dual-boot with windows-10, which I'm sure will be painful.

[Socratis]

Replying to Craig P.:

I can not afford the luxury of attempting to following the debugging / diagnosis steps outlined above. Sorry. If I'm the only person experiencing this problem (doubtful), then this ticket is a non-priority.

I wouldn't call it a non-priority, I would call it "works for me" and close it. Done. VirtualBox is a community driven program. Since you're part of the community (since you're using it and filling bugs against it), I believe that you should do your part, especially if no one else but you can reproduce it, if you want to find a solution to your problem.

My "gut" feeling? Your .vbox file is on a folder that you do not have write access to, therefore you cannot modify it.

Another one? You're working with immutable images. The possibilities for your setup are endless, and unless a developer can reproduce/duplicate what you're seeing, they won't be able to find the root cause (if any) and potentially fix it.

If it's a luxury for you to debug your own problem, imagine the developers with more than 2000 bugs open...

[Craig P.]

Hello,

Just to let you know that VBOX 5.1.14 is good.

What ever got broke in 5.1.12 got fixed in 5.1.14.

I went through the usual motions as in my DR description.

I'll give this another day or so of use and then close the ticket (well, I guess, it's up to me to close the ticket?).

Regards.

[Craig P.]

I do not see a mechanism for me to close this ticket.

[Frank Mehnert]

Thank you for the information. I still cannot imagine which change in 5.1.12 should have caused any harm to your VM image and how it was fixed in 5.1.14.