Il 04/12/2025 23:16, Lewis G Rosenthal ha scritto:

Hi, Max...

On 11/24/25 04:09 am, Massimo S. wrote:

Hi,

i had first a strange "slow down", i connected to the VM and i couldn't neither run "go.exe", the prompt was sluggish.

I was able to give a setboot /b.

After the first reboot i got 3 of these ring0 traps about 1/2 minutes after the boot.
First TCP/IP communications went away (even no ping), r0 trap after some seconds.
Guest VM is AOS 503, 4GB ram, storage is NVME, 4 cores assigned to the VM.

I've attached the r0 trap screen, hope that the ML support attachments.

Anyway it was a version 6.x of Virtual box on Win Server 2019 STD, after i
upgraded to 7.1.14 (170994 released on Cctober 2025), that's still supported.

For now i've seen anymore that r0 trap.

Anyway, someone could tell me why the system had this kind of trap?

I think you will find that 99% of crashes under any hypervisor which mysteriously go away after an upgrade of the hypervisor software are/were originally due to a failure of that hypervisor to properly emulate the hardware as expected by the guest OS. Sometimes, the lack of an exact virtualization of a particular component is either unnecessary or the OS itself can tolerate it (or the function not being implemented as expected is simply not used all that often - or at all). Other times, it can be something critical.

We know that there were a number of changes to the VBox core between 6.x, 7.0, and 7.1 which brought much more stability to OS/2-based guests. Some of this may have been as a result of Arca Noae's requests and suggestions; I cannot say for certain. What I can say is that Arca Noae maintains a very good relationship with a couple of the developers involved/interested in OS/2 support under VBox, and we are grateful for the attention we receive when we ask for it.

Glad this is working better for you under 7.1.

Hi,

unforntunately, it's not.
Nothing improved.

Another suggestion is to keep the guest additions up to date. Later releases of ArcaOS ship with packaged guest additions which are generally current with supported release versions of VBox.

After months running the AOS 503 VM under 7.1 vbox i've seen that issues are not gone.

When the VM (apache+php web srv) runs out of some system resources it hang at the
scheduled reboot at 6,30 in the morning, with the grey popup
"the system is rebooting, please wait ...".

What happens: i turn OFF the VM from the virtualizer (not shutdown, but power off).
I start it again, at the 1st boot it starts regularly and after about 10-15 seconds
it loose TCP/IP connectivity.

Setboot /b in this case don't help, so i've to power off brutally again the VM.

At the 2nd power OFF reboot, i'm lucky i get a blue screen trap and it reboot
at this time it start to work properly.

I'm using E1000 nic driver V3.62 intel pro/1000 network connection inside the VM
and in the virtualizer i'm using Intel PRO/1000 MT server
(sk with bridge, Intel (82574L Gigabit Network Connection).

I've seen on another VM (with eCS 2.2b + AN driver package, that this issue of
the loosing tcpip connectivity after reboot it don't happens, but i'm running
MMLEM 1.1.4 driver).

Do you have any suggestion for the AOS 503 VM?

Eg. Using MMLEM driver there too?
But i've seen and it's 1.1.3 version, is that good enough?

thanks

massimo