Windows VM crashes with 5.1.4 and CIFS operations

[necromonga]

I upgraded 3 Linux hosts (Debian Jessie) from 5.0.26 to 5.1.4 and now have problems when doing file operations on CIFS shares;
When working locally everything is fine, but if i'm doing more on network shares (copying and moving files and folders) at one point the Guest just disappears;
No error message, nothing - VirtualBox status of the VM is 'Aborted'

Are there anything debug options to turn on to find out what happens or what i can do to provide useful infos for the developers?

necro

[Perryg]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

[necromonga]

Attached the log file - was copying some files from one cifs share to another and guest vm disappeared when i was clicking the [back] button in windows explorer to go back one directory up;

[Perryg]

The log does not show anything that stands out so the next thing is to look at the syslog or dmesg on the host the next time this happens and post relevant information.

One other question is do the other hosts have the same resources?

[aanderson]

I am running Ubuntu 16.04 and VirtualBox 5.1.4. I believe my crashes my be related because the VBox.log does not contain any information and the crashes seem to coincide with Windows explorer file operations. Here is a tail of my dmesg:


[177822.154393] EMT-3[25194]: segfault at 10 ip 00007f3a6260ee0a sp 00007f3a96dfaba0 error 4 in VBoxDD.so[7f3a624f6000+28d000]
[177889.360796] vboxdrv: ffffffffc0960020 VMMR0.r0
[177889.719333] vboxdrv: ffffffffc05b5020 VBoxDDR0.r0
[177889.876660] vboxdrv: ffffffffc0012020 VBoxEhciR0.r0
[178588.654926] EMT-3[27862]: segfault at 10 ip 00007f01ed6bd9db sp 00007f020dca8bb0 error 4 in VBoxDD.so[7f01ed5a6000+28d000]
[178594.382033] vboxdrv: ffffffffc085d020 VMMR0.r0
[178594.719962] vboxdrv: ffffffffc0595020 VBoxDDR0.r0
[178618.692352] vboxdrv: ffffffffc085d020 VMMR0.r0
[178619.040493] vboxdrv: ffffffffc0595020 VBoxDDR0.r0
[178619.190773] vboxdrv: ffffffffc0006020 VBoxEhciR0.r0

[frank]

Which VirtualBox package (exact name please) do you have installed?

[aeichner]

Are you using the .deb or .run package from http://www.virtualbox.org ? This is important to get the location of the crash in the source code. Anyway, the best way to report such crashes is our official bug tracker. Please create a ticket there and attach all the information you have like VBox.log etc. It would be great if you could provide us with a core dump too because it makes further investigation much easier.

[TEP]

Having the same problem as necromonga.

Linux Ubuntu Mate 16.04.01LTS.
Kernel 4.4.0-36 (same problem occurred on 4.4.0-34).
VB 5.1.4 with latest extensions installed.

Had been running 5.0.26 for sometime with no errors. Upgraded to 5.1.4 and started having problems. I'm not convinced it's only CIFS operations but that is common to many of the crashes. VB W7 guest just disappears. Last few log files included. Oldest is when it crashed, newer logs are the result of reboot/reset to get the guest running again.

[aanderson]

Thanks for your time. It appears I am encountering this issue: https://www.virtualbox.org/ticket/15684 I installed the virtualbox-5.1_5.1.4-110228-Ubuntu-xenial_amd64.deb Ubuntu package using the Ubuntu Software GUI tool and without using the command line.