Re: [Qemu-devel] [Spice-devel] [Xen-devel] Qemu 2.0 regression with xen: qemu crash on any domUs S.O. start
Il 07/04/2014 15:19, Fabio Fantoni ha scritto:
Il 07/04/2014 12:20, Christophe Fergeau ha scritto:
On Mon, Apr 07, 2014 at 11:59:06AM +0200, Fabio Fantoni wrote:
Today I did some tests also with hvm and spice and I found another
segfault with different backtrace to solve:
(gdb) c
Continuing.
*Program received signal SIGSEGV, Segmentation fault.**
**0x55855d30 in interface_client_monitors_config
(sin=0x563b0260, **
**mc=0x0) at ui/spice-display.c:557**
**557 if (mc->num_of_monitors > 0) {*
(gdb) bt full
#0 0x55855d30 in interface_client_monitors_config (
sin=0x563b0260, mc=0x0) at ui/spice-display.c:557
ssd = 0x563b0210
info = {xoff = 0, yoff = 0, width = 0, height = 0}
rc = 32767
__func__ = "interface_client_monitors_config"
#1 0x74af5113 in ?? ()
from /usr/lib/x86_64-linux-gnu/libspice-server.so.1
No symbol table info available.
A backtrace with spice-server debugging symbols installed would be
helpful.
Christophe
Sorry, the -dbg for spice-server on official debian packages is
missing, now I created and installed also the -dbg package and this is
the new backtrace:
(gdb) c
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x55855d30 in interface_client_monitors_config
(sin=0x563b0260,
mc=0x0) at ui/spice-display.c:557
557 if (mc->num_of_monitors > 0) {
(gdb) bt full
#0 0x55855d30 in interface_client_monitors_config (
sin=0x563b0260, mc=0x0) at ui/spice-display.c:557
ssd = 0x563b0210
info = {xoff = 0, yoff = 0, width = 0, height = 0}
rc = 32767
__func__ = "interface_client_monitors_config"
#1 0x74af5113 in red_dispatcher_use_client_monitors_config ()
at red_dispatcher.c:318
now = 0x563b0300
#2 0x74ad87f5 in agent_msg_filter_process_data (
filter=filter@entry=0x562eb0c4,
data=data@entry=0x7fffe0280128 "\001", len=328, len@entry=348)
at agent-msg-filter.c:95
msg_header = {protocol = , type = out>,
opaque = , size = 328,
data = 0x831fd4 }
__FUNCTION__ = "agent_msg_filter_process_data"
#3 0x74b1af76 in reds_on_main_agent_data (mcc=0x56326e70,
message=0x7fffe0280128, size=348) at reds.c:1117
dev_state = 0x562eb0a8
header =
res =
__FUNCTION__ = "reds_on_main_agent_data"
#4 0x74ae989a in main_channel_handle_parsed
(rcc=0x56326e70,
size=, type=, message=0x7fffe0280128)
---Type to continue, or q to quit---
at main_channel.c:911
main_chan = 0x562ef2b0
mcc = 0x56326e70
__FUNCTION__ = "main_channel_handle_parsed"
#5 0x74aee470 in red_peer_handle_incoming
(handler=0x5632af80,
stream=0x565adba0) at red_channel.c:287
ret_handle =
bytes_read =
msg_type = 107
parsed =
parsed_free = 0x74ba8620
msg_size = 348
#6 red_channel_client_receive (rcc=rcc@entry=0x56326e70)
at red_channel.c:309
No locals.
#7 0x74af0d8c in red_channel_client_event (fd=,
event=, data=0x56326e70) at red_channel.c:1435
rcc = 0x56326e70
#8 0x55851f82 in watch_read (opaque=0x5666e0a0)
at ui/spice-core.c:101
watch = 0x5666e0a0
#9 0x557ce1f8 in qemu_iohandler_poll
(pollfds=0x562e8e00, ret=1)
at iohandler.c:143
revents = 1
pioh = 0x5634e080
---Type to continue, or q to quit---
ioh = 0x5632fa30
#10 0x557cf2a4 in main_loop_wait (nonblocking=0) at
main-loop.c:485
ret = 1
timeout = 4294967295
timeout_ns = 4237075
#11 0x5587acd8 in main_loop () at vl.c:2051
nonblocking = false
last_io = 1
#12 0x558826b2 in main (argc=36, argv=0x7fffe358,
envp=0x7fffe480) at vl.c:4507
i = 64
snapshot = 0
linux_boot = 0
icount_option = 0x0
initrd_filename = 0x0
kernel_filename = 0x0
kernel_cmdline = 0x55a1b5c4 ""
boot_order = 0x562e7ee0 "dc"
ds = 0x563d8fd0
cyls = 0
heads = 0
secs = 0
translation = 0
hda_opts = 0x0
opts = 0x562e7e30
---Type to continue, or q to quit---
machine_opts = 0x562e84b0
olist = 0x55e00e00
optind = 36
optarg = 0x7fffe915
"if=ide,index=1,media=cdrom,cache=writeback,id=ide-832"
loadvm = 0x0
machine_class = 0x562e02a0
machine = 0x55e067e0
cpu_model = 0x0
vga_model = 0x0
qtest_chrdev = 0x0
qtest_log = 0x0
pid_file = 0x0
incoming = 0x0
show_vnc_port = 0
defconfig = true
userconfig = true
log_mask = 0x0
log_file = 0x0
mem_trace = {malloc = 0x5587e56a ,
realloc = 0x5587e5c2 ,
Re: [Qemu-devel] [Spice-devel] [Xen-devel] Qemu 2.0 regression with xen: qemu crash on any domUs S.O. start
Il 07/04/2014 12:20, Christophe Fergeau ha scritto:
On Mon, Apr 07, 2014 at 11:59:06AM +0200, Fabio Fantoni wrote:
Today I did some tests also with hvm and spice and I found another
segfault with different backtrace to solve:
(gdb) c
Continuing.
*Program received signal SIGSEGV, Segmentation fault.**
**0x55855d30 in interface_client_monitors_config
(sin=0x563b0260, **
**mc=0x0) at ui/spice-display.c:557**
**557 if (mc->num_of_monitors > 0) {*
(gdb) bt full
#0 0x55855d30 in interface_client_monitors_config (
sin=0x563b0260, mc=0x0) at ui/spice-display.c:557
ssd = 0x563b0210
info = {xoff = 0, yoff = 0, width = 0, height = 0}
rc = 32767
__func__ = "interface_client_monitors_config"
#1 0x74af5113 in ?? ()
from /usr/lib/x86_64-linux-gnu/libspice-server.so.1
No symbol table info available.
A backtrace with spice-server debugging symbols installed would be helpful.
Christophe
Sorry, the -dbg for spice-server on official debian packages is missing,
now I created and installed also the -dbg package and this is the new
backtrace:
(gdb) c
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x55855d30 in interface_client_monitors_config
(sin=0x563b0260,
mc=0x0) at ui/spice-display.c:557
557 if (mc->num_of_monitors > 0) {
(gdb) bt full
#0 0x55855d30 in interface_client_monitors_config (
sin=0x563b0260, mc=0x0) at ui/spice-display.c:557
ssd = 0x563b0210
info = {xoff = 0, yoff = 0, width = 0, height = 0}
rc = 32767
__func__ = "interface_client_monitors_config"
#1 0x74af5113 in red_dispatcher_use_client_monitors_config ()
at red_dispatcher.c:318
now = 0x563b0300
#2 0x74ad87f5 in agent_msg_filter_process_data (
filter=filter@entry=0x562eb0c4,
data=data@entry=0x7fffe0280128 "\001", len=328, len@entry=348)
at agent-msg-filter.c:95
msg_header = {protocol = , type = ,
opaque = , size = 328,
data = 0x831fd4 }
__FUNCTION__ = "agent_msg_filter_process_data"
#3 0x74b1af76 in reds_on_main_agent_data (mcc=0x56326e70,
message=0x7fffe0280128, size=348) at reds.c:1117
dev_state = 0x562eb0a8
header =
res =
__FUNCTION__ = "reds_on_main_agent_data"
#4 0x74ae989a in main_channel_handle_parsed (rcc=0x56326e70,
size=, type=, message=0x7fffe0280128)
---Type to continue, or q to quit---
at main_channel.c:911
main_chan = 0x562ef2b0
mcc = 0x56326e70
__FUNCTION__ = "main_channel_handle_parsed"
#5 0x74aee470 in red_peer_handle_incoming
(handler=0x5632af80,
stream=0x565adba0) at red_channel.c:287
ret_handle =
bytes_read =
msg_type = 107
parsed =
parsed_free = 0x74ba8620
msg_size = 348
#6 red_channel_client_receive (rcc=rcc@entry=0x56326e70)
at red_channel.c:309
No locals.
#7 0x74af0d8c in red_channel_client_event (fd=,
event=, data=0x56326e70) at red_channel.c:1435
rcc = 0x56326e70
#8 0x55851f82 in watch_read (opaque=0x5666e0a0)
at ui/spice-core.c:101
watch = 0x5666e0a0
#9 0x557ce1f8 in qemu_iohandler_poll (pollfds=0x562e8e00,
ret=1)
at iohandler.c:143
revents = 1
pioh = 0x5634e080
---Type to continue, or q to quit---
ioh = 0x5632fa30
#10 0x557cf2a4 in main_loop_wait (nonblocking=0) at
main-loop.c:485
ret = 1
timeout = 4294967295
timeout_ns = 4237075
#11 0x5587acd8 in main_loop () at vl.c:2051
nonblocking = false
last_io = 1
#12 0x558826b2 in main (argc=36, argv=0x7fffe358,
envp=0x7fffe480) at vl.c:4507
i = 64
snapshot = 0
linux_boot = 0
icount_option = 0x0
initrd_filename = 0x0
kernel_filename = 0x0
kernel_cmdline = 0x55a1b5c4 ""
boot_order = 0x562e7ee0 "dc"
ds = 0x563d8fd0
cyls = 0
heads = 0
secs = 0
translation = 0
hda_opts = 0x0
opts = 0x562e7e30
---Type to continue, or q to quit---
machine_opts = 0x562e84b0
olist = 0x55e00e00
optind = 36
optarg = 0x7fffe915
"if=ide,index=1,media=cdrom,cache=writeback,id=ide-832"
loadvm = 0x0
machine_class = 0x562e02a0
machine = 0x55e067e0
cpu_model = 0x0
vga_model = 0x0
qtest_chrdev = 0x0
qtest_log = 0x0
pid_file = 0x0
incoming = 0x0
show_vnc_port = 0
defconfig = true
userconfig = true
log_mask = 0x0
log_file = 0x0
mem_trace = {malloc = 0x5587e56a ,
realloc = 0x5587e5c2 ,
free = 0x5587e629 , calloc = 0,
try_malloc =
Re: [Qemu-devel] [Spice-devel] [Xen-devel] Qemu 2.0 regression with xen: qemu crash on any domUs S.O. start
On Mon, Apr 07, 2014 at 11:59:06AM +0200, Fabio Fantoni wrote:
>
> Today I did some tests also with hvm and spice and I found another
> segfault with different backtrace to solve:
> >(gdb) c
> >Continuing.
> >
> >*Program received signal SIGSEGV, Segmentation fault.**
> >**0x55855d30 in interface_client_monitors_config
> >(sin=0x563b0260, **
> >**mc=0x0) at ui/spice-display.c:557**
> >**557 if (mc->num_of_monitors > 0) {*
>
> >(gdb) bt full
> >#0 0x55855d30 in interface_client_monitors_config (
> >sin=0x563b0260, mc=0x0) at ui/spice-display.c:557
> >ssd = 0x563b0210
> >info = {xoff = 0, yoff = 0, width = 0, height = 0}
> >rc = 32767
> >__func__ = "interface_client_monitors_config"
> >#1 0x74af5113 in ?? ()
> > from /usr/lib/x86_64-linux-gnu/libspice-server.so.1
> >No symbol table info available.
A backtrace with spice-server debugging symbols installed would be helpful.
Christophe
pgpLb9qHAjCEt.pgp
Description: PGP signature
