Key = "Misc.UsbArbitratorAutoStartDisabled", To check the state: vim-cmd hostsvc/advopt/view Misc.UsbArbitratorAutoStartDisabled You might have guessed the reason: It’s because the service started again and claimed those USB device.įor a permanent and reboot-proof solution, you can disable the UsbArbitrator service from starting with ESXi: vim-cmd hostsvc/advopt/update Misc.UsbArbitratorAutoStartDisabled int 1 After the reboot you would see the storage device as being "Dead" and not accessible. Very important to note: The service usbarbitrator starts when rebooting the ESXi host. Then you’re able to create a datastore on it as you would do on any other storage device. To temporarily workaround this, it’s possible to stop this service by using: /etc/init.d/usbarbitrator stopĪfter re-plugging in the USB device, you should finally see the storage device. You should not use datastores on USB devices in production. Just to be very clear: This is NOT officially supported by VMware. OR having the ability to passthrough USB devices to VMs.This is (one of) the reason you won’t see USB sticks as "Storage Devices" on your ESXi, therefore not allowing you to create a datastore on it.īut at this point you have to make a decision, as you can’t have both:
When attaching any kind of USB devices, the service usbarbitrator claims those devices to allow passing through USB devices into virtual machines. This post was published 1 year 11 months 28 days ago, so the post may be outdated.
0 kommentar(er)
