(SOLVED) Green Turtle in WinXP guest on VB7.02 Host on Ventura 13.01

[mx507]

Another happy guest Windows XP user on Ventura 13.2/VB 7.0.6/iMac2020/Intel i5.

Indeed: Great!

Did anyone try to upgrade Ventura to Sonoma and could it be verified that the configuration continues to work?
Frankly, I am very reluctant to update to Sonoma given the experience when updating to Ventura.

My current configuration Ventura 13.5.2/VB 7.0.4/iMac 2017 Intel i5 is working very, very fine.
I am taking as I have no clue if the issue that must have been the underlying problem when upgrading Monterey -> Ventura will happen again now when I upgrade Ventura -> Sonoma.

Any confirmation from someone who is more brave than I am would be much appreciated.

[multiOS]

VirtualBox V7.0.10 is working fine so far for me on macOS 14.0 (Sonoma). Installation is on a 2019/20 MacBook Pro (Intel i9) which was previously running Ventura.

[mx507]

Great Thanks @multiOS for letting me know! This is good to know.

[solamour]

If I uncheck "Enable I/O APIC", I'm not able to boot the Windows 10 guest. Same thing happens if I try to boot from the Windows installation CD as well. Curious to know whether there are others who are experiencing the same problem.
__
sol

[scottgus1]

@solamour, looks like you read through some to find out about I/O Apic. Ddi you notice the first post where it was mentioned viewtopic.php?p=529501#p529501 There's a procedure there to disable it. You don't disable it before running the procedure. Already-installed XP has to stay on the setting I/O Apic was at when it was installed. (Leastways if XP was installed with I/O Apic on, you can't just turn it off.)

[solamour]

@solamour, looks like you read through some to find out about I/O Apic. Ddi you notice the first post where it was mentioned viewtopic.php?p=529501#p529501 There's a procedure there to disable it.

That's something I wanted to bring up as well. I couldn't find "Advanced Power and Configuration Interface (ACPI) PC" as described in the instruction; the only option available was "ACPI x64-based PC". Perhaps that's the difference between Windows XP and Windows 10?
__
sol

[fth0]

Try not to confuse ACPI (Advanced Power and Configuration Interface) with APIC (Advanced Programmable Interrupt Controller ).

Ah, I see now what you mean. The key is that an I/O APIC is mandatory when having more than 1 vCPU, so turning it off only makes sense when having a single vCPU. Other than that, the device name is different in different Windows versions AFAIR.

[solamour]

Just to see what happens, I tried booting from Windows 10 ISO file with 1 CPU and "Enable I/O APIC" off, and it got stuck with what's in the attached file. This happens regardless the host is macOS or Windows, so at least the behavior is consistent. I'm starting to suspect that perhaps it works with Windows XP guest, but not with Windows 10 guest.
__
sol

[mpack]

Win10 belongs well (about 2 decades) into the IO-APIC era, so turning it off makes no sense at all IMO. Besides which Win10 has lots of requirements that XP did not have - practical differences too, like being pretty much useless on a single core, and as Fth0 mentions, the advanced I/O controller is mandatory if you enable multiple cores.

That said, I'm interested to see that graphics pattern, which is an old favorite around here. Nice to know how you created it.

[scottgus1]

If I recall correctly, the green checkers are from interference with Intel PowerGadget on the host. Try uninstalling that app, see what happens.