Segfault with custom vnc client
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
Expired
|
Undecided
|
Unassigned |
Bug Description
Hey,
I'm using Citrix XenServer 6.5. I worte a script that uses noVNC to connect to the rfb console via xapi. When I use GRML and try to boot it, the QEMU process segfaults and kills my VM. This happens when the screen resizes and the kernel is loading:
recvfrom(3, "\3\1\0\
--- SIGSEGV {si_signo=SIGSEGV, si_code=
I can see in the child process the following message, right before the parent Segfaults:
read(4, "cirrus: blanking the screen line_offset=0 height=480\n", 53) = 53
This issue only happens, when I have my custom php/novnc-client connected. I also tried the nodejs/novnc package from xen-orchestra - same result. Using the stock client from Citrix XenCenter it works just fine. So I think it is related to noVNC. I hope this is just a bug and not exploitable to force a VM to crash or execute code.
XenServer launches the qemu with the following command line:
qemu-dm-25 --syslog -d 25 -m 2048 -boot dc -serial pty -vcpus 1 -videoram 4 -vncunused -k en-us -vnc 127.0.0.1:1 -usb -usbdevice tablet -net nic,vlan=
XenServer 6.5 is using the following version:
# /usr/lib64/
QEMU PC emulator version 0.10.2, Copyright (c) 2003-2008 Fabrice Bellard
Greetings
Uli Stärk
Can you attach GDB to your qemu-dm process and attempt to capture a full stack trace when it crashes (ie thread apply all backtrace)