qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ed Davison <1923497@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1923497] Re: bios_linker_loader_add_checksum: Assertion `start_offset < file->blob->len' failed
Date: Thu, 06 May 2021 18:59:57 -0000	[thread overview]
Message-ID: <162032759790.5917.14185683225066828529.malone@wampee.canonical.com> (raw)
In-Reply-To: 161825934506.9582.2393035423485633300.malonedeb@chaenomeles.canonical.com

Sorry, this has not recurred since you asked for the stack trace. Not
sure what "fixed" it.  Closing the bug.

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  bios_linker_loader_add_checksum: Assertion `start_offset <
  file->blob->len' failed

Status in QEMU:

Bug description:
  Trying boot/start a Windows 10 VM.  Worked until recently when this
  error started showing up.

  I have the following installed on Fedora 33:

  This is the error:

  Error starting domain: internal error: process exited while connecting
  to monitor: qemu-system-x86_64:
  bios_linker_loader_add_checksum: Assertion `start_offset <
  file->blob->len' failed.

  Traceback (most recent call last):
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper
      callback(asyncjob, *args, **kwargs)
    File "/usr/share/virt-manager/virtManager/asyncjob.py", line 101, in tmpcb
      callback(*args, **kwargs)
    File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
      ret = fn(self, *args, **kwargs)
    File "/usr/share/virt-manager/virtManager/object/domain.py", line 1329, in startup
    File "/usr/lib64/python3.9/site-packages/libvirt.py", line 1234, in create
      if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
  libvirt.libvirtError: internal error: process exited while connecting to monitor: qemu-system-x86_64: /builddir/build/BUILD/qemu-5.1.0/hw/acpi/bios-linker-loader.c:239: bios_linker_loader_add_checksum: Assertion `start_offset < file->blob->len' failed.

  I see this were referenced in a patch from some time ago and
  supposedly fixed.  Here is the patch info I was able to find:


To manage notifications about this bug go to:

  parent reply	other threads:[~2021-05-06 19:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-12 20:29 [Bug 1923497] [NEW] bios_linker_loader_add_checksum: Assertion `start_offset < file->blob->len' failed Ed Davison
2021-04-13  9:03 ` Igor Mammedov
2021-04-13  9:03   ` Igor
2021-04-13 21:29 ` [Bug 1923497] " Ed Davison
2021-04-14  8:49   ` Igor Mammedov
2021-04-14  8:49     ` Igor
2021-04-14 19:40 ` Ed Davison
2021-04-19 12:27   ` Igor Mammedov
2021-04-19 12:27     ` Igor
2021-05-06 18:59 ` Ed Davison [this message]
2021-05-06 19:00 ` Ed Davison
2021-05-07  2:34 ` Thomas Huth
2021-07-15 10:08 ` Thomas Huth
2021-08-25  7:12 ` Thomas Huth

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=162032759790.5917.14185683225066828529.malone@wampee.canonical.com \
    --to=1923497@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \


* 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).