qemu-system-x86_64 crashed with SIGABRT

[Paul White]

I was using GNOME Boxes 3.28 in Ubuntu 18.10 and trying to create an installation of Ubuntu 18.10 from a daily ISO image. The installation froze. After managing to regain control of Boxes I was prompted to report the error.

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: qemu-system-x86 1:2.11+dfsg-1ubuntu10
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.10-0ubuntu3
Architecture: amd64
Date: Fri Jun 8 11:34:38 2018
ExecutablePath: /usr/bin/qemu-system-x86_64
InstallationDate: Installed on 2017-11-07 (213 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND
MachineType: Novatech N350DW
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=3f72e489-d608-42fb-a6f0-e46d2871a35c ro quiet splash vt.handoff=1
Signal: 6
SourcePackage: qemu
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1
 () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1
 () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1
 () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1
 () at /usr/lib/x86_64-linux-gnu/libspice-server.so.1
Title: qemu-system-x86_64 crashed with SIGABRT
UpgradeStatus: Upgraded to cosmic on 2018-02-21 (107 days ago)
UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
dmi.bios.date: 03/10/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.asset.tag: Tag 12345
dmi.board.name: N350DW
dmi.board.vendor: Novatech
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Novatech
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd03/10/2017:svnNovatech:pnN350DW:pvrNotApplicable:rvnNovatech:rnN350DW:rvrNotApplicable:cvnNovatech:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: N350DW
dmi.product.version: Not Applicable
dmi.sys.vendor: Novatech

[Christian Ehrhardt  (paelzer)]

This kind of error is frequent enough to be interesting, but so far lacks a good way to debug.
Since the dumps are not directly leading to a bug a reproducer would be great.

We want to join forces so I have Dup'ed this bug onto the first occurance of that kind.
Please report your new insights there from now on.