Custom Query (16363 matches)
Results (694 - 696 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #19762 | invalid | VM's not loading after upgrade Virtual Box Version 6.1.12 r139181 (Qt5.6.2) | ||
| Description |
I recently upgraded to the Version 6.1.12 r139181 (Qt5.6.2) software on Windows 10 Home and now existing VM's will not load, I have an existing Debian VM that worked prior to the upgrade and a Windows XP Pro that worked. Exiting VM error message Not in a hypervisor partition (HVP=0) (VERR_NEM_NOT_AVAILABLE). AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED). Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} I can not even create a new VM, I get the same error. Everything worked fine prior to the VB upgrade. SO I do not see how this could be a issue with the Host Windows 10 Home. |
|||
| #10679 | invalid | Host-only VNIC dose not work for OpenIndiana b151a4 | ||
| Description |
When updating to the latest version of OpenIndiana (now its b151a4), traffic from both sides is missing when using host-only vnic. Its previous versions are okay. For other solaris/illumos-based distributions, I have no ideas. |
|||
| #10692 | fixed | vm cannot be started with type headless | ||
| Description |
It says: VBoxManage: error: No error info VBoxManage: error: Details: code NS_ERROR_CALL_FAILED (0x800706be), component ProgressProxy, interface IProgress, callee |
|||

