VirtualBox

Opened 4 years ago

Last modified 4 years ago

#19761 awaitsfeedback defect

VirtualBox guest OpenWrt OS crashed when using the nmap to scan the wireless network through the USB port

Reported by: MercyLin Owned by:
Component: other Version: VirtualBox 6.1.10
Keywords: Cc:
Guest type: Linux Host type: Windows

Description

Guest OpenWrt OS crashed with the following configuration and operation Host is the Lenovo ThinkCentre M920t desktop PC, WIN 10 professional OS. The VirtualBox v6.1.12 with extension pack 6.1.12 is installed. The Guest OS is Linux 64bit(OpenWrt Lede 17.01). Using the MediaTek USB wifi dongle MT7601U to act as a AP(AccessPoint). It works well, I can connct it by my mobile phone and surf the Internet without problem, but it will be crashed once I use the nmap(v7.31) to scan the wifi network. I have the exactly same configuration with my HP laptop and the sympton won't happen in it, don't why it's crashed with my Lenovo desktop PC.

Attachments (3)

VBox.log (511.4 KB ) - added by MercyLin 4 years ago.
log
VBoxHardening.log (505.8 KB ) - added by MercyLin 4 years ago.
more log
VBox.png (15.4 KB ) - added by MercyLin 4 years ago.
png

Download all attachments as: .zip

Change History (7)

by MercyLin, 4 years ago

Attachment: VBox.log added

log

by MercyLin, 4 years ago

Attachment: VBoxHardening.log added

more log

by MercyLin, 4 years ago

Attachment: VBox.png added

png

comment:1 by Frank Batschulat (Oracle), 4 years ago

the log file shows:

00:14:31.850838 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'
00:14:31.850871 Console: Machine state changed to 'GuruMeditation'
00:14:31.851019 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:14:31.851019 !!
00:14:31.851020 !!         VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)
00:14:31.851044 !!
00:14:31.851049 !! Skipping ring-0 registers and stack, rcErr=VINF_EM_TRIPLE_FAULT
00:14:31.851054 !!
00:14:31.851054 !! {mappings, <NULL>}
00:14:31.851055 !!
00:14:31.851064 !!
00:14:31.851065 !! {hma, <NULL>}
00:14:31.851065 !!
00:14:31.851066 Hypervisor Memory Area (HMA) Layout: Base 00000000a0000000, 0x02800000 bytes
00:14:31.851070 00000000a0662000-00000000a0673000 000000000d2b0000 ffffdb04e44ef000 LOCKED                   alloc once (PGM_PHYS)
00:14:31.851076 00000000a0654000-00000000a0662000 000000000a640000 ffffdb04e4409000 LOCKED                   alloc once (VMM)
00:14:31.851080 00000000a0253000-00000000a0654000 000000000afc0000 ffffd7f945200000 LOCKED                   alloc once (PGM_PHYS)
00:14:31.851084 00000000a0224000-00000000a0253000 000000000a610000 ffffdb04e445f000 LOCKED                   alloc once (PGM_POOL)
00:14:31.851088 00000000a0223000-00000000a0224000 000000000a600000 ffffdb04e4408000 LOCKED                   alloc once (CPUM_CTX)
00:14:31.851091 00000000a0023000-00000000a0223000 000000000abc0000 ffffd7f944e00000 LOCKED                   Heap
00:14:31.851094 00000000a000e000-00000000a0023000 000000000a5c0000 ffffdb04e4449000 LOCKED                   VMCPU
00:14:31.851098 00000000a0000000-00000000a000e000 000000000a5b0000 ffffdb04e4439000 LOCKED                   VM
00:14:31.851101 !!

comment:2 by MercyLin, 4 years ago

Hi, What does it mean ? May I have more comment from you ?

comment:3 by MercyLin, 4 years ago

Change the different nmap arguments can solve the issue, case closed

comment:4 by MercyLin, 4 years ago

Status: newawaitsfeedback
Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use