Custom Query (16363 matches)
Results (598 - 600 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #19767 | duplicate | OK button does'nt work | ||
| Description |
Hi, I have a problem. I open Settings in my VM and I change a setting and i cannot click the OK button.
Regards, Jakub[[Image(file:///home/jakub/Obrazy/Screenshot%20from%202020-07-25%2020-16-21.png
)]] [[Image(file:///home/jakub/Obrazy/Screenshot%20from%202020-07-25%2020-16-32.png)
]] |
|||
| #19765 | invalid | VT-x is not available (VERR_VMX_NO_VMX) | ||
| Description |
I update from V6.0.20 to V6.1.12 : On LapTop PC: Acer4820TZG with Windows 7 Virtual machine : Windows XP With V6.0.20 r137117 : OK : No error With V6.1.12 r139181 : ERROR :
I have not this error on another PC |
|||
| #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. |
|||

