New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VirtualBox: Windows7 guest stopped working #11563
Labels
bug
Something isn't working
Comments
pullmoll
changed the title
VirtualBox: Windows7 host stopped working
VirtualBox: Windows7 guest stopped working
May 8, 2019
Possibly related upstream bug report: https://www.virtualbox.org/ticket/18628 |
|
Possibly related to acpica/acpica#462 |
Oh, yes. Thanks for the pointer. I'll give it a try. |
On May 11, 2019 5:31:26 PM UTC, "Jürgen Buchmüller" ***@***.***> wrote:
Oh, yes. Thanks for the pointer. I'll give it a try.
The linked pull request works for me. I think it's worth a try.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
|
Solved and merged the acpica update. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System
Void 5.0.13_1 x86_64 AuthenticAMD uptodate rrrdFFFFFF
virtualbox-ose-6.0.6_1
Expected behavior
Being able to to use my years old *.vbox and *.vdi files, or at least be able to boot Win7 installer ISO.
Actual behavior
Neither my installed Win7 nor the Windows7 installer ISO will work. They print a message about the ACPI being incompatible and stop "to avoid damage to my software". The stop code is 165 (0x000000a5).
Steps to reproduce the behavior
Try to boot a Win7 installer ISO in VirtualBox 6.0.6 perhaps?
I tried various combinations of # of virtual cores, RAM, PCIIX3 and ICH9 chipsets, accelerator modes. I found no combination that works.
I can use the same *.vdi files in qemu, but of course that invalidates my license because Microsoft thinks this is a different machine. sigh
Any ideas or similar reports yet?
The text was updated successfully, but these errors were encountered: