qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: VoidCC <raidsmainacc@gmail.com>, qemu-devel@nongnu.org
Cc: Laszlo Ersek <lersek@redhat.com>
Subject: Re: qemu/kvm tianocore restart stuck
Date: Fri, 23 Apr 2021 11:51:31 +0200	[thread overview]
Message-ID: <a7247822-3433-b0b1-65c0-8d22b388e134@redhat.com> (raw)
In-Reply-To: <CABZ9ZfUNmxTPxOBh0SCvaxBFRHKkTfmwAQjqFin=20CwMK64_g@mail.gmail.com>

On 4/22/21 10:04 PM, VoidCC wrote:
> Hello,
> 
> I'm hitting a hard wall with qemu and efi.
> I'm running multiple windows server 2019 vms which usually reboot on
> updates.
> 
> The issue is, efi breaks on reboot.
> It randomly(race condition?, does not occur consistently) ends up in a
> blackscreen: no bootloader, no efi screen and the only way to get out of
> that state is to destroy the vm.
> moving the host mouse cursor above the console in virt-manager results
> in a flashing mouse cursor.
> there are no physical devices attached and there is currently no virtio
> attachment in use (os has virtio drivers installed)
> 
> 
> Machine is Q35 with tianocore/ovmf efi.
> I managed to reproduce the same behaviour on rhel 8.3 as well as
> voidlinux (kernel 5.11)
> 
> gdb output of qemu is showing nothing worrisome, else ive compiled ovmf
> manually for debug output.
> libvirt logs don't show any issues.
> 
> root · Slexy.org Pastebin <https://slexy.org/view/s2w8CdNBx5>

I tried to help you yesterday on IRC mentioning SMM / EPT
but then you didn't reply. See:
https://bugzilla.redhat.com/show_bug.cgi?id=1348092#c24

Regards,

Phil.



  reply	other threads:[~2021-04-23  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22 20:04 qemu/kvm tianocore restart stuck VoidCC
2021-04-23  9:51 ` Philippe Mathieu-Daudé [this message]
2021-04-23 10:30 ` 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=a7247822-3433-b0b1-65c0-8d22b388e134@redhat.com \
    --to=philmd@redhat.com \
    --cc=lersek@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=raidsmainacc@gmail.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 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).