Skip to main content
Solved

Can I Reserve VM Resources in AHV 10?

  • July 3, 2025
  • 3 replies
  • 116 views

Forum|alt.badge.img

I want to reserver as mentioned below for a Linux VM running on AHV 10 and AOS 7.3.

  • CPU: 4 vCPUs with a 10,000 MHz reservation

  • Memory: 10 GB with a 10 GB reservation

  • Disk: 1 x 110 GB with thick provisioning

If these reservations exist, how can they be configured? I couldn’t find any information in PE/PC. It also seems that this feature was available up to AOS 6.8 but not in AOS 7.x versions.

Let me know if there are any workarounds as well.

Best answer by JeroenTielen

Memory is explicitly reserved. That is the default behaviour. If you don't want that you need to enable memory overcommit on the VM's you want to disable reservation (you find this in Prism Central if you update/create the VM).  Or run acli vm.update ### memory_overcommit=true

 

acli vm.update ### memory_reservation ← This doesnt exists. Not in 6.# not in 7.#

acli vm.update ### cpu_shares ← This doesnt exists. Not in 6.# not in 7.#

 

Changing memory via cli: acli vm.update ### memory=##G (Or via Prism Element or Prism Central) 

This topic has been closed for replies.

3 replies

JeroenTielen
Forum|alt.badge.img+8
  • Vanguard
  • 1770 replies
  • July 3, 2025

CPU reservation is not possible. And it wasnt is the previous versions either ;)

 

Nutanix doesnt work with thick prov disks. Everything is thin prov. Doesnt matter for performance. That is how Nutanix works ;)

 

Memory reservation is default behaviour. 


Forum|alt.badge.img
  • Author
  • Adventurer
  • 3 replies
  • July 3, 2025

Thanks Jeroen for the response.

 

On Memory reservation, Is there a way to explicitly reserve? Seems it was exist in AOS 6.8 and not any more.

Old commands:

“acli vm.update myvm memory_reservation=4096”

“acli vm.update myvm cpu_shares=custom cpu_shares_value=2000” NOT in MHZ for sure.

Default is below:

Update VM --> Compute Details --> Memory ie.,16GB..This is the only option I see to reserve/update


JeroenTielen
Forum|alt.badge.img+8
  • Vanguard
  • 1770 replies
  • Answer
  • July 3, 2025

Memory is explicitly reserved. That is the default behaviour. If you don't want that you need to enable memory overcommit on the VM's you want to disable reservation (you find this in Prism Central if you update/create the VM).  Or run acli vm.update ### memory_overcommit=true

 

acli vm.update ### memory_reservation ← This doesnt exists. Not in 6.# not in 7.#

acli vm.update ### cpu_shares ← This doesnt exists. Not in 6.# not in 7.#

 

Changing memory via cli: acli vm.update ### memory=##G (Or via Prism Element or Prism Central)