Ticket #1503 (closed defect: fixed)
No VM can be started after upgrade from 1.5.6 to 1.6.0 (Windows XP 32bit host)/AMD-V -> fixed in SVN/1.6.2
|Reported by:||philip.torchinsky||Owned by:|
I was running VirtualBox 1.5.6 on Windows and had three guests: OpenSolaris 2008.05, SXDE 1/08, Ubuntu 7. I could not simply upgrade to 1.6.0 because after running VirtualBox-1.6.0-Win_x86 I received a error message "You have to uninstall VirtualBox 1.5.6 first". I did; then Installed VirtualBox 1.6.0, then run it. It seemed to import all guest VMs, asking what to do with them (Cancel, Save, Backup). I choose Backup and found, that no VM can be started, in spite of all of them seem to be imported correctly.
"Cannot be started" means that after a start a VM does not boot, keeping blank VM window for infinite time. The only way to switch it off - power off the VM. VirtualBox itself looks fine and responds quickly.
- Summary changed from No VM can be started after upgrade from 1.5.6 to 1.6.0 (Windows XP 32bit host) to No VM can be started after upgrade from 1.5.6 to 1.6.0 (Windows XP 32bit host)/AMD-V -> fixed in SVN/1.6.2