VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (802 - 804 of 16363)

Ticket Resolution Summary Owner Reporter
#823 fixed Keil ULINK USB device not usable. rasasi
Description

Linux host, Windows target. I plug this device with usb id c251:2710, I changed the whole /proc/bus/usb to owner the user running vbox. I removed all the filter but on the usb devices list available this device appeared as uknown and grayed where on previous vbox versions, the device was perfectly usable.

Someone at the #vbox channel suggested me that there could be a problem in the parser for the usb devices causing thus the problem.

I'm attaching the /proc/bus/usb/devices

Thanks.

#824 fixed The VirtualBoxservice.exe uses 100% CPU in the Windows 2000Pro or XP Pro guest VM -> Fixed in 1.5.4 Ralf
Description

I had created a Windows 2000Pro and Windows XP Pro guest VM under a Windows XP Pro host - using VirtualBox 1.5.0

When VirtualBox 1.5.2 came out I uninstalled VirtualBox 1.5.0 - installed VirtualBox 1.5.2. Than I uninstalled the Guest Additions 1.5.0 in the guest and installed the guest additions 1.5.2.

Now I have the problem that often - not always - my CPU usage is 100% assigned to the VirtualBoxservice.exe in the guest system! Shocked

You can shut down the service and the guest still works but with normal CPU usage OR ...

Open the Services from the Windows Configuration in the guest, scroll through the list, close it again and suddenly the CPU load for the VirtualBoxservice.exe goes down to a normal level again. Strange behaviour Evil or Very Mad

But chances are still hight that CPU usage reaches again 100% later on.

I posted this in the forum first and so far at least one other user can confirm this.

#825 worksforme VERR_VM_DRIVER_VERSION_MISMATCH on start jim spurlin
Description

i have a dell core duo latptop m90 with several version of linux installed.

when i try to start a new/first windows session.

The VirtualBox support driver which is running is from a different version of VirtualBox. You can correct this by stopping all running instances of VirtualBox and reinstalling the software.. VBox status code: -1912 (VERR_VM_DRIVER_VERSION_MISMATCH).

[root@localhost ~]# find /lib/modules -name vboxdrv*
/lib/modules/2.6.22.5-76.fc7/misc/vboxdrv.ko
/lib/modules/2.6.22.9-91.fc7/misc/vboxdrv.ko
/lib/modules/2.6.22.7-85.fc7/misc/vboxdrv.ko

[root@localhost ~]# /etc/init.d/vboxdrv setup
Stopping VirtualBox kernel module                          [  OK  ]
Recompiling VirtualBox kernel module                       [  OK  ]
Starting VirtualBox kernel module                          [  OK  ]
[root@localhost ~]# VirtualBox &

 modprobe -l vbox*

/lib/modules/2.6.22.5-76.fc7/misc/vboxdrv.ko

help? what next or what am i doing wrong?

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