VirtualBox

Opened 5 years ago

Last modified 5 years ago

#18532 closed defect

Happen Segmentation fault on Virtualbox 6.0.4 — at Version 4

Reported by: Yomo Owned by:
Component: VMM Version: VirtualBox 6.0.4
Keywords: Segmantation fault Cc:
Guest type: Windows Host type: Linux

Description (last modified by janitor)

Using the Bandicut application on Windows10 guest,suddenly segmentaiont fault is happen and Window10 guest is crashed.At this time always below logs are recorded to syslog on Debian host.

Mar 31 15:12:46 svyomo2 kernel: [499770.281800] EMT-5[31291]: segfault at 7fc2c71f9fa0 ip 00007fc3074e9ab4 sp 00007fc2c72f88d8 error 4 in libc-2.28.so[7fc3073af000+148000]
Mar 31 15:12:46 svyomo2 kernel: [499770.281808] Code: 0e 88 0f c3 c5 fa 6f 06 c5 fa 6f 4c 16 f0 c5 fa 7f 07 c5 fa 7f 4c 17 f0 c3 48 8b 4c 16 f8 48 8b 36 48 89 4c 17 f8 48
 89 37 c3 <8b> 4c 16 fc 8b 36 89 4c 17 fc 89 37 c3 0f b7 4c 16 fe 0f b7 36 66
Mar 31 15:12:46 svyomo2 kernel: [499770.709211] device enxcce1d50dc8db left promiscuous mode
Mar 31 15:12:46 svyomo2 kernel: [499770.731370] vboxnetflt: 0 out of 919871 packets were not sent (directed to host)
Mar 31 15:13:08 svyomo2 kernel: [499793.073047] vboxdrv: 00000000409ebfc1 VMMR0.r0
Mar 31 15:13:09 svyomo2 kernel: [499793.424143] vboxdrv: 000000008cff3669 VBoxDDR0.r0
Mar 31 15:13:09 svyomo2 kernel: [499793.573111] VBoxNetFlt: attached to 'enxcce1d50dc8db' / cc:e1:d5:0d:c8:db
Mar 31 15:13:10 svyomo2 kernel: [499794.139029] device enxcce1d50dc8db entered promiscuous mode
Mar 31 15:13:10 svyomo2 kernel: [499794.160265] vboxdrv: 00000000e28984f6 VBoxEhciR0.r0

Could you resolve it?

Change History (5)

comment:1 by Socratis, 5 years ago

  1. 00:00:05.082885 VirtualBox VM 6.0.4_Debian r128164 linux.amd64 (Jan 31 2019 14:42:02) release log
    
    It looks like you're using the Debian fork version of VirtualBox. You can either ask in their forums/channels for help, or completely remove/uninstall/delete/purge their version and install the official version from the Linux Downloads section of VirtualBox.
  1. 00:00:05.256310 File system of '/mnt/ssd0/VBox_image/VBoxGuestAdditions_6.0.4.iso' (DVD) is ext4
    
    Don't download the Guest Additions (GAs) ISO separately; they come bundled with the main program. Just look under the menu "Devices » Insert GAs ISO image..."
  1. 00:00:05.346263 NumCPUs <integer> = 0x0000000000000006 (6)
    00:00:05.969747 CPUM: Physical host cores: 6
    
    You have assigned all your CPUs to the VM. The host is going to run low on resources, since VirtualBox cares about physical processors (cores), not logical ones (threads). See CPU Cores versus threads and Why is it a bad idea to allocate as many VCPUs as there are physical CPUs?.
  1. 00:00:05.346812 [/Devices/hpet/0/Config/] (level 4)
    00:00:05.346815   ICH9 <integer> = 0x0000000000000001 (1)
    
    Any particular reason why you decided to override the template defaults, and go with an unsupported, experimental, OSX-guests-only option? Please change it back to the default PIIX3. Do not change the defaults unless you know what you're getting into. The defaults are selected from people that do this for a living...
  1. 00:00:05.347204 [/Devices/virtio-net/0/] (level 3)
    
    Why virtio-net? And where did you get the drivers from? Again, I suggest that you stick with the defaults. Seriously...
  1. It's usually better and faster, if issues get first addressed in the VirtualBox forums, a lot more eyes there. More than 95% of the issues are resolved in the forums, which keeps the developers focusing on the bug fixes and enhancements, and there is no need for another ticket to keep track of. For example, yours is most probably not a bug and someone from the developers has to deal with it and close it as "Invalid".

Plus a discussion and analysis on the bug tracker is going to help you, me, and potentially a future drive-by user or two. Not so in the forums, many more tend to benefit...

So, if you can, please open a new thread in the Windows Guests section of the forums. Please be sure to mention that you came from the bug tracker and include the ticket number.

But, as I said, all bets are off until you install the official version of VirtualBox. And when you post a log in the forums, make sure the VM is completely shut down before you do. Ans ZIP the logs in the forums...

comment:2 by Yomo, 5 years ago

Hi socratis san

Thank you for your advice.According your opinion,I have doubted fedora virtio-net driver and tried to updated driver version from vritio-win-0.1.141(stable) to 0.1.164(lasted).It is very fine in spite of Debian 10.

Please close this ticket.

Thank you

comment:3 by Socratis, 5 years ago

Thank you for reporting back...

At least now the ticket can be closed.
(I think ;) )

comment:4 by janitor, 5 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy