Now granted I am evaluating XCP-ng on three hosts with massive resources: 1 Pool, three hosts, 288 CPUs, 1.5 TiB of memory and 10 TiB of storage.

I created seven VMs against the one pool. One VM was created on Host-1, three went to Host-2, three VMs went to Host-3. (XOA is running on a different physical box.)

I'm curious how the decision was made where the VMs went. Perhaps I have so much horsepower that the host determination was fooled a little.

Is there a function to rebalance the VM load?

Thanks for a marvelous product. I have a meeting tomorrow with a Vates sales person.

@olivierlambert You are totally right. I 'thought' I had added a firewall rule to allow incoming NTP requests, but I added it again and reloaded and now all three hosts are syncing. Thanks!

@olivierlambert All three hosts say this:

# chronyc tracking
Reference ID    : 00000000 ()
Stratum         : 0
Ref time (UTC)  : Thu Jan 01 00:00:00 1970
System time     : 0.000000000 seconds fast of NTP time
Last offset     : +0.000000000 seconds
RMS offset      : 0.000000000 seconds
Frequency       : 0.000 ppm slow
Residual freq   : +0.000 ppm
Skew            : 0.000 ppm
Root delay      : 1.000000000 seconds
Root dispersion : 1.000000000 seconds
Update interval : 0.0 seconds
Leap status     : Not synchronised

The XOA host says this:

# chronyc tracking
Reference ID    : AC1415FE (172.20.21.254)
Stratum         : 4
Ref time (UTC)  : Wed Sep 04 18:05:52 2024
System time     : 0.000297567 seconds slow of NTP time
Last offset     : -0.000314209 seconds
RMS offset      : 0.000475838 seconds
Frequency       : 9.984 ppm slow
Residual freq   : -0.001 ppm
Skew            : 0.408 ppm
Root delay      : 0.003664614 seconds
Root dispersion : 0.015663998 seconds
Update interval : 1040.9 seconds
Leap status     : Normal

Nothing seems off. Yet, XOA keeps saying "Host time and XOA time are not consistent with each other." I know that time sync is really important.

I have three hosts, all pointing to a single NTP server yet XOA says hosts 2 and 3 are not synchronized.

If I ssh into a host I see this:

# timedatectl
      Local time: Wed 2024-09-04 13:54:08 EDT
  Universal time: Wed 2024-09-04 17:54:08 UTC
        RTC time: Wed 2024-09-04 17:54:08
       Time zone: America/New_York (EDT, -0400)
     NTP enabled: yes
NTP synchronized: no
 RTC in local TZ: no
      DST active: yes
 Last DST change: DST began at
                  Sun 2024-03-10 01:59:59 EST
                  Sun 2024-03-10 03:00:00 EDT
 Next DST change: DST ends (the clock jumps one hour backwards) at
                  Sun 2024-11-03 01:59:59 EDT
                  Sun 2024-11-03 01:00:00 EST

Why is it not synchronized. Is it just a case of "you need to wait."

So this would mean:

• Start the VM with 512 MiB
• Balloon up to 4 GiB
• Balloon down to 1 GiB

What does the 5 GiB setting do?

I must be dense today. I totally get memory ballooning, but from the UI it looks like we have two sets of settings (Static and Dynamic) each with their own minimum and maximum settings. What is the difference between Static and Dynamic min and max?

What is the purpose of the two settings under static?

The documentation explains the Dynamic setting, but not Static. What does it do?

Thank you all for this wonderful information.

BTW: Guest tools are installed in the VM.