ABI-v1 nightly - black screen on VM VirtualBox

[retrofaza]

Have you also stopped working nightly builds of ABI-v1 (pc-x86_64-boot-iso) on VirtualBox VM? After selecting the resolution (no matter which option I choose) I only have a black screen. Could someone please test this on their machine?

[AMIGASYSTEM]

Tested the latest version of 'ABI-v1 night' and it works very well on both VirtualBox and VMware (recommended)

[retrofaza]

Thank you AMIGASYSTEM. Did you check pc-x86_64-boot-iso or pc-i386-boot-iso?

[AMIGASYSTEM]

pc-i386-boot-iso, you can also see it in the screenshot I attached "

 I'm sorry I didn't read it right, now I'll also test !!!

[magorium]

Have you also stopped working nightly builds of ABI-v1 (pc-x86_64-boot-iso) on VirtualBox VM? After selecting the resolution (no matter which option I choose) I only have a black screen. Could someone please test this on their machine?

Do you mean the grub option ? because if that is the case then it is virtualbox which is probably causing issues (it is a known bug that after grub the virtual screen goes black, though the OS is running in such case).

Did you perhaps updated VBox recently ?

[AMIGASYSTEM]

Confirmed, pc-x86_64-boot-iso on VirtualBox regularly does the Boot, after GRUB the screen remains black.

On VMware (recommended for AROS) pc-x86_64-boot-iso works perfectly, see screenshot

[retrofaza]

Thanks guys for the answers. So the fault must be on the Virtualbox side, I'm facing a switch to VMWare in that case

[AMIGASYSTEM]

Yes VMware is the right choice, it works much better, and all operations are smoother!

In the configuration choose 'Other 64-Bit' and add the required hardware 'manually'.

[magorium]

Yes VMware is the right choice, it works much better, and all operations are smoother!

Usually there is  nothing wrong with virtualbox if not for their mental challenged decision makers that fixes an issue and breaks it immediately upon the next release or minor update (sometimes also for issues that where fixed satisfactory years ago).

fwiw I am not stating this is TS' current issue but it sure looks like it. To make sure always try an older known to work version of AROS, if that shows the same behaviour then you can blame it on the virtualization software otherwise there might be regression in the AROS sources.

[AMIGASYSTEM]

Unfortunately, previous builds are no longer available, and verification is not possible.

However, if on VMware the new Build works, this suggests that the problem is on VirtualBox

[magorium]

Unfortunately, previous builds are no longer available, and verification is not possible.

vcs but other than that I really do not understand the latest/newest vs stable/working. Storage is cheap these days btw.

However, if on VMware the new Build works, this suggests that the problem is on VirtualBox

There is code that specifically deals with vmware (also for graphics), so that statement is untrue.

[Studenteer]

I have tested already installed AROS ABIv1 from July 22th and the newest AROS ABIv1 (August 5th) on Virtual Box 7.08 and Virtual Box 7.10.
The blackscreen was detectable during newest AROS ABIv1 on Virtual Box 7.10. Other versions runs well on Virtual Box 7.10 aswell as newest AROS ABIv1 on Virtual Box 7.08. So a downgrade would be an option if using newest AROS ABIv1.

[AMIGASYSTEM]

vcs but other than that I really do not understand the latest/newest vs stable/working. Storage is cheap these days btw.

The deadwood ABI-v0 builds are all available for download, I don't understand why the ABI-v1 builds are not all available. I keep hundreds of ISOs and lots of HardFiles, but since I don't use 64Bit systems, I have no need to keep the builds.

I also use VirtualBox very little, I only use it occasionally to do some testing.

There is code that specifically deals with vmware (also for graphics), so that statement is untrue.

OK, I didn't know there was specific code for VirtualBox, I thought VirtualBox used the same code as VMware