[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] qemu crash on windows 7 resolution change on spice



Il 18/07/2014 09:55, Fabio Fantoni ha scritto:
Il 18/07/2014 04:01, kevin.zhang@xxxxxxxxxxx ha scritto:
Hi Fabio Fantoni,
Â
ÂÂÂÂ I closed vnc options and can reproduce the problem, stack info is as follow:
(gdb)Â target remote localhost:1234
Remote debugging using localhost:1234
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
0x00007ffff7dddaf0 in ?? () from /lib64/ld-linux-x86-64.so.2
(gdb) c
Continuing.
Â
Program received signal SIGABRT, Aborted.
0x00007ffff2e04475 in *__GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
64ÂÂÂÂÂ ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt full
#0Â 0x00007ffff2e04475 in *__GI_raise (sig=<optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
ÂÂÂÂÂÂÂ pid = <optimized out>
ÂÂÂÂÂÂÂ selftid = <optimized out>
#1Â 0x00007ffff2e076f0 in *__GI_abort () at abort.c:92
ÂÂÂÂÂÂÂ act = {__sigaction_handler = {sa_handler = 0x7fffffffce58, sa_sigaction = 0x7fffffffce58}, sa_mask = {__val = {
ÂÂÂÂÂÂÂÂÂÂÂÂÂ 140737488342592, 140737488348103, 33, 140737269326962, 1, 140737269331337, 3, 140737488342587, 5,
ÂÂÂÂÂÂÂÂÂÂÂÂÂ 140737269327027, 1, 140737269336037, 3, 140737488342596, 12, 140737269336041}}, sa_flags = 2,
ÂÂÂÂÂÂÂÂÂ sa_restorer = 0x7ffff2f207e9}
ÂÂÂÂÂÂÂ sigs = {__val = {32, 0 <repeats 15 times>}}
#2Â 0x00007ffff2e3f52b in __libc_message (do_abort=<optimized out>, fmt=<optimized out>)
ÂÂÂ at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
ÂÂÂÂÂÂÂ ap = {{gp_offset = 40, fp_offset = 48, overflow_arg_area = 0x7fffffffd7c0, reg_save_area = 0x7fffffffd6d0}}
ÂÂÂÂÂÂÂ ap_copy = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 0x7fffffffd7c0, reg_save_area = 0x7fffffffd6d0}}
ÂÂÂÂÂÂÂ fd = 2
ÂÂÂÂÂÂÂ out>
ÂÂÂÂÂÂÂ list = <optimized out>
ÂÂÂÂÂÂÂ nlist = 0
ÂÂÂÂÂÂÂ cp = <optimized out>
ÂÂÂÂÂÂÂ written = false
#3Â 0x00007ffff2e48d76 in malloc_printerr (action="" str=0x7ffff2f22908 "double free or corruption (!prev)",
ÂÂÂ ptr=<optimized out>) at malloc.c:6312
ÂÂÂÂÂÂÂ buf = "00007fffd4c390e0"
ÂÂÂÂÂÂÂ cp = 0x0
#4Â 0x00007ffff2e4db1c in *__GI___libc_free (mem=<optimized out>) at malloc.c:3738
ÂÂÂÂÂÂÂ ar_ptr = 0x7fffd4000020
ÂÂÂÂÂÂÂ p = 0x6
#5Â 0x00007ffff3b5b44b in _pixman_image_fini (image=image@entry=0x7fffd4879820) at ../../pixman/pixman-image.c:173
ÂÂÂÂÂÂÂ common = 0x7fffd4879820
ÂÂÂÂÂÂÂ __PRETTY_FUNCTION__ = "_pixman_image_fini"
#6Â 0x00007ffff3b5b399 in pixman_image_unref (image=0x7fffd4879820) at ../../pixman/pixman-image.c:211
No locals.
#7Â 0x000055555585283b in qemu_pixman_image_unref (image=0x7fffd4879820) at ui/qemu-pixman.c:80
No locals.
#8Â 0x000055555587446b in vnc_dpy_switch (dcl=0x7fffe2c99048, surface=0x7fffd40b7c10) at ui/vnc.c:588
ÂÂÂÂÂÂÂ vd = 0x7fffe2c99010
ÂÂÂÂÂÂÂ vs = 0xff000000180420
#9Â 0x000055555584be81 in dpy_gfx_replace_surface (con=0x5555566a90a0, surface=0x7fffd40b7c10) at ui/console.c:1404
---Type <return> to continue, or q <return> to quit---
Â
ÂÂÂÂÂÂÂ s = 0x5555565f64b0
ÂÂÂÂÂÂÂ old_surface = 0x7fffd487a040
ÂÂÂÂÂÂÂ dcl = 0x7fffe2c99048
#10 0x00005555556ecd52 in qxl_render_update_area_unlocked (qxl=0x5555566dba20) at hw/display/qxl-render.c:131
ÂÂÂÂÂÂÂ vga = 0x5555566dc510
ÂÂÂÂÂÂÂ surface = 0x7fffd40b7c10
ÂÂÂÂÂÂÂ i = 0
#11 0x00005555556ed021 in qxl_render_update_area_bh (opaque=0x5555566dba20) at hw/display/qxl-render.c:183
ÂÂÂÂÂÂÂ qxl = 0x5555566dba20
#12 0x00005555555f5330 in aio_bh_poll (ctx=0x5555562f1c20) at async.c:81
ÂÂÂÂÂÂÂ bh = 0x5555566a4770
ÂÂÂÂÂÂÂ bhp = 0x7ffff77bfe86
ÂÂÂÂÂÂÂ next = 0x5555566a3c00
ÂÂÂÂÂÂÂ ret = 1
#13 0x00005555555f4f89 in aio_poll (ctx=0x5555562f1c20, blocking=false) at aio-posix.c:188
ÂÂÂÂÂÂÂ node = 0x7ffff73269a4
ÂÂÂÂÂÂÂ ret = 32767
ÂÂÂÂÂÂÂ progress = false
#14 0x00005555555f5747 in aio_ctx_dispatch (source=0x5555562f1c20, callback=0, user_data=0x0) at async.c:205
ÂÂÂÂÂÂÂ ctx = 0x5555562f1c20
ÂÂÂÂÂÂÂ __PRETTY_FUNCTION__ = "aio_ctx_dispatch"
#15 0x00007ffff730c355 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#16 0x00005555557d41ce in glib_pollfds_poll () at main-loop.c:190
ÂÂÂÂÂÂÂ context = 0x5555562f27c0
ÂÂÂÂÂÂÂ pfds = 0x5555566da480
#17 0x00005555557d42ce in os_host_main_loop_wait (timeout=0) at main-loop.c:235
ÂÂÂÂÂÂÂ ret = 2
ÂÂÂÂÂÂÂ spin_counter = 1
#18 0x00005555557d43a1 in main_loop_wait (nonblocking=0) at main-loop.c:484
ÂÂÂÂÂÂÂ ret = 21845
ÂÂÂÂÂÂÂ timeout = 4294967295
ÂÂÂÂÂÂÂ timeout_ns = 29767176
#19 0x000055555587fe0c in main_loop () at vl.c:2051
ÂÂÂÂÂÂÂ nonblocking = false
ÂÂÂÂÂÂÂ last_io = 1
#20 0x00005555558877e6 in main (argc=64, argv=0x7fffffffdfd8, envp=0x7fffffffe1e0) at vl.c:4507
---Type <return> to continue, or q <return> to quit---
ÂÂÂÂÂÂÂ i = 64
ÂÂÂÂÂÂÂ snapshot = 0
ÂÂÂÂÂÂÂ linux_boot = 0
ÂÂÂÂÂÂÂ icount_option = 0x0
ÂÂÂÂÂÂÂ initrd_filename = 0x0
ÂÂÂÂÂÂÂ kernel_filename = 0x0
ÂÂÂÂÂÂÂ kernel_cmdline = 0x555555a22304 ""
ÂÂÂÂÂÂÂ boot_order = 0x5555562ef840 "dc"
ÂÂÂÂÂÂÂ ds = 0x5555565f64b0
ÂÂÂÂÂÂÂ cyls = 0
ÂÂÂÂÂÂÂ heads = 0
ÂÂÂÂÂÂÂ secs = 0
ÂÂÂÂÂÂÂ translation = 0
ÂÂÂÂÂÂÂ hda_opts = 0x0
ÂÂÂÂÂÂÂ opts = 0x5555562ef790
ÂÂÂÂÂÂÂ machine_opts = 0x5555562f13f0
ÂÂÂÂÂÂÂ olist = 0x555555e08220
ÂÂÂÂÂÂÂ optind = 64
ÂÂÂÂÂÂÂ optarg = 0x7fffffffe92d "if=ide,index=1,media=cdrom,cache=writeback,id=ide-832"
ÂÂÂÂÂÂÂ loadvm = 0x0
ÂÂÂÂÂÂÂ machine_class = 0x5555562e8540
ÂÂÂÂÂÂÂ machine = 0x555555e0de80
ÂÂÂÂÂÂÂ 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 = 0x55555588369e <malloc_and_trace>, realloc = 0x5555558836f6 <realloc_and_trace>,
ÂÂÂÂÂÂÂÂÂ free = 0x55555588375d <free_and_trace>, calloc = 0, try_malloc = 0, try_realloc = 0}
ÂÂÂÂÂÂÂ trace_events = 0x0
ÂÂÂÂÂÂÂ trace_file = 0x0
---Type <return> to continue, or q <return> to quit---
ÂÂÂÂÂÂÂ __func__ = "main"
ÂÂÂÂÂÂÂ args = {machine = 0x555555e0de80, ram_size = 4160749568, boot_order = 0x5555562ef840 "dc",
ÂÂÂÂÂÂÂÂÂ kernel_filename = 0x0, kernel_cmdline = 0x555555a22304 "", initrd_filename = 0x0, cpu_model = 0x0}

