* [Qemu-devel] [Bug 1484925] [NEW] Segfault with custom vnc client
@ 2015-08-14 12:23 Uli Stärk
2015-08-14 14:17 ` [Qemu-devel] [Bug 1484925] " Daniel Berrange
` (6 more replies)
0 siblings, 7 replies; 8+ messages in thread
From: Uli Stärk @ 2015-08-14 12:23 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
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\0\0\0\2\200\1\220\3\0\2\200\0\0\0P\1\220", 4096, 0, NULL, NULL) = 20
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xb28000} ---
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=0,macaddr=8a:43:e2:b1:57:df,model=rtl8139 -net
tap,vlan=0,bridge=xenbr0,ifname=tap25.0 -acpi -monitor pty
XenServer 6.5 is using the following version:
# /usr/lib64/xen/bin/qemu-dm -help
QEMU PC emulator version 0.10.2, Copyright (c) 2003-2008 Fabrice Bellard
Greetings
Uli Stärk
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1484925
Title:
Segfault with custom vnc client
Status in QEMU:
New
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\0\0\0\2\200\1\220\3\0\2\200\0\0\0P\1\220", 4096, 0, NULL, NULL) = 20
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xb28000} ---
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=0,macaddr=8a:43:e2:b1:57:df,model=rtl8139 -net
tap,vlan=0,bridge=xenbr0,ifname=tap25.0 -acpi -monitor pty
XenServer 6.5 is using the following version:
# /usr/lib64/xen/bin/qemu-dm -help
QEMU PC emulator version 0.10.2, Copyright (c) 2003-2008 Fabrice Bellard
Greetings
Uli Stärk
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1484925/+subscriptions
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Qemu-devel] [Bug 1484925] Re: Segfault with custom vnc client
2015-08-14 12:23 [Qemu-devel] [Bug 1484925] [NEW] Segfault with custom vnc client Uli Stärk
@ 2015-08-14 14:17 ` Daniel Berrange
2015-10-01 19:40 ` Dubravko
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Daniel Berrange @ 2015-08-14 14:17 UTC (permalink / raw)
To: qemu-devel
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)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1484925
Title:
Segfault with custom vnc client
Status in QEMU:
New
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\0\0\0\2\200\1\220\3\0\2\200\0\0\0P\1\220", 4096, 0, NULL, NULL) = 20
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xb28000} ---
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=0,macaddr=8a:43:e2:b1:57:df,model=rtl8139 -net
tap,vlan=0,bridge=xenbr0,ifname=tap25.0 -acpi -monitor pty
XenServer 6.5 is using the following version:
# /usr/lib64/xen/bin/qemu-dm -help
QEMU PC emulator version 0.10.2, Copyright (c) 2003-2008 Fabrice Bellard
Greetings
Uli Stärk
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1484925/+subscriptions
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Qemu-devel] [Bug 1484925] Re: Segfault with custom vnc client
2015-08-14 12:23 [Qemu-devel] [Bug 1484925] [NEW] Segfault with custom vnc client Uli Stärk
2015-08-14 14:17 ` [Qemu-devel] [Bug 1484925] " Daniel Berrange
@ 2015-10-01 19:40 ` Dubravko
2015-10-02 7:53 ` Uli Stärk
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Dubravko @ 2015-10-01 19:40 UTC (permalink / raw)
To: qemu-devel
Hi,
Did you resolve your problem? Because I have the same issus..
Dubravko
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1484925
Title:
Segfault with custom vnc client
Status in QEMU:
New
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\0\0\0\2\200\1\220\3\0\2\200\0\0\0P\1\220", 4096, 0, NULL, NULL) = 20
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xb28000} ---
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=0,macaddr=8a:43:e2:b1:57:df,model=rtl8139 -net
tap,vlan=0,bridge=xenbr0,ifname=tap25.0 -acpi -monitor pty
XenServer 6.5 is using the following version:
# /usr/lib64/xen/bin/qemu-dm -help
QEMU PC emulator version 0.10.2, Copyright (c) 2003-2008 Fabrice Bellard
Greetings
Uli Stärk
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1484925/+subscriptions
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Qemu-devel] [Bug 1484925] Re: Segfault with custom vnc client
2015-08-14 12:23 [Qemu-devel] [Bug 1484925] [NEW] Segfault with custom vnc client Uli Stärk
2015-08-14 14:17 ` [Qemu-devel] [Bug 1484925] " Daniel Berrange
2015-10-01 19:40 ` Dubravko
@ 2015-10-02 7:53 ` Uli Stärk
2015-10-02 9:18 ` Dr. David Alan Gilbert
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Uli Stärk @ 2015-10-02 7:53 UTC (permalink / raw)
To: qemu-devel
No, sorry. I've stopped researching this issue.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1484925
Title:
Segfault with custom vnc client
Status in QEMU:
New
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\0\0\0\2\200\1\220\3\0\2\200\0\0\0P\1\220", 4096, 0, NULL, NULL) = 20
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xb28000} ---
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=0,macaddr=8a:43:e2:b1:57:df,model=rtl8139 -net
tap,vlan=0,bridge=xenbr0,ifname=tap25.0 -acpi -monitor pty
XenServer 6.5 is using the following version:
# /usr/lib64/xen/bin/qemu-dm -help
QEMU PC emulator version 0.10.2, Copyright (c) 2003-2008 Fabrice Bellard
Greetings
Uli Stärk
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1484925/+subscriptions
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Qemu-devel] [Bug 1484925] Re: Segfault with custom vnc client
2015-08-14 12:23 [Qemu-devel] [Bug 1484925] [NEW] Segfault with custom vnc client Uli Stärk
` (2 preceding siblings ...)
2015-10-02 7:53 ` Uli Stärk
@ 2015-10-02 9:18 ` Dr. David Alan Gilbert
2015-10-02 16:37 ` Plam
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: Dr. David Alan Gilbert @ 2015-10-02 9:18 UTC (permalink / raw)
To: qemu-devel
Dubravko: can you get a good backtrace from your crash?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1484925
Title:
Segfault with custom vnc client
Status in QEMU:
New
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\0\0\0\2\200\1\220\3\0\2\200\0\0\0P\1\220", 4096, 0, NULL, NULL) = 20
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xb28000} ---
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=0,macaddr=8a:43:e2:b1:57:df,model=rtl8139 -net
tap,vlan=0,bridge=xenbr0,ifname=tap25.0 -acpi -monitor pty
XenServer 6.5 is using the following version:
# /usr/lib64/xen/bin/qemu-dm -help
QEMU PC emulator version 0.10.2, Copyright (c) 2003-2008 Fabrice Bellard
Greetings
Uli Stärk
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1484925/+subscriptions
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Qemu-devel] [Bug 1484925] Re: Segfault with custom vnc client
2015-08-14 12:23 [Qemu-devel] [Bug 1484925] [NEW] Segfault with custom vnc client Uli Stärk
` (3 preceding siblings ...)
2015-10-02 9:18 ` Dr. David Alan Gilbert
@ 2015-10-02 16:37 ` Plam
2016-11-21 16:05 ` Thomas Huth
2017-01-21 4:17 ` Launchpad Bug Tracker
6 siblings, 0 replies; 8+ messages in thread
From: Plam @ 2015-10-02 16:37 UTC (permalink / raw)
To: qemu-devel
Hi,
Xen Orchestra project leader here. Exactly the same problem with noVNC +
qemu-dm.
I assume there is maybe an invalid param from noVNC somewhere, but
crashing the process is not really expected.
The bug is also reported at Citrix (see
https://bugs.xenserver.org/browse/XSO-381)
I don't know how to give you more info, if you have some commands to use
to help you, tell me :)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1484925
Title:
Segfault with custom vnc client
Status in QEMU:
New
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\0\0\0\2\200\1\220\3\0\2\200\0\0\0P\1\220", 4096, 0, NULL, NULL) = 20
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xb28000} ---
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=0,macaddr=8a:43:e2:b1:57:df,model=rtl8139 -net
tap,vlan=0,bridge=xenbr0,ifname=tap25.0 -acpi -monitor pty
XenServer 6.5 is using the following version:
# /usr/lib64/xen/bin/qemu-dm -help
QEMU PC emulator version 0.10.2, Copyright (c) 2003-2008 Fabrice Bellard
Greetings
Uli Stärk
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1484925/+subscriptions
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Qemu-devel] [Bug 1484925] Re: Segfault with custom vnc client
2015-08-14 12:23 [Qemu-devel] [Bug 1484925] [NEW] Segfault with custom vnc client Uli Stärk
` (4 preceding siblings ...)
2015-10-02 16:37 ` Plam
@ 2016-11-21 16:05 ` Thomas Huth
2017-01-21 4:17 ` Launchpad Bug Tracker
6 siblings, 0 replies; 8+ messages in thread
From: Thomas Huth @ 2016-11-21 16:05 UTC (permalink / raw)
To: qemu-devel
QEMU 0.10 is pretty much outdated nowadays... can you reproduce this
issue with the latest version of QEMU, and if so, provide a backtrace of
the crash?
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1484925
Title:
Segfault with custom vnc client
Status in QEMU:
Incomplete
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\0\0\0\2\200\1\220\3\0\2\200\0\0\0P\1\220", 4096, 0, NULL, NULL) = 20
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xb28000} ---
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=0,macaddr=8a:43:e2:b1:57:df,model=rtl8139 -net
tap,vlan=0,bridge=xenbr0,ifname=tap25.0 -acpi -monitor pty
XenServer 6.5 is using the following version:
# /usr/lib64/xen/bin/qemu-dm -help
QEMU PC emulator version 0.10.2, Copyright (c) 2003-2008 Fabrice Bellard
Greetings
Uli Stärk
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1484925/+subscriptions
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Qemu-devel] [Bug 1484925] Re: Segfault with custom vnc client
2015-08-14 12:23 [Qemu-devel] [Bug 1484925] [NEW] Segfault with custom vnc client Uli Stärk
` (5 preceding siblings ...)
2016-11-21 16:05 ` Thomas Huth
@ 2017-01-21 4:17 ` Launchpad Bug Tracker
6 siblings, 0 replies; 8+ messages in thread
From: Launchpad Bug Tracker @ 2017-01-21 4:17 UTC (permalink / raw)
To: qemu-devel
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1484925
Title:
Segfault with custom vnc client
Status in QEMU:
Expired
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\0\0\0\2\200\1\220\3\0\2\200\0\0\0P\1\220", 4096, 0, NULL, NULL) = 20
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xb28000} ---
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=0,macaddr=8a:43:e2:b1:57:df,model=rtl8139 -net
tap,vlan=0,bridge=xenbr0,ifname=tap25.0 -acpi -monitor pty
XenServer 6.5 is using the following version:
# /usr/lib64/xen/bin/qemu-dm -help
QEMU PC emulator version 0.10.2, Copyright (c) 2003-2008 Fabrice Bellard
Greetings
Uli Stärk
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1484925/+subscriptions
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2017-01-21 4:30 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-08-14 12:23 [Qemu-devel] [Bug 1484925] [NEW] Segfault with custom vnc client Uli Stärk
2015-08-14 14:17 ` [Qemu-devel] [Bug 1484925] " Daniel Berrange
2015-10-01 19:40 ` Dubravko
2015-10-02 7:53 ` Uli Stärk
2015-10-02 9:18 ` Dr. David Alan Gilbert
2015-10-02 16:37 ` Plam
2016-11-21 16:05 ` Thomas Huth
2017-01-21 4:17 ` Launchpad Bug Tracker
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.