VirtualBox

Opened 2 months ago

Closed 2 weeks ago

#22328 closed defect (fixed)

Bandwidth Limit Group issue => fixed in SVN/next 7.1.x maintenance

Reported by: thedisbo1125 Owned by: paulson
Component: other Version: VirtualBox-7.1.6
Keywords: Cc:
Guest type: other Host type: Linux

Description

Receive the following error when trying to start VM:

Waiting for VM "test" to power on... VBoxManage: error: The integer value was too big for the requested representation. (VERR_CFGM_INTEGER_TOO_BIG) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole

Issue traced to Bandwidth limit group size for disk being 4 gigs or greater. Suggest adding checks when creating or modifying disk groups.

In

src\VBox\Main\src-server\BandwidthControlImpl.cpp

Add the following lines to "Validate input" section, line 413.

if (aMaxBytesPerSec > 4294967295)

return setError(E_INVALIDARG, tr("Bandwidth limit size is too large for Disk group: %zu, max %zu"),

aMaxBytesPerSec, 4294967296);

Add the following lines to function "BandwidthControl::i_saveSettings" before

group.cMaxBytesPerSec = (uint64_t)(*it)->i_getMaxBytesPerSec();

line 586

if (((uint64_t)(*it)->i_getMaxBytesPerSec() > 4294967295) && (group.enmType == BandwidthGroupType_Disk))

return setError(E_INVALIDARG, tr("Bandwidth limit size is too large for Disk group: %zu, max %zu"),

((uint64_t)(*it)->i_getMaxBytesPerSec()), 4294967296);

Change History (5)

comment:1 by paulson, 2 months ago

Owner: set to paulson
Status: newassigned

Many thanks for the bug report along with the suggested fix. In addition to the code changes we'll get the documentation updated as well because this this limit should be clearly stated so users know the upper bound and don't have to find out the maximum value via trial and error when trying to start a VM.

Version 0, edited 2 months ago by paulson (next)

comment:2 by thedisbo1125, 2 months ago

one correction to the code fix, line with max should be 4294967295, not 4294967296. I messed up and realized earlier today when I was testing.

comment:3 by thedisbo1125, 2 months ago

also, haven't found in the code where the default value gets set if you don't provide a limit, so running the command

vboxmanage bandwidthctl test add test96 --type=disk

produces

VBoxManage: error: Bandwidth size is too large for Disk group: 9223372036854775807, max 4294967295 VBoxManage: error: Details: code NS_ERROR_INVALID_ARG (0x80070057), component BandwidthControlWrap, interface IBandwidthControl, callee nsISupports VBoxManage: error: Context: "CreateBandwidthGroup(name.raw(), enmType, (PRInt64)cMaxBytesPerSec)" at line 188 of file VBoxManageBandwidthControl.cpp

comment:4 by aeichner, 8 weeks ago

Summary: Bandwidth Limit Group issueBandwidth Limit Group issue => fixed in SVN/next 7.1.x maintenance

This will be fixed in the next maintenance release of VirtualBox. Instead of introducing an artificial limit of 4GiB/s (modern SSDs can reach a multitude of that) for a bandwidth group we extended support to 64-bit values.

comment:5 by galitsyn, 2 weeks ago

Resolution: fixed
Status: assignedclosed

Hello,

We just released VirtualBox 7.1.8 which is available on the Downloads page. This issue should be fixed in this version.

Note: See TracTickets for help on using tickets.

© 2025 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette