From: "Kernel.org Bugbot" <bugbot@kernel.org>
To: bugs@lists.linux.dev
Subject: Kernel panic on adding vCPU to guest in Linux 6.9-rc2
Date: Wed, 10 Apr 2024 16:15:10 +0000 [thread overview]
Message-ID: <20240410-b218698c0-cb3e9db062a2@bugzilla.kernel.org> (raw)
xiangfeix.ma added an attachment on Kernel.org Bugzilla:
Created attachment 306112
guest error log
Environment:
Host OS: CentOS 9
Host kernel: 6.9.0-rc1
KVM commit: 9bc60f73
Qemu commit: e5c6528d
Guest kernel: 6.9-rc2
Guest commit: 39cd87c4eb2b893354f3b850f916353f2658ae6f
Guest repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Bug detail description:
When hot adding a vCPU to the guest, the guest happens Call Trace and reboot.
Latest successful guest kernel version: 6.8.0-rc7 (commit: 90d35da658da8cff0d4ecbb5113f5fac9d00eb72).
Reproduce steps:
1. Create guest:
qemu-system-x86_64 -accel kvm -cpu host -smp 4,maxcpus=128 -drive file=/share/xvs/var/tmp-img_vcpu_hot_add_1712412537,if=none,id=virtio-disk0 -device virtio-blk-pci,drive=virtio-disk0,bootindex=0 -m 4096 -monitor pty -daemonize -vnc :16147 -device virtio-net-pci,netdev=nic0,mac=00:c0:82:16:fa:b0 -netdev tap,id=nic0,br=virbr0,helper=/usr/local/libexec/qemu-bridge-helper,vhost=on
2. Add vCPU to guest
echo 'device_add driver=host-x86_64-cpu,socket-id=0,core-id=4,thread-id=0' > /dev/pts/2
cat /dev/pts/2
Error log:
[ 49.782913] Call Trace:
[ 49.783039] <TASK>
[ 49.783147] ? __die+0x24/0x70
[ 49.783309] ? page_fault_oops+0x82/0x150
[ 49.783518] ? kernelmode_fixup_or_oops+0x84/0x110
[ 49.783753] ? exc_page_fault+0xb9/0x160
[ 49.783948] ? asm_exc_page_fault+0x26/0x30
[ 49.784144] ? cpu_update_apic+0x1c/0x70
[ 49.784327] generic_processor_info+0x7e/0x160
[ 49.784541] acpi_register_lapic+0x19/0x80
[ 49.784732] acpi_map_cpu+0x26/0x90
[ 49.784896] acpi_processor_get_info+0x256/0x490
[ 49.785344] acpi_processor_add+0xb9/0x1f0
[ 49.785760] acpi_bus_attach+0x13b/0x220
[ 49.786158] acpi_bus_scan+0x7e/0x1e0
[ 49.786548] acpi_device_hotplug+0x198/0x2b0
[ 49.786963] acpi_hotplug_work_fn+0x1e/0x30
[ 49.787363] process_one_work+0x159/0x370
[ 49.787790] worker_thread+0x302/0x420
[ 49.788184] ? __pfx_worker_thread+0x10/0x10
[ 49.788592] kthread+0xe3/0x120
[ 49.788955] ? __pfx_kthread+0x10/0x10
[ 49.789335] ret_from_fork+0x31/0x50
[ 49.789720] ? __pfx_kthread+0x10/0x10
[ 49.790100] ret_from_fork_asm+0x1b/0x30
[ 49.790491] </TASK>
File: serial_error_guest.log (text/plain)
Size: 98.02 KiB
Link: https://bugzilla.kernel.org/attachment.cgi?id=306112
---
guest error log
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (peebz 0.1)
next reply other threads:[~2024-04-10 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 16:15 Kernel.org Bugbot [this message]
2024-04-10 16:15 ` Kernel panic on adding vCPU to guest in Linux 6.9-rc2 Kernel.org Bugbot
2024-04-10 16:15 ` Kernel.org Bugbot
2024-04-10 16:15 ` Kernel.org Bugbot
2024-04-10 16:15 ` Kernel.org Bugbot
2024-04-10 19:50 ` Kernel.org Bugbot
2024-04-17 7:25 ` Kernel.org Bugbot
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=20240410-b218698c0-cb3e9db062a2@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=bugs@lists.linux.dev \
/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).