From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34494) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XPWoI-0006u1-8L for qemu-devel@nongnu.org; Thu, 04 Sep 2014 09:10:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XPWoD-0000qH-UH for qemu-devel@nongnu.org; Thu, 04 Sep 2014 09:10:46 -0400 Received: from mail-qc0-x229.google.com ([2607:f8b0:400d:c01::229]:38631) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XPWoD-0000q3-N5 for qemu-devel@nongnu.org; Thu, 04 Sep 2014 09:10:41 -0400 Received: by mail-qc0-f169.google.com with SMTP id l6so10568917qcy.28 for ; Thu, 04 Sep 2014 06:10:41 -0700 (PDT) Date: Thu, 4 Sep 2014 09:10:39 -0400 From: "Gabriel L. Somlo" Message-ID: <20140904131038.GC1675@ERROL.INI.CMU.EDU> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140904084313.24944.7145.malone@soybean.canonical.com> 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: qemu-devel@nongnu.org Cc: marco.minetti@novetica.org 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 migration-compatibility of ACPI tables > 868270f23d8db2cce83e4f082fe75e8625a5fbf9 acpi-build: tweak acpi migration limits > > The migration limits make x86 chameleon bootloader generate a memory > allocation error with 0xdeadbeef address at line 899 in source file: > > http://forge.voodooprojects.org/p/chameleon/source/tree/2360/branches/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