Happen Segmentation fault on Virtualbox 6.0.4

[Yomo]

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?

[Socratis]

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.

2. 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..."

3. 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?.

4. 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...

5. 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...

6. 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...

[Yomo]

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

[Socratis]

Thank you for reporting back...

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

[Yomo]

Hi I changed to modify environment of VirtualBox according your suggestions. OS is Debian 9/ Cores is physical and network card is also standard VBox.

But crash is happen reproducibility.

Please see not only attached VBox log but also core dump which is happen crash getting teams suggestion ( https://www.virtualbox.org/wiki/Core_dump )

Could you analyze?

Thank you

Yomo

[Yomo]

I have already gotten core dump file...but Sorry core dump is a little too big. Could you know how send to you that coredump file?

Thank you

Yomo

[Yomo]

I have already gotten core dump file...but Sorry core dump is a little too big. Could you know how send to you that coredump file?

also syslog

Apr 7 11:58:38 svyomo2 kernel: [ 4920.048447] 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 Apr 7 11:58:39 svyomo2 kernel: [ 4921.121471] device enxcce1d50dc8db left promiscuous mode Apr 7 11:58:39 svyomo2 kernel: [ 4921.154532] vboxnetflt: 0 out of 333635 packets were not sent (directed to host)

[Yomo]

I have already gotten core dump file...but Sorry core dump is a little too big. Could you know how send to you that coredump file?

sorry mistake

Apr 7 11:58:38 svyomo2 kernel: [ 4920.048441] EMT-0[23804]: segfault at 7fcece814fe0 ip 00007fcf1a8310b4 sp 00007fcece913928 error 4 in libc-2.24.so[7fcf1a708000+195000] Apr 7 11:58:38 svyomo2 kernel: [ 4920.048447] 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 Apr 7 11:58:39 svyomo2 kernel: [ 4921.121471] device enxcce1d50dc8db left promiscuous mode Apr 7 11:58:39 svyomo2 kernel: [ 4921.154532] vboxnetflt: 0 out of 333635 packets were not sent (directed to host)

[Yomo]

Hi I analyzed core by gdb. It seems glic bug(​https://www.suse.com/ja-jp/security/cve/CVE-2019-6488/) not Virtualbox bug.So I close this ticket. Below is dump information.

Thank you so much.

root@svyomo2:/home/yomo# gdb /usr/lib/virtualbox/VirtualBoxVM core GNU gdb (Debian 7.12-6) 7.12.0.20161007-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <​http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <​http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <​http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib/virtualbox/VirtualBoxVM...(no debugging symbols found)...done. [New LWP 23804] [New LWP 23764] [New LWP 23768] [New LWP 23763] [New LWP 23807] [New LWP 23803] [New LWP 23776] [New LWP 23813] [New LWP 23765] [New LWP 23771] [New LWP 23808] [New LWP 23811] [New LWP 23845] [New LWP 23815] [New LWP 23825] [New LWP 23769] [New LWP 23806] [New LWP 23809] [New LWP 23842] [New LWP 23779] [New LWP 23810] [New LWP 23817] [New LWP 23823] [New LWP 23819] [New LWP 23864] [New LWP 23827] [New LWP 23824] [New LWP 23814] [New LWP 23820] [New LWP 23821] [New LWP 23818] [New LWP 23826] [New LWP 23816] [New LWP 23781] [New LWP 23770] [New LWP 23758] [New LWP 23812] [New LWP 23775] [New LWP 23822]

warning: .dynamic section for "/lib/x86_64-linux-gnu/libsystemd.so.0" is not at the expected address (wrong library or version mismatch?) [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/lib/virtualbox/VirtualBoxVM --comment Windows10 --startvm 4fd22306-4227-40'. Program terminated with signal SIGSEGV, Segmentation fault. #0 memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:299 299 ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S: そのようなファイルやディレクトリはありません. [Current thread is 1 (Thread 0x7fcece914700 (LWP 23804))] (gdb) bt #0 memmove_avx_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:299 #1 0x00007fcea5515e02 in ?? () from /usr/lib/virtualbox/VBoxDD.so #2 0x00007fcea551633d in ?? () from /usr/lib/virtualbox/VBoxDD.so #3 0x00007fcea550ada6 in ?? () from /usr/lib/virtualbox/VBoxDD.so #4 0x00007fcef4beb47b in ?? () from /usr/lib/virtualbox/components/VBoxVMM.so #5 0x00007fcef4beecdb in ?? () from /usr/lib/virtualbox/components/VBoxVMM.so #6 0x00007fcef4b899e1 in ?? () from /usr/lib/virtualbox/components/VBoxVMM.so #7 0x00007fcef4b8e9c8 in ?? () from /usr/lib/virtualbox/components/VBoxVMM.so #8 0x00007fcef4b8abaf in ?? () from /usr/lib/virtualbox/components/VBoxVMM.so #9 0x00007fcef4bf8bff in ?? () from /usr/lib/virtualbox/components/VBoxVMM.so #10 0x00007fcf1a34ca0c in ?? () from /usr/lib/virtualbox/VBoxRT.so #11 0x00007fcf1a3f7a5a in ?? () from /usr/lib/virtualbox/VBoxRT.so #12 0x00007fcf1acb24a4 in start_thread (arg=0x7fcece914700) at pthread_create.c:456 #13 0x00007fcf1a7f0d0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97 (gdb)

[Yomo]

Segfault and VBox guest crash is allways happen using video encording software on guest. ​https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906532

Not Virtualbox Bug. Please close this ticket.

Thank you

Yomo