qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Crash when booting KDE Neon using qxl-vga


From: Leonardo Soares Müller
Subject: Re: [Qemu-devel] Crash when booting KDE Neon using qxl-vga
Date: Fri, 1 Feb 2019 17:57:57 +0000

Mageia 7 guest is crashing too. The command line:

qemu-system-x86_64 \
-name "Mageia 7" -k pt-br -nodefaults -accel kvm -cpu host -smp
cores=2,threads=1 -m 1G \
-device qxl-vga,xres=1366,yres=768 \
-device qemu-xhci,id=xhcihub -device usb-audio,id=usbaudio,buffer=6144  \
-device usb-tablet,id=usbtablet -bios /usr/share/ovmf/OVMF.fd -display
gtk,gl=on \
-drive if=virtio,file=mageia7.qcow2 \
-monitor vc -serial vc -cdrom "Mageia-7-beta1-Live-Xfce-x86_64.iso" \
-machine kernel_irqchip=on -global PIIX4_PM.disable_s3=1 -global
PIIX4_PM.disable_s4=1 -M pc,usb=true \
-netdev user,id=net0 -device e1000,netdev=net0,addr=8

It seems that:

-drive if=virtio,file=

is the cause of this. Replacing it with -hda makes the Mageia 7 guest
work normally. KDE Neon guest still crashes because of the other problem.

(gdb) bt
#0  0x00007ffff0371e97 in __GI_raise (address@hidden) at
../sysdeps/unix/sysv/linux/raise.c:51
#1  0x00007ffff0373801 in __GI_abort () at abort.c:79
#2  0x000055555589eac9 in kvm_mem_ioeventfd_add
(listener=0x555556b4ffd8, section=0x7fffcdf23a90, match_data=false,
data=0, e=0x555557b51658) at
/home/usuario/Documentos/qemu/accel/kvm/kvm-all.c:866
#3  0x000055555588300a in address_space_add_del_ioeventfds
(as=0x5555567e5a00 <address_space_memory>, fds_new=0x7fffc4560fc0,
fds_new_nb=1, fds_old=0x0, fds_old_nb=0) at
/home/usuario/Documentos/qemu/memory.c:793
#4  0x00005555558832f4 in address_space_update_ioeventfds
(as=0x5555567e5a00 <address_space_memory>) at
/home/usuario/Documentos/qemu/memory.c:843
#5  0x000055555588415b in memory_region_transaction_commit () at
/home/usuario/Documentos/qemu/memory.c:1094
#6  0x00005555558871c8 in memory_region_add_eventfd (mr=0x555557b3fa00,
addr=0, size=0, match_data=false, data=0, e=0x555557b51658) at
/home/usuario/Documentos/qemu/memory.c:2303
#7  0x0000555555c26cd0 in virtio_pci_ioeventfd_assign (d=0x555557b3ed30,
notifier=0x555557b51658, n=0, assign=true) at hw/virtio/virtio-pci.c:243
#8  0x0000555555c24dd5 in virtio_bus_set_host_notifier
(bus=0x555557b46e28, n=0, assign=true) at hw/virtio/virtio-bus.c:283
#9  0x00005555558ce648 in virtio_blk_data_plane_start
(vdev=0x555557b46ea0) at
/home/usuario/Documentos/qemu/hw/block/dataplane/virtio-blk.c:200
#10 0x0000555555c24af2 in virtio_bus_start_ioeventfd
(bus=0x555557b46e28) at hw/virtio/virtio-bus.c:223
#11 0x0000555555c26e57 in virtio_pci_start_ioeventfd
(proxy=0x555557b3ed30) at hw/virtio/virtio-pci.c:282
#12 0x0000555555c29285 in virtio_pci_common_write
(opaque=0x555557b3ed30, addr=20, val=15, size=1) at
hw/virtio/virtio-pci.c:1233
#13 0x0000555555881ebd in memory_region_write_accessor
(mr=0x555557b3f700, addr=20, value=0x7fffcdf23f38, size=1, shift=0,
mask=255, attrs=...) at /home/usuario/Documentos/qemu/memory.c:502
#14 0x00005555558820cd in access_with_adjusted_size (addr=20,
value=0x7fffcdf23f38, size=1, access_size_min=1, access_size_max=4,
access_fn=
    0x555555881dd4 <memory_region_write_accessor>, mr=0x555557b3f700,
attrs=...) at /home/usuario/Documentos/qemu/memory.c:568
#15 0x0000555555885100 in memory_region_dispatch_write
(mr=0x555557b3f700, addr=20, data=15, size=1, attrs=...) at
/home/usuario/Documentos/qemu/memory.c:1499
#16 0x000055555581bca9 in flatview_write_continue (fv=0x7fffb8000fc0,
addr=34644951060, attrs=..., buf=0x7ffff7ff4028 <error: Não é possível
acessar a memória no endereço 0x7ffff7ff4028>, len=1, addr1=20, l=1,
mr=0x555557b3f700) at /home/usuario/Documentos/qemu/exec.c:3234
#17 0x000055555581bdf3 in flatview_write (fv=0x7fffb8000fc0,
addr=34644951060, attrs=..., buf=0x7ffff7ff4028 <error: Não é possível
acessar a memória no endereço 0x7ffff7ff4028>, len=1)
    at /home/usuario/Documentos/qemu/exec.c:3273
#18 0x000055555581c0f9 in address_space_write (as=0x5555567e5a00
<address_space_memory>, addr=34644951060, attrs=..., buf=0x7ffff7ff4028
<error: Não é possível acessar a memória no endereço 0x7ffff7ff4028>,
len=1) at /home/usuario/Documentos/qemu/exec.c:3363
#19 0x000055555581c14a in address_space_rw (as=0x5555567e5a00
<address_space_memory>, addr=34644951060, attrs=..., buf=0x7ffff7ff4028
<error: Não é possível acessar a memória no endereço 0x7ffff7ff4028>,
len=1, is_write=true) at /home/usuario/Documentos/qemu/exec.c:3374
#20 0x00005555558a146f in kvm_cpu_exec (cpu=0x555556bcc410) at
/home/usuario/Documentos/qemu/accel/kvm/kvm-all.c:2031
#21 0x0000555555865a3e in qemu_kvm_cpu_thread_fn (arg=0x555556bcc410) at
/home/usuario/Documentos/qemu/cpus.c:1281
#22 0x0000555555e1ba02 in qemu_thread_start (args=0x555556bedaa0) at
util/qemu-thread-posix.c:502
#23 0x00007ffff072b6db in start_thread (arg=0x7fffcdf27700) at
pthread_create.c:463
#24 0x00007ffff045488f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


reply via email to

[Prev in Thread] Current Thread [Next in Thread]