Hi! I was trying to use Blackberry Desktop under Windows XP under a QEMU virtual machine under Linux.

My problem is that the device is recognized as device id 0fca:0006 and after some seconds it switch to 0fca:0004 . So when I make a "usb_add host:0fca:0006" QEMU lose my request and if I try to make a "usb_add host:0fca:004" the system forever wait something with the CPU at 100%.

Someone have successful experience?

I'll try with a USB bluetooth dongle to bypass the USB interface... i hope that this will help...

Wow, what a cool idea. I've not done it, but I can help with details I've learned from barry/bcharge that seem to be affecting you and maybe will help.

The change from 0006 -> 0004 is how the device works by design, it's the Desktop software sending a special USB message to the device to switch modes. 0006 is USB Mass Storage only - the default it will stay at with no Desktop software (well, really the USB drivers portion of it) or under regular Linux or Mac. The 0004 interface is a special dual mode; it has 4 'endpoints', supporting *both* Mass Storage and the control channel at the same time. (mode 0001 is control channel only).

It makes sense why 0006 is failing -- as soon as you plug in the device the USB drivers tell it to switch to 0004 mode; the only way you can stop this is to uninstall the BB Desktop/drivers software. :-/

It *sounds* like when you try and add the usb_host to 0004 it's trying to bind to the wrong endpoints - I'm not sure which ones it's after, but I'm guessing you want to bind the control channels, not the usb mass storage channels. Is there any way you can debug the usb_add command (strace, etc.) to see why it's pegging the CPU @ 100%?

ps: after plugging in the device, did you run "rmmod usb_storage" in linux before trying to use usb_add commands for QEMU?

I probably found where is the mistake. I use qemu 0.9.0 of debian unstable.
With the tree version: if I try to add the BB 004 or another USB bluetooth dongle the cli say:
"Could not add UBS device 'host....'
and in the logs
"usb_host: only one interface supported"
This happen because qemu does not support usb multiple interface... (this is what i understood) so I patched with [Qemu-devel] USB Multiple interface devices .
With this patch i have the result reported in my opening thread and i have the SAME effect with the usb bluetooth dongle (after 10 hours of driver recognition no ending...)

So I think that is not a BB throuble but a USB - QEMU problem.

Ever tried innotek virtualbox? I can plug my blackberry in and it's recognized as so. Just can't get the desktop manager to see it as of yet though. I'm using version 1.5

Hey,

funny to see that some other had the same problem as I am before ;)

Did someone found a solution for it? I'm using KVM with a patched QEMU (kvm-67 from 28th april this year) but on usb_add commando my guest (32 bit Vista Business on a 64 multilib Linux with 2.6.25 vanilla Kernel) is hanging until I remove the device with usb_del.

I need a solution to sync my BB with my Windows After solving this problem I can delete my native Windows installation and put the space to my penguin :P


Regards

Bingo! The bluetooth USB dongle worked like a charm! I'm using XP SP2 installed on VirtualBox on Ubuntu Hardy Heron.