Version
trunk/main
Host OS Type
Windows
Host Architecture
x86
Guest OS Type
Linux
Guest Architecture
x86
Component
Other
What happened?
This happened after updating to VirtualBox 7.1.12, released July 15 2025. But that version does not seem to exist here. I don't understand
Starting my virtual machines gave me errors in the DisplayWrap module: "Argument aWidth is invalid (must be aWidth != 0 && aWidth <= 32767)".
Above that in the log, I see some weird values, maybe related:
00:00:05.484833 Max display size: 2048x2048
00:00:05.484834 Display size: 4294967295x4294967295 32bpp
00:00:05.484835 Scanline: 0 (0x0)
00:00:05.484836 Viewport position: 0x0
00:00:05.484836 Viewport size: 0x0
In one case (maybe I clicked "Ignore" to continue trying the boot process) the error was in the ConsoleWrap module: "The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND".
Reverting to VirtualBox 7.1.10 fixed these issues and the VMs start.
Two logs: one of them contains messages after reverting to 7.1.10 and booting OK. But also the error.
VBox.log
VBox.log
How can we reproduce this?
Not sure. Boot existing Linux 32 bit VMs in a Windows host after updating to 7.1.12. The VMs have fairly old OS versions, BTW (e.g. Ubuntu 10 IIRC in one case).
I tried two Display drivers (VMSVGA, VBoxSVGA) and the result was the same.
Did you upload all of your necessary log files, screenshots, etc.?
Version
trunk/main
Host OS Type
Windows
Host Architecture
x86
Guest OS Type
Linux
Guest Architecture
x86
Component
Other
What happened?
This happened after updating to VirtualBox 7.1.12, released July 15 2025. But that version does not seem to exist here. I don't understand
Starting my virtual machines gave me errors in the DisplayWrap module: "Argument aWidth is invalid (must be aWidth != 0 && aWidth <= 32767)".
Above that in the log, I see some weird values, maybe related:
In one case (maybe I clicked "Ignore" to continue trying the boot process) the error was in the ConsoleWrap module: "The VBoxGuestPropSvc service call failed with the error VERR_HGCM_SERVICE_NOT_FOUND".
Reverting to VirtualBox 7.1.10 fixed these issues and the VMs start.
Two logs: one of them contains messages after reverting to 7.1.10 and booting OK. But also the error.
VBox.log
VBox.log
How can we reproduce this?
Not sure. Boot existing Linux 32 bit VMs in a Windows host after updating to 7.1.12. The VMs have fairly old OS versions, BTW (e.g. Ubuntu 10 IIRC in one case).
I tried two Display drivers (VMSVGA, VBoxSVGA) and the result was the same.
Did you upload all of your necessary log files, screenshots, etc.?