| Summary: | app-emulation/virtualbox-4.1.8: fails with kernel linux-3.2.2-hardened-r1 and above | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Gabriel <gabriel> |
| Component: | Current packages | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | hardened, lubomir.krajcovic, pageexec, patrick, proxy-maint, spender, swapon |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Kernel crashes logs
log for failing vanilla 64-bit gentoo on hardened host hardened kernel config under which the problem occurs kernel config for hardened-sources-3.2.11 kernel crash log |
||
|
Description
Gabriel
2012-02-06 17:52:11 UTC
Created attachment 301047 [details]
Kernel crashes logs
Apparently I cannot change my comment, so just to be clear, this is the configuration that works fine: 3.1.5-hardened app-emulation/virtualbox-4.1.8 app-emulation/virtualbox-additions-4.1.8 app-emulation/virtualbox-extpack-oracle-4.1.8 app-emulation/virtualbox-modules-4.1.4 (note the use of the old modules) @ hardened team. Can you look into this, please? (In reply to comment #3) > @ hardened team. Can you look into this, please? I can confirm this. Specifically I looked at virtualbox-4.1.8 (modules and all) and hardened-sources-3.2.7 = grsecurity-2.9-3.2.7-201202251203. When I try to start vbox I get the following pop-up warning: <quote> A critical error has occurred while running the virtual machine and the machine execution has been stopped. For help, please see the Community section on http://www.virtualbox.org or your support contract. Please provide the contents of the log file VBox.log and the image file VBox.png, which you can find in the /home/blueness/.VirtualBox/Machines/soft64/Logs directory, as well as a description of what you were doing when this error happened. Note that you can also access the above files by selecting Show Log from the Machine menu of the main VirtualBox window. Press OK if you want to power off the machine or press Ignore if you want to leave it as is for debugging. Please note that debugging requires special knowledge and tools, so it is recommended to press OK now. </quote> One can then kill the machine or ignore, in which case the vm goes suspended (what they call "guru meditation"). The log ends with <log> 00:02:38.993 VMSetError: /var/tmp/portage/app-emulation/virtualbox-4.1.8-r1/work/VirtualBox-4.1.8_OSE/src/VBox/VMM/VMMR3/MM.cpp(684) int MMR3AdjustFixedReservation(VM*, int32_t, const char*); rc=VERR_VMM_SET_JMP_ABORTED_RESUME 00:02:38.993 VMSetError: Failed to reserve physical memory (0x1004 -> 0x1000; VMMDev Heap) 00:02:38.994 VMSetError: /var/tmp/portage/app-emulation/virtualbox-4.1.8-r1/work/VirtualBox-4.1.8_OSE/src/VBox/VMM/VMMR3/MM.cpp(684) int MMR3AdjustFixedReservation(VM*, int32_t, const char*); rc=VERR_VMM_SET_JMP_ABORTED_RESUME 00:02:38.994 VMSetError: Failed to reserve physical memory (0x1004 -> 0xc04; VMMDev) 00:02:38.996 VMSetError: /var/tmp/portage/app-emulation/virtualbox-4.1.8-r1/work/VirtualBox-4.1.8_OSE/src/VBox/VMM/VMMR3/MM.cpp(684) int MMR3AdjustFixedReservation(VM*, int32_t, const char*); rc=VERR_VMM_SET_JMP_ABORTED_RESUME 00:02:38.996 VMSetError: Failed to reserve physical memory (0x1004 -> 0x404; VRam) 00:02:39.031 AssertLogRel /var/tmp/portage/app-emulation/virtualbox-4.1.8-r1/work/VirtualBox-4.1.8_OSE/src/VBox/VMM/VMMR3/VMM.cpp(1969) int VMMR3CallR0(VM*, uint32_t, uint64_t, SUPVMMR0REQHDR*): rc == VINF_SUCCESS || RT_FAILURE(rc) 00:02:39.031 uOperation=29 rc=VINF_PGM_SYNC_CR3 </log> I'll attach a full copy of the log for comparison. Note: I do not get any kernel messages. Created attachment 303583 [details]
log for failing vanilla 64-bit gentoo on hardened host
what's the host kernel .config? in particular, is any of UDEREF/KERNEXEC enabled? Created attachment 303641 [details]
hardened kernel config under which the problem occurs
Pipacs, note that this is our VIRTUALIZATION option which masks out UDEREF and KERNEXEC so that it doesn't even show up in the config file.
I'm confirming exactly the same problem with hardened kernels in .32 stable series. I've tested hardened-sources-2.6.32-r90 & -r92. -r77 works. Virtualbox 4.1.8 and whole environment except kernel) remains the same. emerge --info: http://pastebin.com/dVppY0tw used kernel config for -r90 (obtained from -r77 with make oldconfig): http://pastebin.com/DeGJsGa8 Just tested newest hardened-sources-2.6.32-r93 (based on 2.6.32.57 + genpatches-2.6.32-48 + grsecurity-2.9-2.6.32.57-201203022148), problem remains. Virtualbox log: http://pastebin.com/naZp8EST Is there any update on this? I have just tried with hardened-sources-3.2.11 and virtualbox-4.1.14* and still the same results. It is still working with hardened-sources-3.1.5 though. Created attachment 310335 [details]
kernel config for hardened-sources-3.2.11
Created attachment 310337 [details]
kernel crash log
Currently, some kind of workaround like pax-mark m "/usr/$(get_libdir)/virtualbox/VirtualBox" may help for now. After that - it will not fail, so - works for me. |
