NS_ERROR_INVALID_ARG related to aWidth after migrating to 6.1.14-dfsg-4 on Debian sid

[Tekkk]

Hi everyone,

I migrated this week from Virtualbox 6.1.14-dfsg-3 to 6.1.14-dfsg-4 on my debian sid machine. I now have an issue that makes every single VM I have to crash with the following error:

Code: Select all

00:00:01.052726 emR3Debug: rc=VERR_INVALID_STATE
00:00:01.548740 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 1912x985
00:00:01.551342 ERROR [COM]: aRC=NS_ERROR_INVALID_ARG (0x80070057) aIID={4680b2de-8690-11e9-b83d-5719e53cf1de} aComponent={DisplayWrap} aText={Argument aWidth is invalid (must be aWidth != 0 && aWidth <= 32767)}, preserve=false aResultDetail=0
00:00:03.072946 GUI: User request to power VM off on Guru Meditation.

I cannot find any clear explanation of what this aWidth parameter is, I have checked in all configuration files and this parameter does not exist. I have not changed any configuration recently and it does not seem to come from the Virtual Machines as they are all breaking, including newly created one.

Any idea where it could come from? Could that be a bug?

[mpack]

00:00:00.838875 VirtualBox VM 6.1.14_Debian r140239 linux.amd64 (Sep 16 2020 09:58:39) release log

I don't recognize the error. In any case you are not using VirtualBox, you are using a fork created by the Debian people, so you need to go to them for support.

One thing that sticks out is that you grossly overcommitted RAM. You need to free up some, add more, or allocate less to the VM - I'd go with 4GB.

00:00:00.839192 Host RAM: 15695MB (15.3GB) total, 6668MB (6.5GB) available
...
00:00:00.890045 RamSize <integer> = 0x00000001f7000000 (8 438 939 648, 8 048 MB, 7.8 GB)
00:00:00.890309 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)

On the other hand you seem to have paid no attention to CPU allocation: Win10 will run like molasses on 1 core. You have 4 available, so you can afford to give 2 to the VM.

00:00:00.890041 NumCPUs <integer> = 0x0000000000000001 (1)

[Tekkk]

I found the issue, it was indeed a system problem with the package (my use somehow got removed from the vboxusers group) and not a VirtualBox issue.

One thing that sticks out is that you grossly overcommitted RAM. You need to free up some, add more, or allocate less to the VM - I'd go with 4GB.

I have 16GB, not 8 as shown here, could there be an issue there too?

On the other hand you seem to have paid no attention to CPU allocation: Win10 will run like molasses on 1 core. You have 4 available, so you can afford to give 2 to the VM.

Good point, I will update that, thanks!

Edit: I am not sure why I cannot edit the first post to add [Solved], is that something blocked for new users?

[scottgus1]

I have 16GB, not 8

8 is the guest RAM. 16 (15.3), of which 6.5 is available, is shown in the Host RAM line above. The problem is 8 > 6.5.

why I cannot edit the first post

New users are asked to build up good forum activity for a while before being able to edit.