qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: "longguang.yue" <kvmluck@163.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
	"mst@redhat.com" <mst@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: LTP test related to virtio releasing and reassigning resource leads to guest hung
Date: Thu, 10 Aug 2023 10:13:35 -0400	[thread overview]
Message-ID: <20230810141335.GA2931656@fedora> (raw)
In-Reply-To: <3c1a93da.16493.189df040e16.Coremail.kvmluck@163.com>

[-- Attachment #1: Type: text/plain, Size: 2073 bytes --]

On Thu, Aug 10, 2023 at 06:35:32PM +0800, longguang.yue wrote:
> could you please give me some tips to diagnose?  I could do tests on qemu 8.0, but product environment could not update.
> I test on different kernel version 5.10.0-X, one is better and results show problem is more about host kernel  rather than qemu.
> 
> 
> test cases are different combination of i440fx/q35 and virtio/scsi and kernel.

Can you post the guest kernel messages (dmesg)? If the guest is hanging
then it may be easiest to configure a serial console so the kernel
messages are sent to the host where you can see them.

Does the hang occur during the LTP code you linked or afterwards when
the PCI device is bound to a virtio driver?

Which virtio device causes the problem?

Can you describe the hang in more detail: is the guest still responsive
(e.g. console or network)? Is the QEMU HMP/QMP monitor still responsive?

Thanks,
Stefan

> 
> 
> 
> 
> thanks
> 
> 
> 
> 
> ---- Replied Message ----
> | From | Michael Tokarev<mjt@tls.msk.ru> |
> | Date | 08/10/2023 17:08 |
> | To | longguang.yue<kvmluck@163.com> ,
> qemu-devel<qemu-devel@nongnu.org> ,
> linux-kernel<linux-kernel@vger.kernel.org> |
> | Subject | Re: LTP test related to virtio releasing and reassigning resource leads to guest hung |
> 10.08.2023 11:57, longguang.yue wrote:
> Hi, all:
> A ltp test leads to guest hung(io hung), the test releases virtio device resource and then reassign.
> I find device’s mem prefetchable resource 64-bit is changed.
> 
> ltp
> test: https://github.com/linux-test-project/ltp/blob/522d7fba4afc84e07b252aa4cd91b241e81d6613/testcases/kernel/device-drivers/pci/tpci_kernel/ltp_tpci.c#L428
> 
> Do you know what cause the problem?
> 
> Thanks very much.
> 
> --------------------------
> ENV: kernel 5.10.0, qemu 6.2
> 
> Current qemu is 8.1 (well, almost, to be released this month;
> previous release is 8.0 anyway).
> 
> This might be interesting to test in a current version before
> going any further.
> 
> Thanks,
> 
> /mjt

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2023-08-10 14:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10  8:57 LTP test related to virtio releasing and reassigning resource leads to guest hung longguang.yue
2023-08-10  9:08 ` Michael Tokarev
2023-08-10 10:35   ` longguang.yue
2023-08-10 14:13     ` Stefan Hajnoczi [this message]
2023-08-10 15:24       ` Stefan Hajnoczi
2023-08-11  2:26         ` longguang.yue
2023-08-15 15:18           ` Stefan Hajnoczi

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=20230810141335.GA2931656@fedora \
    --to=stefanha@redhat.com \
    --cc=kvmluck@163.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --cc=mst@redhat.com \
    --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).