Thanks for the full backtrace.
I added qemu-devel and spice-devel as cc.
Can someone take a look at this backtrace of qemu crash on windows 7 resolution change when connect with spice and help to solve it please?
Some other details are in previous mails below.

Thanks for any reply.


@Kevin, can you post the output of xl -vvv create please?
Looking backtrace seems still using something about vnc and is strange if you disabled it from domU's xl cfg:
#8Â 0x000055555587446b in vnc_dpy_switch (dcl=0x7fffe2c99048, surface=0x7fffd40b7c10) at ui/vnc.c:588
Thanks for any reply.





Best Regards

Date:Â2014-07-17Â16:52
Subject:ÂRe: [Xen-devel] QXL problem: Xen 4.4.1 rc1 and xen 4.5 unstable
Il 17/07/2014 03:48, kevin.zhang@xxxxxxxxxxx ha scritto:
Hi Fabio Fantoni,
Â
ÂÂÂÂ I finally got it. If that's not enough, I will provide more as u guide.
ÂÂÂÂ I adjust the timeÂto just after xl create and can get stack info as followÂ:
(gdb) target remote localhost:1234
Remote debugging using localhost:1234
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
0x00007ffff7dddaf0 in ?? () from /lib64/ld-linux-x86-64.so.2
(gdb) c
Continuing.
Â
Program received signal SIGABRT, Aborted.
0x00007ffff2e04475 in raise () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt full
#0Â 0x00007ffff2e04475 in raise () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#1Â 0x00007ffff2e076f0 in abort () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#2Â 0x00007ffff2e3f52b in ?? () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#3Â 0x00007ffff2e48d76 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#4Â 0x00007ffff2e4db1c in free () from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#5Â 0x00007ffff3b5b44b in ?? () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
No symbol table info available.
#6Â 0x00007ffff3b5b399 in pixman_image_unref () from /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
No symbol table info available.
#7Â 0x000055555585283b in qemu_pixman_image_unref (image=0x555558cd1170) at ui/qemu-pixman.c:80
No locals.
#8Â 0x000055555587446b in vnc_dpy_switch (dcl=0x7fffe2cbc048, surface=0x5555563263c0) at ui/vnc.c:588
ÂÂÂÂÂÂÂ vd = 0x7fffe2cbc010
ÂÂÂÂÂÂÂ vs = 0xff000000180420
#9Â 0x000055555584be81 in dpy_gfx_replace_surface (con=0x5555566a2550, surface=0x5555563263c0) at ui/console.c:1404
ÂÂÂÂÂÂÂ s = 0x555556715b90
ÂÂÂÂÂÂÂ old_surface = 0x5555566e01e0
ÂÂÂÂÂÂÂ dcl = 0x7fffe2cbc048
#10 0x00005555556ecd52 in qxl_render_update_area_unlocked (qxl=0x555556715bc0) at hw/display/qxl-render.c:131
ÂÂÂÂÂÂÂ vga = 0x5555567166b0
ÂÂÂÂÂÂÂ surface = 0x5555563263c0
ÂÂÂÂÂÂÂ i = 0
#11 0x00005555556ed021 in qxl_render_update_area_bh (opaque=0x555556715bc0) at hw/display/qxl-render.c:183
ÂÂÂÂÂÂÂ qxl = 0x555556715bc0
#12 0x00005555555f5330 in aio_bh_poll (ctx=0x5555562f1c30) at async.c:81
ÂÂÂÂÂÂÂ bh = 0x5555565fb700
ÂÂÂÂÂÂÂ bhp = 0x7ffff77bfe86
ÂÂÂÂÂÂÂ next = 0x5555566afd00
ÂÂÂÂÂÂÂ ret = 1
#13 0x00005555555f4f89 in aio_poll (ctx=0x5555562f1c30, blocking=false) at aio-posix.c:188
ÂÂÂÂÂÂÂ node = 0x7ffff73269a4
ÂÂÂÂÂÂÂ ret = 32767
---Type <return> to continue, or q <return> to quit---
ÂÂÂÂÂÂÂ progress = false
#14 0x00005555555f5747 in aio_ctx_dispatch (source=0x5555562f1c30, callback=0, user_data=0x0) at async.c:205
ÂÂÂÂÂÂÂ ctx = 0x5555562f1c30
ÂÂÂÂÂÂÂ __PRETTY_FUNCTION__ = "aio_ctx_dispatch"
#15 0x00007ffff730c355 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#16 0x00005555557d41ce in glib_pollfds_poll () at main-loop.c:190
ÂÂÂÂÂÂÂ context = 0x5555562f27c0
ÂÂÂÂÂÂÂ pfds = 0x5555566f75c0
#17 0x00005555557d42ce in os_host_main_loop_wait (timeout=0) at main-loop.c:235
ÂÂÂÂÂÂÂ ret = 1
ÂÂÂÂÂÂÂ spin_counter = 1
#18 0x00005555557d43a1 in main_loop_wait (nonblocking=0) at main-loop.c:484
ÂÂÂÂÂÂÂ ret = 21845
ÂÂÂÂÂÂÂ timeout = 4294967295
ÂÂÂÂÂÂÂ timeout_ns = 17515866
#19 0x000055555587fe0c in main_loop () at vl.c:2051
ÂÂÂÂÂÂÂ nonblocking = false
ÂÂÂÂÂÂÂ last_io = 0
#20 0x00005555558877e6 in main (argc=64, argv=0x7fffffffdfb8, envp=0x7fffffffe1c0) at vl.c:4507
ÂÂÂÂÂÂÂ i = 64
ÂÂÂÂÂÂÂ snapshot = 0
ÂÂÂÂÂÂÂ linux_boot = 0
ÂÂÂÂÂÂÂ icount_option = 0x0
ÂÂÂÂÂÂÂ initrd_filename = 0x0
ÂÂÂÂÂÂÂ kernel_filename = 0x0
ÂÂÂÂÂÂÂ kernel_cmdline = 0x555555a22304 ""
ÂÂÂÂÂÂÂ boot_order = 0x5555562ef840 "dc"
ÂÂÂÂÂÂÂ ds = 0x555556715b90
ÂÂÂÂÂÂÂ cyls = 0
ÂÂÂÂÂÂÂ heads = 0
ÂÂÂÂÂÂÂ secs = 0
ÂÂÂÂÂÂÂ translation = 0
ÂÂÂÂÂÂÂ hda_opts = 0x0
ÂÂÂÂÂÂÂ opts = 0x5555562ef790
ÂÂÂÂÂÂÂ machine_opts = 0x5555562f13f0
ÂÂÂÂÂÂÂ olist = 0x555555e08220
---Type <return> to continue, or q <return> to quit---
ÂÂÂÂÂÂÂ optind = 64
ÂÂÂÂÂÂÂ optarg = 0x7fffffffe915 "if=ide,index=1,media=cdrom,cache=writeback,id=ide-832"
ÂÂÂÂÂÂÂ loadvm = 0x0
ÂÂÂÂÂÂÂ machine_class = 0x5555562e8540
ÂÂÂÂÂÂÂ machine = 0x555555e0de80
ÂÂÂÂÂÂÂ 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 = 0x55555588369e <malloc_and_trace>, realloc = 0x5555558836f6 <realloc_and_trace>,
ÂÂÂÂÂÂÂÂÂ free = 0x55555588375d <free_and_trace>, calloc = 0, try_malloc = 0, try_realloc = 0}
ÂÂÂÂÂÂÂ trace_events = 0x0
ÂÂÂÂÂÂÂ trace_file = 0x0
ÂÂÂÂÂÂÂ __func__ = "main"
ÂÂÂÂÂÂÂ args = {machine = 0x555555e0de80, ram_size = 4160749568, boot_order = 0x5555562ef840 "dc",
ÂÂÂÂÂÂÂÂÂ kernel_filename = 0x0, kernel_cmdline = 0x555555a22304 "", initrd_filename = 0x0, cpu_model = 0x0}

