Summary: | app-emulation/virtualbox-5: INTNET-RECV[...] general protection ... in VBoxRT.so | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Ervin Peters <ervin.peters> |
Component: | Current packages | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | ervin.peters, jstein, masterzorag, proxy-maint, tabascoz |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Ervin Peters
2018-01-10 17:51:45 UTC
Correction: 5.1.30 runs for hours, 5.2.4 crashes randomly with 1 CPU configured. Now I try 5.2.2. ervin Switching back to stable 5.1.30, 5.2.2 crashed, too. Does anyone recognize similar behaviour? ervin After upgrading to virtualbox-5.1.32 this spontaneous bug reappear. I played around and added some IOMMMU option to the kernel, because vbox didn't find it. I also upgraded to unstable 5.2.26, with same behaviour. No success, vbox crashes a few minutes after boot the vm, while windows inside tries to update itself. At least I found the option of emulated Network Hardware. Since the paravirtual device seem a somehow logical option, but windows doesn't support it. So I switched to the Intel Pro/1000 MT Server (82545EM). Because of that switching, DesktopNIC -> Paravirtual NIC -> ServerNIC Windows reinstalls some drivers. Since then, no crashes occurred for hours. Maybe, those crashes are related to Windows drivers, the vbox emulation of the desktop NIC or some windows confusness with those nic drivers. I hope that's because around in the world there is no Idea what causes this, even in the partially unfriendly Community VBOX issue tracker. I test tomorrow and then, if no crash occur, mark this bug as resolved. Kind regards, Viele Grüße, много привет, 許多問候, Ervin 10 hours running virtualbox/win10 and no segfault. set to resolved / worksforme ervin After a Kernel (and many other) update(s) it starts again segfaulting. Usually when Windows 10 update is running. Is this still an issue with recent virtualbox releases? (In reply to Lars Wendler (Polynomial-C) from comment #6) > Is this still an issue with recent virtualbox releases? Seems not. I switched back to some standard intel network card and used the current ~amd64 virtualbox a few days (~30hours) without rhat issue. Inclusive some windows updates @ startup of the vm. Mark this item as Resolved/obsolete |