Yes you are quite right. But its not my money to spend. If it were left up to me I would spend it. Since XCP seems to be lots and lots and lots of times better then VMWare for what you pay for even when you have to pay.
There is no way to compare pricing. But not my company not my money. And no one asks or seems to want my option.
Yes you are quite right. But its not my money to spend. If it were left up to me I would spend it. Since XCP seems to be lots and lots and lots of times better then VMWare for what you pay for even when you have to pay.
There is no way to compare pricing. But not my company not my money. And no one asks or seems to want my option.
Yes but under that it says that building it your self is not so easy unless you have built Nodejs apps before. I have not.
But I would be willing to try.
Anyway. For what we are doing (pool migration) its going fine. And we are just about done. Once done I am going to destroy the old pool and rebuild it as part of the new pool.
But thank you for your help.
Actually I have read that. And unless I am mistaken XOA (in all its forms. WebUI, CLI and API) are for pay. I did not see that XCP Center was community based. And that finally leaves doing it using XE Cli (XAPI). Not a very good way to do things.
But I think we are getting off the point here. My question is is there a limitation in XCP Center ( or a bug) that is causing this? We can work around it by doing 2 migrations. First to the pool master and second to some where else in the pool.
Huh??? Is not XCP-ng Center a supported client?
I cannot use XOA because no one in the company wants to pay for that..
What other client is there?
Using XCP-ng Center ( am on version 20.04.01). If I right click on a running VM then click on Migrate to Server and then Migrate VM Wizard.
So now that I am doing this myself rather then listening to some one else explain it to me. Here is whats happening.
We have 2 pools. When I Live migrate from pool01 (which is running an xcp 7.6) to pool02 running xcp 8.2.1. We do the migration with the Migration Wizard. Ever Live migration like this sends the vm to the pool master on pool02. And when the pool master exceeds CPU or Memory utilization the migration will fail and send it back.
Should it not Live migrate from pool to pool to other pool members not just the pool master?
Also, once migrated to the pool master I can then Live migrate again to another host in the pool just fine. So its not a resource issue.
I have a pool of 4 identical hosts all running XCP 8.2.1 and using NFS shared storage for the VMs. When I export from an older pool a VM then import it in to the new pool the VMs do not auto balance in the pool.
When we start up a vm and not select where to start it. It tries to start the vm on the first pool member. Then fails when that pool member is out of memory.
In previous versions it would start it on the pool member with the most free memory.