Ticket #11291 (closed defect: fixed)
Kernel Panic Inside vboxsf guest kernel module => Fixed in SVN
| Reported by: | parem | Owned by: | |
|---|---|---|---|
| Priority: | major | Component: | guest additions |
| Version: | VirtualBox 4.2.4 | Keywords: | vboxsf kernel shutdown restart |
| Cc: | Guest type: | Linux | |
| Host type: | Mac OS X |
Description
I'm experiencing a kernel crash from inside the vboxsf guest kernel module when I attempt to shutdown or restart the guest os. I can make this problem not occur by not loading the vboxguest, vboxsf or vboxvideo kernel modules.
I'm running VirtualBox VM 4.2.4 r81684 on darwin.x86 (OS X 10.6.8). Results of guest uname -a are below.
uname -a Linux arch1 3.6.9-1-ARCH #1 SMP PREEMPT Tue Dec 4 09:31:43 CET 2012 i686 GNU/Linux
I've attached a screen shot of crash, cat /proc/cpuinfo, vBox.log, vboxsf.ko.
Attachments
-
pare_VBox.log
(51.3 KB) -
added by parem 2 years ago.
- Log file after a crash
-
badarch.tiff
(54.7 KB) -
added by parem 2 years ago.
- screen shot of described crash
-
vboxsf.ko.gz
(21.5 KB) -
added by parem 2 years ago.
- vboxsf kernel module
-
pare_cpuinfo.txt
(558 bytes) -
added by parem 2 years ago.
- /proc/cpuinfo
Change History
Changed 2 years ago by parem
-
attachment
pare_VBox.log
added
comment:1 Changed 2 years ago by frank
Can you reproduce the crash with
mount.vboxsf -o remount <sharename> <mountpoint>
? If so, can you attach the output of
strace -f -o foo.log -s128 mount.vboxsf -o remount <sharename> <mountpoint>
? Thank you!
comment:2 Changed 2 years ago by parem
I was not able to recreate the crash using
# mount.vboxsf -o remount <sharename> <mountpoint>
comment:3 Changed 2 years ago by frank
- Summary changed from Kernel Panic Inside vboxsf guest kernel module to Kernel Panic Inside vboxsf guest kernel module => Fixed in SVN
Thanks. I think we found the problem. This should be fixed in the next maintenance release.
comment:4 Changed 2 years ago by frank
- Status changed from new to closed
- Resolution set to fixed
Fix is part of VBox 4.2.6.
Log file after a crash