I spent some time trying to find this in the forums, but I couldn't find an answer on this one. I apologize if I missed it.
Is VMware's CBT bug limited only to VMDKs that are expanded "past any 128GB boundary"? This isn't an aggregate of the VMDK sizes, correct?
As in, this DOESN'T trigger the CBT bug: You have a 60GB VMDK for boot and a 60GB VMDK for storage. You extend the storage VMDK to 80GB, not crossing a 128GB threshold for that VMDK, but the VM size does grow past 128GB. You're still okay, right?
Thanks!
-Jim
-
itfnb
- Enthusiast
- Posts: 58
- Liked: 9 times
- Joined: Mar 12, 2012 8:18 pm
- Contact:
-
Vitaliy S.
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: VMware CBT bug - a per VMDK issue?
Correct.itfnb wrote:Is VMware's CBT bug limited only to VMDKs that are expanded "past any 128GB boundary"? This isn't an aggregate of the VMDK sizes, correct?
Right.itfnb wrote:As in, this DOESN'T trigger the CBT bug: You have a 60GB VMDK for boot and a 60GB VMDK for storage. You extend the storage VMDK to 80GB, not crossing a 128GB threshold for that VMDK, but the VM size does grow past 128GB. You're still okay, right?
-
itfnb
- Enthusiast
- Posts: 58
- Liked: 9 times
- Joined: Mar 12, 2012 8:18 pm
- Contact:
Re: VMware CBT bug - a per VMDK issue?
Awesome. Thanks!
Who is online
Users browsing this forum: Semrush [Bot] and 12 guests