Custom Query (16363 matches)
Results (598 - 600 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #612 | fixed | Feature request: usb 2.0 ehci support | ||
| Description |
It would be nice if VirtualBox emulated a usb 2.0/ehci host controller on the guest operating system at near-native bandwidth. Usb support in VirtualBox has been a huge boon to users already, and high-speed usb support would allow the use of usb cameras, microphones, video-capture devices, and other high-bandwidth devices inside the guest. Currently VMware Workstation >= 6.0 and Player >= 2.0 are the only x86 virtualization softwares I know of to claim to support ehci, although they seem to support it better under a Windows host than a Linux one. It seems someone was working on an ehci patch for Qemu at some point, but that it was never finished; see this thread: http://marc.info/?l=qemu-devel&m=117483468018061&w=2 Is ehci support on the roadmap for VirtualBox 1.6.0? For 1.7.0? At all? Just curious to know. |
|||
| #613 | fixed | OSE Build Failure => Fixed in 1.5.6 | ||
| Description |
Build from the 1.5.0 OSE tarball fails with the following error: kmk.exe[3]: Leaving directory `C:/build/VirtualBox-1.5.0_OSE/src/VBox/Frontends' kmk.exe[3]: Entering directory `C:/build/VirtualBox-1.5.0_OSE/src/VBox/Installer ' kmk.exe: Entering an unknown directory kmk.exe: *** win32: No such file or directory. Stop. kmk.exe: Leaving an unknown directory kmk.exe[3]: *** [pass_libraries_before] Error 2 kmk.exe[3]: Leaving directory `C:/build/VirtualBox-1.5.0_OSE/src/VBox/Installer' kmk.exe[2]: *** [pass_libraries_before] Error 2 kmk.exe[2]: Leaving directory `C:/build/VirtualBox-1.5.0_OSE/src/VBox' kmk.exe[1]: *** [pass_libraries_before] Error 2 kmk.exe[1]: Leaving directory `C:/build/VirtualBox-1.5.0_OSE/src' kmk: *** [pass_libraries_before] Error 2 |
|||
| #614 | fixed | VirtualBox hangs on "Starting the virtual machine... 0%" | ||
| Description |
When starting a VM with VirtualBox 1.5, it hangs on "Starting the virtual machine..." at 0%. I am forced to use kill -9 to kill the process - it hangs indefinitely. The dmesg output is below: [ 157.048000] CPU: 0 [ 157.048000] EIP: 0060:[<c01675bf>] Tainted: PF VLI [ 157.048000] EFLAGS: 00210202 (2.6.20-15-generic #2) [ 157.048000] EIP is at split_vma+0x6f/0xe0 [ 157.048000] eax: 00000001 ebx: c03a9c98 ecx: 00000000 edx: 00000054 [ 157.048000] esi: b3f0c000 edi: 00000000 ebp: f5980668 esp: f5a8fdc4 [ 157.048000] ds: 007b es: 007b ss: 0068 [ 157.048000] Process VirtualBox (pid: 8157, ti=f5a8e000 task=f6604560 task.ti=f5a8e000) [ 157.048000] Stack: 00000000 00000000 b3f0c000 c03a9cb4 c03a9c98 b3f26000 c01676c8 00000000 [ 157.048000] f65899b0 ffffffff ffffffff b3f26000 00000007 00000000 0000001a b3f0c000 [ 157.048000] f6604560 f70b3490 f8fc1fb0 f6604560 00000007 f70b3490 f5a8fe60 00000027 [ 157.048000] Call Trace: [ 157.048000] [<c01676c8>] do_munmap+0x98/0x1e0 [ 157.048000] [<f8fc1fb0>] rtR0MemObjNativeMapUser+0x260/0x270 [vboxdrv] [ 157.048000] [<f8fc07b0>] RTR0MemObjMapUser+0xe0/0x190 [vboxdrv] [ 157.048000] [<f8fbd639>] SUPR0LowAlloc+0xc9/0x190 [vboxdrv] [ 157.048000] [<f8fbe8cf>] supdrvIOCtl+0x3df/0x1540 [vboxdrv] [ 157.048000] [<c016b30c>] __vmalloc_area_node+0xdc/0x130 [ 157.048000] [<c0102210>] __switch_to+0xa0/0x1f0 [ 157.048000] [<f8fbc1bb>] VBoxSupDrvDeviceControl+0xeb/0x160 [vboxdrv] [ 157.048000] [<c0102210>] __switch_to+0xa0/0x1f0 [ 157.048000] [<c0102210>] __switch_to+0xa0/0x1f0 [ 157.048000] [<c01826e8>] do_ioctl+0x78/0x90 [ 157.048000] [<c018275c>] vfs_ioctl+0x5c/0x2a0 [ 157.048000] [<c0182a12>] sys_ioctl+0x72/0x90 [ 157.048000] [<c01031f0>] sysenter_past_esp+0x69/0xa9 [ 157.048000] [<c0102210>] __switch_to+0xa0/0x1f0 [ 157.048000] ======================= [ 157.048000] Code: ba d0 00 00 00 e8 e2 b5 00 00 85 c0 89 c5 74 d2 b9 54 00 00 00 89 da e8 50 a3 08 00 85 ff 74 45 89 75 08 8b 45 48 85 c0 74 04 90 <ff> 40 14 8b 45 40 85 c0 74 0a 8b 10 85 d2 74 04 89 e8 ff d2 85 [ 157.048000] EIP: [<c01675bf>] split_vma+0x6f/0xe0 SS:ESP 0068:f5a8fdc4 This is on Ubuntu 7.04 32-bit on an AMD64 processor, 2GB RAM, if that helps. |
|||

