Opened 8 years ago
Last modified 8 years ago
#15761 new defect
Upgrade to 5.1.2 destroyed all VM
| Reported by: | TH3rb5t | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.2 |
| Keywords: | Cc: | ||
| Guest type: | all | Host type: | Mac OS X |
Description
After upgrading from version 5.0.24, 5.0.26 and 5.1.0 directly to 5.1.2 destroyed all my virtual machines on three independent Macintosh systems after the first start up, using version 5.1.2 of VirtualBox.
As I was able to see, what's going on, an error with the chipset was displayed with an error message, that the virtual machine was damaged or Could behave like having technical trouble, while there is an issue within the audio codec/ chipset/ driver.
Microsoft Windows VM (7 Ultimate and 10 Pro, both 64-bit) crashed at first and displayed the sad smily. Then the Ubuntu Server, Linux Mint and a FreeNAS crashed after additional reboot. One Windows VM restarted again and again - while the guest addition image was mounted. After ejecting it, a blue screen appeared at the next boot loop.
I've tried to downgrade the version or use the virtual machines on another computer, where no update has been done, but the machines was destroyed, we weren't able to recover it. For sure we've used snapshots before upgrading, but a roll back to the last working snapshot was not successful.
Fortunately, we keep all important data outside the virtual machines, so we only lost the virtual systems, but that was very annoying.
And it doesn't matter, what you change in the virtual machines configuration, the same error messages appears, only with your changed configuration of chipset and audio codec.
We've tried to identify some logs, but what we found is not useful.
May be you can take a look of your structure and another one knows this issue too and can give further informations, why and when his happens exactly.
We've also tried a fresh install of MacOS X (10.10.5 and 10.11.6) with a newly downloaded 5.1.2 of VirtualBox and by creating a new VM, the issue persists even out of the box.
The last working versions of VirtualBox are 5.0.26 and 5.1.0 - so the issue must be directly located in the code of version 5.1.2
May be, you can find the bug and fix it, because we wanna upgrade securely to the next version.
Change History (3)
follow-up: 2 comment:1 by , 8 years ago
comment:2 by , 8 years ago
Replying to socratis:
Replying to TH3rb5t:
As I was able to see, what's going on, an error with the chipset was displayed with an error message, that the virtual machine was damaged or Could behave like having technical trouble, while there is an issue within the audio codec/ chipset/ driver.
Well, you're not very accurate on your descriptions, you do not provide any logs, and unless you become more exact, there is not that much of a chance that the devs can reproduce and/or fix your problem.
However, your vague description (audio, chipset), coupled with your host (Mac), makes me think that you might have a problem similar to #15659. Take a look at it and see if they are the same.
Yes, exactly... but with the additional Informationen, dass it doesn't matter which audio you're using in the preferences of the virtual machine. But I'm not a programmer, so I can't give you further informations, as I was able to investigate.
Replying to TH3rb5t:
Well, you're not very accurate on your descriptions, you do not provide any logs, and unless you become more exact, there is not that much of a chance that the devs can reproduce and/or fix your problem.
However, your vague description (audio, chipset), coupled with your host (Mac), makes me think that you might have a problem similar to #15659. Take a look at it and see if they are the same.