- Local time
- 4:02 PM
- Posts
- 2,874
- Location
- Hafnarfjörður IS
- OS
- Windows XP,7,10,11 Linux Arch Linux
Hi folks
It seems (at least I can't make it work) when using VMWare to create a VM on a Physical disk then somehow this interferes with the USB arbitration service and you can't "dynamically" attach externally connected USB devices. You can set them up of course in the VM config but a lot of the flexibility is lost if you can't dynamically attach / detach devices after boot.
(If the boot disk is not a physical disk and you have other physical disks attached then it all works normally).
I'm not sure if this problem occurs on VBOX (any users of that I'd be grateful if they have found a similar problem). The other issue might be because the physical disk I'm creating the VM on is itself on an external SSD attached to the host - whether that's an issue also I don't know.
One reason I want to use a "physical disk" is for a Linux VM to be able to use the f2fs file system which was specifically written for nvme and ssd type devices -- however I also get the same issue when trying Windows VM's -- the HOST is W11 build 22518.1012.
Cheers
jimbo
It seems (at least I can't make it work) when using VMWare to create a VM on a Physical disk then somehow this interferes with the USB arbitration service and you can't "dynamically" attach externally connected USB devices. You can set them up of course in the VM config but a lot of the flexibility is lost if you can't dynamically attach / detach devices after boot.
(If the boot disk is not a physical disk and you have other physical disks attached then it all works normally).
I'm not sure if this problem occurs on VBOX (any users of that I'd be grateful if they have found a similar problem). The other issue might be because the physical disk I'm creating the VM on is itself on an external SSD attached to the host - whether that's an issue also I don't know.
One reason I want to use a "physical disk" is for a Linux VM to be able to use the f2fs file system which was specifically written for nvme and ssd type devices -- however I also get the same issue when trying Windows VM's -- the HOST is W11 build 22518.1012.
Cheers
jimbo
My Computer
System One
-
- OS
- Windows XP,7,10,11 Linux Arch Linux
- Computer type
- PC/Desktop
- CPU
- 2 X Intel i7
