All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Hohl <1481272@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1481272] Re: main-loop: WARNING: I/O thread spun for 1000 iterations
Date: Sun, 29 Nov 2015 22:47:23 -0000	[thread overview]
Message-ID: <20151129224723.3322.79104.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 20150804095638.25012.1470.malonedeb@chaenomeles.canonical.com

I have experienced this behavior (main-loop: WARNING: I/O thread spun
for 1000 iterations) and the resulting degraded performance.  The VM
becomes very unresponsive but eventually recovers.  My setup:

Ubuntu 15.10 | qemu-system-x86_64 --version  QEMU emulator version 2.3.0 (Debian 1:2.3+dfsg-5ubuntu9)
HW = Dell Precision M6600 with Intel(R) Core(TM) i7-2760QM CPU

I agree with other comments that it seems related to high disk I/O as
the problem seems to occur during VM install or other VM operations
which read/write large amounts of data.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1481272

Title:
  main-loop: WARNING: I/O thread spun for 1000 iterations

Status in QEMU:
  New

Bug description:
  I compile the latest qemu to launch a VM but the monitor output the
  "main-loop: WARNING: I/O thread spun for 1000 iterations".

  # /usr/local/bin/qemu-system-x86_64 -name rhel6 -S -no-kvm -m 1024M -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid c9dd2a5c-40f2-fd3d-3c54-9cd84f8b9174 -rtc base=utc  -drive file=/home/samba-share/ubuntu.img,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=disk,serial=425618d4-871f-4021-bc5d-bcd7f1b5ca9c,bootindex=0 -vnc :1 -boot menu=on -monitor stdio
  QEMU 2.3.93 monitor - type 'help' for more information
  (qemu) c
  (qemu) main-loop: WARNING: I/O thread spun for 1000 iterations               <-----------------------

  qemu]# git branch -v
  * master               e95edef Merge remote-tracking branch 'remotes/sstabellini/tags/xen-migration-2.4-tag' into staging

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1481272/+subscriptions

  parent reply	other threads:[~2015-11-29 22:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-04  9:56 [Qemu-devel] [Bug 1481272] [NEW] main-loop: WARNING: I/O thread spun for 1000 iterations Sibiao Luo
2015-08-04  9:57 ` [Qemu-devel] [Bug 1481272] " Sibiao Luo
2015-08-04  9:58 ` Sibiao Luo
2015-08-04 13:15 ` [Qemu-devel] [Bug 1481272] [NEW] " Stefan Hajnoczi
2015-08-17  7:59 ` [Qemu-devel] [Bug 1481272] " Sibiao Luo
2015-08-17  8:22 ` Sibiao Luo
2015-09-04 20:57 ` Arghya Banerjee
2015-09-07 11:59 ` Paolo Bonzini
2015-11-29 22:47 ` Bruce Hohl [this message]
2016-01-01 10:05 ` T-artem
2016-01-30 20:29 ` Martin von Gagern
2017-04-07 14:16 ` Marcin Mielniczuk
2017-04-07 14:18 ` Marcin Mielniczuk
2017-04-10 13:48 ` Marcin Mielniczuk
2017-04-10 14:07 ` Peter Maydell
2017-04-21 12:24 ` Andreas Gustafsson
2018-03-31 17:48 ` Andreas Gustafsson
2018-04-03  8:38 ` ChristianEhrhardt
2018-04-03  8:39 ` ChristianEhrhardt
2018-04-03 17:38 ` Thomas Huth
2018-10-10 14:31 ` Afsah Anwar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151129224723.3322.79104.malone@chaenomeles.canonical.com \
    --to=1481272@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.