Re: [Qemu-devel] QEMU 2.0 RC with Spice

[Rick Vernam]

Looks like it's in Spice:

[New Thread 0x7ffe5dffb700 (LWP 28129)]
main_channel_handle_parsed: agent start
main_channel_handle_parsed: agent start
[Thread 0x7fff5a7fc700 (LWP 28072) exited]

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff2152ee5 in ?? () from /usr/lib64/libspice-server.so.1
(gdb) bt
#0  0x00007ffff2152ee5 in ?? () from /usr/lib64/libspice-server.so.1
#1  0x00007ffff2153d28 in ?? () from /usr/lib64/libspice-server.so.1
#2  0x00007ffff21a0821 in spice_server_vm_start () from 
/usr/lib64/libspice-server.so.1
#3  0x00005555556a1119 in ?? ()
#4  0x00005555556a0958 in ?? ()
#5  0x00005555556a0878 in ?? ()
#6  0x00005555556a0958 in ?? ()
#7  0x00005555557d717a in ?? ()
#8  0x00005555555f9e2f in main ()


I'll see if I can build spice with debugging symbols and what not and write 
back with findings.
Are others have problems with Qemu 2.0 RCs & Spice?

Here is how I started qemu with gdb:

QEMU_AUDIO_DRV=spice
TMPDIR=/home/rick/qemu/hds gdb --args /usr/local/bin/qemu-system-x86_64 -cpu 
host -enable-kvm \
-m 1536 -name Win7Pro64 -localtime -no-fd-bootchk -smp cores=4 \
-pidfile /home/rick/qemu/hds/win7pro64.pid \
-drive file=/home/rick/qemu/hds/win7pro64.qed,if=virtio,index=0,snapshot=on \
-vga qxl \
-net nic,model=virtio -net user \
-device virtio-serial-pci,id=virtio-serial0,max_ports=16,bus=pci.0,addr=0x5 \
-chardev spicevmc,name=vdagent,id=vdagent \
-device 
virtserialport,nr=1,bus=virtio-serial0.0,chardev=vdagent,name=com.redhat.spice.0
 \
-spice port=1247,disable-ticketing \
-monitor telnet:localhost:12471,server,nowait \
-drive if=none,id=cd,file=/dev/sg1 \
-device virtio-scsi-pci,id=scsi \
-device scsi-generic,drive=cd \
-balloon virtio \
-soundhw hda \
-device usb-ehci


Thanks,
-Rick

On Tuesday 15 April 2014 15:22:04 Dr. David Alan Gilbert wrote:
> * Rick Vernam (address@hidden) wrote:
> > I have been trying out the 2.0 RCs, and I've noticed that when I use spice
> > qemu aborts when I reboot the VM.  This occurs on Win XP guest, Win 7
> > (64-bit) guest and Win 8 (64-bit) guest.
> > Is this something that anybody else experiences?
> > I don't care to divert anybody's energy if this a spice thing - how best
> > to
> > determine this?
> 
> You say qemu aborts; can you get a backtrace and the abort message?
> 
> Dave
> --
> Dr. David Alan Gilbert / address@hidden / Manchester, UK