Ref: https://github.com/harvester/harvester/issues/1537
Verify Items
- Overcommit can be edit on Dashboard
- VM can allocate exceed Memory on the host Node
- VM can chage allocated Memory after created
Case: Update Overcommit configuration
- Install Harvester with any Node
- Login to Dashboard, then navigate to Advanced Settings
- Edit
overcommit-config
- The field of Memory should be editable
- Created VM can allocate maximum Memory should be
<HostMemory> * [<overcommit-Memory>/100] - <Host Reserved>
Case: VM can allocate Memory more than Host have
- Install Harvester with any Node
- Create a cloud image for VM Creation
- Create a VM with
<HostMemory> * 1.2
Memory - VM should start successfully
lscpu
in VM should display allocated Memory- Page of Virtual Machines should display allocated Memory correctly
Case: Update VM allocated Memory
- Install Harvester with any Node
- Create a cloud image for VM Creation
- Create a VM with
<HostMemory> * 1.2
Memory - VM should start successfully
- Increase/Reduce VM allocated Memory to minimum/maximum
- VM should start successfully
lscpu
in VM should display allocated Memory- Page of Virtual Machines should display allocated Memory correctly