* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
@ 2018-04-25 6:17 ` ChristianEhrhardt
2018-04-25 6:18 ` ChristianEhrhardt
` (24 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: ChristianEhrhardt @ 2018-04-25 6:17 UTC (permalink / raw)
To: qemu-devel
Thanks Leonardo, with that confirmed:
- not dependent on the guest distribution
- affecting latest upstream
- good logs on the crash
The videos are not needed but nice to proove your case (just as my pre-
analysis of the code path is nice but likely not useful to a developer
that regularly works on that code sections).
Overall this should really be ready for upstreams attention, I added a
Qemu task which will auto mirror this to the Mailing list.
** Also affects: qemu
Importance: Undecided
Status: New
** Changed in: qemu (Ubuntu)
Status: Incomplete => Confirmed
** Information type changed from Private to Public
--
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:
New
Status in qemu package in Ubuntu:
Confirmed
Bug description:
When using qemu-system-x86_64 with the option -vga qxl, it crashes.
The easiest way to crash it is by trying to change the guest's
resolution. However, the system may randomly crash too, not happening
only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
2018-04-25 6:17 ` [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl ChristianEhrhardt
@ 2018-04-25 6:18 ` ChristianEhrhardt
2018-06-29 19:12 ` Leonardo Müller
` (23 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: ChristianEhrhardt @ 2018-04-25 6:18 UTC (permalink / raw)
To: qemu-devel
The bug traces so far had no private information, so I opened up the
state to be visible to everyone.
--
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:
New
Status in qemu package in Ubuntu:
Confirmed
Bug description:
When using qemu-system-x86_64 with the option -vga qxl, it crashes.
The easiest way to crash it is by trying to change the guest's
resolution. However, the system may randomly crash too, not happening
only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
2018-04-25 6:17 ` [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl ChristianEhrhardt
2018-04-25 6:18 ` ChristianEhrhardt
@ 2018-06-29 19:12 ` Leonardo Müller
2018-07-07 8:41 ` Apport retracing service
` (22 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Leonardo Müller @ 2018-06-29 19:12 UTC (permalink / raw)
To: qemu-devel
QEMU from git apparently is fixed, but Ubuntu's version is still
problematic.
Using an Xubuntu 18.04 guest, it's possible to reproduce the crash
using:
while true ; do xrandr --output Virtual-0 --mode 640x480 ; sleep 1 ;
xrandr --output Virtual-0 --mode 1280x720 ; sleep 1 ; xrandr --output
Virtual-0 --mode 1920x1080 ; sleep 1 ; done
In less than 20 seconds the guest crash with:
(process:16447): Spice-CRITICAL **: 15:34:52.047: display-channel.c:2035:display_channel_update: condition `display_channel_validate_surface(display, surface_id)' failed
Abortado (imagem do núcleo gravada)
--
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:
New
Status in qemu package in Ubuntu:
Confirmed
Bug description:
When using qemu-system-x86_64 with the option -vga qxl, it crashes.
The easiest way to crash it is by trying to change the guest's
resolution. However, the system may randomly crash too, not happening
only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (2 preceding siblings ...)
2018-06-29 19:12 ` Leonardo Müller
@ 2018-07-07 8:41 ` Apport retracing service
2018-07-16 13:29 ` Christian Ehrhardt
` (21 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Apport retracing service @ 2018-07-07 8:41 UTC (permalink / raw)
To: qemu-devel
** Tags added: cosmic
--
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:
New
Status in qemu package in Ubuntu:
Confirmed
Bug description:
When using qemu-system-x86_64 with the option -vga qxl, it crashes.
The easiest way to crash it is by trying to change the guest's
resolution. However, the system may randomly crash too, not happening
only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (3 preceding siblings ...)
2018-07-07 8:41 ` Apport retracing service
@ 2018-07-16 13:29 ` Christian Ehrhardt
2018-07-16 13:30 ` Christian Ehrhardt
` (20 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Christian Ehrhardt @ 2018-07-16 13:29 UTC (permalink / raw)
To: qemu-devel
Very interesting, Still not triggering for me :-/
Could you check if the PPA in [1] (with qemu 2.12 planned for Cosmic) already fixes it for you?
[1]: https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3306/+packages
--
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:
New
Status in qemu package in Ubuntu:
Confirmed
Bug description:
When using qemu-system-x86_64 with the option -vga qxl, it crashes.
The easiest way to crash it is by trying to change the guest's
resolution. However, the system may randomly crash too, not happening
only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (4 preceding siblings ...)
2018-07-16 13:29 ` Christian Ehrhardt
@ 2018-07-16 13:30 ` Christian Ehrhardt
2018-07-16 15:26 ` Leonardo Müller
` (19 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Christian Ehrhardt @ 2018-07-16 13:30 UTC (permalink / raw)
To: qemu-devel
Link is better as https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3306
--
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:
New
Status in qemu package in Ubuntu:
Confirmed
Bug description:
When using qemu-system-x86_64 with the option -vga qxl, it crashes.
The easiest way to crash it is by trying to change the guest's
resolution. However, the system may randomly crash too, not happening
only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (5 preceding siblings ...)
2018-07-16 13:30 ` Christian Ehrhardt
@ 2018-07-16 15:26 ` Leonardo Müller
2018-07-16 16:29 ` Christian Ehrhardt
` (18 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Leonardo Müller @ 2018-07-16 15:26 UTC (permalink / raw)
To: qemu-devel
Unfortunately it did not work, the error is still the same although it
used the GTK interface this time. The command I used was:
$ qemu-system-x86_64 -vga qxl -enable-kvm -cpu host -smp
cores=2,threads=2 -m 2048 -cdrom xubuntu-18.04-desktop-amd64.iso
I have noticed Ubuntu's QEMU and this QEMU don't have the OpenGL option
enabled, may this be related to the issue?
--
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:
New
Status in qemu package in Ubuntu:
Confirmed
Bug description:
When using qemu-system-x86_64 with the option -vga qxl, it crashes.
The easiest way to crash it is by trying to change the guest's
resolution. However, the system may randomly crash too, not happening
only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (6 preceding siblings ...)
2018-07-16 15:26 ` Leonardo Müller
@ 2018-07-16 16:29 ` Christian Ehrhardt
2018-07-16 17:26 ` Leonardo Müller
` (17 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Christian Ehrhardt @ 2018-07-16 16:29 UTC (permalink / raw)
To: qemu-devel
Yeah we switched to gtk.
With OpenGL which do you mean - the virtgl based support or some other config option?
Since it still fails to reproduce for me, but you already have a self build qemu that is good.
Could you based on this build 2.12 from source as well and confirm that it fails.
If it does you could bisect from 2.12 to master what fixed it so that we can consider that patch.
Otherwise if 2.12 from source in your own build works lets take a look at the build options that you mentioned.
--
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:
New
Status in qemu package in Ubuntu:
Confirmed
Bug description:
When using qemu-system-x86_64 with the option -vga qxl, it crashes.
The easiest way to crash it is by trying to change the guest's
resolution. However, the system may randomly crash too, not happening
only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (7 preceding siblings ...)
2018-07-16 16:29 ` Christian Ehrhardt
@ 2018-07-16 17:26 ` Leonardo Müller
2018-07-16 19:38 ` Leonardo Müller
` (16 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Leonardo Müller @ 2018-07-16 17:26 UTC (permalink / raw)
To: qemu-devel
I meant the option --enable-opengl and, for old versions, --enable-gtk-
gl. I know it is required to use virtual machines using Intel GVT-g with
dma-buf, and is a option strangely absent from QEMU configuration from
Ubuntu's build. Without it, virgl fails too, making virt-manager have an
option that does not work (under Spice Display, OpenGL option does not
work).
The 2.12 build does crash when tested. That while loop is pretty
efficient to trigger it. The git version can keep running it for hours
straight with no problem, while the problematic versions crash in
seconds.
As QEMU configuration is a result mixed between packages found
automatically and those manually set by me, here is the configure
command and its results from my QEMU build:
https://paste.ubuntu.com/p/z9vnFdTnkD/
Please note that I had no need to build other targets for my use, so the
configuration is much smaller than the one used by Ubuntu's QEMU.
--
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:
New
Status in qemu package in Ubuntu:
Confirmed
Bug description:
When using qemu-system-x86_64 with the option -vga qxl, it crashes.
The easiest way to crash it is by trying to change the guest's
resolution. However, the system may randomly crash too, not happening
only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (8 preceding siblings ...)
2018-07-16 17:26 ` Leonardo Müller
@ 2018-07-16 19:38 ` Leonardo Müller
2018-07-17 9:48 ` Christian Ehrhardt
` (15 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Leonardo Müller @ 2018-07-16 19:38 UTC (permalink / raw)
To: qemu-devel
The bisect is done and this is the result:
5bd5c27c7d284d01477c5cc022ce22438c46bf9f is the first new commit
commit 5bd5c27c7d284d01477c5cc022ce22438c46bf9f
Author: Gerd Hoffmann <kraxel@redhat.com>
Date: Fri Apr 27 13:55:28 2018 +0200
qxl: fix local renderer crash
Make sure we only ask the spice local renderer for display updates in
case we have a valid primary surface. Without that spice is confused
and throws errors in case a display update request (triggered by
screendump for example) happens in parallel to a mode switch and hits
the race window where the old primary surface is gone and the new isn't
establisted yet.
Cc: qemu-stable@nongnu.org
Fixes: https://bugzilla.redhat.com//show_bug.cgi?id=1567733
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Message-id: 20180427115528.345-1-kraxel@redhat.com
:040000 040000 ed86f864314483660b3c2abe045361ae7c98a5dc
f0d55b3e98dd0864d6686fba052d83ae5545d007 M hw
** Bug watch added: bugzilla.redhat.com// #1567733
https://bugzilla.redhat.com//show_bug.cgi?id=1567733
--
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:
New
Status in qemu package in Ubuntu:
Confirmed
Bug description:
When using qemu-system-x86_64 with the option -vga qxl, it crashes.
The easiest way to crash it is by trying to change the guest's
resolution. However, the system may randomly crash too, not happening
only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (9 preceding siblings ...)
2018-07-16 19:38 ` Leonardo Müller
@ 2018-07-17 9:48 ` Christian Ehrhardt
2018-07-19 6:28 ` Christian Ehrhardt
` (14 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Christian Ehrhardt @ 2018-07-17 9:48 UTC (permalink / raw)
To: qemu-devel
Nice, thanks Leonardo for the Bisect - lets call upstream Fixed
Committed then (as there is no 2.13 released yet).
For the separate gl discussion feel free to subscribe/chime in on bug
1657409
Currently 2.12 is on its way into Cosmic.
I'll add and test that patch afterwards, it looks small and safe to me.
** Changed in: qemu
Status: New => Fix Committed
** Changed in: qemu (Ubuntu)
Status: Confirmed => Triaged
** Tags added: qemu-18.10 server-next
--
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 Committed
Status in qemu package in Ubuntu:
Triaged
Bug description:
When using qemu-system-x86_64 with the option -vga qxl, it crashes.
The easiest way to crash it is by trying to change the guest's
resolution. However, the system may randomly crash too, not happening
only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (10 preceding siblings ...)
2018-07-17 9:48 ` Christian Ehrhardt
@ 2018-07-19 6:28 ` Christian Ehrhardt
2018-07-20 7:37 ` Launchpad Bug Tracker
` (13 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Christian Ehrhardt @ 2018-07-19 6:28 UTC (permalink / raw)
To: qemu-devel
** Also affects: qemu (Ubuntu Bionic)
Importance: Undecided
Status: New
--
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 Committed
Status in qemu package in Ubuntu:
Triaged
Status in qemu source package in Bionic:
New
Bug description:
When using qemu-system-x86_64 with the option -vga qxl, it crashes.
The easiest way to crash it is by trying to change the guest's
resolution. However, the system may randomly crash too, not happening
only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (11 preceding siblings ...)
2018-07-19 6:28 ` Christian Ehrhardt
@ 2018-07-20 7:37 ` Launchpad Bug Tracker
2018-08-20 8:28 ` Christian Ehrhardt
` (12 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Launchpad Bug Tracker @ 2018-07-20 7:37 UTC (permalink / raw)
To: qemu-devel
This bug was fixed in the package qemu - 1:2.12+dfsg-3ubuntu3
---------------
qemu (1:2.12+dfsg-3ubuntu3) cosmic; urgency=medium
* d/p/lp-1755912-qxl-fix-local-renderer-crash.patch: Fix an issue triggered
by migrations with UI frontends or frequent guest resolution changes
(LP: #1755912)
-- Christian Ehrhardt <christian.ehrhardt@canonical.com> Thu, 19 Jul
2018 08:26:52 +0200
** Changed in: qemu (Ubuntu)
Status: Triaged => 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 Committed
Status in qemu package in Ubuntu:
Fix Released
Status in qemu source package in Bionic:
New
Bug description:
When using qemu-system-x86_64 with the option -vga qxl, it crashes.
The easiest way to crash it is by trying to change the guest's
resolution. However, the system may randomly crash too, not happening
only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (12 preceding siblings ...)
2018-07-20 7:37 ` Launchpad Bug Tracker
@ 2018-08-20 8:28 ` Christian Ehrhardt
2018-08-21 6:28 ` Thomas Huth
` (11 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Christian Ehrhardt @ 2018-08-20 8:28 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu (Ubuntu Bionic)
Status: New => Triaged
--
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 Committed
Status in qemu package in Ubuntu:
Fix Released
Status in qemu source package in Bionic:
Triaged
Bug description:
When using qemu-system-x86_64 with the option -vga qxl, it crashes.
The easiest way to crash it is by trying to change the guest's
resolution. However, the system may randomly crash too, not happening
only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (13 preceding siblings ...)
2018-08-20 8:28 ` Christian Ehrhardt
@ 2018-08-21 6:28 ` Thomas Huth
2018-08-21 9:37 ` Christian Ehrhardt
` (10 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Thomas Huth @ 2018-08-21 6:28 UTC (permalink / raw)
To: qemu-devel
** Changed in: qemu
Status: Fix Committed => 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:
Triaged
Bug description:
When using qemu-system-x86_64 with the option -vga qxl, it crashes.
The easiest way to crash it is by trying to change the guest's
resolution. However, the system may randomly crash too, not happening
only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (14 preceding siblings ...)
2018-08-21 6:28 ` Thomas Huth
@ 2018-08-21 9:37 ` Christian Ehrhardt
2018-08-22 6:24 ` Christian Ehrhardt
` (9 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Christian Ehrhardt @ 2018-08-21 9:37 UTC (permalink / raw)
To: qemu-devel
Working on Bionic SRu prep in https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3367/+packages
--
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:
Triaged
Bug description:
When using qemu-system-x86_64 with the option -vga qxl, it crashes.
The easiest way to crash it is by trying to change the guest's
resolution. However, the system may randomly crash too, not happening
only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (15 preceding siblings ...)
2018-08-21 9:37 ` Christian Ehrhardt
@ 2018-08-22 6:24 ` Christian Ehrhardt
2018-08-27 14:29 ` Łukasz Zemczak
` (8 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Christian Ehrhardt @ 2018-08-22 6:24 UTC (permalink / raw)
To: qemu-devel
** Description changed:
- When using qemu-system-x86_64 with the option -vga qxl, it crashes. The
- easiest way to crash it is by trying to change the guest's resolution.
- However, the system may randomly crash too, not happening only when
- changing resolution. Here is the terminal output of one of these random
- crashes:
+ [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=qemu.git;a=commit;h=5bd5c27c7d284d01477c5cc022ce22438c46bf9f
+ 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=2,threads=2 -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 Virtual-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 easiest way to crash it is by trying to change the guest's resolution. However, the system may randomly crash too, not happening only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
- Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
- Specify the 'raw' format explicitly to remove the restrictions.
+ Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
+ Specify the 'raw' format 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-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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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
+ () 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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80UG
dmi.product.version: Lenovo ideapad 310-14ISK
dmi.sys.vendor: LENOVO
--
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:
Triaged
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=qemu.git;a=commit;h=5bd5c27c7d284d01477c5cc022ce22438c46bf9f
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=2,threads=2 -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 Virtual-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 easiest way to crash it is by trying to change the guest's resolution. However, the system may randomly crash too, not happening only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (16 preceding siblings ...)
2018-08-22 6:24 ` Christian Ehrhardt
@ 2018-08-27 14:29 ` Łukasz Zemczak
2018-08-28 2:46 ` Leonardo Müller
` (7 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Łukasz Zemczak @ 2018-08-27 14:29 UTC (permalink / raw)
To: qemu-devel
Hello Leonardo, or anyone else affected,
Accepted qemu into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:2.11+dfsg-
1ubuntu7.5 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance!
** Changed in: qemu (Ubuntu Bionic)
Status: Triaged => Fix Committed
** Tags added: verification-needed verification-needed-bionic
--
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 Committed
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=qemu.git;a=commit;h=5bd5c27c7d284d01477c5cc022ce22438c46bf9f
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=2,threads=2 -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 Virtual-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 easiest way to crash it is by trying to change the guest's resolution. However, the system may randomly crash too, not happening only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (17 preceding siblings ...)
2018-08-27 14:29 ` Łukasz Zemczak
@ 2018-08-28 2:46 ` Leonardo Müller
2018-08-28 8:11 ` Christian Ehrhardt
` (6 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Leonardo Müller @ 2018-08-28 2:46 UTC (permalink / raw)
To: qemu-devel
Thank you for the effort to backport this bug fix, I have tested the
proposed version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.5) and the crash
when changing resolution is no longer happening. Unfortunately, after
some time (about 10 minutes, much longer than without this fix), the
guest freezes.
I reported that in https://bugs.launchpad.net/qemu/+bug/1787070
I'll change the tag to verification-done-bionic, as this particular
issue was corrected. The other issue still exists in QEMU upstream.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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 Committed
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=qemu.git;a=commit;h=5bd5c27c7d284d01477c5cc022ce22438c46bf9f
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=2,threads=2 -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 Virtual-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 easiest way to crash it is by trying to change the guest's resolution. However, the system may randomly crash too, not happening only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (18 preceding siblings ...)
2018-08-28 2:46 ` Leonardo Müller
@ 2018-08-28 8:11 ` Christian Ehrhardt
2018-08-28 9:08 ` Christian Ehrhardt
` (5 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Christian Ehrhardt @ 2018-08-28 8:11 UTC (permalink / raw)
To: qemu-devel
Note: The code change already passed the general regression checks on
the identical content against a PPA (Also on the weekend prior to the
full maturing period I'll have another automated run on proposed).
--
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 Committed
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=qemu.git;a=commit;h=5bd5c27c7d284d01477c5cc022ce22438c46bf9f
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=2,threads=2 -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 Virtual-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 easiest way to crash it is by trying to change the guest's resolution. However, the system may randomly crash too, not happening only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (19 preceding siblings ...)
2018-08-28 8:11 ` Christian Ehrhardt
@ 2018-08-28 9:08 ` Christian Ehrhardt
2018-08-28 9:10 ` Christian Ehrhardt
` (4 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Christian Ehrhardt @ 2018-08-28 9:08 UTC (permalink / raw)
To: qemu-devel
Running the Bionic ISO like:
$ qemu-system-x86_64 -cpu host -smp cores=4,threads=2 -boot d -m 2048 -enable-kvm -vga qxl -vnc :21 -cdrom ubuntu-18.04-desktop-amd64.iso
Attaching like:
$ vncviewer FullColor=1 AutoSelect=0 10.245.168.42:5921
(alternatives on tigervnc)
Well for me it had "-k de" as well :-)
Then boot into the "try Ubuntu" live CD mode.
There opened a terminal to loop on xrandr.
Running the loop of above in that guest to crash it after a while.
Upgrade to proposed:
$ sudo apt install qemu-system-x86=1:2.11+dfsg-1ubuntu7.5
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
samba vde2 qemu-block-extra sgabios ovmf
The following packages will be upgraded:
qemu-system-x86
1 upgraded, 0 newly installed, 0 to remove and 16 not upgraded.
Need to get 5.168 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 qemu-system-x86 amd64 1:2.11+dfsg-1ubuntu7.5 [5.168 kB]
Fetched 5.168 kB in 1s (7.666 kB/s)
(Reading database ... 127990 files and directories currently installed.)
Preparing to unpack .../qemu-system-x86_1%3a2.11+dfsg-1ubuntu7.5_amd64.deb ...
Unpacking qemu-system-x86 (1:2.11+dfsg-1ubuntu7.5) over (1:2.11+dfsg-1ubuntu7.4) ...
Setting up qemu-system-x86 (1:2.11+dfsg-1ubuntu7.5) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Running the loop again with the same setup - no crash in 15 minutes - assume that means good now.
I'd be glad about someone else checking the result as well, best someone formerly affected by it.
(and having a tick in the eye for seeing my right screen change sizes and flicker all the time)
Setting verified
** Tags removed: verification-needed
** Tags added: verification-done
--
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 Committed
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=qemu.git;a=commit;h=5bd5c27c7d284d01477c5cc022ce22438c46bf9f
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=2,threads=2 -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 Virtual-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 easiest way to crash it is by trying to change the guest's resolution. However, the system may randomly crash too, not happening only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (20 preceding siblings ...)
2018-08-28 9:08 ` Christian Ehrhardt
@ 2018-08-28 9:10 ` Christian Ehrhardt
2018-08-28 9:11 ` Christian Ehrhardt
` (3 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Christian Ehrhardt @ 2018-08-28 9:10 UTC (permalink / raw)
To: qemu-devel
Thanks Leonardo for your check as well!
I agree that this particular issue here is fixed as we hoped.
The other one with the freeze did not occur for me, you might open another bug if you have any pointers how we could go on on this.
--
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 Committed
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=qemu.git;a=commit;h=5bd5c27c7d284d01477c5cc022ce22438c46bf9f
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=2,threads=2 -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 Virtual-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 easiest way to crash it is by trying to change the guest's resolution. However, the system may randomly crash too, not happening only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (21 preceding siblings ...)
2018-08-28 9:10 ` Christian Ehrhardt
@ 2018-08-28 9:11 ` Christian Ehrhardt
2018-08-28 9:26 ` Christian Ehrhardt
` (2 subsequent siblings)
25 siblings, 0 replies; 26+ messages in thread
From: Christian Ehrhardt @ 2018-08-28 9:11 UTC (permalink / raw)
To: qemu-devel
Arr reading is hard today, you had the other bug open already ... grml
:-)
Never the less - This bug here is fixed in the proposed version and for
now that is the important part.
--
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 Committed
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=qemu.git;a=commit;h=5bd5c27c7d284d01477c5cc022ce22438c46bf9f
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=2,threads=2 -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 Virtual-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 easiest way to crash it is by trying to change the guest's resolution. However, the system may randomly crash too, not happening only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (22 preceding siblings ...)
2018-08-28 9:11 ` Christian Ehrhardt
@ 2018-08-28 9:26 ` Christian Ehrhardt
2018-09-06 8:57 ` [Qemu-devel] [Bug 1755912] Update Released Łukasz Zemczak
2018-09-06 9:07 ` [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl Launchpad Bug Tracker
25 siblings, 0 replies; 26+ messages in thread
From: Christian Ehrhardt @ 2018-08-28 9:26 UTC (permalink / raw)
To: qemu-devel
Subscribed there as well now to stay on top of it if upstream gets to a
conclusion.
--
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 Committed
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=qemu.git;a=commit;h=5bd5c27c7d284d01477c5cc022ce22438c46bf9f
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=2,threads=2 -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 Virtual-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 easiest way to crash it is by trying to change the guest's resolution. However, the system may randomly crash too, not happening only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Update Released
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (23 preceding siblings ...)
2018-08-28 9:26 ` Christian Ehrhardt
@ 2018-09-06 8:57 ` Łukasz Zemczak
2018-09-06 9:07 ` [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl Launchpad Bug Tracker
25 siblings, 0 replies; 26+ messages in thread
From: Łukasz Zemczak @ 2018-09-06 8:57 UTC (permalink / raw)
To: qemu-devel
The verification of the Stable Release Update for qemu has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
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=qemu.git;a=commit;h=5bd5c27c7d284d01477c5cc022ce22438c46bf9f
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=2,threads=2 -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 Virtual-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 easiest way to crash it is by trying to change the guest's resolution. However, the system may randomly crash too, not happening only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
* [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
` (24 preceding siblings ...)
2018-09-06 8:57 ` [Qemu-devel] [Bug 1755912] Update Released Łukasz Zemczak
@ 2018-09-06 9:07 ` Launchpad Bug Tracker
25 siblings, 0 replies; 26+ messages in thread
From: Launchpad Bug Tracker @ 2018-09-06 9:07 UTC (permalink / raw)
To: qemu-devel
This bug was fixed in the package qemu - 1:2.11+dfsg-1ubuntu7.5
---------------
qemu (1:2.11+dfsg-1ubuntu7.5) bionic; urgency=medium
[Christian Ehrhardt]
* d/p/lp-1755912-qxl-fix-local-renderer-crash.patch: Fix an issue triggered
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 <christian.ehrhardt@canonical.com> Tue, 21 Aug
2018 11:25:45 +0200
** Changed in: qemu (Ubuntu Bionic)
Status: Fix Committed => 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=qemu.git;a=commit;h=5bd5c27c7d284d01477c5cc022ce22438c46bf9f
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=2,threads=2 -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 Virtual-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 easiest way to crash it is by trying to change the guest's resolution. However, the system may randomly crash too, not happening only when changing resolution. 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=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
WARNING: Image format was not specified for '/dev/sdb' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write operations on block 0 will be restricted.
Specify the 'raw' format 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úcleo 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=2 -m 512 -enable-kvm -cpu host -vga qxl -nodefaults -netdev user,id=hostnet0 -device virtio-net-pci,id=net0,netdev=hostnet0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
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 bionic on 2017-10-20 (145 days ago)
UserGroups: adm bluetooth cdrom dialout dip disk kvm libvirt lpadmin netdev 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:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10: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
^ permalink raw reply [flat|nested] 26+ messages in thread
end of thread, other threads:[~2018-09-06 9:21 UTC | newest]
Thread overview: 26+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <152106105315.14602.6749093724412548748.malonedeb@chaenomeles.canonical.com>
2018-04-25 6:17 ` [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl ChristianEhrhardt
2018-04-25 6:18 ` ChristianEhrhardt
2018-06-29 19:12 ` Leonardo Müller
2018-07-07 8:41 ` Apport retracing service
2018-07-16 13:29 ` Christian Ehrhardt
2018-07-16 13:30 ` Christian Ehrhardt
2018-07-16 15:26 ` Leonardo Müller
2018-07-16 16:29 ` Christian Ehrhardt
2018-07-16 17:26 ` Leonardo Müller
2018-07-16 19:38 ` Leonardo Müller
2018-07-17 9:48 ` Christian Ehrhardt
2018-07-19 6:28 ` Christian Ehrhardt
2018-07-20 7:37 ` Launchpad Bug Tracker
2018-08-20 8:28 ` Christian Ehrhardt
2018-08-21 6:28 ` Thomas Huth
2018-08-21 9:37 ` Christian Ehrhardt
2018-08-22 6:24 ` Christian Ehrhardt
2018-08-27 14:29 ` Łukasz Zemczak
2018-08-28 2:46 ` Leonardo Müller
2018-08-28 8:11 ` Christian Ehrhardt
2018-08-28 9:08 ` Christian Ehrhardt
2018-08-28 9:10 ` Christian Ehrhardt
2018-08-28 9:11 ` Christian Ehrhardt
2018-08-28 9:26 ` Christian Ehrhardt
2018-09-06 8:57 ` [Qemu-devel] [Bug 1755912] Update Released Łukasz Zemczak
2018-09-06 9:07 ` [Qemu-devel] [Bug 1755912] Re: qemu-system-x86_64 crashed with SIGABRT when using option -vga qxl Launchpad Bug Tracker
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.