Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1619471

Summary:	[RFE][TestOnly]Increase maximum VM disk size to 12 TB
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Ameya Charekar <achareka>
Component:	ovirt-engine	Assignee:	Nobody <nobody>
Status:	CLOSED DEFERRED	QA Contact:	mlehrer
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.2.5	CC:	aefrat, aperotti, dagur, lsurette, mkalinin, nsoffer, srevivo, tnisan
Target Milestone:	---	Keywords:	FutureFeature, Performance, TestOnly
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-23 16:06:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ameya Charekar 2018-08-21 00:24:23 UTC

Description of problem:
Currently default allowed max VM disk size is 8 TB, need to test and support larger disk size.


Version-Release number of selected component (if applicable):
rhvm-4.2.5.2-0.1.el7ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. Create a disk larger than 8 TB.
2.
3.

Actual results:
It is not allowed.

Expected results:
Increase default supported maximum VM disk size.

Additional info:
As per Bug 1402315 we can adjust this value by engine-config tool by changing parameter MaxBlockDiskSize which is currently set to default value of 8192.

Comment 3 Sandro Bonazzola 2019-01-28 09:40:06 UTC

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 6 Marina Kalinin 2019-05-22 06:44:43 UTC

Hi Daniel,
Can you please update if this RFE is still relevant or we already have this?

Comment 7 Daniel Gur 2019-05-22 07:38:17 UTC

We did not received or tested such fix.
Tal?

Comment 8 Tal Nisan 2019-05-22 11:58:50 UTC

(In reply to Daniel Gur from comment #7)
> We did not received or tested such fix.
> Tal?

Of course, we did not change it for now, the bug is still on NEW

Fred, do you see any reason why we should not enlarge the limit?

Comment 9 Fred Rolland 2019-05-29 11:48:34 UTC

AFAIK, it's not a limitation on RHV. We should support whatever RHEL LVM/NFS supports.
Of course, it needs to be tested.

Nir, any limitations you are aware of?

Comment 10 Nir Soffer 2019-05-29 13:14:03 UTC

(In reply to Fred Rolland from comment #9)
On our side, the limits are:

- engine 4294967295 GiB -> 4194303 TiB
  (using java int value for size in GiB)

- vdsm, we assume 1 PiB as practical limit for preallocated volume.

I think the practical limit on RHEL is 16 TiB, see:
https://access.redhat.com/articles/rhel-limits

Comment 11 Daniel Gur 2019-10-31 14:10:40 UTC

Do we expect the disk to be Thin provisioned or RAW?
Do we expect full utilization of  12 Tera?

Comment 26 Avihai 2022-03-23 16:06:41 UTC

Closing as deferred if scale team will have testing capacity later.

Code wise it's there and should work with configuration and reach 12T is there per Bug 1402315 changing engine-config parameter MaxBlockDiskSize.

Testing wise scale QE team are focusing on other priorities so testing 12T (as mentioned by Daniel Gur in Comment23) will not be tested, the last tested max disk size was 8TB.