From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40900) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XQ0El-0004lD-Sy for qemu-devel@nongnu.org; Fri, 05 Sep 2014 16:36:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XQ0Eh-0004co-TO for qemu-devel@nongnu.org; Fri, 05 Sep 2014 16:36:03 -0400 Received: from mx1.redhat.com ([209.132.183.28]:17733) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XQ0Eh-0004cZ-M3 for qemu-devel@nongnu.org; Fri, 05 Sep 2014 16:35:59 -0400 Message-ID: <540A1EA7.60502@redhat.com> Date: Fri, 05 Sep 2014 16:35:51 -0400 From: John Snow MIME-Version: 1.0 References: <20140904131038.GC1675@ERROL.INI.CMU.EDU> <1409840479.3390.1.camel@novetica.org> In-Reply-To: <1409840479.3390.1.camel@novetica.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [Bug 1358722] Re: latest acpi commits causes memory allocation fault in macosx List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Marco Minetti , "Gabriel L. Somlo" Cc: Paolo Bonzini , qemu-devel@nongnu.org On 09/04/2014 10:21 AM, Marco Minetti wrote: > On Thu, 2014-09-04 at 09:10 -0400, Gabriel L. Somlo wrote: >> On Thu, 04 Sep 2014 08:43:12, Marco Minetti wrote: >>> The experiments for running MacOSXon KVM/QEMU I followed are here: >>> http://www.contrib.andrew.cmu.edu/~somlo/OSXKVM/ >>> >> [...] >>> >>> Bug description: >>> qemu release 2.1.0 >>> >>> Hi, >>> I've found a regression on MacOSX guest (10.9.4) after merging the= following commits >>> >>> 18045fb9f457a0f0cba2bd113c748a2dcb4ed39e pc: future-proof migratio= n-compatibility of ACPI tables >>> 868270f23d8db2cce83e4f082fe75e8625a5fbf9 acpi-build: tweak acpi mi= gration limits >>> >>> The migration limits make x86 chameleon bootloader generate a memo= ry >>> allocation error with 0xdeadbeef address at line 899 in source fil= e: >>> >>> http://forge.voodooprojects.org/p/chameleon/source/tree/2360/branc= hes/Bungo/i386/libsaio/acpi_patcher.c >>> >>> I've not tried to recompile chameleon yet. >>> >>> To manage notifications about this bug go to: >>> https://bugs.launchpad.net/qemu/+bug/1358722/+subscriptions >> >> If you absolutely need those commits, you may be better off just >> using qemu's git master branch altogether (which works fine, at >> least for me). Grabbing two more or less arbitrary commits from git >> and applying them on top of 2.1.0 may cause you to miss other changes >> which actually enable those patches to work. >> >> HTH, >> --Gabriel > > Those commits are already included into 2.1.0 release tag. I tested > almost any commit refs from tag v2.1.0-rc3 to v2.1.0. Things get broken > with the commits above with or without following commits. > > I'll wait for the next 2.1.x release on git.qemu.org to test again. I > actually prefer not to use master to build packages for my bleeding-edg= e > Ubuntu-based distro. > > Thanks! > > Hi, for what it's worth, I've observed other regressions related to the=20 same commits. RedHat BZ 1128608;=20 https://bugzilla.redhat.com/show_bug.cgi?id=3D1128608 appears to be a=20 regression caused by commit 18045f. These are definitely present in Qemu 2.1 and downstream packages based=20 on 2.1. --=20 =E2=80=94js