5.1.4/5.1.6 crash WIN10 guests

[ucrasher]

Hello,
I have two WIN10 VMs. Starting with the update to 5.1.x (from 5.0) both suddenly close/crash. The VM window simply disappears. Log files do not contain anything about the crash, the process is probably dying before they can be written.
The actions that lead to the crash are navigating in the file explorer and unplug of a USB device (passed into the VM). Repeating the same explorer navigation a second time did not trigger the issue. USB unplug is more reproducible.

Update to 5.1.4 happend at Monday. First I had the old 5.0.26 GA installed and assumed that would be the reason. Update of GA did not fix it. Then 5.1.6 came out, but did not help (latest GA now).

Host is Ubuntu 16.04, guests are Win10-1607 and Win10-1511.

I do not attach the VB-log now, will save it on next crash. Also will check if dmesg will expose something useful.

My hope is that such behavior is already known.....
Thanks!

[ucrasher]

Hello,
at that day the crashes occurred frequently. Even after reboot of the host. But now I did not have a single crash on any of the VMs. (I have lots of USB unplug/replug - no crash).

Very strange. But for now it looks like ok.
Perhaps my hardware is dying....

[ucrasher]

Hello,
just a few minutes I wrote the issue did not show up since. It can read it here It just happened again on USB unplug of a CDC-ACM device.
This time I have VB and syslogs. I can also share the USB crash report with the devs.

And there are interesting details, a segfault in VBoyDD.so:

Code: Select all

04:11:12.098613 VUSB: Detached '00007fe874d5be50[proxy 0c2e:096a]' from port 1
04:11:12.098710 AssertLogRel /home/vbox/vbox-5.1.6/src/VBox/VMM/VMMR3/TM.cpp(1727) int TMR3TimerDestroy(PTMTIMER): <NULL>

And syslog:

Code: Select all

Sep 15 17:14:41 don kernel: [27511.485796] USBDevIo--1[19180]: segfault at e8 ip 00007fe89133910a sp 00007fe85557ae90 error 4
Sep 15 17:14:41 don kernel: [27511.485802] EhciFramer[14246]: segfault at f0 ip 00007fe891335ca0 sp 00007fe85600eb50 error 4 in VBoxDD.so[7fe89127a000+28e000]
Sep 15 17:14:41 don kernel: [27511.485808]  in VBoxDD.so[7fe89127a000+28e000]

I will create a bug report.

[ucrasher]

Ticket
https://www.virtualbox.org/ticket/15936

[Xotas]

Hello,
I have a similar issue Linux 17.3 Mint Rosa Host onto W10 guest, started with VB 5.1 with the mic prob. and sorted it by upgrading to 5.1.6 but now I have issues with the sharing folders communication as suddenly stops and freezes the W10 OS only sorted for a little longer with a reset on the guest.
Any suggestions or fixes welcomed.

Thanks to all the members of this great community.

[ucrasher]

Hi Xotas,
I don't think it is related to my report.
Did you reinstall the guest additions? That often fixes issues with shared folders.

Regards, ucrasher.

[Sisterpixel]

Ticket
https://www.virtualbox.org/ticket/15936

Hello. Can you take a look at my Topic too please? Thanks
viewtopic.php?f=7&t=79913

[ucrasher]

Hi Sisterpixel,
I do not see anything related to my post. Sorry, I cannot help.

[Xotas]

Hi Xotas,
I don't think it is related to my report.
Did you reinstall the guest additions? That often fixes issues with shared folders.

Regards, ucrasher.

Hi ucrasher
Yes I have everything as it should and still have that issue and the initial boot abort is also frequent, I overcome the folders communication issue by whilst still working in the beginning I copy the file I'm working on onto the guest OS and this way I have had not much issues, but if I forgot to do that, half way trough the work it just freezes everything, having to reset the guest and try to recover as much as I can.
I have VB Version 5.1.6 r110634 (Qt5.6.1) and respective Guest Addition 5.1.6r 110634 installed properly I believe.

Thanks for your time and sorry if miss match your post but it seemed my issue was related to this one

[ChrisMW]

I have something similar, but only on W10 / 64bit. The 32 bit client works pretty well, although it sometimes needs a second VM start before booting. Both W10's were converted from a running W7. But the symptom is the same, the VM just disappears. Sometimes in the middle of doing something, sometimes not doing anything. I've not discovered a pattern, but leaving Skype For Business and Outlook running will trigger a 'disappear' within 48 hours.

Another observation, whilst W7 works well with paravirtualized nic's, W10 doesn't. 32 bits will run with the win 8.1 stable version of the driver, but the 64bits just fails all the time. The W10 driver doesn't work, ever, but that is most likely a bug with the driver. W7 runs very well with the W7 driver in both 32/64 bit mode.

My main machine is the 64 bit client, so I have had to revert to W7 in order to be able to work.