Custom Query (16363 matches)
Results (1249 - 1251 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16640 | invalid | Guru medication during start Mac OSX Lion | ||
| Description |
Guru medication during start Mac OSX Lion |
|||
| #4313 | worksforme | Host Memory Low error | ||
| Description |
I recently upgraded to VB 2.2.4 and since then I cannot use any(!) VM anymore. I am using a 6 GB Quadcore System, which normally has 2 GB of RAM available. Even a VM set to 1 GB RAM does sometimes not even start. Right now, the VMs do start to a Windows login, but then freeze: 00:00:34.704 Console: VM runtime error: fatal=false, errorID=HostMemoryLow message="Unable to allocate and lock memory. The virtual machine will be paused. Please close applications to free up memory or close the VM" When I cannot start the system directly throws a memory related error as well: 00:00:00.620 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={9511bc54-15ee-4ddf-808e-472aba03809c} aComponent={Console} aText={Unknown error creating VM (VERR_NO_MEMORY)} aWarning=false, preserve=false 00:00:00.627 Power up failed (vrc=VERR_NO_MEMORY, rc=E_FAIL (0X80004005)) I am quite sure, that I do have enough memory available. I even stopped the SQL Server (normally running at around 3 GB allocated RAM) to verify this. The task manager normally does not report more then 4 or 4.5 GB of used physical memory. Any hints would be appreciated. If you need any more information, please let me know. |
|||
| #19160 | fixed | VirtualBox 6.1 cannot use old VMs with disc encryption => fixed in 6.1.2 | ||
| Description |
I have used disc encryption with my VMs (Windows host, Linux guests), latest ones created with 6.0.14, and some older. When I upgraded to VirtualBox 6.1 (including extension pack), booted the host machine(just to be safe), and tried to run the old VMs they did not anymore ask for disc encryption password, but instead the VM just tried to boot and failed with "No bootable medium found". Luckily uninstalling 6.1 and installing 6.0.14 (and it's extension pack) worked, and I can again run my VMs. |
|||

