Opened 14 years ago
Closed 12 years ago
#7976 closed defect (fixed)
4.0 on linux host segfaults after resume from disk
| Reported by: | bleun | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.0.0 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Linux |
Description (last modified by )
Running VirtualBox 4.0 on Ubuntu 10.10 host results in a segfault in VBoxVMM.so if the host resumes from a suspend to disk.
Suspend/Resume to ram works flawless, 3.2.12 showed the same error, for relevant info from /var/log/messages see attachements.
Attachments (6)
Change History (18)
by , 14 years ago
by , 14 years ago
comment:1 by , 14 years ago
comment:2 by , 14 years ago
Similar error when resuming Linux guests in VirtualBox 4.0.2, though this worked fine in VirtualBox 3.1
by , 14 years ago
| Attachment: | VBox.2.log added |
|---|
comment:4 by , 14 years ago
Have installed VBox 4.0.6. KUbuntu guest seems to resume ok, but Slackware guest doesn't resume, even after updating Guest additions from 4.0.2 to 4.0.6. Virtual machine doesn't return guru meditation now, but it shows static picture of guest screen and there is no response to keyboard and mouse.
by , 14 years ago
| Attachment: | VBox.3.log added |
|---|
comment:5 by , 14 years ago
Uploaded core dump of the meditating VM to: http://www.sendspace.com/file/7f4sr0 ('kill -4' didn't work, so I used 'VBoxManage debugvm dumpguestcore' instead)
comment:7 by , 14 years ago
Hmm, actually that core file is not usable. You say that kill -4 <process id> did not work, does that mean that the process did not terminate? Are you sure that you specified the correct process ID?
comment:8 by , 14 years ago
Host distro is Slackware 13.0. I retried and managed to make a dump with kill this time - http://www.sendspace.com/file/ve1xh8
comment:9 by , 14 years ago
I get some information from your core dump but as I don't have Slackware 13 here, the backtraces are not entirely correct. Do you still have the corresponding VBox.log file available? Also, can you reproduce the hanging process when you try to resume that VM?
Btw, your problem is very different from the original problem...
comment:10 by , 14 years ago
Yes, I have the log, and it also contains some dumps since I chose Ignore in the Guru Meditation box. The VM doesn't hang on resume after pause, it only hangs after starting from saved state. Yes, problem is different, I see. Initially, I searched the bugtracker and this ticket was found, so I decided to complement it...
by , 14 years ago
| Attachment: | VBox.log.gz added |
|---|
comment:11 by , 13 years ago
If it is helpful by any means: the crash also occurs on other machine (host - Slackware 13.1). Maybe the problem is caused by the guest OS?..
comment:12 by , 12 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Please reopen if still relevant with VBox 4.1.22.
Any chance to provide a core dump? If so, mail me at frank _dot_ mehnert _at_ oracle _dot_ com (I can tell you a server for uploading the file).