In your test vnc is still enabled, right? Can you try disabling vnc (vnc=0 in domU's xl cfg)?
Install also these packages for missed symbols: libc6-dbg libpixman-1-0-dbg


Thanks for any reply.


Â
Â

Best Regards

åääïÂFabio Fantoni
åéæéïÂ2014-07-16Â17:03
äéïÂRe:åå: Re: [Xen-devel] QXL problem: Xen 4.4.1 rc1 and xen 4.5 unstable
Il 16/07/2014 09:04, kevin.zhang@xxxxxxxxxxx ha scritto:
Hi Fabio Fantoni,
Â
ÂÂÂÂ Thank you for your advice for building xen unstable.
ÂÂÂÂ Because I have to use debian wheezy as production distro, I've got to do the test in it.
ÂÂÂÂ Today, I edit Config.mk and write:
QEMU_UPSTREAM_URL = git://git.qemu.org/qemu.git
QEMU_UPSTREAM_REVISION = master
 Then, the built qemu-xen binary works well. Therefore, I guess that git://xenbits.xen.org/qemu-upstream-unstable.git has some very little difference
compared to qemu.git. Maybe your environment cannot repeat that problem either, I'd like to provide any useful information to resolve this problem.

I also use wheezy for both production and develop/testing.
I tried now on my latest testing build, of some days ago xen from rebase/m2r-staging branch and qemu mainline with same Config.mk before build.
On windows 7 pro 64 bit domUs with latest spice guest tools auto and manual resolution change works without problem.
I'm still unable to reproduce your qemu crash.

You can retry to catch and post backtrace with my latest better explain?


I know, I already posted the solution but I try to explain better.

# after xl create with (qemu gdb), do it fast after xl create when arrive on qemu process launch (before timeout or xl create will fails)
target remote localhost:1234 # prepare this command in other ssh to the xen dom0 and enter on xl create when arrive on qemu launch
c # press immediatly
bt full # when qemu stops


Sorry for my bad english.


Â

Best Regards

Date:Â2014-07-15Â16:09
Subject:ÂRe: [Xen-devel] QXL problem: Xen 4.4.1 rc1 and xen 4.5 unstable
Il 15/07/2014 07:53, kevin.zhang@xxxxxxxxxxx ha scritto:
Hi Fabio Fantoni,
ÂÂÂÂÂ Today I tried to use wheezy backports version of spice-server, the problem persists with qemu-xen binary, while my self compiled qemu 2.0 works well.
I think it is a problem and can be repeated.
ÂÂÂÂ Then, I will summarize my compilation process here:
ÂÂÂÂ Firstly install debian wheezy 7.5 amd64 and necessary build dependency. Then:
2. install backport version libspice-server-dev libspice-protocol-dev
root@debian:~#Â apt-cache policy libspice-server-dev libspice-protocol-dev
libspice-server-dev:
 Installed: 0.12.4-0nocelt2~bpo70+1
 Candidate: 0.12.4-0nocelt2~bpo70+1
 Version table:
*** 0.12.4-0nocelt2~bpo70+1 0
ÂÂÂÂÂÂÂ 100 http://cdn.debian.net/debian/ wheezy-backports/main amd64 Packages
ÂÂÂÂÂÂÂ 100 /var/lib/dpkg/status
libspice-protocol-dev:
 Installed: 0.12.6-1~bpo70+2
 Candidate: 0.12.6-1~bpo70+2
 Version table:
*** 0.12.6-1~bpo70+2 0
ÂÂÂÂÂÂÂ 100 http://cdn.debian.net/debian/ wheezy-backports/main amd64 Packages
ÂÂÂÂÂÂÂ 100 /var/lib/dpkg/status
Â3. patch for QXL option
Â4. ./configure --prefix=/usrÂ
Â5. add spice and usb-redir optionÂfor qemu-xen-upstream
Â6. make xen;make tools;makeÂinstall-xen;make install-tools
Â
ÂÂÂÂÂÂ To compile qemu 2.0 from qemu.org:
ÂÂÂÂÂÂ 2. ./configure --enable-xen --target-list=i386-softmmu --extra-cflags="-I/usr/src/xen/tools/include -I/usr/src/xen/tools/libxc -I/usr/src/xen/tools/xenstore"Â\
ÂÂÂÂÂÂÂÂÂÂ Â--enable-spice --enable-usb-redir
ÂÂÂÂÂÂ 3 .make;make install
Â
Â

For fast unstable tests I do this (using my github rebase/m2r-*):
Install of opus, usbredir and libusbx from backports.
Rebuild and install new seabios 1.7.5-1 and spice packages (server 0.12.5-1 and protocol
0.12.7-1) from sid that contains many fixes (simply and fast with git clone of debian repository and debuild).
./configure --prefix=/usr --enable-qemu-traditional=no --with-system-seabios=/usr/share/seabios/bios-256k.bin --with-extra-qemuu-configure-args="--enable-spice --enable-usb-redir"
make debball
dpkg -i of xen package in dist (contain both xen and qemu)
And if I need to test newer qemu in development I simply change the qemu git with mainline in Config.mk.


And for newer production servers I start prepared new xen's debian packages awaiting debian maintainers replies:
https://github.com/Fantu/pkg-xen/tree/wheezy-backports
Needs also qemu rebuild to use new xen 4.4 libraries (simply and fast with git clone of debian repository and debuild).


There is also a problem of jpeg-turbo in debian and for have better performances and not too many cpu waste I for now solved with:
apt-key adv --recv-keys --keyserver keys.gnupg.net E1F958385BFE2B6E
vi /etc/apt/sources.list.d/x2go.list
# X2Go Repository (for jpeg-turbo as default and with full -dev package)
deb http://packages.x2go.org/debian wheezy heuler
deb-src http://packages.x2go.org/debian wheezy heuler
aptitude update
aptitude install x2go-keyring && aptitude update
aptitude install libjpeg8-turbo-dev


Â

Best Regards

åéæéïÂ2014-07-14Â16:49
äéïÂåå: Re: [Xen-devel] QXL problem: Xen 4.4.1 rc1 and xen 4.5 unstable
Hi Fabio Fantoni,
ÂÂÂÂ
ÂÂÂÂÂÂThank you for your reply.
ÂÂÂÂÂ It is really weird.
 I compiled both qemu binary ( qemu-upstream in xenÂand qemu-2.0 fromÂqemu.org website) in the same environment, theÂbinary in xenÂhas the problem while
the other one works well.
ÂÂÂÂÂ I willÂcheck whether wheezy backport has libspice-server-dev and libspice-protocol-dev and try again.Â
Â

Best Regards

Date:Â2014-07-14Â15:59
Subject:ÂRe: [Xen-devel] QXL problem: Xen 4.4.1 rc1 and xen 4.5 unstable
Il 14/07/2014 07:29, kevin.zhang@xxxxxxxxxxx ha scritto:
Hi Fabio Fantoni,
ÂÂÂ
ÂÂÂÂ Today, I've done another test on xenbits xen 4.5 unstable.
 This time, I directly compiled xen on my test server, and use default libspice-server-dev and libspice-protocol-dev header files for spice option.
ÂÂÂ
root@debian:~# apt-cache policy libspice-server-dev libspice-protocol-dev
libspice-server-dev:
 Installed: 0.11.0-1+deb7u1
 Candidate: 0.11.0-1+deb7u1
 Version table:
*** 0.11.0-1+deb7u1 0
ÂÂÂÂÂÂÂ 500 http://cdn.debian.net/debian/ wheezy/main amd64 Packages
ÂÂÂÂÂÂÂ 100 /var/lib/dpkg/status
libspice-protocol-dev:
 Installed: 0.10.1-1
 Candidate: 0.10.1-1
 Version table:
*** 0.10.1-1 0
ÂÂÂÂÂÂÂ 500 http://cdn.debian.net/debian/ wheezy/main amd64 Packages
ÂÂÂÂÂÂÂ 100 /var/lib/dpkg/status
Â
ÂÂÂÂÂI also download qemu-2.0 source code from qemu.org, and compiled it by the way mentioned in http://wiki.xen.org/wiki/QEMU_Upstream.
ÂÂÂÂ Then I create win7 hvm with qemu-xen and /usr/local/bin/qemu-system-i386 respectively.
ÂÂÂÂ The result shows that:
ÂÂÂÂÂÂ1 . qemu-upstream used in xen 4.5 unstable still exited when changing screen resolution,
 2. my self-compiled qemu2.0 behave normally.
ÂÂÂÂ I think maybe there's still some differences between the two qemu repository.

Use spice from backports or recompile the latest from Sid, wheezy packages are too old for newer qemu.
xen already download and compile qemu upstream automatically if you not specify binary in repository.
I also use use wheezy dom0 with same xen and qemu and same domU and spice guest tools installed automatically resize the windows resolution without problem (except rare cases when I connect remote-viewer before windows start).

Below also reply to other mail.

Â
ÂÂÂÂ I'm actively waiting for your advice and willing to do the following debug.
ÂÂÂÂ vm config file is as follow:
name='Win7'
builder="hvm"
memory=2048
vcpus=2
vif=['bridge=br0']
disk=['/srv/vm_templates/1.qcow2,qcow2,hda,rw',',raw,hdb,ro,cdrom']
boot='dc'
device_model_version="qemu-xen"
#device_model_override="/usr/lib/xen/bin/qemu-gdb"
#device_model_override="/usr/local/bin/qemu-system-i386"
viridian=1
vnc=1
vnclisten="0.0.0.0"
vga="qxl"
spice=1
spicehost='0.0.0.0'
spiceport=6000
spicedisable_ticketing=1
spicevdagent=1
spice_clipboard_sharing=1
spiceusbredirection=4
soundhw="hda"
localtime=1
videoram=128

videoram=128 is not needed with qxl as already the default.
Try to disable vnc when you use spice, even if I used with also vnc many times without problem time ago.

Â
 Â
Â

Best Regards

Date:Â2014-07-14Â10:26
Subject:ÂRe: [Xen-devel] QXL problem: Xen 4.4.1 rc1 and xen 4.5 unstable
Hi Fabio Fantoni,
ÂÂÂ Thank you for your help.
ÂÂÂÂ If I use your method to run qemu-gdb when using xl create, xl will complain startup timeout.

I know, I already posted the solution but I try to explain better.

# after xl create with (qemu gdb), do it fast after xl create when arrive on qemu process launch (before timeout or xl create will fails)
target remote localhost:1234 # prepare this command in other ssh to the xen dom0 and enter on xl create when arrive on qemu launch
c # press immediatly
bt full # when qemu stops


Sorry for my bad english.

ÂÂÂ Perhaps I did not describe my problem clearly enough, I can successfully create windows HVM, my problem happened when I change windows screen resolution.
The qemu process suddenly Âexited while xl list can still list the domU information.
Â
ÂÂÂ I am using debian wheezy 7.5 amd 64, I am using fantu's xen 4.5 unstable and the qemu-xen-remote in his code repository,
root@debian:~# /usr/lib/xen/bin/qemu-system-i386 -version
QEMU emulator version 2.0.0, Copyright (c) 2003-2008 Fabrice BellardÂÂ
ÂAnd I compiled Xen from fantu's xen repository in compilation server, then use install.sh in dist dir to install xen packages in my test server.
ÂMy compilation server has spice 0.12.4 compiled and installed.
ÂMy test server has debian wheezy backport qemu installed with spice-server:
dpkg -l |grep spice
ii libspice-server1:amd64 0.12.4-0nocelt2~bpo70+1ÂÂÂ
ÂThen how can I obtain useful debug information after qemu exit with vm running?
Â

Best Regards

Date:Â2014-07-11Â18:06
Subject:ÂRe: [Xen-devel] QXL problem: Xen 4.4.1 rc1 and xen 4.5 unstable
Il 11/07/2014 04:38, kevin.zhang@xxxxxxxxxxx ha scritto:
Hi all,
Â
Firstly please forgive me if I put this problem in the wrong mail list.
However, it seems that xen-users mail list cannot resolve this QXL problems. Therefore, I have to post QXL problem in devel mail list.
My problem is as follow:
Â
I'm testing QXL for windows HVM, spice works well with stdvga.
However, when I switch to QXL, qemu exit abnormally:
I specify vga="qxl" and videoram=128, using qemu-xen. The windows 7 boots and automatially switch resolution for me in virt-viewer.
While display and sound transfering very well, if I change display resolution, the virt-viewer will be suddenly closed and
I check the physical server, the qemu process disappear simultaneously.
Then I switch to wheezy backport qemu 2.0 as device model, the qemu process will exit as soon as the welcome page appears and at the beginning of resolution change.
I tested and found the same bug on both xenbits xen 4.4.1 rc1 and Fantu's Xen 4.5 unstable, this problem exists in both branches.
Is it a known issue or is there any solution for this bug?
Thank you very much!

Thanks for testing spice and qxl and report issue.
I have spice + qxl working as kvm on xen unstable except this problem:
http://lists.xen.org/archives/html/xen-devel/2014-07/msg01021.html

Please post details on your dom0 installation and domU (for example xl cfg,
spice guest tools version ecc...)
About qemu crash try to take a full backtrace with gdb and post it here.

Small help with gdb of qemu launched by xl:

Add the line below in domU's xl cfg:
device_model_override="/usr/lib/xen/bin/qemu-gdb"

vi /usr/lib/xen/bin/qemu-gdb # create the file, change the qemu path if
needed
#!/bin/sh
exec gdbserver 0.0.0.0:1234 /usr/lib/xen/bin/qemu-system-i386 "$@"

# after xl create, do it fast (before timeout or xl create will fails)
target remote localhost:1234
c
bt full # when qemu stops

You should install also all needed dbg packages before, spice qemu ecc or
without package should be compiled with debug enabled (for xen and qemu
default in unstable).

The latest qemu crash with spice I saw was in 2.0-rc solved before 2.0.0
final, your qemu is at least 2.0.0 final?
http://git.qemu.org/?p=qemu.git;a=commit;h=dc491cfc14074064ed54a872b62cce6ca1330644


Â
Â
Kevin
Best Regards,

Â








_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.