I am evaluating VMWare 6 (just downloaded evaluation copy, so should be most recent. Computer is a HP xw4400 1.86Ghz Core 2 Duo with plenty of ram, etc. Host operating system is XP Pro, fairly fresh install.
I test software that communicates with a USB Device that declares itself as a Human Interface Device (HID). This device has worked robustly on everthing from 98SE to Vista with no problems, and is working fine in the host OS. I can see that when I plug it in, an XP Pro (fresh install) is being allowed to see the device, but windows declares that it's an unrecognised device. When looking at Device Manager in the Guest OS, it shows PID and UID of 0 (of course this is wrong).
Any ideas? If I cannot get this to work, then VMWare is not for me; if it can be made to work, then this would be a great solution, and a better alterantive than the multi-booting I do now to test the app under different OS's before release to the public.
If its not clear what is happening and someone is willing to help, I'd be happy to allow remote access to this PC and/or send the hardware device to someone who can help.
Thanks for listening.
\-- Scott
While we wait for VMware to help, would you try adding:
usb.generic.skipsetconfig = "true"
usb.generic.allowHID = "true"
to the .vmx file, and see if that helps.
I will try as soon as I can; but now have a new problem: today when I boot up XP, it's fine. But about 10 seconds after launching VMWare Workstation, the computer BSOD+immediate reset before I can see what the BSOD was... so, I guess I've gotta fix this first...
I added the suggested parameters under the usb.present parameter, but still same problem... Next suggestion?
\-- Scott
PS: This time VMWare ran fine, I think it has to do with something about the IDE vs Intel Matrix controller settings....
First of all, you can remove skipsetconfig from the VM's vmx file as it only applies to Linux hosts. Also, you powered off the VM and closed VMware before editing the VM's vmx config file, correct?
What is the device? Does it have any interfaces in addition to HID (say a vendor specific interface)? Could you please post any lines in the vmware.log file of the VM that contain USB, UHCI, or EHCI after trying to use the device in that VM and post them here?
Yes, I powerd off the VM and closed VMWare before editing the vmx file.
The device is a performance monitor for a rowing machine, www.concept2.com/pm3 or /pm4. In normal device manager it would show up as 2 lines (I'm not sure the reasons, but I can find out from the developer if it's important): as a "HID Compliant Device" and "USB Human Interface Device". It should be reporting a VID of 17A4 and PID of 0002 for a PM4, or 0001 for a PM3 device. Specidifially in this case, it would be reported in DeviceManager as HID\VID_17A4&PID_0002\6&1341A8FC&0&000, however in the guest OS it shows up with PID and VID of 0
The lines to the log file that were added AFTER the device was plugged in are as follows:
Aug 02 08:44:17.796: vmx| VIDE: ATAPI DMA 0x51 Failed: key 0x2, asc 0x3a, ascq 0x0
Aug 02 08:44:53.484: vcpu-0| VMMouse: CMD Read ID
Aug 02 08:44:53.484: vcpu-0| MKS switching absolute mouse on
Aug 02 08:44:58.718: usbEnum| USBGW: Autoconnecting e010002117a40002
Aug 02 08:44:58.718: usbEnum| USB: Automatically connecting virtual hub
Aug 02 08:44:58.718: usbEnum| USB: Connecting device 0xc00000010e0f0002
Aug 02 08:44:58.718: vmx| USB: Found device \[name:Dell\ Input\ Device vid:413c pid:2002 path:1/0/1/0 speed:full family:hid,hid-bootable]
Aug 02 08:44:58.718: vmx| USB: Found device \[name:Input\ Device vid:17a4 pid:0002 path:1/0/1/2 speed:full family:hid]
Aug 02 08:44:58.718: vmx| USB: Found device \[name:Microsoft\ Input\ Device vid:045e pid:0040 path:1/1/1 speed:low family:hid,hid-bootable]
Aug 02 08:44:58.718: vmx| VMXVmdbLoadUsbDevices: New set of 3 USB devices
Aug 02 08:45:04.109: vmx| USB: Found device \[name:Dell\ Input\ Device vid:413c pid:2002 path:1/0/1/0 speed:full family:hid,hid-bootable]
Aug 02 08:45:04.109: vmx| USB: Found device \[name:Input\ Device vid:17a4 pid:0002 path:1/0/1/2 speed:full family:hid]
Aug 02 08:45:04.109: vmx| USB: Found device \[name:Microsoft\ Input\ Device vid:045e pid:0040 path:1/1/1 speed:low family:hid,hid-bootable]
Aug 02 08:45:09.359: vmx| USB: Found device \[name:Dell\ Input\ Device vid:413c pid:2002 path:1/0/1/0 speed:full family:hid,hid-bootable]
Aug 02 08:45:09.359: vmx| USB: Found device \[name:Input\ Device vid:17a4 pid:0002 path:1/0/1/2 speed:full family:hid]
Aug 02 08:45:09.359: vmx| USB: Found device \[name:Microsoft\ Input\ Device vid:045e pid:0040 path:1/1/1 speed:low family:hid,hid-bootable]
And then on disconnect:
Aug 02 08:48:37.328: usbEnum| USB: Disconnecting device 0xe010002117a40002
Aug 02 08:48:37.328: vmx| USB: Found device \[name:Dell\ Input\ Device vid:413c pid:2002 path:1/0/1/0 speed:full family:hid,hid-bootable]
Aug 02 08:48:37.328: vmx| USB: Found device \[name:Microsoft\ Input\ Device vid:045e pid:0040 path:1/1/1 speed:low family:hid,hid-bootable]
Aug 02 08:48:37.328: vmx| VMXVmdbLoadUsbDevices: New set of 2 USB devices
Aug 02 08:48:39.359: vmx| USB: Found device \[name:Dell\ Input\ Device vid:413c pid:2002 path:1/0/1/0 speed:full family:hid,hid-bootable]
Aug 02 08:48:39.359: vmx| USB: Found device \[name:Microsoft\ Input\ Device vid:045e pid:0040 path:1/1/1 speed:low family:hid,hid-bootable]
In this instance the device was plugged into a Dell USB Keyboard with internal USB hub and 2 ports, hence the references to Dell. I've tried direct ports on the PC, no change there.
Thanks for the help folks, I it is very much appreciated.
So it looks like it's a pure HID device. Since it's not hid-bootable, you don't really need the allowHID line. Unfortunately, it seems as if there is some issue with this specific device and I can't think of any workaround that will help. Could you turn on Full debugging via VM->Settings->Options->Advanced->Settings->Gather debugging information and then add the line usb.analzer.enable = "true" and post all usb/uhci/ehci lines after trying the device? There will probably be more lines than can be posted here, but post as many as you can or PM me. Also, could you file a formal Service Request for this issue?
Removed the generic line you advised, here is the info from the .log file... all the information from just before to just after plugging in the USB device are below...
Aug 03 07:50:53.968: vmx| USB: Found device \[name:Input\ Device vid:17a4 pid:0002 path:1/3/1 speed:full family:hid]
Aug 03 07:50:53.968: vmx| VMXVmdbLoadUsbDevices: New set of 1 USB devices
Aug 03 07:50:55.906: mks| MKS got focus 25029a
Aug 03 07:50:56.296: vmx| USB: Found device \[name:Input\ Device vid:17a4 pid:0002 path:1/3/1 speed:full family:hid]
Aug 03 07:51:53.000: vmx| VMMEM 0 1 74688 437401 437401 491520 500958 50
Aug 03 07:51:53.000: vmx| VMMEM checked 7852 bad 0 badKey 0 badMPN 0 badCOW 0
Aug 03 07:51:53.000: vmx| COWStats: numHints 1343 unique 9 shared 992 totalUnique 26 totalBreaks 402
Aug 03 07:51:53.000: vmx| COWStats Hot Page: hash 0xbf7142bb49e776b0 count 3
Aug 03 07:51:53.000: vmx| COWStats Hot Page: hash 0x3b3fba9e840e3703 count 5
Aug 03 07:51:53.000: vmx| COWStats Hot Page: hash 0x5d5d5547019d1334 count 8
Aug 03 07:51:53.000: vmx| COWStats Hot Page: hash 0xdb48bc9019b8bce8 count 46
Aug 03 07:51:53.000: vmx| COWStats Hot Page: hash 0x2bd8e6157e6af6d6 count 922
Aug 03 07:51:53.000: vmx| VMMEM VM 0 min 50370 max 83138 share 65536 paged 73533 nonpaged 9605 locked 74679 cowed 992 usedPct 66
Aug 03 07:52:11.921: vmx| VMXVmdbLoadUsbDevices: New set of 0 USB devices
Aug 03 07:52:16.453: usbEnum| USBGW: Autoconnecting e010002117a40002
Aug 03 07:52:16.453: usbEnum| USB: Automatically connecting virtual hub
Aug 03 07:52:16.453: usbEnum| USB: Connecting device 0xc00000010e0f0002
Aug 03 07:52:16.453: vmx| USB: Found device \[name:Input\ Device vid:17a4 pid:0002 path:1/0/1/2 speed:full family:hid]
Aug 03 07:52:16.453: vmx| VMXVmdbLoadUsbDevices: New set of 1 USB devices
Aug 03 07:52:26.953: vmx| USB: Found device \[name:Input\ Device vid:17a4 pid:0002 path:1/0/1/2 speed:full family:hid]
Aug 03 07:52:32.703: vmx| USB: Found device \[name:Input\ Device vid:17a4 pid:0002 path:1/0/1/2 speed:full family:hid]
Aug 03 07:52:46.234: mks| MKS lost focus 0
Aug 03 07:52:46.234: mks| MKS starting full screen: off
Aug 03 07:52:46.234: mks| MKS already off
Aug 03 07:52:46.234: mks| MKS finished full screen: done
Actually, plugged it in twice: once to a usb port on the computer, but never saw the usb icon show up, thought it wasn't recognised, then moved it to the Dell keyboard hub... so I think that's why we see 2 instances on different USB hub ports... I hope I turned on all the items you wanted...
I have filed a Service Request with VMWare, I'm awaiting a response...
Message was edited by:
skaterdad
Message was edited by: Skaterdad
skaterdad
Any thoughts o vmware gurus?
I just realized I made a typo in the vmx line. It should be:
usb.analyzer.enable = "true"
Sorry for the mistake. Could you please try this again? Thanks.