From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: kraxel@redhat.com
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Postcopy+spice crash
Date: Fri, 2 Dec 2016 17:44:55 +0000 [thread overview]
Message-ID: <20161202174015.GE15373@work-vm> (raw)
Hi Gerd,
I've got a moderately repeatable crash with spice playing
a video + postcopy. Some of the time I just get a warning
(that I also get in precopy) but sometimes it turns into
a backtrace;
This is:
f24 guest playing youtube fullscreen.
migration between 2.7.0<->current head (had crash both ways)
The warning I get with precopy most of the time is:
./x86_64-softmmu/qemu-system-x86_64:26921): Spice-Warning **: red_memslots.c:94:validate_virt: virtual address out of range
virt=0x7f5397ed002a+0x2925ff31 slot_id=1 group_id=1
slot=0x7f5397c00000-0x7f539bbfe000 delta=0x7f5397c00000
The crash I've had with postcopy is:
red_dispatcher_loadvm_commands:
id 0, group 0, virt start 0, virt end ffffffffffffffff, generation 0, delta 0
id 1, group 1, virt start 7fbe83c00000, virt end 7fbe87bfe000, generation 0, delta 7fbe83c00000
id 2, group 1, virt start 7fbe7fa00000, virt end 7fbe83a00000, generation 0, delta 7fbe7fa00000
(./x86_64-softmmu/qemu-system-x86_64:22376): Spice-CRITICAL **: red_memslots.c:123:get_virt: slot_id 128 too big, addr=8000000000000000
#0 0x00007fc0aa42f49d in read () from /lib64/libpthread.so.0
#1 0x00007fc0a8c36c01 in spice_backtrace_gstack () from /lib64/libspice-server.so.1
#2 0x00007fc0a8c3e4f7 in spice_logv () from /lib64/libspice-server.so.1
#3 0x00007fc0a8c3e655 in spice_log () from /lib64/libspice-server.so.1
#4 0x00007fc0a8bfc6de in get_virt () from /lib64/libspice-server.so.1
#5 0x00007fc0a8bfcb73 in red_get_data_chunks_ptr () from /lib64/libspice-server.so.1
#6 0x00007fc0a8bff3fa in red_get_cursor_cmd () from /lib64/libspice-server.so.1
#7 0x00007fc0a8c0fd79 in handle_dev_loadvm_commands () from /lib64/libspice-server.so.1
#8 0x00007fc0a8bf9523 in dispatcher_handle_recv_read () from /lib64/libspice-server.so.1
#9 0x00007fc0a8c1d5a5 in red_worker_main () from /lib64/libspice-server.so.1
#10 0x00007fc0aa428dc5 in start_thread () from /lib64/libpthread.so.0
#11 0x00007fc0a61786ed in clone () from /lib64/libc.so.6
and:
red_dispatcher_loadvm_commands:
id 0, group 0, virt start 0, virt end ffffffffffffffff, generation 0, delta 0
id 1, group 1, virt start 7f3b93800000, virt end 7f3b977fe000, generation 0, delta 7f3b93800000
id 2, group 1, virt start 7f3b8f400000, virt end 7f3b93400000, generation 0, delta 7f3b8f400000
(/opt/qemu/v2.7.0/bin/qemu-system-x86_64:41053): Spice-CRITICAL **: red_memslots.c:123:get_virt: slot_id 80 too big, addr=5000000000000000
I'm using:
spice-server-devel-0.12.4-19.el7.x86_64
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next reply other threads:[~2016-12-02 17:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 17:44 Dr. David Alan Gilbert [this message]
2016-12-05 8:33 ` [Qemu-devel] Postcopy+spice crash Gerd Hoffmann
2016-12-05 9:46 ` Dr. David Alan Gilbert
2016-12-05 12:06 ` [Qemu-devel] [Spice-devel] " Uri Lublin
2016-12-06 6:59 ` Gerd Hoffmann
2016-12-06 10:53 ` Dr. David Alan Gilbert
2016-12-06 12:37 ` Gerd Hoffmann
2016-12-06 16:47 ` Dr. David Alan Gilbert
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=20161202174015.GE15373@work-vm \
--to=dgilbert@redhat.com \
--cc=kraxel@redhat.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).