VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (955 - 957 of 16363)

Ticket Resolution Summary Owner Reporter
#2448 fixed Assertion error (iNew != NIL_PGMPOOL_IDX) in pgmPoolAlloc injinius
Description

Setup:

  • openSolaris (nevada 99) host (16GB RAM, 250GB local drive)
  • virtual box version 2.0.2r36488
  • OpenSuse 11 guest OS (4GB RAM, 30GB drive allocated)

I'm trying to run some benchmarks (from iozone.org) in the guest operating system. These benchmarks appear to crash the guest OS (into an "unknon" state). The dmesg log that appears to be related to the guest OS crash looks like:

Oct 17 22:08:52 somehost vboxdrv: [ID 702911 kern.notice] 
Oct 17 22:08:52 somehost !!R0-Assertion Failed!!
Oct 17 22:08:52 somehost Expression: iNew != NIL_PGMPOOL_IDX
Oct 17 22:08:52 somehost Location  : /export/home/vbox/tinderbox/sol64-rel/src/VBox/VMM/VMMAll/PGMAllPool.cpp(3800) int pgmPoolAlloc(VM*, RTGCPHYS, PGMPOOLKIND, uint16_t, uint32_t, PGMPOOLPAGE**)

I didn't see anything in the bugs or discussion lists that matched.

#6728 fixed Assertion error in PGMAllPool.cpp(4091) void pgmPoolTracDerefGCPhysHint (Ubuntu 10.04 x64 host, Windows 7 x64 guest, raw disk mode) -> fixed in SVN nxmehta
Description

When attempting to boot up a Windows 7 x64 guest in a Ubuntu 10.04 x64 host, the guest crashes before fully booting into Windows. The Windows 7 vmdk points to a raw disk (created using the raw disk instructions in the VirtualBox manual). I get to the "Starting Windows" screen and that's it- the guest aborts and closes. I can boot into safe mode without any problems. The error printed in the VBox.log file is:

!!Assertion Failed!!
Expression: <NULL>
Location  : /home/vbox/vbox-3.2.0/src/VBox/VMM/VMMAll/PGMAllPool.cpp(4091) void pgmPoolTracDerefGCPhysHint(PGMPOOL*, PGMPOOLPAGE*, RTHCPHYS, RTGCPHYS, uint16_t)
00:00:19.475 HCPhys=0000000081c32000 GCPhysHint=00000000e0230000

Most interestingly, if I downgrade to VirtualBox 3.1.8, this problem goes away (and can be considered a workaround to anyone else having the same problem). Using 3.1.8 I can boot into my raw disk guest without any errors. So something must have been introduced in 3.2.0 to create this bug.

I've attached the VBox.log file that documents the assertion error.

#1414 fixed Assertion error in VMMDevHGCM.cpp user-jon
Description

Host PC: Ubuntu Gutsy 7.10, Virtualbox 1.5.6
Guest: Ubuntu Feisty 7.04, Virtualbox Guest Additions 1.5.6

VirtualBox works well for me most of the time, so this is not easily reproducible.

  • First thing I noticed was that the VM had mostly hung.. (ie.I could see the display via VRDP, but it was completely unresponsive, it did respond to pings, but connections via ssh or http were immediately accepted then disconnected so I couldn't log on).
  • So I did a, VBoxManage 'savestate', which completed very quickly (I was a bit surprised how fast that was).
  • Then when I restarted the VM, I encountered the error message below:
    user@zeus:~$ VBoxVRDP -startvm Feisty
    VirtualBox VRDP Headless Interface 1.5.6
    (C) 2005-2008 innotek GmbH
    All rights reserved
    
    Listening on port 3393
    
    !!Assertion Failed!!
    Expression: (null)
    Location  : /home/vbox/vbox-1.5.6/src/VBox/Devices/VMMDev/VMMDevHGCM.cpp(896) int vmmdevHGCMLoadStateDone(VMMDevState*, SSMHANDLE*)
    Trace/breakpoint trap
    
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy