Ticket #1574 (closed defect: fixed)

Opened 10 years ago

Last modified 9 years ago

Guru Meditation -2304 (VERR_REM_TOO_MANY_TRAPS)

Reported by: mjlucas Owned by:
Priority: major Component: VMM
Version: VirtualBox 1.5.6 Keywords:
Cc: Guest type: other
Host type: other


Using Virtual Box to teach operating systems concepts to students (Using unsupported Minix). I have had a few students trigger the error Guru Meditation -2304 (VERR_REM_TOO_MANY_TRAPS) when modifying the schedulers in the guest.

What does this error mean? What are possible causes? The only fix I have found is to reinstall the system.

This is on Version 1.5.6 (Cannot upgrade at the current time), Redhat RHEL5 Update 1 64-bit AMD host.

Other common errors seen when the crashes happen are:

VERR_REM_TOO_MANY_TRAPS -> uTrap=d error=30 next_eip=00000055 eip=00000055 cr2=00000000

ERROR [COM]: aRC=0x80004005 aIID={fd443ec1-0006-4f5b-9282-d72760a66916} aComponent={Mouse} aText={Could not send the mouse event to the virtual mouse (VERR_PDM_NO_QUEUE_ITEMS)} aPreserve=false

ERROR [COM]: aRC=0x80004005 aIID={fd443ec1-000a-4f5b-9282-d72760a66916} aComponent={Keyboard} aText={Could not send scan code 0x000000C5 to the virtual keyboard (VERR_PDM_NO_QUEUE_ITEMS)} aPreserve=false


VBox.log Download (192.4 KB) - added by mjlucas 10 years ago.
Crash file from one machine

Change History

Changed 10 years ago by mjlucas

Crash file from one machine

comment:1 Changed 10 years ago by sandervl73

Keep in mind that you'll get such a guru meditation when triggering a double fault in the guest. So if your students made a mistake, this is the likely result.

comment:2 Changed 10 years ago by sandervl73

There are other causes as well, but it's kind of hard to pinpoint them.

comment:3 Changed 10 years ago by mjlucas

Thanks for the quick reply. I have their code so should be able to pinpoint what they are doing. We use the closed source build (VRDP) so can't compile with debug.

comment:4 Changed 10 years ago by frank

  • Component changed from other to VMM

comment:5 Changed 9 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Please reopen if this bug still applies to the latest release (2.2.2).

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use