diff for duplicates of <20210419142719.226ddb77@redhat.com> diff --git a/a/1.txt b/N1/1.txt index 4b03c2d..9c3464c 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -16,3 +16,53 @@ I don't see anything in this config that could trigger the assert. 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 diff --git a/a/content_digest b/N1/content_digest index 643fc1f..ed508bd 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,10 +1,9 @@ "ref\0161825934506.9582.2393035423485633300.malonedeb@chaenomeles.canonical.com\0" "ref\0161842923676.15588.10923516048871617719.malone@chaenomeles.canonical.com\0" - "From\0Igor Mammedov <imammedo@redhat.com>\0" + "From\0Igor <1923497@bugs.launchpad.net>\0" "Subject\0Re: [Bug 1923497] Re: bios_linker_loader_add_checksum: Assertion `start_offset < file->blob->len' failed\0" - "Date\0Mon, 19 Apr 2021 14:27:19 +0200\0" - "To\0Ed Davison <1923497@bugs.launchpad.net>\0" - "Cc\0qemu-devel@nongnu.org\0" + "Date\0Mon, 19 Apr 2021 12:27:19 -0000\0" + "To\0qemu-devel@nongnu.org\0" "\00:1\0" "b\0" "On Wed, 14 Apr 2021 19:40:36 -0000\n" @@ -24,6 +23,56 @@ "(RAM size is 2Kb off 4Gb, but that's probably not the issue)\n" "\n" "Can you provide a stack trace, it should help to find out\n" - which path triggers assert. + "which path triggers assert.\n" + "\n" + "-- \n" + "You received this bug notification because you are a member of qemu-\n" + "devel-ml, which is subscribed to QEMU.\n" + "https://bugs.launchpad.net/bugs/1923497\n" + "\n" + "Title:\n" + " bios_linker_loader_add_checksum: Assertion `start_offset <\n" + " file->blob->len' failed\n" + "\n" + "Status in QEMU:\n" + " New\n" + "\n" + "Bug description:\n" + " Trying boot/start a Windows 10 VM. Worked until recently when this\n" + " error started showing up.\n" + "\n" + " I have the following installed on Fedora 33:\n" + " qemu-kvm-5.1.0-9.fc33.x86_64\n" + "\n" + " This is the error:\n" + "\n" + " Error starting domain: internal error: process exited while connecting\n" + " to monitor: qemu-system-x86_64:\n" + " /builddir/build/BUILD/qemu-5.1.0/hw/acpi/bios-linker-loader.c:239:\n" + " bios_linker_loader_add_checksum: Assertion `start_offset <\n" + " file->blob->len' failed.\n" + "\n" + " Traceback (most recent call last):\n" + " File \"/usr/share/virt-manager/virtManager/asyncjob.py\", line 65, in cb_wrapper\n" + " callback(asyncjob, *args, **kwargs)\n" + " File \"/usr/share/virt-manager/virtManager/asyncjob.py\", line 101, in tmpcb\n" + " callback(*args, **kwargs)\n" + " File \"/usr/share/virt-manager/virtManager/object/libvirtobject.py\", line 57, in newfn\n" + " ret = fn(self, *args, **kwargs)\n" + " File \"/usr/share/virt-manager/virtManager/object/domain.py\", line 1329, in startup\n" + " self._backend.create()\n" + " File \"/usr/lib64/python3.9/site-packages/libvirt.py\", line 1234, in create\n" + " if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)\n" + " 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.\n" + "\n" + " I see this were referenced in a patch from some time ago and\n" + " supposedly fixed. Here is the patch info I was able to find:\n" + "\n" + " http://next.patchew.org/QEMU/1515677902-23436-1-git-send-email-\n" + " peter.maydell@linaro.org/1515677902-23436-10-git-send-email-\n" + " peter.maydell@linaro.org/\n" + "\n" + "To manage notifications about this bug go to:\n" + https://bugs.launchpad.net/qemu/+bug/1923497/+subscriptions -8803bb51448e180ef8e3e778037ef6592afa9c127afa714a67e1a0c48a8e28ed +ac94e128091b0b5e5f5185c5361518047e7aaa57a67f4f562c9717a0bb01a153
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.