Opened 8 years ago
Closed 8 years ago
#16824 closed defect (invalid)
Error starting Windows 10 64 guest os (VERR_VMX_UNEXPECTED_INTERRUPTION_EXIT_TYPE)
| Reported by: | Cyb3rgh057 | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 5.1.22 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Linux |
Description
Its giving me guru error. I tried every thing and using latest versionof v box for ubuntu zetsy.
Attachments (2)
Change History (5)
by , 8 years ago
| Attachment: | VBox.log.1 added |
|---|
by , 8 years ago
comment:1 by , 8 years ago
00:00:00.906238 Host RAM: 7981MB (7.7GB) total, 1733MB available 00:00:01.126143 RamSize <integer> = 0x00000000fb800000 (4 219 469 824, 4 024 MB, 3 GB) 00:00:01.126582 VRamSize <integer> = 0x0000000008000000 ( 134 217 728, 128 MB)
4024+128 >> 1736.
You are assigning memory to your guest, that you do not have available. Either close some applications on the host, buy more RAM for the host, or reduce the amount of RAM assigned to the guest.
May I also suggest something? It's usually better and faster, if issues like this one (configuration, question) get first addressed in the VirtualBox forums. More than 95% of the issues are resolved over there, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of.
comment:2 by , 8 years ago
The VM crashes quite soon during boot. You didn't mention which guest you are using. The OS type is set to Windows 10 / 64-bit but are you really running Windows 10?
comment:3 by , 8 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
Actually you are running VirtualBox as guest in another VMM. Please reopen if you can reproduce the problem on bare metal.
Fresh Attachment