From: Launchpad Bug Tracker <1890069@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1890069] [NEW] QEMU is not allowing multiple cores with mips architecture
Date: Mon, 03 Aug 2020 01:38:14 -0000 [thread overview]
Message-ID: <159641869421.15668.10068956949302786413.launchpad@wampee.canonical.com> (raw)
In-Reply-To: 159641864326.4737.3834879940434032325.malonedeb@soybean.canonical.com
You have been subscribed to a public bug:
I may have found a bug as when trying to boot up an QEMU VM with the
following command: "qemu-system-mips -M malta -m 512 -hda hda.img
-kernel vmlinux-4.19.0-10-4kc-malta -initrd initrd.img-4.19.0-10-4kc-
malta -append "root=/dev/sda1 console=ttyS0" -nographic -device
e1000,netdev=user.0 -netdev user,id=user.0,hostfwd=tcp::5555-:22 -smp
cores=12,threads=1,sockets=1", it will use up all of the CPU cores on
the host, but not bootup?
Kernel log also shows:
[ 100.303136] perf: interrupt took too long (2506 > 2500), lowering kernel.perf_event_max_sample_rate to 79750
[ 107.656869] perf: interrupt took too long (3195 > 3132), lowering kernel.perf_event_max_sample_rate to 62500
[ 117.668390] perf: interrupt took too long (4033 > 3993), lowering kernel.perf_event_max_sample_rate to 49500
[ 217.166763] perf: interrupt took too long (5126 > 5041), lowering kernel.perf_event_max_sample_rate to 39000
[ 231.910132] perf: interrupt took too long (6445 > 6407), lowering kernel.perf_event_max_sample_rate to 31000
[ 250.170677] perf: interrupt took too long (8087 > 8056), lowering kernel.perf_event_max_sample_rate to 24500
[ 285.391451] perf: interrupt took too long (10126 > 10108), lowering kernel.perf_event_max_sample_rate to 19750
[ 778.588911] perf: interrupt took too long (12770 > 12657), lowering kernel.perf_event_max_sample_rate to 15500
[ 1554.825129] perf: interrupt took too long (15982 > 15962), lowering kernel.perf_event_max_sample_rate to 12500
[ 1622.838910] hrtimer: interrupt took 14758063 ns
[ 1712.932777] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 0.000 msecs
[ 1712.932780] perf: interrupt took too long (59793 > 19977), lowering kernel.perf_event_max_sample_rate to 3250
System details:
OS: Ubuntu 20.04
QEMU emulator version 4.2.0 (Debian 1:4.2-3ubuntu6.3)
** Affects: qemu
Importance: Undecided
Status: New
--
QEMU is not allowing multiple cores with mips architecture
https://bugs.launchpad.net/bugs/1890069
You received this bug notification because you are a member of qemu-devel-ml, which is subscribed to QEMU.
prev parent reply other threads:[~2020-08-03 1:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 1:37 [Bug 1890069] [NEW] QEMU is not allowing multiple cores with mips architecture Skyler Mäntysaari
2020-08-03 1:38 ` Launchpad Bug Tracker [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=159641869421.15668.10068956949302786413.launchpad@wampee.canonical.com \
--to=1890069@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).