Displaying 3 results from an estimated 3 matches for "3773b389".
Did you mean:
373389
2018 Sep 20
2
Re: Which objects does dynamic_ownership apply to?
...But how about host devices such as USB and PCI devices? For example
<hostdev managed="no" mode="subsystem" type="usb">
<source>
<address bus="3" device="2" />
</source>
<alias name="ua-3773b389-54be-4fd5-ae8b-2f954470b1a9" />
<address bus="0" port="1" type="usb" />
</hostdev>
doesn't change the owner of /dev/bus/usb/003/002 (the same for
managed="yes"). Similarly for a PCI hostdev device /dev/vfio/* owners
are not c...
2018 Sep 20
0
Re: Which objects does dynamic_ownership apply to?
...ch as USB and PCI devices? For example
>
> <hostdev managed="no" mode="subsystem" type="usb">
> <source>
> <address bus="3" device="2" />
> </source>
> <alias name="ua-3773b389-54be-4fd5-ae8b-2f954470b1a9" />
> <address bus="0" port="1" type="usb" />
> </hostdev>
>
> doesn't change the owner of /dev/bus/usb/003/002 (the same for
> managed="yes").
Are you perhaps using namespaces and...
2018 Sep 19
2
Which objects does dynamic_ownership apply to?
Hi, I'm playing with dynamic ownership and not all objects have their
owners changed.
Is dynamic_ownership and its scope documented somewhere, besides the
comment in qemu.conf?
And what kinds of objects are handled by dynamic ownership? While some
objects seem to be handled, other objects are apparently unaffected.
For instance /dev/hwrng or a USB host device keep their root owners and
are