diff options
Diffstat (limited to 'results/classifier/118/none/1923497')
| -rw-r--r-- | results/classifier/118/none/1923497 | 154 |
1 files changed, 154 insertions, 0 deletions
diff --git a/results/classifier/118/none/1923497 b/results/classifier/118/none/1923497 new file mode 100644 index 000000000..dd14603db --- /dev/null +++ b/results/classifier/118/none/1923497 @@ -0,0 +1,154 @@ +TCG: 0.588 +ppc: 0.544 +x86: 0.544 +KVM: 0.536 +hypervisor: 0.532 +vnc: 0.528 +virtual: 0.511 +VMM: 0.505 +graphic: 0.467 +risc-v: 0.458 +arm: 0.448 +permissions: 0.444 +boot: 0.439 +peripherals: 0.435 +performance: 0.405 +architecture: 0.403 +PID: 0.403 +device: 0.397 +register: 0.396 +files: 0.376 +socket: 0.363 +user-level: 0.358 +mistranslation: 0.351 +assembly: 0.345 +semantic: 0.343 +kernel: 0.338 +network: 0.330 +debug: 0.312 +i386: 0.262 + +bios_linker_loader_add_checksum: Assertion `start_offset < file->blob->len' failed + +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.<email address hidden><email address hidden>/ + +On Mon, 12 Apr 2021 20:29:04 -0000 +Ed Davison <email address hidden> wrote: + +> Public bug reported: +> +> 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 + +Could you add used QEMU command line in your case? + +> +> 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- +> <email address hidden>/1515677902-23436-10-git-send-email- +> <email address hidden>/ +> +> ** Affects: qemu +> Importance: Undecided +> Status: New +> + + + +Hmmm. Well, I don't know what the command line was. I use Virtual Machine Manager (virt-manager.org) for my interface to the VM and it does the startup. The error shows up when I start the VM. + + +On Tue, 13 Apr 2021 21:29:45 -0000 +Ed Davison <email address hidden> wrote: + +> Hmmm. Well, I don't know what the command line was. I use Virtual +> Machine Manager (virt-manager.org) for my interface to the VM and it +> does the startup. The error shows up when I start the VM. +In this case you should be able to attach domain xml. (View->Details->Overview->XML) + +Also try and see if the following patch helps: +https://<email address hidden>/T/#md70161e63276e9d5b6fd50fd835d2e62895810b8 + + + +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. + +On Wed, 14 Apr 2021 19:40:36 -0000 +Ed Davison <email address hidden> 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. + + + +Sorry, this has not recurred since you asked for the stack trace. Not sure what "fixed" it. Closing the bug. + +I guess I should say, you may close the bug. + +This was the fix: +https://gitlab.com/qemu-project/qemu/-/commit/bb9feea43179ef8aba2 + |