Re: strace showing QEMU process doing >99% ppoll

["Daniel P. Berrangé" <berrange@redhat.com>]

On Mon, Jul 10, 2023 at 02:34:10PM +0200, Fiona Ebner wrote:

> > Thread 14 (Thread 0x7efd24d54700 (LWP 1153824) "iou-wrk-50948"):
> > #0  0x0000000000000000 in ?? ()
> > Backtrace stopped: Cannot access memory at address 0x0
> > 
> > Thread 13 (Thread 0x7efd1ffff700 (LWP 1148438) "iou-wrk-50949"):
> > #0  0x0000000000000000 in ?? ()
> > Backtrace stopped: Cannot access memory at address 0x0
> > 
> > Thread 12 (Thread 0x7efd1ffff700 (LWP 1133766) "iou-wrk-50949"):
> > #0  0x0000000000000000 in ?? ()
> > Backtrace stopped: Cannot access memory at address 0x0
> > 
> > Thread 11 (Thread 0x7efd24d54700 (LWP 2639435) "iou-wrk-50948"):
> > #0  0x0000000000000000 in ?? ()
> > Backtrace stopped: Cannot access memory at address 0x0

These thread names look suprising/interestnig to me - 'iou-wrk-XXXXXX'.

I can't immediately see any code in QEMU creates threads with this
naming convention.

Possibly it could be from a library that QEMU is linking to, but I'm
not finding relevant google hits for this search string 'iou-wrk'.

Does Proxmox have any local patches to QEMU that are relevant ?


With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|