| Summary: | app-emulation/virtualbox-5.0.20 with ?-sources-4.6.0-rc6: Guru Meditation -2708 (VERR_VMM_SET_JMP_ABORTED_RESUME) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Helmut Jarausch <jarausch> |
| Component: | [OLD] Development | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | bkohler, steven |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 586630 | ||
| Bug Blocks: | |||
| Attachments: |
VBox.log
VBox.png |
||
Created attachment 433284 [details]
VBox.png
Hi, what's Guru Meditation and why is this bug fixed? I can confirm this bug. Disabling CONFIG_X86_INTEL_MEMORY_PROTECTION_KEYS in kernel 4.6.0 does not help. Upstream bug: https://www.virtualbox.org/ticket/15439 The same with linux-4.7.0_rc1. Compile fix for linux-4.7: https://www.virtualbox.org/raw-attachment/ticket/15459/VBoxNetAdp-linux.c.patch https://www.virtualbox.org/changeset/61429/vbox "netadp: do not update trans_start for 2.6.31+" "This fix will be included in the next maintenance releases." (In reply to jospezial from comment #5) > https://www.virtualbox.org/changeset/61429/vbox > "netadp: do not update trans_start for 2.6.31+" > "This fix will be included in the next maintenance releases." that was the linux-4.7 compile fix. (In reply to jospezial from comment #6) > (In reply to jospezial from comment #5) > > https://www.virtualbox.org/changeset/61429/vbox > > "netadp: do not update trans_start for 2.6.31+" > > "This fix will be included in the next maintenance releases." > > that was the linux-4.7 compile fix. Well, it compiles but it dies nevertheless under Linux-4.7.0-rc3 As written on the upstream bug I can confirm enabling PREEMPT_NOTIFIERS in kernelconfig it runs stable. CONFIG_PREEMPT_NOTIFIERS is not available as a config option. Because of that it is only enabled with kvm in kernel enabled. https://www.virtualbox.org/changeset/61806/vbox "VMM: bugref:8412, ticketref:15439: workaround for changed stack layout of Linux >= 4.6" VirtualBox 5.0.24 (released 2016-06-28)
This is a maintenance release. The following items were fixed and/or added:
VMM: reverted to the old I/O-APIC code for now to fix certain regressions with 5.0.22 (bug #15529). This means that the networking performance with certain guests will drop to the 5.0.20 level (bug #15295). One workaround is to disable GRO for Linux guests.
Main: when taking a screenshot, don't save garbage for blanked screens
NAT: correctly parse resolv.conf file with multiple separators (5.0.22 regression)
Storage: fixed a possible corruption of stream optimized VMDK images from VMware when opened in read/write mode for the first time
Audio: imlemented dynamic re-attaching of input/output devices on Mac OS X hosts
ACPI: notify the guest when the battery / AC state changes instead of relying on guest polling
Linux hosts: fixed VERR_VMM_SET_JMP_ABORTED_RESUME Guru Meditations on hosts with Linux 4.6 or later (bug #15439)
Solaris hosts: make the GUI work on Solaris 10 again (bug #15549)
So, Please bump!
@Helmut Let this depend on bug 586630 This bug here has been fixed upstream in virtualbox 5.0.24. Compiling with linux-4.7 has also been fixed as far as I know. virtualbox-5.0.26.ebuild is in the tree (bug 586630 fixed) Older versions were removed from the tree. So I think this bug can be closed. |
Created attachment 433282 [details] VBox.log I have app-emulation/virtualbox app-emulation/virtualbox-additions app-emulation/virtualbox-extpack-oracle app-emulation/virtualbox-guest-additions app-emulation/virtualbox-modules installed here - each of version 5.0.20. These build (now) fine under the 4.6.0-rc6 kernel, but it crashes when I try to boot a Windows7 machine. Exactly the same image runs just fine with a 4.5 kernel and then Virtualbox 5.0.16. I get A critical error has occurred while running the virtual machine and the machine execution has been stopped. I've attached VBox.log and VBox.png Thanks for looking into it!