Custom Query (16363 matches)
Results (1744 - 1746 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2775 | fixed | VB-2.1.0 crashed on starting 2nd guest while 1st is being installed with VT-x and AMD-V enabled (Mac OS X) | ||
| Description |
Host: Mac OS X 10.5.6 with 2gb RAM
Complain/error: An active VM already uses Intel VT-x hw accel. it is not allowed to simultaneously use software virtualization. Settings of the 2nd guest:
From the crash log: Process: VBoxSVC [8165] Path: /Applications/VirtualBox.app/Contents/MacOS/VBoxSVC Identifier: VBoxSVC Version: ??? (???) Code Type: X86 (Native) Parent Process: launchd [1] Date/Time: 2008-12-18 09:57:44.103 +0800 OS Version: Mac OS X 10.5.6 (9G55) Report Version: 6 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c01de1cf Crashed Thread: 9 Thread 9 Crashed: 0 VBoxXPCOM.dylib 0x005e3fbc pt_PostNotifyToCvar + 14 1 VBoxXPCOM.dylib 0x005e4600 PR_NotifyAll + 22 2 VBoxXPCOMIPCC.dylib 0x01130a02 DConnectWorker::Run() + 134 3 VBoxXPCOM.dylib 0x005d02e3 nsThread::Main(void*) + 45 4 VBoxXPCOM.dylib 0x006038dd _pt_iprt_root + 141 5 VBoxRT.dylib 0x005114c0 rtThreadMain + 64 6 VBoxRT.dylib 0x0053b334 rtThreadNativeMain(void*) + 132 7 libSystem.B.dylib 0x91992095 _pthread_start + 321 8 libSystem.B.dylib 0x91991f52 thread_start + 34 PS: If I enable "VT-x and AMD-V", I can start that guest (tried with another 32-bit guest installed earlier) |
|||
| #673 | invalid | Wrong spelling of \vboxsvr on help strings | ||
| Description |
On same help strings of virtualbox "\vboxsvr" is mispelled in "\vboxsrv", confusing users that want mount guest folders from Windows. Example: open Shared Folder icon on right-bottom of virtual machine windows, select a virtual folder and select "What is this?". The same in the help-text under the relevant sector of proprieties. |
|||
| #18607 | obsolete | VM crashed upon booting/accessing an encrypted virtual USB drive. | ||
| Description |
When running a VM with an encrypted virtual USB device (a mounted VDI in my case) the VM crashes upon attemping to access/boot from said virtual USB device. I am given an error saying that the program was trying to access an invalid RAM location (like 0x00000000000...) if this assists repair of the bug. |
|||

