XenServer 8.0 - Major update due Q1 2019
-
We had this feature exposed in Xen Orchestra since the start (or so). It's just that Citrix only added this in XenCenter recently. So it's more a client limitation done by Citrix than a real modification.
-
Even with XOA, we have the same problem with XCenter. With vCPU the rule works because you set a usage limit and can increase to the maximum that the host supports.
But for memory, we have only the minimum and maximum and the dynamic memory feature, which allows only a better allocation of the entire host.
But imagine the situation where a customer hires an 8GB VM and then wants a feature upgrade, to 16GB, the increase can not be done "hot," with the server on, requiring a schedule to perform the upgrade.
In the case of VMWare, HOTPLUG is supported, that is, I can upgrade to 16GB without turning off the VM. I believe this is a limit on qemu, since all versions of Xen (Source) support hotplug for vCPU, RAM, Disk and Network,
In XOA:
VM_BAD_POWER_STATE(OpaqueRef:8727f5ec-37ad-4273-8130-a1c0df0ed96b, halted, running)
MEMORY_CONSTRAINT_VIOLATION(Memory limits must satisfy: static_min ≤ dynamic_min ≤ dynamic_max ≤ static_max) -
I don't see the problem: just extend the static memory to the max of the host capacity and with a dynamic max to the amount you need right now.
After a while, if you need more RAM, just raise dynamic max up to static max.
Am I missing something here?
-
When I adjust the FIXED memory to 100GB, and the minimum dynamic to 40GB and maximum dynamic to 60GB.
But when I click Ok, the static memory gets the same value as the maximum dynamic.
At least in XenServer 7.1 CU2, the configuration you report does not work for me.
-
Please try with Xen Orchestra. You should be able to have this setting done once for all when the VM is halted, and then enjoy to set within the whole dynamic setting while it's up.
-
@olivierlambert said in XenServer 8.0 - Major update due Q1 2019:
Please try with Xen Orchestra. You should be able to have this setting done once for all when the VM is halted, and then enjoy to set within the whole dynamic setting while it's up.
I LOVE XOA! hehehehe
That'S exactly what I wanted.
Thanks so Much for the help and sorry for the persistence.
But See the problem, VM Guest recognizes total memory.
Is That a bug?
-
I need to run some tests on XCP-ng, but IMHO you shouldn't be able to see the static max inside the VM. You should be able to see dynamic max.
-
It's as expected in XCP-ng:
-
I tested on other VMs and the memory displayed is always the maximum static.
Will a Bug on XS 7.1? -
Possible, dynamic memory management changed a lot since 7.1
-
If I remember correctly what I read, I think Windows guests see all the memory (static max or dynamic max, I don't remember) but there's a special device that "eats" the memory that is not available to the VM, so that what's really available to it corresponds to the dynamic value (between dynamic min and dynamic max).
-
It's dynamic max. But I'm pretty sure it was heavily changed in 7.2
-
@stormi It has always been the way that the daemon of xentools bloated up, when you need to free up dynamic memory within the range. I just have 7.1 LTSR running, can't verify for any CR, right now.
-
@olivierlambert I Did a test with the XS 7.6 and CentOS7 (HVM) and the memory calculation does not work correctly.
Sometimes it decreases the memory in the Guest VM, but never displays the values correctly. I am reinstalling the Host for XCP 7.6 and perform new tests. I'll open a new thread for that matter.
-
Behavior should be the same in XS and XCP-ng 7.6
If you have lower than dyn max in your VM, it's due to pressure of other VMs on the host. Also during a live migration, Xen will "deflate" the VM to dynamic min to allow faster migration.
-
Did anyone notice, that Citrix not only sucks with improvments for (non VDI) server admins, but also doesn't keep their promised releasedates?
Q1 is gone for some days and still no updates...
In fall our support contract ends, I'm following xcp-ngs roadmap and changes quite intense... -
Well, in software development I prefer slipping release dates over broken software, so I won't throw the stone here
-
@stormi said in XenServer 8.0 - Major update due Q1 2019:
Well, in software development I prefer slipping release dates over broken software, so I won't throw the stone here
I could say: They had 3 months to geht their job done.
-
@cg 3 months is short.
-
