Custom Query (16363 matches)
Results (1480 - 1482 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #245 | invalid | VBoxManage controlvm poweroff does not work when >= VBoxVRDP processes running | ||
| Description |
I'm not able to poweroff my machines if there are more than two VBoxVRDP processes running. I will shortly summarize two test cases: Working caseI have started VBoxSVC in a shell:
In another shell I start a virtual box:
The machine boots up. To poweroff I issue:
This works perfectly, the VBoxVRDP process exits. Output of VBoxSVC is: ********************************************* InnoTek VirtualBox XPCOM Server Version 1.3.8 (C) 2004-2007 InnoTek Systemberatung GmbH All rights reserved. Starting event loop.... [press Ctrl-C to quit] Informational: VirtualBox object created (rc=00000000). Informational: VirtualBox object deleted. not working caseNow, again, I start a VBoxSVC process as described above. Also as described above I start VBoxVRDP. But this time, I start >= 2 different virtual boxes the same time. As described above, I issue a poweroff command to one of the running virtual boxes. This gives no special output, but the VBoxVRDP process keeps on running. When I issue the poweroff a 2nd time, I get: irtualBox Command Line Management Interface Version 1.3.8
(C) 2005-2007 InnoTek Systemberatung GmbH
All rights reserved.
[!] FAILED calling virtualBox->OpenExistingSession (session, uuid) at line 3860!
[!] Primary RC = 0x80070005
[!] Full error info present: true , basic error info present: true
[!] Result Code = 0x80070005
[!] Text = The machine 'machine02' does not have an open session
[!] Component = Machine, Interface: IMachine, {fd443ec1-0009-4f5b-9282-d72760a66916}
[!] Callee = IVirtualBox, {e1d95593-f579-4f47-b489-0b67181014e1}
So, well, I'm not able to poweroff my machine through VBoxManage. The only thing I can do is to either kill the VBoxVRDP process or press Ctrl-C in the shell. Another interesting thing is the output of VBoxSVC: ********************************************* InnoTek VirtualBox XPCOM Server Version 1.3.8 (C) 2004-2007 InnoTek Systemberatung GmbH All rights reserved. Starting event loop.... [press Ctrl-C to quit] Informational: VirtualBox object created (rc=00000000). Shouldn't I get a "object created" for every virtual box I start? And shouldn't I get a "object deleted" after the poweroff? I tried to get rid of this error for a few hours now - but in any case, I wasn't able to proper poweroff my virtual boxes with VBoxManage in case I had >= 2 virtual boxes running... |
|||
| #6386 | obsolete | Ubuntu Server guest causes VBox to crash during boot if host is under load | ||
| Description |
The VirtualBox process crashes (Win7 32 bit, software virtualization) quite reliably if I have other CPU hungry tasks running (e.g. zipping a huge folder) and then attempt to boot up a Ubuntu Server guest. It seems to be reproducible relatively reliably. 00:04:07.928 AssertLogRel D:\tinderbox\win-3.1\src\VBox\VMM\PGMPhys.cpp(3123) PGMR3PhysAllocateHandyPages: RT_SUCCESS(rc) 00:04:07.929 idPage=0x52e00 HCPhysGCPhys=0000000051d91000 rc=VERR_MAP_FAILEDAssertLogRel D:\tinderbox\win-3.1\src\VBox\VMM\PGMPhys.cpp(3357) PGMR3PhysTlbGCPhys2Ptr: RT_SUCCESS_NP(rc2) 00:04:07.970 VERR_MAP_FAILED (-75) - Failed to map a memory object. 00:04:07.970 AssertLogRel D:\tinderbox\win-3.1\src\VBox\VMM\VMMAll\PGMAllPhys.cpp(2255) PGMPhysWrite: <NULL> 00:04:07.970 pgmPhysGCPhys2CCPtrInternal failed on 0000000007e49f18 / A--:RAM:000042148000:0052e52:U03d7 -> VERR_MAP_FAILED |
|||
| #6497 | obsolete | Ubuntu guest occasional guru meditation during boot (Win7 32 bit host, RAW mode) | ||
| Description |
VBox 3.1.6 displays a critical error message occasionally when I boot my Ubuntu Server guest. 00:01:11.300 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'. 00:01:11.438 Display::handleDisplayResize(): uScreenId = 0, pvVRAM=06f80000 w=640 h=480 bpp=16 cbLine=0x500 |
|||

