Custom Query (16363 matches)
Results (1720 - 1722 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #9429 | obsolete | Cannot Resume Fedora 15 Client guest on Mac Lion Virtual Box 4.1 | ||
| Description |
Attempting to resume a saved Fedora 15 vm causes a crash ( but the VM app remains open) with an abort listed as the vm state. I have 1GB of memory allocated, 128MB of video allocated and use Bridged networking. 3d support turned on. And I am using the Gnome 3 shell. I can 'Start from Scratch" i.e. a VM restart. Although I occassionally start up with the gnome 'fallback' shell. |
|||
| #14661 | fixed | Cannot Start VM After Moving From 4.3.30 to 5.0.4 | ||
| Description |
Host: Windows 8.1 Pro x64 on a Surface Pro 3 512GB Gurest: Windows 8 x64 I have a number of VMs that I use as base machines. That is when I have to test something in a specific environment I clone the machine. To avoid having a huge delay in using one when I need it I periodically start each one and apply Windows Updates. I recently upgraded my VirtualBox from 4.3.30 to 5.0.4. I was able to update most of my test VMs including a Windows 8 x64 machine. However, when I tried to start another Windows 8 x64 VM I got: Failed to open a session for the virtual machine <VM Name>. Configuration error: TM setting "MaybeUseOffsettedHostTSC" is no longer supported. Use the "Mode" setting instead. (VERR_CFGM_CONFIG_UNKNOWN_VALUE). Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} The above is not very informative. I don't know why the setting was needed and I have no idea how to replace it. I cannot find any reference to it in the documentation. |
|||
| #6518 | fixed | Cannot Start VM Because VirtualBox Thinks It is Read-Only | ||
| Description |
VirtualBox cannot start a VM because it thinks the vdi file is read only. Retrying startup eventually works. The problem is not consistent. One day it is one VM and the next day it happens with a different one. Please note that although VirtualBox is at 3.1.2 the guest additions are at 1.4 although the problem did not start immediately after the guest additions were updated. There are two log files attached -- one for the last failure today and one for the successfull startup. |
|||

