Opened 11 years ago
Last modified 8 years ago
#12375 closed defect
Host crashed after a processor offline — at Version 2
Reported by: | mzprx | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 4.3.2 |
Keywords: | Cc: | ||
Guest type: | other | Host type: | Solaris |
Description (last modified by )
I'm running VirtualBox 4.3.2 on this host:
- OS: OpenIndiana 151a8
- CPU: Intel Xeon E3-1240 V2
I had one virtual machine guest running.
Once I ran psradm -f 1
on the host to offline one CPU the machine panicked with this info:
> ::status debugging crash dump vmcore.0 (64-bit) from raven operating system: 5.11 oi_151a8 (i86pc) image uuid: bce29343-bd66-4abc-9670-96f69cb1d15c panic message: BAD TRAP: type=6 (#ud Invalid opcode) rp=ffffff001f36aab0 addr=1 dump content: kernel pages only > ::stack 0xfffffffff822afa4() 0xfffffffff822aae6() 0xfffffffff823d6bb() supdrvIOCtlFast+0x8c() VBoxDrvSolarisIOCtl+0x109() cdev_ioctl+0x45(10e00000002, 200056c1, 1, 202003, ffffff04e462a468, ffffff001f36ae24) spec_ioctl+0x5a(ffffff04e65e5700, 200056c1, 1, 202003, ffffff04e462a468, ffffff001f36ae24) fop_ioctl+0x7b(ffffff04e65e5700, 200056c1, 1, 202003, ffffff04e462a468, ffffff001f36ae24) ioctl+0x18e(12, 200056c1, 1) sys_syscall+0x17a() > ::cpuinfo ID ADDR FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD PROC 0 fffffffffbc30640 1f 0 0 -1 no no t-0 ffffff001e005c40 (idle) 1 ffffff04d865e080 2f 0 0 -1 no no t-10 ffffff001e364c40 (idle) 2 ffffff04d8642a80 1f 0 0 59 no no t-0 ffffff04db148ae0 VBoxHeadless 3 ffffff04d8ac8540 1f 0 0 -1 no no t-0 ffffff001e4a2c40 (idle) 4 ffffff04d8ac7040 1f 0 0 -1 no no t-0 ffffff001e852c40 (idle) 5 ffffff04d8ac5080 1f 0 0 -1 no no t-4 ffffff001e454c40 (idle) 6 fffffffffbc3ae50 1b 0 0 59 no no t-0 ffffff04da579bc0 VBoxHeadless 7 ffffff04d8aba540 1f 1 0 -1 no no t-9 ffffff001e97bc40 (idle) >
I'll provide the crash dump file on request.
Change History (2)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Description: | modified (diff) |
---|
Note:
See TracTickets
for help on using tickets.
Could you please attach VBox.log for the VM when the crash happened.