Opened 15 years ago
Last modified 11 years ago
#4705 closed defect
seeing opensolaris 118 guest panic — at Initial Version
| Reported by: | Will Fiveash | Owned by: | |
|---|---|---|---|
| Component: | VMM | Version: | VirtualBox 3.0.4 |
| Keywords: | Cc: | ||
| Guest type: | Solaris | Host type: | Mac OS X |
Description
I just saw my OpenSolaris snv_118 guest session panic when running in a VB 3.0.4 guest. Here is the stack of the panic dump:
print ::stack | mdb unix.4 vmcore.4 _Z24vbglPhysHeapExcludeBlockP18_VBGLPHYSHEAPBLOCK+0x26() VbglPhysHeapFree+0x8b() VbglHGCMCall+0x2a2() _Z29VBoxGuestCommonIOCtl_HGCMCallP15VBOXGUESTDEVEXTP16VBOXGUESTSESSIONP22_VBoxGu estHGCMCallInfojbbmmPm+0x176() VBoxGuestCommonIOCtl+0x3cb() VBoxGuestSolarisIOCtl+0x2ac() cdev_ioctl+0x45(10900000000, c0105692, fffffd7fff0fccf0, 202003, ffffff00d38126d8, ffffff0002551e24) spec_ioctl+0x83(ffffff00d350fb00, c0105692, fffffd7fff0fccf0, 202003, ffffff00d38126d8, ffffff0002551e24) fop_ioctl+0x7b(ffffff00d350fb00, c0105692, fffffd7fff0fccf0, 202003, ffffff00d38126d8, ffffff0002551e24) ioctl+0x18e(3, c0105692, fffffd7fff0fccf0) sys_syscall+0x17a()
This occurred when the VM was configured with two virtual CPUs. The hosting OS is OS X 10.5.8 running on a MacBook Pro with 4GB RAM. I have the unix and vmcore images to upload/attach somewhere if someone needs them, just let me know.
