On 16.09.2019 12:09, Peter Krempa wrote:
> On Mon, Sep 16, 2019 at 08:58:10 +, Nikolay Shirokovskiy wrote:
>>
>>
>> On 16.09.2019 11:30, Peter Krempa wrote:
>>> On Mon, Sep 09, 2019 at 14:33:12 +0300, Nikolay Shirokovskiy wrote:
First I don't want to add code to handle dummy device
On Mon, Sep 16, 2019 at 08:58:10 +, Nikolay Shirokovskiy wrote:
>
>
> On 16.09.2019 11:30, Peter Krempa wrote:
> > On Mon, Sep 09, 2019 at 14:33:12 +0300, Nikolay Shirokovskiy wrote:
> >> First I don't want to add code to handle dummy device that is used when
> >> host usb device is not
On 16.09.2019 11:30, Peter Krempa wrote:
> On Mon, Sep 09, 2019 at 14:33:12 +0300, Nikolay Shirokovskiy wrote:
>> First I don't want to add code to handle dummy device that is used when
>> host usb device is not present at the moment of starting/migrating etc.
>> Second supporting non mandatory
On Mon, Sep 09, 2019 at 14:33:12 +0300, Nikolay Shirokovskiy wrote:
> First I don't want to add code to handle dummy device that is used when
> host usb device is not present at the moment of starting/migrating etc.
> Second supporting non mandatory policies would require to handle races
> when
On 9/9/19 8:33 AM, Nikolay Shirokovskiy wrote:
First I don't want to add code to handle dummy device that is used when
host usb device is not present at the moment of starting/migrating etc.
Second supporting non mandatory policies would require to handle races
when host usb device is plugged
First I don't want to add code to handle dummy device that is used when
host usb device is not present at the moment of starting/migrating etc.
Second supporting non mandatory policies would require to handle races
when host usb device is plugged to host and libvirtd starts adding
device but if in