1 files changed, 52 insertions, 0 deletions
diff --git a/results/classifier/118/x86/1358722 b/results/classifier/118/x86/1358722
new file mode 100644
index 000000000..9e96a431d
--- /dev/null
+++ b/results/classifier/118/x86/1358722
@@ -0,0 +1,52 @@
+x86: 0.921
+device: 0.825
+boot: 0.799
+architecture: 0.792
+i386: 0.767
+ppc: 0.718
+graphic: 0.693
+KVM: 0.628
+semantic: 0.623
+files: 0.591
+PID: 0.580
+vnc: 0.574
+performance: 0.527
+mistranslation: 0.522
+register: 0.493
+kernel: 0.490
+socket: 0.476
+virtual: 0.469
+debug: 0.411
+user-level: 0.401
+network: 0.378
+risc-v: 0.316
+arm: 0.315
+TCG: 0.293
+permissions: 0.281
+assembly: 0.266
+VMM: 0.262
+peripherals: 0.238
+hypervisor: 0.091
+
+latest acpi commits causes memory allocation fault in macosx
+
+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.
+
+The experiments for running MacOSXon KVM/QEMU I followed are here: http://www.contrib.andrew.cmu.edu/~somlo/OSXKVM/
+
+Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+