Support binary units (GiB/TiB) for virtual disk size display / Add option to display disk sizes in GiB/TiB (binary units) instead of GB/TB #11577

Closed
opened 2025-12-29 21:47:03 +01:00 by adam · 0 comments
Owner

Originally created by @Robertas1975 on GitHub (Sep 5, 2025).

NetBox version

v4.3.7

Feature type

Change to existing functionality

Proposed functionality

Infrastructure teams rely on NetBox to be the source of truth for VM definitions, including disk sizes.
When comparing values with vCenter (or other hypervisors), discrepancies appear:

  • A VM with a 32 GB disk in vCenter shows as 32.77 GB in NetBox.
  • This discrepancy may look like a mismatch or data error, even though it is simply a difference in units.
  • Administrators expect disk sizes to match hypervisor reporting for consistency and troubleshooting.

Example:

Source Reported Size Expected Unit NetBox Display
vCenter 33,554,432 kB 32 GB 32.77 GB
NetBox API 32,768 MB 32 GB 32.77 GB

Related discussions and references:

Use case

Infrastructure teams rely on NetBox to be the source of truth for VM definitions, including disk sizes.
When comparing values with vCenter (or other hypervisors), discrepancies appear:

  • A VM with a 32 GB disk in vCenter shows as 32.77 GB in NetBox.
  • This discrepancy may look like a mismatch or data error, even though it is simply a difference in units.
  • Administrators expect disk sizes to match hypervisor reporting for consistency and troubleshooting.

Related discussions and references:

Database changes

No response

External dependencies

No response

Originally created by @Robertas1975 on GitHub (Sep 5, 2025). ### NetBox version v4.3.7 ### Feature type Change to existing functionality ### Proposed functionality Infrastructure teams rely on NetBox to be the source of truth for VM definitions, including disk sizes. When comparing values with vCenter (or other hypervisors), discrepancies appear: - A VM with a **32 GB disk in vCenter** shows as **32.77 GB in NetBox**. - This discrepancy may look like a mismatch or data error, even though it is simply a difference in units. - Administrators expect disk sizes to match hypervisor reporting for consistency and troubleshooting. Example: | Source | Reported Size | Expected Unit | NetBox Display | |------------|-----------------|---------------|----------------| | vCenter | 33,554,432 kB | 32 GB | 32.77 GB | | NetBox API | 32,768 MB | 32 GB | 32.77 GB | Related discussions and references: - [#8897](https://github.com/netbox-community/netbox/issues/8897) - [Binary prefix explanation (IEC vs SI)](https://en.wikipedia.org/wiki/Binary_prefix) ### Use case Infrastructure teams rely on NetBox to be the source of truth for VM definitions, including disk sizes. When comparing values with vCenter (or other hypervisors), discrepancies appear: - A VM with a **32 GB disk in vCenter** shows as **32.77 GB in NetBox**. - This discrepancy may look like a mismatch or data error, even though it is simply a difference in units. - Administrators expect disk sizes to match hypervisor reporting for consistency and troubleshooting. Related discussions and references: - [#8897](https://github.com/netbox-community/netbox/issues/8897) - [Binary prefix explanation (IEC vs SI)](https://en.wikipedia.org/wiki/Binary_prefix) ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:47:03 +01:00
adam closed this issue 2025-12-29 21:47:03 +01:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11577