Hi All,
Fedora 31 qemu-kvm-4.1.0-5.fc31.x86_64
If I have a virtual machine running and I insert a flash drive into a USB socket, the virtual machine steels the flash drive from the host, not that it will actually work in the VM, which they don't. To get them to work in my VM's I have to add them as a piece of hardware to my configuration, then they work.
I have to exit all my VM's to be able to see my flash drives again from the hosts system (FC31). This is a pain in the neck.
Any way around this?
Many thanks, -T
On Wed, 13 Nov 2019 at 20:52, Todd Chester via users < users@lists.fedoraproject.org> wrote:
Hi All,
Fedora 31 qemu-kvm-4.1.0-5.fc31.x86_64
If I have a virtual machine running and I insert a flash drive into a USB socket, the virtual machine steels the flash drive from the host, not that it will actually work in the VM, which they don't. To get them to work in my VM's I have to add them as a piece of hardware to my configuration, then they work.
I have to exit all my VM's to be able to see my flash drives again from the hosts system (FC31). This is a pain in the neck.
Any way around this?
Has the USB controller been assigned as a PCI device to the VM? If so it would be detached from the host machine.
Many thanks, -T _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 11/14/19 8:51 AM, Todd Chester via users wrote:
Fedora 31 qemu-kvm-4.1.0-5.fc31.x86_64
If I have a virtual machine running and I insert a flash drive into a USB socket, the virtual machine steels the flash drive from the host, not that it will actually work in the VM, which they don't. To get them to work in my VM's I have to add them as a piece of hardware to my configuration, then they work.
I have to exit all my VM's to be able to see my flash drives again from the hosts system (FC31). This is a pain in the neck.
Any way around this?
If you are using the Virtual Machine Manager?
On the top Menu select "Virtual Machine--->Redirect USB Device" and uncheck the flash drive in question to release it and return it to the host system.
On 11/14/19 8:51 AM, Todd Chester via users wrote:
Hi All,
Fedora 31 qemu-kvm-4.1.0-5.fc31.x86_64
If I have a virtual machine running and I insert a flash drive into a USB socket, the virtual machine steels the flash drive from the host, not that it will actually work in the VM, which they don't. To get them to work in my VM's I have to add them as a piece of hardware to my configuration, then they work.
Oh, BTW, I forgot to add that I just installed an F31 system under qemu and I didn't have to do anything to use a flash drive in the VM. The host system is also F31.
Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/fedora_localhost--live-root 28683172 5907560 21295524 22% / /dev/vda1 999320 217372 713136 24% /boot /dev/sda1 123569632 2471936 121097696 3% /run/media/egreshko/FLASH
The USB drive happens to have been labeled "FLASH" and was auto mounted by GNOME.
[egreshko@f31gq ~]$ ll /run/media/egreshko/FLASH/ total 32 drwxr-xr-x. 2 egreshko egreshko 32768 Jun 20 20:33 HPSCANS
On 11/13/19 5:54 PM, Ed Greshko wrote:
On 11/14/19 8:51 AM, Todd Chester via users wrote:
Fedora 31 qemu-kvm-4.1.0-5.fc31.x86_64
If I have a virtual machine running and I insert a flash drive into a USB socket, the virtual machine steels the flash drive from the host, not that it will actually work in the VM, which they don't. To get them to work in my VM's I have to add them as a piece of hardware to my configuration, then they work.
I have to exit all my VM's to be able to see my flash drives again from the hosts system (FC31). This is a pain in the neck.
Any way around this?
If you are using the Virtual Machine Manager?
Yes
On the top Menu select "Virtual Machine--->Redirect USB Device" and uncheck the flash drive in question to release it and return it to the host system.
I did. It does not work.
:'(
On 11/13/19 8:05 PM, Ed Greshko wrote:
On 11/14/19 8:51 AM, Todd Chester via users wrote:
Hi All,
Fedora 31 qemu-kvm-4.1.0-5.fc31.x86_64
If I have a virtual machine running and I insert a flash drive into a USB socket, the virtual machine steels the flash drive from the host, not that it will actually work in the VM, which they don't. To get them to work in my VM's I have to add them as a piece of hardware to my configuration, then they work.
Oh, BTW, I forgot to add that I just installed an F31 system under qemu and I didn't have to do anything to use a flash drive in the VM. The host system is also F31.
Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/fedora_localhost--live-root 28683172 5907560 21295524 22% / /dev/vda1 999320 217372 713136 24% /boot /dev/sda1 123569632 2471936 121097696 3% /run/media/egreshko/FLASH
The USB drive happens to have been labeled "FLASH" and was auto mounted by GNOME.
[egreshko@f31gq ~]$ ll /run/media/egreshko/FLASH/ total 32 drwxr-xr-x. 2 egreshko egreshko 32768 Jun 20 20:33 HPSCANS
The only way I can get a flash drive to actually work in my VM's is to add it as a piece of hardware in the manager (and reboot the VM).
On 11/13/19 5:22 PM, George N. White III wrote:
On Wed, 13 Nov 2019 at 20:52, Todd Chester via users <users@lists.fedoraproject.org mailto:users@lists.fedoraproject.org> wrote:
Hi All, Fedora 31 qemu-kvm-4.1.0-5.fc31.x86_64 If I have a virtual machine running and I insert a flash drive into a USB socket, the virtual machine steels the flash drive from the host, not that it will actually work in the VM, which they don't. To get them to work in my VM's I have to add them as a piece of hardware to my configuration, then they work. I have to exit all my VM's to be able to see my flash drives again from the hosts system (FC31). This is a pain in the neck. Any way around this?Has the USB controller been assigned as a PCI device to the VM? If so it would be detached from the host machine.
It just says USB Controller. I will look more closely tomorrow to see if there is anything like that.
On 11/14/19 12:31 PM, Todd Chester via users wrote:
On 11/13/19 5:54 PM, Ed Greshko wrote:
On 11/14/19 8:51 AM, Todd Chester via users wrote:
Fedora 31 qemu-kvm-4.1.0-5.fc31.x86_64
If I have a virtual machine running and I insert a flash drive into a USB socket, the virtual machine steels the flash drive from the host, not that it will actually work in the VM, which they don't. To get them to work in my VM's I have to add them as a piece of hardware to my configuration, then they work.
I have to exit all my VM's to be able to see my flash drives again from the hosts system (FC31). This is a pain in the neck.
Any way around this?
If you are using the Virtual Machine Manager?
Yes
On the top Menu select "Virtual Machine--->Redirect USB Device" and uncheck the flash drive in question to release it and return it to the host system.
I did. It does not work.
:'(
Well, it works fine for me here on multiple hosts.
If you want to keep the guest from grabbing the USB device you could always remove the USB Redirect from the HW in the guest.
On 11/14/19 12:33 PM, Todd Chester via users wrote:
On 11/13/19 8:05 PM, Ed Greshko wrote:
On 11/14/19 8:51 AM, Todd Chester via users wrote:
Hi All,
Fedora 31 qemu-kvm-4.1.0-5.fc31.x86_64
If I have a virtual machine running and I insert a flash drive into a USB socket, the virtual machine steels the flash drive from the host, not that it will actually work in the VM, which they don't. To get them to work in my VM's I have to add them as a piece of hardware to my configuration, then they work.
Oh, BTW, I forgot to add that I just installed an F31 system under qemu and I didn't have to do anything to use a flash drive in the VM. The host system is also F31.
Filesystem 1K-blocks Used Available Use% Mounted on /dev/mapper/fedora_localhost--live-root 28683172 5907560 21295524 22% / /dev/vda1 999320 217372 713136 24% /boot /dev/sda1 123569632 2471936 121097696 3% /run/media/egreshko/FLASH
The USB drive happens to have been labeled "FLASH" and was auto mounted by GNOME.
[egreshko@f31gq ~]$ ll /run/media/egreshko/FLASH/ total 32 drwxr-xr-x. 2 egreshko egreshko 32768 Jun 20 20:33 HPSCANS
The only way I can get a flash drive to actually work in my VM's is to add it as a piece of hardware in the manager (and reboot the VM).
No need here.
Maybe something odd in your machine's xml definition.
On 11/13/19 8:55 PM, Ed Greshko wrote:
On 11/14/19 12:31 PM, Todd Chester via users wrote:
On 11/13/19 5:54 PM, Ed Greshko wrote:
On 11/14/19 8:51 AM, Todd Chester via users wrote:
Fedora 31 qemu-kvm-4.1.0-5.fc31.x86_64
If I have a virtual machine running and I insert a flash drive into a USB socket, the virtual machine steels the flash drive from the host, not that it will actually work in the VM, which they don't. To get them to work in my VM's I have to add them as a piece of hardware to my configuration, then they work.
I have to exit all my VM's to be able to see my flash drives again from the hosts system (FC31). This is a pain in the neck.
Any way around this?
If you are using the Virtual Machine Manager?
Yes
On the top Menu select "Virtual Machine--->Redirect USB Device" and uncheck the flash drive in question to release it and return it to the host system.
I did. It does not work.
:'(
Well, it works fine for me here on multiple hosts.
If you want to keep the guest from grabbing the USB device you could always remove the USB Redirect from the HW in the guest.
Any of your VM's Windows 7 Pro or Windows 10 Pro?
On 11/14/19 2:30 PM, Todd Chester via users wrote:
On 11/13/19 8:55 PM, Ed Greshko wrote:
On 11/14/19 12:31 PM, Todd Chester via users wrote:
On 11/13/19 5:54 PM, Ed Greshko wrote:
On 11/14/19 8:51 AM, Todd Chester via users wrote:
Fedora 31 qemu-kvm-4.1.0-5.fc31.x86_64
If I have a virtual machine running and I insert a flash drive into a USB socket, the virtual machine steels the flash drive from the host, not that it will actually work in the VM, which they don't. To get them to work in my VM's I have to add them as a piece of hardware to my configuration, then they work.
I have to exit all my VM's to be able to see my flash drives again from the hosts system (FC31). This is a pain in the neck.
Any way around this?
If you are using the Virtual Machine Manager?
Yes
On the top Menu select "Virtual Machine--->Redirect USB Device" and uncheck the flash drive in question to release it and return it to the host system.
I did. It does not work.
:'(
Well, it works fine for me here on multiple hosts.
If you want to keep the guest from grabbing the USB device you could always remove the USB Redirect from the HW in the guest.
Any of your VM's Windows 7 Pro or Windows 10 Pro?
No, but that shouldn't make a difference. It would be HW level. What HW is presented to the guest.
I do have a Win10 iso if I have time I'll install to see if this does make a difference.
On 11/14/19 2:43 PM, Ed Greshko wrote:
No, but that shouldn't make a difference. It would be HW level. What HW is presented to the guest.
I do have a Win10 iso if I have time I'll install to see if this does make a difference.
OK, it didn't take long and I did have the time.
Installed Win10-Pro. Works the same as with an F31 guest.
Plug in the flash drive and the guest grabs it. Uncheck the drive from the Redirect menu and the guest releases it.
On 11/13/19 10:56 PM, Ed Greshko wrote:
On 11/14/19 2:43 PM, Ed Greshko wrote:
No, but that shouldn't make a difference. It would be HW level. What HW is presented to the guest.
I do have a Win10 iso if I have time I'll install to see if this does make a difference.
OK, it didn't take long and I did have the time.
Installed Win10-Pro. Works the same as with an F31 guest.
Plug in the flash drive and the guest grabs it. Uncheck the drive from the Redirect menu and the guest releases it.
Would you fire up your 10 VM, do a ps on it, and copy and paste me the run line?
On 11/14/19 3:03 PM, Todd Chester via users wrote:
On 11/13/19 10:56 PM, Ed Greshko wrote:
On 11/14/19 2:43 PM, Ed Greshko wrote:
No, but that shouldn't make a difference. It would be HW level. What HW is presented to the guest.
I do have a Win10 iso if I have time I'll install to see if this does make a difference.
OK, it didn't take long and I did have the time.
Installed Win10-Pro. Works the same as with an F31 guest.
Plug in the flash drive and the guest grabs it. Uncheck the drive from the Redirect menu and the guest releases it.
Would you fire up your 10 VM, do a ps on it, and copy and paste me the run line?
qemu 61702 1 98 14:47 ? 00:17:29 /usr/bin/qemu-system-x86_64 -name guest=win10,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-win10/master-key.aes -machine pc-q35-4.1,accel=kvm,usb=off,vmport=off,dump-guest-core=off -cpu Nehalem-IBRS,vme=on,vmx=on,x2apic=on,tsc-deadline=on,hypervisor=on,arat=on,tsc-adjust=on,umip=on,stibp=on,arch-capabilities=on,ssbd=on,rdtscp=on,skip-l1dfl-vmentry=on,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff -m 4096 -overcommit mem-lock=off -smp 2,sockets=2,cores=1,threads=1 -uuid b50c7539-161a-40fb-b6a3-2dcfba8e6926 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=36,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global ICH9-LPC.disable_s3=1 -global ICH9-LPC.disable_s4=1 -boot strict=on -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.2,addr=0x0 -device virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 -drive file=/var/lib/libvirt/images/win10.qcow2,format=qcow2,if=none,id=drive-sata0-0-0 -device ide-hd,bus=ide.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 -drive file=/syntegra/linux-releases/MicroSoft/Win10_1607_English_x64.iso,format=raw,if=none,id=drive-sata0-0-1,readonly=on -device ide-cd,bus=ide.1,drive=drive-sata0-0-1,id=sata0-0-1 -netdev tap,fd=38,id=hostnet0 -device e1000e,netdev=hostnet0,id=net0,mac=52:54:00:24:a0:ea,bus=pci.1,addr=0x0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -spice port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 -device ich9-intel-hda,id=sound0,bus=pcie.0,addr=0x1b -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on
On 11/13/19 11:06 PM, Ed Greshko wrote:
On 11/14/19 3:03 PM, Todd Chester via users wrote:
On 11/13/19 10:56 PM, Ed Greshko wrote:
On 11/14/19 2:43 PM, Ed Greshko wrote:
No, but that shouldn't make a difference. It would be HW level. What HW is presented to the guest.
I do have a Win10 iso if I have time I'll install to see if this does make a difference.
OK, it didn't take long and I did have the time.
Installed Win10-Pro. Works the same as with an F31 guest.
Plug in the flash drive and the guest grabs it. Uncheck the drive from the Redirect menu and the guest releases it.
Would you fire up your 10 VM, do a ps on it, and copy and paste me the run line?
qemu 61702 1 98 14:47 ? 00:17:29 /usr/bin/qemu-system-x86_64 -name guest=win10,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-win10/master-key.aes -machine pc-q35-4.1,accel=kvm,usb=off,vmport=off,dump-guest-core=off -cpu Nehalem-IBRS,vme=on,vmx=on,x2apic=on,tsc-deadline=on,hypervisor=on,arat=on,tsc-adjust=on,umip=on,stibp=on,arch-capabilities=on,ssbd=on,rdtscp=on,skip-l1dfl-vmentry=on,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff -m 4096 -overcommit mem-lock=off -smp 2,sockets=2,cores=1,threads=1 -uuid b50c7539-161a-40fb-b6a3-2dcfba8e6926 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=36,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global ICH9-LPC.disable_s3=1 -global ICH9-LPC.disable_s4=1 -boot strict=on -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.2,addr=0x0 -device virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 -drive file=/var/lib/libvirt/images/win10.qcow2,format=qcow2,if=none,id=drive-sata0-0-0 -device ide-hd,bus=ide.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 -drive file=/syntegra/linux-releases/MicroSoft/Win10_1607_English_x64.iso,format=raw,if=none,id=drive-sata0-0-1,readonly=on -device ide-cd,bus=ide.1,drive=drive-sata0-0-1,id=sata0-0-1 -netdev tap,fd=38,id=hostnet0 -device e1000e,netdev=hostnet0,id=net0,mac=52:54:00:24:a0:ea,bus=pci.1,addr=0x0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -spice port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 -device ich9-intel-hda,id=sound0,bus=pcie.0,addr=0x1b -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on
Thank you!
When I get some office time on Friday, I will do a side by comparison of yours vs mine. Bet I did something dumb.
On 11/13/19 5:22 PM, George N. White III wrote:
Has the USB controller been assigned as a PCI device to the VM? If so it would be detached from the host machine.
Controller USB 0 Controller: Type USB; Model USB2 XML: <controller type="usb" index="0" model="ich9-ehci1"> <address type="pci" domain="0x0000" bus="0x00" slot="0x05" function="0x7"/> </controller>
On Thu, 14 Nov 2019 at 12:28, ToddAndMargo via users < users@lists.fedoraproject.org> wrote:
On 11/13/19 5:22 PM, George N. White III wrote:
Has the USB controller been assigned as a PCI device to the VM? If so it would be detached from the host machine.
Controller USB 0 Controller: Type USB; Model USB2 XML: <controller type="usb" index="0" model="ich9-ehci1"> <address type="pci" domain="0x0000" bus="0x00" slot="0x05" function="0x7"/> </controller>
I think this indicates that the USB controller is managed as a PCI device, but it has been a few years since I looked at this.
I found https://libvirt.org/formatdomain.html#elementsHostDev:
"For PCI devices, when managed is "yes" it is detached from the host before being passed on to the guest and reattached to the host after the guest exits. If managed is omitted or "no", the user is responsible to call virNodeDeviceDetachFlags (or virsh nodedev-detach before starting the guest or hot-plugging the device and virNodeDeviceReAttach (or virsh nodedev-reattach) after hot-unplug or stopping the guest."
Since managed is omitted, it seems the automatic detach/reattach should not be done.
https://libvirt.org/formatdomain.html says: "Controllers https://libvirt.org/formatdomain.html#elementsControllers
Depending on the guest architecture, some device buses can appear more than once, with a group of virtual devices tied to a virtual controller. Normally, libvirt can automatically infer such controllers without requiring explicit XML markup, but sometimes it is necessary to provide an explicit controller element, notably when planning the PCI topology https://libvirt.org/pci-hotplug.html for guests where device hotplug is expected."
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
On 11/14/19 9:55 AM, George N. White III wrote:
On Thu, 14 Nov 2019 at 12:28, ToddAndMargo via users <users@lists.fedoraproject.org mailto:users@lists.fedoraproject.org> wrote:
On 11/13/19 5:22 PM, George N. White III wrote: > Has the USB controller been assigned as a PCI device to the VM? If so > it would be > detached from the host machine. Controller USB 0 Controller: Type USB; Model USB2 XML: <controller type="usb" index="0" model="ich9-ehci1"> <address type="pci" domain="0x0000" bus="0x00" slot="0x05" function="0x7"/> </controller>I think this indicates that the USB controller is managed as a PCI device, but it has been a few years since I looked at this.
I found https://libvirt.org/formatdomain.html#elementsHostDev:
"For PCI devices, when |managed| is "yes" it is detached from the host before being passed on to the guest and reattached to the host after the guest exits. If |managed| is omitted or "no", the user is responsible to call |virNodeDeviceDetachFlags| (or |virsh nodedev-detach| before starting the guest or hot-plugging the device and |virNodeDeviceReAttach| (or |virsh nodedev-reattach|) after hot-unplug or stopping the guest."
Since managed is omitted, it seems the automatic detach/reattach should not be done.
https://libvirt.org/formatdomain.html%C2%A0says:
"Controllers <https://libvirt.org/formatdomain.html#elementsControllers>Depending on the guest architecture, some device buses can appear more than once, with a group of virtual devices tied to a virtual controller. Normally, libvirt can automatically infer such controllers without requiring explicit XML markup, but sometimes it is necessary to provide an explicit controller element, notably when planning the PCI topology https://libvirt.org/pci-hotplug.html for guests where device hotplug is expected."
Hi George,
Thank you!
-T
On 11/15/19 12:27 AM, ToddAndMargo via users wrote:
On 11/13/19 5:22 PM, George N. White III wrote:
Has the USB controller been assigned as a PCI device to the VM? If so it would be detached from the host machine.
Controller USB 0 Controller: Type USB; Model USB2 XML: <controller type="usb" index="0" model="ich9-ehci1"> <address type="pci" domain="0x0000" bus="0x00" slot="0x05" function="0x7"/> </controller>
I missed this post until just now.
I see that there is a difference in our configuration as I am using a Virtual USB controller.
<controller type="usb" index="0" model="qemu-xhci" ports="15">
On 11/14/19 7:48 PM, Ed Greshko wrote:
On 11/15/19 12:27 AM, ToddAndMargo via users wrote:
On 11/13/19 5:22 PM, George N. White III wrote:
Has the USB controller been assigned as a PCI device to the VM? If so it would be detached from the host machine.
Controller USB 0 Controller: Type USB; Model USB2 XML: <controller type="usb" index="0" model="ich9-ehci1"> <address type="pci" domain="0x0000" bus="0x00" slot="0x05" function="0x7"/> </controller>
I missed this post until just now.
I see that there is a difference in our configuration as I am using a Virtual USB controller.
<controller type="usb" index="0" model="qemu-xhci" ports="15">
Hi Ed,
Whilst we wait for the graphics I sent with my USB controller options to be approved by the moderator, where did you find that option? I only have USB2, USB3, Hypervisor default (USB2).
Perplexed, -T
On 11/16/19 5:31 AM, ToddAndMargo via users wrote:
Whilst we wait for the graphics I sent with my USB controller options to be approved by the moderator, where did you find that option? I only have USB2, USB3, Hypervisor default (USB2).
I doubt we'll get the graphics here. Image files, especially larger ones, are frowned upon on these mailing lists. Some folks still use links which have data charges. If you want to show images you'll have to place them someplace and put the URL in your message.
Anyway, if you add HW to your system and pick "Controller" and then pick USB3 and look at the XML (next to Details) you'll see it defaults to model="qemu-xhci".
On Fri, 15 Nov 2019 at 17:32, ToddAndMargo via users < users@lists.fedoraproject.org> wrote:
On 11/14/19 7:48 PM, Ed Greshko wrote:
On 11/15/19 12:27 AM, ToddAndMargo via users wrote:
On 11/13/19 5:22 PM, George N. White III wrote:
Has the USB controller been assigned as a PCI device to the VM? If so it would be detached from the host machine.
Controller USB 0 Controller: Type USB; Model USB2 XML: <controller type="usb" index="0" model="ich9-ehci1"> <address type="pci" domain="0x0000" bus="0x00" slot="0x05" function="0x7"/> </controller>
I missed this post until just now.
I see that there is a difference in our configuration as I am using a Virtual USB controller.
<controller type="usb" index="0" model="qemu-xhci" ports="15">
Hi Ed,
Whilst we wait for the graphics I sent with my USB controller options to be approved by the moderator, where did you find that option? I only have USB2, USB3, Hypervisor default (USB2).
USB options may depend on previous choices. For example, different "machine types" have different capabilities.
https://github.com/qemu/qemu/blob/master/docs/usb2.txt menitions differences for XHCI, EHCI, and UHCI. XHCI does USB's1, 2, &3.
On 11/15/19 2:44 PM, Ed Greshko wrote:
On 11/16/19 5:31 AM, ToddAndMargo via users wrote:
Whilst we wait for the graphics I sent with my USB controller options to be approved by the moderator, where did you find that option? I only have USB2, USB3, Hypervisor default (USB2).
I doubt we'll get the graphics here. Image files, especially larger ones, are frowned upon on these mailing lists. Some folks still use links which have data charges. If you want to show images you'll have to place them someplace and put the URL in your message.
Anyway, if you add HW to your system and pick "Controller" and then pick USB3 and look at the XML (next to Details) you'll see it defaults to model="qemu-xhci".
Hi Ed,
You called it.
<controller type="usb" index="0" model="qemu-xhci" ports="15"> <address type="pci" domain="0x0000" bus="0x00" slot="0x05" function="0x0"/> </controller>
My Windows 10 VM now gives back flash drives, but first I had to take a trip over to virtio-win-0.1.173.2.iso/virtio-win-gt-x64.msi
Now my Windows 7 VM can't find them at all, unless I mount them as hardware. And that is fine with me. virtio-win-0.1.173.2.iso is missing the USB driver for Windows 7. I opened a bug report on it:
https://bugzilla.redhat.com/show_bug.cgi?id=1773152
Thank you! -T
On 11/15/19 2:46 PM, George N. White III wrote:
On Fri, 15 Nov 2019 at 17:32, ToddAndMargo via users <users@lists.fedoraproject.org mailto:users@lists.fedoraproject.org> wrote:
On 11/14/19 7:48 PM, Ed Greshko wrote: > On 11/15/19 12:27 AM, ToddAndMargo via users wrote: >> On 11/13/19 5:22 PM, George N. White III wrote: >>> Has the USB controller been assigned as a PCI device to the VM? If >>> so it would be >>> detached from the host machine. >> >> Controller USB 0 >> Controller: Type USB; Model USB2 >> XML: >> <controller type="usb" index="0" model="ich9-ehci1"> >> <address type="pci" domain="0x0000" bus="0x00" slot="0x05" >> function="0x7"/> >> </controller> >> > > I missed this post until just now. > > I see that there is a difference in our configuration as I am using a > Virtual USB controller. > > <controller type="usb" index="0" model="qemu-xhci" ports="15"> Hi Ed, Whilst we wait for the graphics I sent with my USB controller options to be approved by the moderator, where did you find that option? I only have USB2, USB3, Hypervisor default (USB2).USB options may depend on previous choices. For example, different "machine types" have different capabilities.
https://github.com/qemu/qemu/blob/master/docs/usb2.txt%C2%A0menitions differences for XHCI, EHCI, and UHCI. XHCI does USB's1, 2, &3.
-- George N. White III
Hi George,
The USB3 driver works perfectly with my Son-of-Frankenstein (Windows 10) VM, but is missing its drivers from Windows 7. I opened a bug report on it:
https://bugzilla.redhat.com/show_bug.cgi?id=1773152
Thank you!
-T
On 11/13/19 4:51 PM, Todd Chester via users wrote:
Hi All,
Fedora 31 qemu-kvm-4.1.0-5.fc31.x86_64
If I have a virtual machine running and I insert a flash drive into a USB socket, the virtual machine steels the flash drive from the host, not that it will actually work in the VM, which they don't. To get them to work in my VM's I have to add them as a piece of hardware to my configuration, then they work.
I have to exit all my VM's to be able to see my flash drives again from the hosts system (FC31). This is a pain in the neck.
Any way around this?
Many thanks, -T
Found the nec-xhci driver for Windows 7:
https://www.dell.com/support/home/us/en/04/drivers/driversdetails?driverid=3...
But it still steels my drive. I will open a bug report on it at Fedora's bugzilla
-
Ed Greshko -
George N. White III -
Todd Chester -
ToddAndMargo