Opened 6 years ago
Closed 5 years ago
#18101 closed defect (fixed)
Guest machine has expected. Avorted
Reported by: | Sizy458 | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 5.2.18 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | other |
Description
My guest machine has expected. Passing status executing to Aborded
Attachments (6)
Change History (12)
by , 6 years ago
comment:1 by , 6 years ago
comment:2 by , 6 years ago
It's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. 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.
So, if you can, please open a new thread in the VirtualBox on Linux Hosts, or in the Windows Guests section of the forums. Please be sure to mention that you came from the bug tracker and include the ticket number.
Just a quick comment here:
00:00:02.436535 Changing the VM state from 'CREATED' to 'LOADING'
That looks like you're trying to start the VM from a "Saved State", which you didn't mention in your report. That could be an issue, if for example you changed your host's VirtualBox version.
BTW, here's the way to get a complete VBox.log, from a complete VM run:
- Start the VM from cold-boot (not from a paused or saved state) / Observe error / Shutdown the VM (force close it if you have to).
- With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
- Save only the first "VBox.log", and attach it to your response.
by , 6 years ago
Attachment: | VBox.log.1 added |
---|
by , 6 years ago
Attachment: | Mon work multi-boot(x64).vbox added |
---|
comment:4 by , 6 years ago
Suspect log :
....
00:04:17.816495 RTC: period=0x20 (32) 1024 Hz
00:04:38.049874 RTC: period=0x200 (512) 64 Hz
00:04:49.816133 RTC: period=0x20 (32) 1024 Hz
00:04:49.846784 RTC: period=0x200 (512) 64 Hz
00:04:50.628988 RTC: period=0x20 (32) 1024 Hz
00:04:55.065408 RTC: period=0x200 (512) 64 Hz
00:04:59.722907 RTC: period=0x20 (32) 1024 Hz
00:04:59.753125 RTC: period=0x200 (512) 64 Hz
00:05:00.409983 RTC: period=0x20 (32) 1024 Hz
00:05:02.097056 RTC: period=0x200 (512) 64 Hz
00:05:33.613101 RTC: period=0x20 (32) 1024 Hz
00:05:52.893341 RTC: period=0x200 (512) 64 Hz
00:06:25.691495 RTC: period=0x20 (32) 1024 Hz
00:06:25.830823 RTC: period=0x200 (512) 64 Hz
00:06:26.207463 RTC: period=0x20 (32) 1024 Hz
00:06:26.346590 RTC: period=0x200 (512) 64 Hz
00:07:47.457131 RTC: period=0x20 (32) 1024 Hz
00:07:47.612144 RTC: period=0x200 (512) 64 Hz
00:07:47.707278 RTC: period=0x20 (32) 1024 Hz
00:07:47.862480 RTC: period=0x200 (512) 64 Hz
00:07:50.566156 RTC: period=0x20 (32) 1024 Hz
00:07:50.721794 RTC: period=0x200 (512) 64 Hz
00:07:51.706986 RTC: period=0x20 (32) 1024 Hz
00:07:51.846726 RTC: period=0x200 (512) 64 Hz
.....
For VirtualBox version 5.2.12.
by , 6 years ago
Attachment: | Mon work multi-boot(x64)-2018-11-17-11-21-26.log added |
---|
For VirtualBox Version 5.2.12
comment:6 by , 5 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I don't know if this log can solved this bug. The log seems incomplete and there is no information on the exception trap.