Re: qemu-kvm steels my flash drives

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 11/14/19 9:55 AM, George N. White III wrote:
On Thu, 14 Nov 2019 at 12:28, ToddAndMargo via users <users@xxxxxxxxxxxxxxxxxxxxxxx <mailto:users@xxxxxxxxxxxxxxxxxxxxxxx>> 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."

Hi George,

    Thank you!

-T
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux