I ran across this and glad I did...saved my .10 worth of sanity I got left:
It came from: http://kb.vmware.com/KanisaPlatform/Publishing/612/774_f.SAL_Public.html
Guest Cannot See USB Device on RHEL4-x64 Host
This problem was identified on VMware Server, but may affect other VMware products.
When you connect a USB device to a host running the RHEL4-x64 operating system, then try to access the USB from the VMware guest, the following error message appears: The Existing driver (usbhid) could not be successfully disconnected. (operation not permitted) Unload the driver manually then try again <OK>.
In this situation, you cannot unload the driver manually from the host, because it does not exist as a module—it is compiled directly into the RHEL4-x64 kernel. Normally, this situation is not a problem for VMware software, but the kernel does not support the required ioctl (control device) function to allow VMware to disconnect the device from the usbhid driver.
As a workaround, you can recompile the host's kernel with usbhid as a module, then manage its removal with rmmod. However, because the usbhid driver is necessary to allow the host and guest operating systems to interact with a USB mouse and keyboard, removing the module from the recompiled kernel may not be appropriate for your system. You may need to use an upgraded kernel or a different operating system instead.
thx
John Rose
On Fri, 2006-09-22 at 00:39 -0500, rado wrote:
I ran across this and glad I did...saved my .10 worth of sanity I got left:
It came from: http://kb.vmware.com/KanisaPlatform/Publishing/612/774_f.SAL_Public.html
Guest Cannot See USB Device on RHEL4-x64 Host
<snip>
As a workaround, you can recompile the host's kernel with usbhid as a module, then manage its removal with rmmod. However, because the usbhid driver is necessary to allow the host and guest operating systems to interact with a USB mouse and keyboard, removing the module from the recompiled kernel may not be appropriate for your system. You may need to use an upgraded kernel or a different operating system instead.
John, I've not used VM stuff, so this might be dumb (never stopped me yet).
Can't the initrd be modified and remade to automatically load the modules? It's just another device driver, right?
thx
John Rose
<snip sig stuff>
-- Bill
On Fri, 2006-09-22 at 08:54 -0400, William L. Maltby wrote:
On Fri, 2006-09-22 at 00:39 -0500, rado wrote:
I ran across this and glad I did...saved my .10 worth of sanity I got left:
It came from: http://kb.vmware.com/KanisaPlatform/Publishing/612/774_f.SAL_Public.html
Guest Cannot See USB Device on RHEL4-x64 Host
<snip>
As a workaround, you can recompile the host's kernel with usbhid as a module, then manage its removal with rmmod. However, because the usbhid driver is necessary to allow the host and guest operating systems to interact with a USB mouse and keyboard, removing the module from the recompiled kernel may not be appropriate for your system. You may need to use an upgraded kernel or a different operating system instead.
John, I've not used VM stuff, so this might be dumb (never stopped me yet).
Can't the initrd be modified and remade to automatically load the modules? It's just another device driver, right? Bill
oh, I found that bit in some knowledge base after letting this certain problem beat me up for a spell. Since, I just set up to host a print server from a real(base) OS, run a smb host and handle the vm -windows OS printing needs so this is a dun deal on my end.
It seems like printing is one of those things where there are many diff ways to accomplish the same task.
I sure don't want this little misfortune of the rhel kernel to be led into a path that we all endured the last few days w/the selinux thang...
Just be aware of that so as not to waste a bunch of time on it. Just find a better way to do it.
John Rose
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sep 22, 2006, at 7:51 PM, rado wrote:
On Fri, 2006-09-22 at 08:54 -0400, William L. Maltby wrote:
On Fri, 2006-09-22 at 00:39 -0500, rado wrote:
<snip>
oh, I found that bit in some knowledge base after letting this certain problem beat me up for a spell. Since, I just set up to host a print server from a real(base) OS, run a smb host and handle the vm -windows OS printing needs so this is a dun deal on my end.
It seems like printing is one of those things where there are many diff ways to accomplish the same task.
I sure don't want this little misfortune of the rhel kernel to be led into a path that we all endured the last few days w/the selinux thang...
Just be aware of that so as not to waste a bunch of time on it. Just find a better way to do it.
John Rose
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
maybe this is not directly related to your problem - but i noticed a problem also related to usb devices and vmware.
in my case i'm running vmware server 1.0.1-build-29996 on centos 4 x86_64 2.6.9-34.0.2.ELsmp kernel on a dell poweredge 1855 blade.
after removing virtual usb hub device from the win2003 std. server guest i could not see any usb device on the host anymore while it was still visible in /proc/bus/usb/devices. fdisk -l shows up nothing. what solved my little problem here was to rmmod the usb_storage module and modprobe it afterwards. maybe this can help somebody...
regards, carsten
- -- 0803 18A7 4828 D4AB B1D9 AB47 98D4 7B78 B8BD 6FF2
-
Carsten Probst -
rado -
William L. Maltby