Received-SPF: pass (google.com: domain of linux-kernel+bounces-12675-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Date: Thu, 28 Dec 2023 14:18:02 +0100
From: Lukas Wunner <lukas@wunner.de>
To: Steven Haigh <netwiz@crc.id.au>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	f.ebner@proxmox.com
Subject: Re: Qemu KVM thread spins at 100% CPU usage on scsi hot-unplug
 (kernel 6.6.8 guest)
Message-ID: <20231228131802.GA21994@wunner.de>
References: <3a7656ab-df4c-4d57-8866-661beffcddd7@crc.id.au>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3a7656ab-df4c-4d57-8866-661beffcddd7@crc.id.au>
User-Agent: Mutt/1.10.1 (2018-07-13)

On Thu, Dec 28, 2023 at 01:03:10PM +1100, Steven Haigh wrote:
> At some point in kernel 6.6.x, SCSI hotplug in qemu VMs broke. This was
> mostly fixed in the following commit to release 6.6.8:
> 	commit 5cc8d88a1b94b900fd74abda744c29ff5845430b
> 	Author: Bjorn Helgaas <bhelgaas@google.com>
> 	Date:   Thu Dec 14 09:08:56 2023 -0600
> 	Revert "PCI: acpiphp: Reassign resources on bridge if necessary"
> 
> After this commit, the SCSI block device is hotplugged correctly, and a device node as /dev/sdX appears within the qemu VM.
> 
> New problem:
> 
> When the same SCSI block device is hot-unplugged, the QEMU KVM process will
> spin at 100% CPU usage. The guest shows no CPU being used via top, but the
> host will continue to spin in the KVM thread until the VM is rebooted.

Find out the PID of the qemu process on the host, then cat /proc/$PID/stack
to see where the CPU time is spent.