From: Andreas Kinzler <hfp@posteo.de>
To: xen-devel@lists.xen.org, stefano.stabellini@eu.citrix.com,
fabio.fantoni@m2r.biz
Subject: Re: Regression: qemu crash of hvm domUs with spice (backtrace included)
Date: Thu, 08 Oct 2015 17:58:05 +0200 [thread overview]
Message-ID: <5616928D.4050308@posteo.de> (raw)
In-Reply-To: <555351BA.9060807@m2r.biz>
Is this still current? I made an interesting observation:
I had no problems with SPICE and vanilla Xen 4.5.1 when using it on
Gentoo with glibc 2.19/gcc 4.6.4.
Segfaults started when I switched to glibc 2.20/gcc 4.9.3 - I did not
change Xen source code at all.
All this might be related to:
https://lists.nongnu.org/archive/html/qemu-devel/2015-06/msg02764.html
Andreas
> https://github.com/Fantu/Xen/commits/rebase/m2r-staging
> Latest test with regression based on latest stable-4.5, more exactly:
> https://github.com/Fantu/Xen/commits/rebase/m2r-testing
> Some days ago on same dom0 and domU I tried with latest stable version
> (that I use on only 2 production servers for now but I not saw the
> regression), more exactly:
> https://github.com/Fantu/Xen/commits/rebase/m2r-stable-4.5
> Dom0 debian 7 with kernel 3.16 from backports, seabios 1.8.1-2 from
> unstable and this xen configure:
> ./configure --prefix=/usr --disable-blktap1 --disable-qemu-traditional
> --disable-rombios
> --with-system-seabios=/usr/share/seabios/bios-256k.bin
> --with-extra-qemuu-configure-args="--enable-spice --enable-usb-redir"
> --disable-blktap2
>
> I suppose that there is unexpected case caused by a backports or
> missed patch/es to backports from unstable.
> I not found with a fast look rilevant patch to try to revert, can
> anyone suggest me the more probable point/s for bisect and/or patch to
> revert or I must try full bisect 4.5.0->stable-4.5?
>
next prev parent reply other threads:[~2015-10-08 15:58 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 14:10 [Qemu-devel] Regression: qemu crash of hvm domUs with spice (backtrace included) Fabio Fantoni
2015-04-21 10:49 ` Stefano Stabellini
2015-04-21 11:38 ` Fabio Fantoni
2015-04-21 12:53 ` Stefano Stabellini
2015-04-21 12:53 ` [Qemu-devel] " Stefano Stabellini
2015-05-11 15:04 ` Fabio Fantoni
2015-05-11 15:04 ` [Qemu-devel] " Fabio Fantoni
2015-05-12 9:23 ` Fabio Fantoni
2015-05-12 9:23 ` [Qemu-devel] " Fabio Fantoni
2015-05-12 10:26 ` Fabio Fantoni
2015-05-12 10:26 ` [Qemu-devel] " Fabio Fantoni
2015-05-12 13:54 ` Fabio Fantoni
2015-05-12 13:54 ` [Qemu-devel] " Fabio Fantoni
2015-05-12 14:38 ` Stefano Stabellini
2015-05-12 14:44 ` Stefano Stabellini
2015-05-13 13:29 ` Fabio Fantoni
2015-05-15 10:26 ` Stefano Stabellini
2015-05-15 10:26 ` [Qemu-devel] " Stefano Stabellini
2015-10-08 15:58 ` Andreas Kinzler [this message]
2015-10-08 16:24 ` Andreas Kinzler
2015-10-09 7:56 ` Fabio Fantoni
2015-10-16 12:09 ` Regression: qemu crash of hvm domUs with spice (backtrace included) - patch backport propose Fabio Fantoni
2015-10-16 14:01 ` Stefano Stabellini
2015-10-19 15:06 ` Stefano Stabellini
2015-05-13 13:29 ` Regression: qemu crash of hvm domUs with spice (backtrace included) Fabio Fantoni
2015-05-12 14:44 ` Stefano Stabellini
2015-05-12 14:38 ` Stefano Stabellini
2015-04-21 11:38 ` Fabio Fantoni
2015-04-21 10:49 ` Stefano Stabellini
-- strict thread matches above, loose matches on Subject: below --
2015-04-20 14:10 Fabio Fantoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5616928D.4050308@posteo.de \
--to=hfp@posteo.de \
--cc=fabio.fantoni@m2r.biz \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.