VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (874 - 876 of 16363)

Ticket Resolution Summary Owner Reporter
#1503 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 Philip
Description

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.

#1504 fixed Virtualbox 1.6 appears to be corrupting VMDK files nzchris73
Description

After upgrading to Virtualbox 1.6 I got the following error in Event Viewer when trying to mount the VMDK file used as a secondary HDD for one of my machines. I created a new VMDK file and tried it again but got the same result. After reverting back to 1.5.6 VMDK files worked ok. Windows XP SP3 host running Windows XP client.

Command ""C:\Program Files\VMware\VMware DiskMount Utility\vmware-mount.exe" V: "E:\Virtual Machines\UBCD4WIN\Windows XP Professional.vmdk" /y" failed with COM error: 0x80004005 (last partition extends past end of disk (2609:1023))

#1505 fixed Guru Meditation running memtest86+ V1.7 (Trap 0x0d) Adrian
Description

when I start memtest from the kubuntu hardy installtion, I get the Guru Mediation. Log is attached

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy