From: Igor Mammedov <imammedo@redhat.com>
To: Ed Davison <1923497@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Bug 1923497] Re: bios_linker_loader_add_checksum: Assertion `start_offset < file->blob->len' failed
Date: Mon, 19 Apr 2021 14:27:19 +0200 [thread overview]
Message-ID: <20210419142719.226ddb77@redhat.com> (raw)
In-Reply-To: <161842923676.15588.10923516048871617719.malone@chaenomeles.canonical.com>
On Wed, 14 Apr 2021 19:40:36 -0000
Ed Davison <1923497@bugs.launchpad.net> wrote:
> The patch may be a bit beyond me at the moment as I use a package to
> install this and would have to figure out how to download source, get it
> configure, patched and compiled. Whew! Maybe ...
>
> But here is my XML config file.
>
> ** Attachment added: "domain xml file"
> https://bugs.launchpad.net/qemu/+bug/1923497/+attachment/5487970/+files/win10-virt-domain.xml
>
I don't see anything in this config that could trigger the assert.
(RAM size is 2Kb off 4Gb, but that's probably not the issue)
Can you provide a stack trace, it should help to find out
which path triggers assert.
WARNING: multiple messages have this Message-ID (diff)
From: Igor <1923497@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Bug 1923497] Re: bios_linker_loader_add_checksum: Assertion `start_offset < file->blob->len' failed
Date: Mon, 19 Apr 2021 12:27:19 -0000 [thread overview]
Message-ID: <20210419142719.226ddb77@redhat.com> (raw)
Message-ID: <20210419122719.ku_uVyyWLGVcfMJUMzsExpt7-uvOizJjNOlAsN6Pq70@z> (raw)
In-Reply-To: 161842923676.15588.10923516048871617719.malone@chaenomeles.canonical.com
On Wed, 14 Apr 2021 19:40:36 -0000
Ed Davison <1923497@bugs.launchpad.net> wrote:
> The patch may be a bit beyond me at the moment as I use a package to
> install this and would have to figure out how to download source, get it
> configure, patched and compiled. Whew! Maybe ...
>
> But here is my XML config file.
>
> ** Attachment added: "domain xml file"
> https://bugs.launchpad.net/qemu/+bug/1923497/+attachment/5487970/+files/win10-virt-domain.xml
>
I don't see anything in this config that could trigger the assert.
(RAM size is 2Kb off 4Gb, but that's probably not the issue)
Can you provide a stack trace, it should help to find out
which path triggers assert.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1923497
Title:
bios_linker_loader_add_checksum: Assertion `start_offset <
file->blob->len' failed
Status in QEMU:
New
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:
qemu-kvm-5.1.0-9.fc33.x86_64
This is the error:
Error starting domain: 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.
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
self._backend.create()
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:
http://next.patchew.org/QEMU/1515677902-23436-1-git-send-email-
peter.maydell@linaro.org/1515677902-23436-10-git-send-email-
peter.maydell@linaro.org/
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1923497/+subscriptions
next prev parent reply other threads:[~2021-04-19 12:28 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 [this message]
2021-04-19 12:27 ` Igor
2021-05-06 18:59 ` Ed Davison
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:
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=20210419142719.226ddb77@redhat.com \
--to=imammedo@redhat.com \
--cc=1923497@bugs.launchpad.net \
--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 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.