I'm using an Ubuntu 16.04 guest on Windows 10.
I have this strange problem: all USB devices are not attached even the ones that were working fine with a filter.
The devices are captured but not attached. If I try to click on a device under "Devices->USB->" I receive a message saying that the device is busy.
Have a look at UpperFilters key at this path Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{36fc9e60-c465-11cf-8056-444553540000} in the Windows registry.
Remove the UpperFilters.
For example Wireshark setup the UpperFilters and stopped all devices from being attached to VirtualBox.
Download and install the extension pack from here: https://www.virtualbox.org/wiki/Downloads
Be sure that you are not already using that pendrive in your host or guest.
And check in "Devices->USB" if your are choosing right type (usb 1.0, 2.0, or 3.0)
Related
I used to work on my Virtual Box normally until it started giving me critical errors, so i backed up my machine and reinstalled virtualbox and loaded my backed up machine. Now i am working on a project that needs the use of the Webcam, so i use my PC's built in webcam usually. I used to enable it from the VM settings. However, now it the webcam seetings doesn't show in the devices. The photos below show the problem i am facing.
The image below shows that the webcam option is checked in the devices.
However, when i enter to enable my camera from the devices, i don't find the webcam options! (image below)
Is it recommended to reinstall my Virtual box again? If a solution couldn't be found?
The VirtualBox Extension Pack is required to allow Webcam passthrough.
Available here -
https://www.virtualbox.org/wiki/Downloads
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).
When connecting HoloLens via USB to my computer, the device portal is still not available after setting it up as explained in the install tools page.
All I get in the browser 127.0.0.1:10080 is the generic "unable to connect" page.
Is there any way to know what is failing? What could I check? Any tip will be appreciated!
EDIT: browsers used: Edge, Firefox and Chrome.
EDIT2: Hololens development mode is on.
Connecting over USB requires the PC be running IPoverUSB, which is installed with the Windows 10 SDK. You can verify that it's running by checking the Services tab of Task Manager for IpOverUsbSvc.
FYI, another resolution to this issue may be the USB port you are using.
I initially was using a USB 3 port (which I've used to flash my HoloLens many times) and had the same issues.
On a whim, I switched to an older USB2 port and it's working perfectly now. SO try different USB ports if you are having this issue.
When i start a new virtual device with genymotion sometimes it will get stuck on the black screen and not load. Sometimes it will work especially just after a restart, otherwise it will hang on the black screen and become unusable.
If the emulator freezes or crashes this is likely due to incompatability with your video card driver.
If however it just hangs on the black screen, this can be due to two reasons:
Your Firewall or other program is blocking genymotion
If this is likely the case then try disconnecting any vpn services or other software which could be hindering this, and ensuring that genymotion is able to connect to the virtual device over the local network.
If you have a firewall, make sure that you allowed connections to the Genymotion network, set to 192.168.56.0/24 by default.
Your network adaptor is misconfigured
If this is the case you should try the following
Run VirtualBox.
Open File > Preferences > Network (or VirtualBox > Preferences for Mac OS X).
Edit the Host-only Network by clicking .
Check that the adapter IPv4 address is in the same network (192.168.56.0/24 by default) as the DHCP server address, lower address bound and upper address bound. If not, your virtual device cannot start.
You can also remove the Host-only Network by clicking . Genymotion will automatically recreate it at the next virtual device start.
I had this problem in Windows 10 after I updated to VirtualBox 6.0.4 and Genymotion 3.0.1. I am using 2nd generation core i5 cpu (i5 2400). Update to this graphics card is not available. According to the official documentation:
Your graphics card no longer matches Genymotion requirements. Please see https://www.genymotion.com/help/desktop/faq/#supported-graphics-cards.
If you are using a dual graphics card laptop (e.g. Intel/Nvidia or Intel/AMD), make sure you are using the most recent/powerful one.
https://www.genymotion.com/help/desktop/faq/#virtual-device-window-empty
Only solution to my problem was keep the VirtualBox 6.0.4 but downgrade genymotion to 2.12.2 version because my graphics cards is no longer supported and only supported intel graphics card is intel hd graphics 4000 generation. Link to Genymotion 2.12.2 is below:
https://dl.genymotion.com/releases/genymotion-2.12.2/genymotion-2.12.2.exe
Following the below steps solved the issue for me.
Open Windows Settings > Network & Internet > Change adapter options
Right-click on VirtualBox Host-Only Ethernet Adapter
Select Disable
Right-click on the VirtualBox Host-Only Ethernet Adapter again and Select Enable
Press power button doesn't start until then they will stuck on android logo screen then restart
I had the same problem in Windows. updating the video card driver solved the issue.
Genymotion 3.0.1
VirtualBox 6.0.4
I solved the issue in 2 steps:
Check the Android API versions installed on your system from \SDK\platforms directory.
Create New AVD using available Android versions only.
You need to check 4 different things:
proxy connections to be off( Gennymotion/setting/Network)
SDK be set( Gennymotion/ABD/SDK)
Graphic card driver be successfully installed
Virtual box installed and working correctly
Try again please. hope you will fix it easily.
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! ;) )