You are not logged in.

#1 2014-05-04 17:26:29

adventurer
Member
Registered: 2014-05-04
Posts: 128

Can't start Virtualbox VMs with linux-grsec

Hello everybody,

I'm new to Arch Linux after running (K)Ubuntu and openSuse for several years. Now I'm faced with the following problem:

Whenever I boot my system with the linux-grsec kernel I'm not able to start my Virtualbox VMs. I get an error message that says something like this (my translation): "A serious error happened and the execution of the virtual machine was interrupted."

Note that linux-grsec-headers, gcc, libtool, dkms,virtualbox-host-dkms and virtualbox-guest-dkms are installed.

Executing

# dkms install vboxhost/4.3.10 -k 3.14.2-1-grsec

yields

Module vboxhost/4.3.10 already installed on kernel 3.14.2-1-grsec/x86_64

VBox.log says:

00:00:28.922036 VMSetError: /build/virtualbox/src/VirtualBox-4.3.10/src/VBox/VMM/VMMR3/MM.cpp(673) int MMR3AdjustFixedReservation(PVM, int32_t, const char*); rc=VERR_VMM_SET_JMP_ABORTED_RESUME
00:00:28.922048 VMSetError: Failed to reserve physical memory (0x8404 -> 0x8400; VMMDev Heap)
00:00:28.922521 VMSetError: /build/virtualbox/src/VirtualBox-4.3.10/src/VBox/VMM/VMMR3/MM.cpp(673) int MMR3AdjustFixedReservation(PVM, int32_t, const char*); rc=VERR_VMM_SET_JMP_ABORTED_RESUME
00:00:28.922528 VMSetError: Failed to reserve physical memory (0x8404 -> 0x8004; VMMDev)
00:00:28.933699 VMSetError: /build/virtualbox/src/VirtualBox-4.3.10/src/VBox/VMM/VMMR3/MM.cpp(673) int MMR3AdjustFixedReservation(PVM, int32_t, const char*); rc=VERR_VMM_SET_JMP_ABORTED_RESUME
00:00:28.933709 VMSetError: Failed to reserve physical memory (0x8404 -> 0x404; VRam)
00:00:28.934089 AIOMgr: Flush failed with VERR_INVALID_PARAMETER, disabling async flushes
00:00:28.934256 NAT: zone(nm:mbuf_cluster, used:0)
00:00:28.934446 NAT: zone(nm:mbuf_packet, used:0)
00:00:28.934462 NAT: zone(nm:mbuf, used:0)
00:00:28.934467 NAT: zone(nm:mbuf_jumbo_pagesize, used:0)
00:00:28.934500 NAT: zone(nm:mbuf_jumbo_9k, used:0)
00:00:28.934608 NAT: zone(nm:mbuf_jumbo_16k, used:0)
00:00:28.934666 NAT: zone(nm:mbuf_ext_refcnt, used:0)
00:00:28.938363 VMMR3Term: R0 term failed, rc=VERR_VMM_SET_JMP_ABORTED_RESUME (-2708) - VMM set jump resume error.. (warning)
00:00:28.938589 Changing the VM state from 'DESTROYING' to 'TERMINATED'.

I should add that the VMs start without any problems if I boot the normal kernel.

Any help would be appreciated.

Offline

#2 2014-05-07 09:34:59

nthrow
Member
Registered: 2014-05-07
Posts: 2

Re: Can't start Virtualbox VMs with linux-grsec

I'm also unable to start any VirtualBox instances with a grsec kernel, despite dkms successfully compiling the modules using the grsec kernel headers.  The specific error message the log ends with is:

00:00:02.317211 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={480b372c-c0b5-4c23-9bd7-dcbb85b1594c} aComponent={Display} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false
00:00:02.321293 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={480b372c-c0b5-4c23-9bd7-dcbb85b1594c} aComponent={Display} aText={Could not take a screenshot (VERR_NOT_SUPPORTED)}, preserve=false

I've also pasted the entire VBox.log output here.  Let me know if there's any more information I can provide that might be useful.

Last edited by nthrow (2014-05-07 09:36:45)

Offline

#3 2014-05-07 14:45:14

andy123
Member
Registered: 2011-11-04
Posts: 169
Website

Re: Can't start Virtualbox VMs with linux-grsec

There seems to be an issue about this on the virtualbox bugtracker: https://www.virtualbox.org/ticket/2652

A quick search also turned up this result, but I haven't checked yet if this option (still) exists.


i'm sorry for my poor english wirting skills…

Offline

#4 2014-05-13 11:06:22

adventurer
Member
Registered: 2014-05-04
Posts: 128

Re: Can't start Virtualbox VMs with linux-grsec

andy123 wrote:

A quick search also turned up this result, but I haven't checked yet if this option (still) exists.

This option is not available in /etc/sysctl.d/05-grsecurity.conf. I guess it can be used when compiling your own kernel. I won't do that for sure.

Offline

Board footer

Powered by FluxBB