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 > > 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
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-edge Ubuntu-based distro. Thanks!