From: Igor Mammedov <imammedo@redhat.com>
To: "Kallol Biswas [C]" <kallol.biswas@nutanix.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>, lersek@redhat.com
Subject: Re: General KVM/QEMU VM debugging techniques
Date: Mon, 4 Apr 2022 14:36:30 +0200 [thread overview]
Message-ID: <20220404143630.02992ea4@redhat.com> (raw)
In-Reply-To: <SJ0PR02MB8862328DCA089E7B5699B927FEE09@SJ0PR02MB8862.namprd02.prod.outlook.com>
On Fri, 1 Apr 2022 23:50:16 +0000
"Kallol Biswas [C]" <kallol.biswas@nutanix.com> wrote:
> Hi,
> We are observing a problem with CPU hotplug.
>
> If secureboot option is enabled under UEFI and then if we try to do CPU hotplug the VM crashes/just reboots.
>
> No crash dump is generated, no panic message, just VM restarts. Issue seems like:
> https://bugzilla.redhat.com/show_bug.cgi?id=1834250
CPU hotplug with SMM (for q35) was merged in QEMU-5.2
and unplug part in 6.0, you also need a matching OVMF build
to make it work. Later upto 6.2 (included) there were minor
fixes dealing with incorrect configs.
> What are the debugging techniques we can apply to halt the VM and examine what's going on?
> VM has been configured with crash dump.
I'd start with https://www.linux-kvm.org/page/Tracing
to find out when it goes south.
> Nucleodyne at Nutanix
> 408-718-8164
>
next prev parent reply other threads:[~2022-04-04 12:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SJ0PR02MB886210F928C7CD01DFAD5FD0FEE09@SJ0PR02MB8862.namprd02.prod.outlook.com>
2022-04-01 23:50 ` General KVM/QEMU VM debugging techniques Kallol Biswas [C]
2022-04-04 12:36 ` Igor Mammedov [this message]
2022-04-04 13:01 ` Laszlo Ersek
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=20220404143630.02992ea4@redhat.com \
--to=imammedo@redhat.com \
--cc=kallol.biswas@nutanix.com \
--cc=kvm@vger.kernel.org \
--cc=lersek@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.