[VBox-users] Problem with XPSP3 VM in VBox 7.0.XX

[<sa...@xs...>]

Hello:

I have a problem with a XPSP3 VM running on VirtualBox 7.0.12, in 
turn on a Devuan Beowulf box with a backported kernel.

[code]
~$ vboxmanage --version
7.0.12r159484
~$ 
~$ uname -a
Linux devuan 5.10.0-0.deb10.16-amd64 #1 SMP Debian 5.10.127-2~bpo10+1 
(2022-07-28) x86_64 GNU/Linux
~$ 
[/code]

I only use this VM every so often to run BlackBerry desktop and sync 
my handheld to the only thing available today to do so, Outlook 
Express.   8^/

For the sake of clarity/brevity I will skip the long story and just 
post the essentials:

1.
Discovered the problem and rolled back to a VM snapshot from 30 days 
ago, the oldest one I have.

Concurrently, rolled back to VBox (7.0.6) along with its 
GuestAdditions 7.0.6.  

I thought that it would rule out (?) a VBox update or some corruption 
in the XPSP3 VM as everything happened way after that date.   

At least I did not notice it as I do not use the XP VM often. 

Problem did *not* go away.

2.
Removed VBox 7.0.6 / GuestAdditions 7.0.6, reinstalled the latest 
available (7.0.12) along with GuestAdditions and the Extension Pack 
which was missing.

Problem did *not* go away.

3.
Went back to the last snapshot and tried to fix things by mucking 
around the XPSP3 installation but only managed to screw it up even 
more.

The net result being that it is now on a 'black screen select how to 
boot' and 'blue screen with whatever' loop.

ie: useless

4.
I attempted to add a new XP VM using three or four of the 
downloadable XP isos I found on the web and was able to install one 
of them as a VM.

Problem did *not* go away and shutdown does not work.
Not even shutting down X via ctrl+backspace.
Have to reboot my box.

TL;DR

The problem exists whether I use VirtualBox 7.06 or 7.0.12, with a 
recovered version of the VM or the latest one.

Installing a new XPSP3 VM, whether in VirtualBox 7.0.6 or 7.0.12, 
complete with GA+EP does not solve the problem.

In all cases, disconnecting the host from the web (cable and all) 
does not solve the problem so phoning home does not seem to be a 
posible cause.

This is (part of) what I get in a rolling dmesg screen:

[code]
------------[ cut here ]------------
--- snip ---

WARNING: CPU: 0 PID: 16511 at arch/x86/kernel/fpu/core.c:129 
kernel_fpu_begin_mask+0xc9/0xe0
--- snip ---
Call Trace:
[  +0.000031]  SUPR0FpuBegin+0x13/0x20 [vboxdrv]
[  +0.000006]  ? up+0x12/0x50
[  +0.000014]  ? VBoxHost_RTThreadCtxHookEnable+0x32/0x40 [vboxdrv]
[  +0.000012]  ? supdrvIOCtl+0xc5e/0x3650 [vboxdrv]
[  +0.000013]  ? rtR0MemAllocEx+0x57/0xd0 [vboxdrv]
[  +0.000012]  ? supdrvIOCtlFast+0x58/0xb0 [vboxdrv]
[  +0.000011]  ? VBoxDrvLinuxIOCtl_7_0_12+0x57/0x230 [vboxdrv]
[  +0.000003]  ? __x64_sys_ioctl+0x84/0xc0
[  +0.000004]  ? do_syscall_64+0x33/0x80
[  +0.000003]  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[  +0.000002] ---[ end trace 2d76295c57757cc8 ]---
[/code]

Let me know if you need to see the whole shebang or any other data.

That said, it seems that *here be modules* at work:

[code]
~$ lsmod | grep vbox
vboxnetadp             28672  0
vboxnetflt             32768  1
vboxdrv               589824  4 vboxnetadp,vboxnetflt   # <- this one
~$ 
[/code]

If anyone has a clue as to what the trace in dmesng indicates, I'm 
all ears.

Thanks in advance.

Best.