i have try many solutions in internet and all solutions does not work to me. i set the usb filter of usb setting in virtual box, but it keep to pop-up error for me.
Here is the errors:
Failed to attach the USB device Ralink 54M.USB....... [0001] to the virtual machine BT5.
USB device 'Ralink 54M.USB.......' with UUID {ID} is in use by someone else.
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: HostUSBDevice
Interface: IHostUSBDevice
Callee: IConsole
can someone help me?
thank you for any suggestions.
Your extensions for Ralink are not allowing VirtualBox to attach to it. I found out that the Ralink wireless utility or the driver won't release it to the guest OS on VirtualBox. I deleted the kext (making sure I backed it up first) and rebooted. Now the VirtualBox guest OS (bt5 r3 in my case) sees it under lsusb after recompiling the driver for it, using modprobe rt5370sta, and blacklisting the other rt2x00 and rt2800.
Related
Step by step:
My PC has connected printer via USB (I know VID:XXXX and PID:YYYY)
I took image of my PC and put inside virtual machine (VMWare)
Of course image on my VM doesn't has connected USB-printer (because real printer is connected to my real USB-port on my real PC).
One program is running and checking accessibility of printer by check connection with the printer via USB (I don't know how exactly - maybe via WMI, maybe via other way).
Results:
a) on my real PC this program works
b) on image doesn't work
QUESTION: is possible to emulate on VM-side that USB-port (VID:XXXX and PID:YYYY) is alive?
Thanks.
P.S. I don't want to install USB-redirect-via-TCP or similar approach.
You should switch to the QEMU emulator and to Linux to do that. VMWare probably doesn't support this of thing especially in a Windows environment.
If you are already on Linux, QEMU has hardware emulation of the xHCI and you can assign the host USB devices to KVM (read here: https://www.linux-kvm.org/page/USB_Host_Device_Assigned_to_Guest).
On Windows, I don't think this will be possible.
USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
The problem was described here - https://communities.vmware.com/thread/612551
but anyone has no answer for it.
Generally, the problem is like so:
launch vm
connect usb stick or usb phone cable
vm freezes
it is not possible to terminate vmware-vmx.exe process (even as a SYSTEM user with highest privs).
The issue occurs on vmware workstation 14 & 15 on Windows 10 Pro Build 1903
Also tried disabling windows defender (maybe some strange scan policy) but no results.
Tried also to change almost every setting in workstation but no results...
please help
I was facing exactly the same issue and I have finally found the solution.
Update to VMWare Workstation version 15.5. Update the VM Tools in the Guest operating System, and it works!! Tried with Android Devices, in USB Tethering Mode also.
I've created a virtualbox via docker-machine:
$ docker-machine create --driver virtualbox default
Within the Guest-OS I'd like to access my USB-Serial device, which is a Nordic nRF52840 DevKit, which is listed in macos as /dev/tty.usbmodem144241.
However, this device is not listed as USB device by virtualbox. I've also tried adding the devices as a Serial Port with the Port Mode "Host-Device" as described in this link, but without any success:
If I add the Serial Port as .tty-usbmodem the virtualbox will hang in 'Starting', I have to kill all virtualbox processes or disconnect the serial cable in order to start again. If I use .cu-usbmodem the virtualbox starts up but immediately crashes.
I'm running out of ideas here. I'm stuck at this issues since docker for mac does not support the --devices mapping without virtual machine, and for the virtual machine I somehow can't manage to add the port.
Any ideas on what else I could try?
So as it turns out virtualbox is quite picky about when a device is actually connected and does not work as seamlessly as I'm used from using VMWare:
The device I was using really just shows up as SEGGER J-Link in the USB menu
It must be added as filter (filter is really confusing > first I thought it would ignore the device)
The device cannot be added to the virtualbox 'on the fly' (using the USB-icon in the 'Show' window, see screenshot), it must not be connected before the virtualbox starts up.
The serial-tab is irrelevant > it's all handled via the USB tab.
The important fact is that the device must not be connected wenn the virtualbox fires up. So the steps to add a device are the following:
Power down the virtualbox
Make sure the USB controller is enabled
Connect the USB/serial device to the computer (host)
Add it to the filter in the virtual box
Now every time you want to use the device with the virtualbox:
Make sure the virtualbox is down (e.g. docker-machine stop default)
Disconnect the USB/serial device from the computer
Start up the virtualbox (e.g., docker-machine start default)
Virtualbox should now be able to "intercept" the device and list it under /dev, e.g., as /dev/ttyACM0
Un-/Plugging a filtered device once the box is up also works (you don't have to power down the virtualbox again if you forgot to disconnect the device before starting it up. Just wait for the box to be up, unplug, plug in, should be good).
First of all, there's a similar thread on OpenQNX posted years ago but the solutions don't really apply for me.
Having said that, I want to create an OS image of QNX 6.6.0 to put on a Compact Flash card. This card is plugged in an USB adapter which is connected to my host pc. I'm running Neutrino in a VM (VMware/VirtualBox) for which I enabled USB support. Generally, the adapter works fine under Win (current host) and Linux.
The (apparently out-dated) tutorial I was following stated to search for devices named umass* or hd* after connecting the USB adapter. But there aren't any (except for hd0).
See also "ls /dev" screenshot.
The processes devb-umass and io-usb are running. So I expect that the adapter is detected automatically.
Any suggestions what went wrong?
OK, it seems that I had to restart the usb driver 'devb-umass' (several times). When the card reader is already plugged-in during the booting the driver will not detect it autoamtically. Thus one has to unplug and plug it in again after the devb-umass was getting re-started. It also might have been that the Host Controller Driver (HCD) was set to 'ohci' instead of 'ehci'.
Everything is working now as expected.
(Thanks Tim from the OpenQNX forum! ;) )
I up the Centos image using VirtualBox ,clone image and convert it into Qcow2 format and tried up using Virt-manager. But i found interface not available in VM.
It displays
"Bringing up interface eth0: Device eth0 does not seems to be present,"
I also tried removing the presistance rules , chkconfig network on and rebooting VM.
But could not able to achieving the interface in VM.
Please advice me with any ideas.
This issue was due to NIC Device model ,
Base machine NIC driver was e1000 and VM it was set as rtl8139. Beacuse of which eth ports are not displayed.
Once i changed to correct e1000 driver. it works.
New learning. Things that can be added into checklist. :)