qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurel32@debian.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1091241] Re: NetBSD/i386 6.0 guest suffers interrupt storm since	qemu BIOS update
Date: Mon, 20 May 2013 17:33:22 -0000	[thread overview]
Message-ID: <20130520173323.7052.20320.launchpad@wampee.canonical.com> (raw)
In-Reply-To: 20121217141546.24058.16747.malonedeb@soybean.canonical.com

** Changed in: qemu
       Status: Fix Committed => Fix Released

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

Title:
  NetBSD/i386 6.0 guest suffers interrupt storm since qemu BIOS update

Status in QEMU:
  Fix Released

Bug description:
  Since the pc-bios update of qemu commit
  d7a51dbbaa70677846453f8c961590913052dd86, booting a NetBSD/i386 guest
  takes a very long time, apparently due to interrupt load.

  For example, booting the NetBSD/i386 6.0 serial console install CD
  with

    wget ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-6.0/i386/installation/cdrom/boot-com.iso
    qemu-system-i386 -nographic -cdrom boot-com.iso

  used to take less than a minute, but now takes more like ten minutes
  to enter the "sysinst" installer; it's so slow that at first I thought
  it had hung.  If I then exit the installer and type "vmstat -i", it
  shows a high interrupt rate on ioapic0 pin 9:

  # vmstat -i
  interrupt                                     total     rate
  cpu0 timer                                   336942      102
  ioapic0 pin 9                             256791232    78052
  ioapic0 pin 1                                     1        0
  ioapic0 pin 15                                  345        0
  ioapic0 pin 4                                   102        0
  ioapic0 pin 6                                     1        0
  Total                                     257128623    78154

  According to dmesg, this is the piixpm0 device:

  # dmesg
  [...]
  piixpm0 at pci0 dev 1 function 3: vendor 0x8086 product 0x7113 (rev. 0x03)
  timecounter: Timecounter "piixpm0" frequency 3579545 Hz quality 1000
  piixpm0: 24-bit timer
  piixpm0: interrupting at ioapic0 pin 9
  [...]

  Versions of qemu lacking commit
  d7a51dbbaa70677846453f8c961590913052dd86 do not have this problem.

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

      parent reply	other threads:[~2013-05-20 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 14:15 [Qemu-devel] [Bug 1091241] [NEW] NetBSD/i386 6.0 guest suffers interrupt storm since qemu BIOS update Andreas Gustafsson
2013-01-05 20:28 ` [Qemu-devel] [Bug 1091241] " Andreas Gustafsson
2013-05-20 17:33 ` Aurelien Jarno [this message]

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=20130520173323.7052.20320.launchpad@wampee.canonical.com \
    --to=aurel32@debian.org \
    --cc=1091241@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).