Custom Query (16363 matches)
Results (1540 - 1542 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1573 | fixed | Ubuntu Hardy: VirtualBox resume causes system reboot (host) | ||
| Description |
On 4 separate occasions now, VirtualBox crashed after doing a resume of a saved session and it causes my host (Ubuntu Hardy) to reboot without warning. I'm not sure what's causing it, but in each case, after the host reloads and I try to start the VirtualBox guest (Windows XP), I get an error stating that the host is inaccessible with a message of: Could not load the settings file '/home/cdukes/.VirtualBox/Machines/XPSP3/XPSP3.xml'.
Premature end of data in tag VirtualBox line 3.
Location: '/home/cdukes/.VirtualBox/Machines/XPSP3/XPSP3.xml', line 65 (3), column 49.
Result Code:
0x80004005
Component:
VirtualBox
Interface:
IVirtualBox {2d3b9ea7-25f5-4f07-a8e1-7dd7e0dcf667}
When I look at that file, it looks like the file is truncated. The only option I have is to delete the host and recreate it using the the same virtual disk. VirtualBox seemed so much more stable in v1.5x, what happened? |
|||
| #1574 | fixed | Guru Meditation -2304 (VERR_REM_TOO_MANY_TRAPS) | ||
| Description |
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 |
|||
| #1575 | fixed | display not working properly in FEdora Core 9 live | ||
| Description |
I tried running FC 9 live cd as a guest: http://download.fedoraproject.org/pub/fedora/linux/releases/9/Live/i686/Fedora-9-i686-Live.iso It went fine but the default resolution is set to something horrendously large (probably because the host system has a non-standard 1024x1280 screen resolution). The result is that about half of the guest screen is not visible. When I log in, go to top menu System -> Preferences -> Hardware -> Screen Resolution, and set the resolution to something sane like 800x600 or 1024x768 the bottom half of the guest screen is not properly refreshed. It is black most of the time, moving the guest windows usually displays some garbage there, moving the host window sometimes refreshes the screen until the guest mouse pointer is moved. The host is OS X 10.4 |
|||

