From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:47407) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fxqU2-0006ma-3s for qemu-devel@nongnu.org; Thu, 06 Sep 2018 05:21:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fxqTy-000558-0u for qemu-devel@nongnu.org; Thu, 06 Sep 2018 05:21:50 -0400 Received: from indium.canonical.com ([91.189.90.7]:46170) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fxqTx-00051Z-QI for qemu-devel@nongnu.org; Thu, 06 Sep 2018 05:21:45 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1fxqTu-0001HQ-VX for ; Thu, 06 Sep 2018 09:21:42 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id E99B12E80C9 for ; Thu, 6 Sep 2018 09:21:42 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Thu, 06 Sep 2018 09:07:14 -0000 From: Launchpad Bug Tracker <1755912@bugs.launchpad.net> Reply-To: Bug 1755912 <1755912@bugs.launchpad.net> Sender: bounces@canonical.com References: <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com> Message-Id: <153622483731.27367.9749710566555526579.malone@ackee.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu7.5 --------------- qemu (1:2.11+dfsg-1ubuntu7.5) bionic; urgency=3Dmedium [Christian Ehrhardt] * d/p/lp-1755912-qxl-fix-local-renderer-crash.patch: Fix an issue trigger= ed by migrations with UI frontends or frequent guest resolution changes (LP: #1755912) [ Murilo Opsfelder Araujo ] * d/p/ubuntu/target-ppc-extend-eieio-for-POWER9.patch: Backport to extend eieio for POWER9 emulation (LP: #1787408). -- Christian Ehrhardt Tue, 21 Aug 2018 11:25:45 +0200 ** Changed in: qemu (Ubuntu Bionic) Status: Fix Committed =3D> Fix Released -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1755912 Title: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl Status in QEMU: Fix Released Status in qemu package in Ubuntu: Fix Released Status in qemu source package in Bionic: Fix Released Bug description: [Impact] * There are conditions where the vga/qxl driver can crash the qemu = process. * It is like a very complex case of a non initialized var - without the = fix it might try to ask for updates without having a valid primary = surface. * Backport from upstream https://git.qemu.org/?p=3Dqemu.git;a=3Dcommit;h=3D5bd5c27c7d284d01477c5cc= 022ce22438c46bf9f to avoid the crash = [Test Case] * Sometimes booting xubuntu was reported to be enough, at other times it was needed to change resolution a few times to trigger. # get xubuntu iso (actually other UI Isos should do as well) $ qemu-system-x86_64 -vga qxl -enable-kvm -cpu host -smp cores=3D2,thre= ads=3D2 -m 2048 -cdrom xubuntu-18.04-desktop-amd64.iso # If it boots successfully, change resolution until it crashes. $ while true ; do xrandr --output Virtual-0 --mode 640x480 ; sleep 1 ; = xrandr --output Virtual-0 --mode 1280x720 ; sleep 1 ; xrandr --output Virtu= al-0 --mode 1920x1080 ; sleep 1 ; done * Without the fix that will trigger the qemu crash [Regression Potential] * The change "just" adds QXL_MODE_UNDEFINED as one more trigger to leave = the rendering update. That sounds rather safe. But thinking hard on = potential updates I could think of theoretical setups that were in = undefined mode all the time (unlikely or impossible I think) that now = would get no updates anymore. Well I really don't think this is an = issue, but since this section should be open thinking on "potential" = regressions that is what comes to my mind. [Other Info] = * Thanks to Leonardo for most of the bisecting and discussion work! = --- = When using qemu-system-x86_64 with the option -vga qxl, it crashes. The e= asiest way to crash it is by trying to change the guest's resolution. Howev= er, the system may randomly crash too, not happening only when changing res= olution. Here is the terminal output of one of these random crashes: -------- $ qemu-system-x86_64 -hda /dev/sdb -m 2048 -enable-kvm -cpu host -vga qxl= -nodefaults -netdev user,id=3Dhostnet0 -device virtio-net-pci,id=3Dnet0,ne= tdev=3Dhostnet0 WARNING: Image format was not specified for '/dev/sdb' and probing guesse= d raw. =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Automatically detec= ting the format is dangerous for raw images, write operations on block 0 wi= ll be restricted. =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Specify the 'raw' f= ormat explicitly to remove the restrictions. (process:21313): Spice-WARNING **: 16:01:45.759: display- channel.c:2431:display_channel_validate_surface: canvas address is 0x7f8eb948ab18 for 0 (and is NULL) (process:21313): Spice-WARNING **: 16:01:45.759: display- channel.c:2432:display_channel_validate_surface: failed on 0 (process:21313): Spice-CRITICAL **: 16:01:45.759: display-channel.c:2035:= display_channel_update: condition `display_channel_validate_surface(display= , surface_id)' failed Abortado (imagem do n=C3=BAcleo gravada) -------- I was running QEMU as a normal user which is on the groups kvm and disk. Initially I supposed the problem was because I was running QEMU as root, but as a normal user this happens too. I have tested with guests with different Ubuntu version: 18.04, 17.10 and 16.04. It is happening with them all. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: qemu-system-x86 1:2.11+dfsg-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 14 17:13:52 2018 ExecutablePath: /usr/bin/qemu-system-x86_64 InstallationDate: Installed on 2017-06-13 (273 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: LENOVO 80UG ProcCmdline: qemu-system-x86_64 -hda /dev/sdb -smp cpus=3D2 -m 512 -enabl= e-kvm -cpu host -vga qxl -nodefaults -netdev user,id=3Dhostnet0 -device vir= tio-net-pci,id=3Dnet0,netdev=3Dhostnet0 ProcKernelCmdLine: BOOT_IMAGE=3D/boot/vmlinuz-4.15.0-10-generic.efi.signe= d root=3DUUID=3D6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet Signal: 6 SourcePackage: qemu StacktraceTop: =C2=A0() at /usr/lib/x86_64-linux-gnu/libspice-server.so.1 =C2=A0() at /usr/lib/x86_64-linux-gnu/libspice-server.so.1 =C2=A0() at /usr/lib/x86_64-linux-gnu/libspice-server.so.1 =C2=A0() at /usr/lib/x86_64-linux-gnu/libspice-server.so.1 =C2=A0() at /usr/lib/x86_64-linux-gnu/libspice-server.so.1 Title: qemu-system-x86_64 crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2017-10-20 (145 days ago) UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netd= ev plugdev sambashare sudo dmi.bios.date: 07/10/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvr= Lenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct= 10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1755912/+subscriptions