From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Kinzler Subject: Re: Regression: qemu crash of hvm domUs with spice (backtrace included) Date: Thu, 08 Oct 2015 17:58:05 +0200 Message-ID: <5616928D.4050308@posteo.de> References: <553508EB.6030400@m2r.biz> <553636BF.9060609@m2r.biz> <5550C517.70602@m2r.biz> <5551C6A9.6040400@m2r.biz> <5551D568.4010006@m2r.biz> <55520630.1080901@m2r.biz> <555351BA.9060807@m2r.biz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <555351BA.9060807@m2r.biz> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org, stefano.stabellini@eu.citrix.com, fabio.fantoni@m2r.biz List-Id: xen-devel@lists.xenproject.org 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? >