On Monday, April 20, 2020 11:27:59 A.M. EDT Mark Asselstine wrote:
> On Monday, April 20, 2020 10:22:06 A.M. EDT Michal Privoznik wrote:
> > On 4/20/20 3:54 PM, Mark Asselstine wrote:
> > > No problem. Thanks for taking the patches and making the necessary
> > > tweaks.
> >
> > In return, I've
On Monday, April 20, 2020 10:22:06 A.M. EDT Michal Privoznik wrote:
> On 4/20/20 3:54 PM, Mark Asselstine wrote:
> > No problem. Thanks for taking the patches and making the necessary tweaks.
>
> In return, I've just posted a follow up patches that remove the device
> on "move":
>
>
On 4/20/20 3:54 PM, Mark Asselstine wrote:
No problem. Thanks for taking the patches and making the necessary tweaks.
In return, I've just posted a follow up patches that remove the device
on "move":
https://www.redhat.com/archives/libvir-list/2020-April/msg00936.html
Could you please
On Monday, April 20, 2020 9:30:56 A.M. EDT Michal Privoznik wrote:
> On 4/20/20 3:09 PM, Mark Asselstine wrote:
> > On Monday, April 20, 2020 6:11:25 A.M. EDT Michal Privoznik wrote:
> >> On 4/16/20 5:57 PM, Mark Asselstine wrote:
> >>> The udev monitor thread "udevEventHandleThread()" will lag
On 4/20/20 3:09 PM, Mark Asselstine wrote:
On Monday, April 20, 2020 6:11:25 A.M. EDT Michal Privoznik wrote:
On 4/16/20 5:57 PM, Mark Asselstine wrote:
The udev monitor thread "udevEventHandleThread()" will lag the
actual/real view of devices in sysfs as it serially processes udev
monitor
On Monday, April 20, 2020 6:11:25 A.M. EDT Michal Privoznik wrote:
> On 4/16/20 5:57 PM, Mark Asselstine wrote:
> > The udev monitor thread "udevEventHandleThread()" will lag the
> > actual/real view of devices in sysfs as it serially processes udev
> > monitor events. So for instance if you were
On 4/16/20 5:57 PM, Mark Asselstine wrote:
The udev monitor thread "udevEventHandleThread()" will lag the
actual/real view of devices in sysfs as it serially processes udev
monitor events. So for instance if you were to run the following cmd
to create a new veth pair and rename one of the veth
The udev monitor thread "udevEventHandleThread()" will lag the
actual/real view of devices in sysfs as it serially processes udev
monitor events. So for instance if you were to run the following cmd
to create a new veth pair and rename one of the veth endpoints
you might see the following monitor
