The platform is Ubuntu 10.10, x86_64, qemu-kvm is kvm.v28 from spice qemu git, with spice 0.8.0. Guest is windows xp 32bit, with virtserialio and vdagent installed. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f7198ef6700 (LWP 29307)] region_add (rgn=0x7f7198d216f0, r=0x2ba266000000000) at ../common/region.c:464 464 r->bottom - r->top); (gdb) bt #0 region_add (rgn=0x7f7198d216f0, r=0x2ba266000000000) at ../common/region.c:464 #1 0x00007f71e47f667c in red_update_area (worker=0x7f7198d219a0, area=<value optimized out>, surface_id=<value optimized out>) at red_worker.c:4138 #2 0x00007f71e47ff423 in handle_dev_update (listener=<value optimized out>, events=<value optimized out>) at red_worker.c:9728 #3 handle_dev_input (listener=<value optimized out>, events=<value optimized out>) at red_worker.c:9936 #4 0x00007f71e47fce15 in red_worker_main (arg=<value optimized out>) at red_worker.c:10286 #5 0x00007f71e5a08971 in start_thread () from /lib/libpthread.so.0 #6 0x00007f71e364b92d in clone () from /lib/libc.so.6 #7 0x0000000000000000 in ?? () (gdb) p r->bottom Cannot access memory at address 0x2ba26600000000c (gdb) p r->top Cannot access memory at address 0x2ba266000000004 (gdb)
The command line of kvm: sudo /usr/bin/kvm -M pc-0.14 -enable-kvm -m 1024 -smp 1,sockets=1,cores=1,threads=1 -name testxp -boot c -device virtio-serial-pci,id=virtio-serial1,bus=pci.0,addr=0x5 -drive file=/home/test/vms/winxp.qcow2,if=none,id=drive-ide0-0-0,format=qcow2 -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial1.0,nr=3,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -usb -device usb-tablet,id=input0 -spice port=5903,addr=0.0.0.0,password=test4321 -vga qxl -device AC97,id=sound0,bus=pci.0,addr=0x4 -vnc :2
I can't reproduce the crash with spice-server-0.8.1-1.fc15.x86_64 and qemu-kvm from Fedora 15 qemu-common-0.14.0-7.fc15.x86_64. RedUEC, could you try with more recent versions and provide more informations about the circumstances of the crash?
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.