Hi, i've this situation in Task

What's this task?
Now i've ~50 of this call..

olivierlambert now work fine, thank you

olivierlambert ops.. why the best topology?

olivierlambert live migration, the vm is very important (today, in christmas holyday, i've received some phone calls for 7 minutes of freeze..)

olivierlambert hi, today i've upgraded my host..
The big VM frozen for ~7 minutes, is a big vm (96 gbram and 32 cpu) but 7 minutes is a very long time (for customer!)
i've setting 96/06 in dynamic: is a normal time?

Good morning, today i see a strange thing in my pool

I've not update ctx7..
I login to host (ctx7 and ctx6 for comparision), do a yum update and i see the same 9 packages: why xoa not see the patch for ctx7?

olivierlambert said in Clarification of "VM Limits" in XO:

2. Static is the global range that can be modified only when the VM is halted. Dynamic is the range when the the VM memory can be changed while the VM is running. Obviously, dynamic range is included inside the static one.

Most of the time, except if you have a very good reason for it, do not use dynamic memory.

ok.. but if i set memory limit static 1gb-16gb
and dynamic 16gb-16gb XCP assign 16 gb to vm?
the static limit is only a "barrier" for dynamic?

nikade
in VM (linux) with a free i see 94 gb of total memory

bleader said in update via yum or via xoa?:

yes you're basically doing an RPU manually.
But it is indeed odd that the process is stuck at 0%, it should be fairly fast to do the install patches, no errors in the logs?

i've another install all patches and install all.
Now i'll use rpm update and see if speed is the same or not

bleader said in update via yum or via xoa?:

It actually depends if you chose "rolling pool update" or "Install all pool patches", as you're talking about evacuate I assume you went with the first one.

Rolling pool update (RPU) is documented here and Pool updates here.

But to sum it up, "Install all pool patches" button will indeed run the yum update on all server, so similar as doing it manually, while RPU will do hosts one by one, moving VM to other hosts in the pool, install updates and reboot host. Therefore it can take way longer to complete, time will vary based on the number of VMs that have to be migrated around, network speed between hosts, etc…

RPU is the recommanded way as it allows hosts to restart and therefore take hypervisor, microcode and dom0 kernel updates into account right away with no service interruption. But if you don't really mind shutting down some of the VMs to restart hosts, or if there are no low level updates that requires a reboot, you could get away with just the yum update manually. But if the RPU is started already, I would not advise trying to do things manually at the same time.

ok, i've do a "install all patches" from xoa host page, i want some control form move vm to other hosts
But is the same thing at all (if i evacuate by hand the host, rpm update, reboot host), right?

Hi, i'm updating my poo; i evacuate the master, goes to patch, install all patch..
for now is at 0% (11 minutes from start)
Why is too slow?
It's the same if i go with console and do a yum update to all server?

Too many error for me..
Time for backup very very long, error at start (with retry) and at the end (with error on backup:

Couldn't deleted snapshot data
Couldn't deleted snapshot data
Retry the VM backup due to an error
the writer IncrementalRemoteWriter has failed the step writer.beforeBackup() with error Lock file is already being held. It won't be used anymore in this job execution.
Retry the VM backup due to an error
Transfer data using NBD
will delete snapshot data
Snapshot data has been deleted
Snapshot data has been deleted
Transfer data using NBD

    Clean VM directory
    cleanVm: incorrect backup size in metadata
    Start: 2024-07-11 20:23
    End: 2024-07-11 20:24
    Snapshot
    Start: 2024-07-11 20:24
    End: 2024-07-11 20:25
    Backup XEN OLD
    Start: 2024-07-11 20:25
    End: 2024-07-11 20:27
    Duration: 2 minutes
    Clean VM directory
    cleanVm: incorrect backup size in metadata
    Start: 2024-07-12 01:44
    End: 2024-07-12 01:44
    Snapshot
    Start: 2024-07-12 01:44
    End: 2024-07-12 01:46
    Backup XEN OLD
        transfer
        Start: 2024-07-12 01:46
        End: 2024-07-12 05:39
        Duration: 4 hours
        Size: 397.86 GiB
        Speed: 29.12 MiB/s
    Start: 2024-07-12 01:46
    End: 2024-07-12 05:39
    Duration: 4 hours

Start: 2024-07-11 20:23
End: 2024-07-12 05:39
Duration: 9 hours
Error: Disk is still attached to DOM0 VM
Type: delta

not good..