From: Marco Minetti <marco.minetti@novetica.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1358722] Re: latest acpi commits causes memory allocation fault in macosx
Date: Thu, 04 Sep 2014 08:43:12 -0000 [thread overview]
Message-ID: <20140904084313.24944.7145.malone@soybean.canonical.com> (raw)
In-Reply-To: 20140819123712.28945.58932.malonedeb@chaenomeles.canonical.com
The experiments for running MacOSXon KVM/QEMU I followed are here:
http://www.contrib.andrew.cmu.edu/~somlo/OSXKVM/
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1358722
Title:
latest acpi commits causes memory allocation fault in macosx
Status in QEMU:
New
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
next prev parent reply other threads:[~2014-09-04 8:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 12:37 [Qemu-devel] [Bug 1358722] [NEW] latest acpi commits causes memory allocation fault in macosx Marco Minetti
2014-09-04 8:43 ` Marco Minetti [this message]
2014-09-04 13:10 ` [Qemu-devel] [Bug 1358722] " Gabriel L. Somlo
2014-09-04 14:21 ` Marco Minetti
2014-09-05 20:35 ` John Snow
2017-10-26 13:21 ` Thomas Huth
2017-12-26 4:17 ` Launchpad Bug Tracker
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=20140904084313.24944.7145.malone@soybean.canonical.com \
--to=marco.minetti@novetica.org \
--cc=1358722@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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.