Peter Krempa writes:
> On Mon, Oct 15, 2018 at 09:56:39 +0200, Milan Zamazal wrote:
>> Peter Krempa writes:
>>
>
>> > On Fri, Oct 12, 2018 at 19:33:54 +0200, Milan Zamazal wrote:
>> >> Hi, when working on hot unplugs of various devices, I've found out that
>> >> hot unplugging device doesn't g
On Mon, Oct 15, 2018 at 09:56:39 +0200, Milan Zamazal wrote:
> Peter Krempa writes:
>
> > On Fri, Oct 12, 2018 at 19:33:54 +0200, Milan Zamazal wrote:
> >> Hi, when working on hot unplugs of various devices, I've found out that
> >> hot unplugging device doesn't generate
> >> VIR_DOMAIN_EVENT_ID
Peter Krempa writes:
> On Fri, Oct 12, 2018 at 19:33:54 +0200, Milan Zamazal wrote:
>> Hi, when working on hot unplugs of various devices, I've found out that
>> hot unplugging device doesn't generate
>> VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED event. also doesn't have an
>> alias, so it wouldn't be
On Fri, Oct 12, 2018 at 19:33:54 +0200, Milan Zamazal wrote:
> Hi, when working on hot unplugs of various devices, I've found out that
> hot unplugging device doesn't generate
> VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED event. also doesn't have an
> alias, so it wouldn't be identifiable in the correspo
Hi, when working on hot unplugs of various devices, I've found out that
hot unplugging device doesn't generate
VIR_DOMAIN_EVENT_ID_DEVICE_REMOVED event. also doesn't have an
alias, so it wouldn't be identifiable in the corresponding callback.
Is this difference from other hotpluggable devices i
