1 files changed, 122 insertions, 0 deletions
diff --git a/results/classifier/118/all/1042084 b/results/classifier/118/all/1042084
new file mode 100644
index 00000000..3f06b018
--- /dev/null
+++ b/results/classifier/118/all/1042084
@@ -0,0 +1,122 @@
+permissions: 0.972
+graphic: 0.957
+mistranslation: 0.954
+semantic: 0.953
+assembly: 0.950
+performance: 0.949
+PID: 0.945
+arm: 0.943
+boot: 0.942
+register: 0.940
+peripherals: 0.937
+user-level: 0.937
+VMM: 0.935
+debug: 0.933
+risc-v: 0.929
+architecture: 0.924
+hypervisor: 0.923
+virtual: 0.909
+vnc: 0.901
+files: 0.901
+device: 0.900
+ppc: 0.898
+socket: 0.886
+KVM: 0.875
+TCG: 0.872
+kernel: 0.866
+x86: 0.829
+network: 0.806
+i386: 0.779
+
+Windows 7 guest cannot boot after seabios updated
+
+Hi,
+
+I can no longer boot my Windows 7 guest after this commit (update seabios to latest master)
+
+http://git.qemu.org/?p=qemu.git;a=commitdiff;h=01afdadc92e71e29700e64f3a5f42c1c543e3cf9
+
+When I tried to boot Windows, it BSOD and said "The BIOS in this system is not fully ACPI compliant. Please contact your system vendor for an updated  BIOS". Reverting this commit will fix the issue.
+
+On Mon, Aug 27, 2012 at 7:54 AM, Vic <llyzs@163.com> wrote:
+> Public bug reported:
+>
+> Hi,
+>
+> I can no longer boot my Windows 7 guest after this commit (update
+> seabios to latest master)
+>
+> http://git.qemu.org/?p=qemu.git;a=commitdiff;h=01afdadc92e71e29700e64f3a5f42c1c543e3cf9
+>
+> When I tried to boot Windows, it BSOD and said "The BIOS in this system
+> is not fully ACPI compliant. Please contact your system vendor for an
+> updated  BIOS". Reverting this commit will fix the issue.
+
+Gerd, Kevin: Any ideas?
+
+>
+> ** Affects: qemu
+>      Importance: Undecided
+>          Status: New
+>
+> --
+> You received this bug notification because you are a member of qemu-
+> devel-ml, which is subscribed to QEMU.
+> https://bugs.launchpad.net/bugs/1042084
+>
+> Title:
+>   Windows 7 guest cannot boot after seabios updated
+>
+> Status in QEMU:
+>   New
+>
+> Bug description:
+>   Hi,
+>
+>   I can no longer boot my Windows 7 guest after this commit (update
+>   seabios to latest master)
+>
+>   http://git.qemu.org/?p=qemu.git;a=commitdiff;h=01afdadc92e71e29700e64f3a5f42c1c543e3cf9
+>
+>   When I tried to boot Windows, it BSOD and said "The BIOS in this
+>   system is not fully ACPI compliant. Please contact your system vendor
+>   for an updated  BIOS". Reverting this commit will fix the issue.
+>
+> To manage notifications about this bug go to:
+> https://bugs.launchpad.net/qemu/+bug/1042084/+subscriptions
+>
+
+
+On 08/28/12 10:07, Stefan Hajnoczi wrote:
+> On Mon, Aug 27, 2012 at 7:54 AM, Vic <llyzs@163.com> wrote:
+>> Public bug reported:
+>>
+>> Hi,
+>>
+>> I can no longer boot my Windows 7 guest after this commit (update
+>> seabios to latest master)
+>>
+>> http://git.qemu.org/?p=qemu.git;a=commitdiff;h=01afdadc92e71e29700e64f3a5f42c1c543e3cf9
+>>
+>> When I tried to boot Windows, it BSOD and said "The BIOS in this system
+>> is not fully ACPI compliant. Please contact your system vendor for an
+>> updated  BIOS". Reverting this commit will fix the issue.
+> 
+> Gerd, Kevin: Any ideas?
+
+Not yet.  My win7 32bit guests boots fine.  Installing 64bit version
+right now to see how that behaves, at least the windows setup booted
+just fine too.
+
+cheers,
+  Gerd
+
+
+I have tried both 32-bit and 64-bit Windows 7, both have the same issue. But I can also boot into the Window 7 setup. I have tried to use the repair option but it cannot repair it. I then recreated the partion and do a fresh installation and it then boots fine. So this issue only affects the guest which was installed before the BIOS update.
+
+I am now trying to reinstall a new instance without the BIOS update, then update the BIOS after that to see if I can reproduce the issue.
+
+I cannot reproduce the issue with newly created image, so looks like this is not a qemu bug, but just a problem of my corrupted image. Sorry for the noise, please close the issue and I will report another one if I find other things.
+
+Closing, according to comment #5.
+