------- Comment From <email address hidden> 2020-09-09 09:44 EDT-------
(In reply to comment #67)
> Thanks for the quick answer!
> Any particular uperf profile that was found to be more likely/reliably to
> trigger it?
> I assume with driver=qemu you actually mean something like:
> <interface type='network'>
> <source network='default'/>
> <model type='virtio'/>
> <driver name='qemu'
> Which is the only driver=qemu that makes sense for [1] I think.
You are right, that is what we mean.
> If you have a libvirt XML of the guest that was used somewhere could you
> please just attach it.
------- Comment From <email address hidden> 2020-09-09 09:44 EDT-------
(In reply to comment #67)
> Thanks for the quick answer!
> Any particular uperf profile that was found to be more likely/reliably to
> trigger it?
> I assume with driver=qemu you actually mean something like:
> <interface type='network'>
> <source network='default'/>
> <model type='virtio'/>
> <driver name='qemu'
> Which is the only driver=qemu that makes sense for [1] I think.
You are right, that is what we mean.
> If you have a libvirt XML of the guest that was used somewhere could you
> please just attach it.
Will have a look.
> /libvirt. org/formatdomai n.html# network- interfaces
> [1]: https:/
(In reply to comment #67)
> Thanks for the quick answer!
> Any particular uperf profile that was found to be more likely/reliably to
> trigger it?
Actually I used iperf in a loop to trigger this (from the guest)
for i in $(seq 1 100) ;
do
echo $i
iperf -c 192.168.122.1 || break
done
Hope that helps.