From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Leonardo Soares Müller" <leozinho29_eu@hotmail.com>
Cc: "kraxel@redhat.com" <kraxel@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Crash when booting KDE Neon using qxl-vga
Date: Thu, 14 Feb 2019 10:42:26 +0000 [thread overview]
Message-ID: <20190214104225.GB2617@work-vm> (raw)
In-Reply-To: <RO1P152MB148380E67D93DAB6C8093EFE97920@RO1P152MB1483.LAMP152.PROD.OUTLOOK.COM>
* Leonardo Soares Müller (leozinho29_eu@hotmail.com) wrote:
> I can confirm this, KDE Neon using the command line similar to yours
> crashes QEMU to me too. I will test with Mageia 7 later to see if it
> behaves differently.
>
> But this is a completely different crash. This crash is happening
> earlier, what I reported first is a crash when the login screen should
> load, this is happening earlier on boot.
>
> The command line I used this time:
>
> qemu-system-x86_64 -M pc,accel=kvm -smp 3 -m 4G -drive
> if=virtio,file=neonbroken.qcow2 -vga qxl -bios /usr/share/ovmf/OVMF.fd
Yes, this was: https://bugs.launchpad.net/qemu/+bug/1813940
Dave
> The backtrace:
>
> (gdb) bt
> #0 0x00007ffff0371e97 in __GI_raise (sig=sig@entry=6) 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=0x555556a1fdc8, section=0x7fffc7ffba90, match_data=false,
> data=0, e=0x5555578c7fc8) 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=0x7fffbc000d30,
> 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=0x5555578b6420,
> addr=0, size=0, match_data=false, data=0, e=0x5555578c7fc8) at
> /home/usuario/Documentos/qemu/memory.c:2303
> #7 0x0000555555c26cd0 in virtio_pci_ioeventfd_assign (d=0x5555578b5750,
> notifier=0x5555578c7fc8, n=0, assign=true) at hw/virtio/virtio-pci.c:243
> #8 0x0000555555c24dd5 in virtio_bus_set_host_notifier
> (bus=0x5555578bd848, n=0, assign=true) at hw/virtio/virtio-bus.c:283
> #9 0x00005555558ce648 in virtio_blk_data_plane_start
> (vdev=0x5555578bd8c0) at
> /home/usuario/Documentos/qemu/hw/block/dataplane/virtio-blk.c:200
> #10 0x0000555555c24af2 in virtio_bus_start_ioeventfd
> (bus=0x5555578bd848) at hw/virtio/virtio-bus.c:223
> #11 0x0000555555c26e57 in virtio_pci_start_ioeventfd
> (proxy=0x5555578b5750) at hw/virtio/virtio-pci.c:282
> #12 0x0000555555c29285 in virtio_pci_common_write
> (opaque=0x5555578b5750, addr=20, val=15, size=1) at
> hw/virtio/virtio-pci.c:1233
> #13 0x0000555555881ebd in memory_region_write_accessor
> (mr=0x5555578b6120, addr=20, value=0x7fffc7ffbf38, 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=0x7fffc7ffbf38, size=1, access_size_min=1, access_size_max=4,
> access_fn=0x555555881dd4 <memory_region_write_accessor>,
> mr=0x5555578b6120, attrs=...) at /home/usuario/Documentos/qemu/memory.c:568
> #15 0x0000555555885100 in memory_region_dispatch_write
> (mr=0x5555578b6120, addr=20, data=15, size=1, attrs=...) at
> /home/usuario/Documentos/qemu/memory.c:1499
> #16 0x000055555581bca9 in flatview_write_continue (fv=0x7fffcc50f4f0,
> addr=34359738388, attrs=..., buf=0x7ffff7fee028 "\017", len=1, addr1=20,
> l=1, mr=0x5555578b6120) at /home/usuario/Documentos/qemu/exec.c:3234
> #17 0x000055555581bdf3 in flatview_write (fv=0x7fffcc50f4f0,
> addr=34359738388, attrs=..., buf=0x7ffff7fee028 "\017", len=1) at
> /home/usuario/Documentos/qemu/exec.c:3273
> #18 0x000055555581c0f9 in address_space_write (as=0x5555567e5a00
> <address_space_memory>, addr=34359738388, attrs=..., buf=0x7ffff7fee028
> "\017", len=1) at /home/usuario/Documentos/qemu/exec.c:3363
> #19 0x000055555581c14a in address_space_rw (as=0x5555567e5a00
> <address_space_memory>, addr=34359738388, attrs=..., buf=0x7ffff7fee028
> "\017", len=1, is_write=true) at /home/usuario/Documentos/qemu/exec.c:3374
> #20 0x00005555558a146f in kvm_cpu_exec (cpu=0x555556afe140) at
> /home/usuario/Documentos/qemu/accel/kvm/kvm-all.c:2031
> #21 0x0000555555865a3e in qemu_kvm_cpu_thread_fn (arg=0x555556afe140) at
> /home/usuario/Documentos/qemu/cpus.c:1281
> #22 0x0000555555e1ba02 in qemu_thread_start (args=0x555556b20440) at
> util/qemu-thread-posix.c:502
> #23 0x00007ffff072b6db in start_thread (arg=0x7fffc7fff700) at
> pthread_create.c:463
> #24 0x00007ffff045488f in clone () at
> ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
>
>
> Às 11:36 de 01/02/2019, Dr. David Alan Gilbert escreveu:
> >
> > Hmm, I'm also getting a crash, but I think it's very different from
> > yours:
> >
> > ./x86_64-softmmu/qemu-system-x86_64 -M pc,accel=kvm -smp 3 -m 8G -cdrom /home/vmimages/neon-useredition-current.iso -drive if=virtio,file=/home/vmimages/kde-neon.qcow2 -vga qxl
> >
> > kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device
> > Aborted (core dumped)
> > --
> > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> >
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2019-02-14 10:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 23:44 [Qemu-devel] Crash when booting KDE Neon using qxl-vga Leonardo Soares Müller
2019-01-28 12:13 ` Dr. David Alan Gilbert
2019-01-28 17:14 ` Leonardo Soares Müller
2019-01-28 17:35 ` Dr. David Alan Gilbert
2019-01-28 19:48 ` Leonardo Soares Müller
2019-02-01 13:36 ` Dr. David Alan Gilbert
2019-02-01 15:39 ` Leonardo Soares Müller
2019-02-01 20:28 ` Dr. David Alan Gilbert
2019-02-01 22:39 ` Leonardo Soares Müller
2019-02-14 10:42 ` Dr. David Alan Gilbert [this message]
2019-02-01 17:57 ` Leonardo Soares Müller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190214104225.GB2617@work-vm \
--to=dgilbert@redhat.com \
--cc=kraxel@redhat.com \
--cc=leozinho29_eu@hotmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).