Thanks for keeping us posted, really appreciated here by all the team

@icompit Thank you. It seems that the backup process fails to get the file lock on the backup directory. Have you modified anything on your remote recently? Also, could you tell me if this is happening on all of this job's runs, all of your backup runs, or if it only happened once on this specific backup job execution?

@iLix The sizing of the VM in XCP-NG was bigger compared to the source

Great news! Thanks for the feedback.

@olivierlambert can you close this thread?

That's the reason, then. The update will update files on the disk, not on what's running in memory, so after updates you must reboot to actually use those updates

No, it's fine, as long the issue contains all the relevant details it's fine

Hello @ronan-a Just to be sure, you want logs of the node which want to join or the master ? Bonne journée

@bogikornel As discussed in the thread, pygrub doesn't work. (It might be fixable, because copying kernel and initrd to dom-0 and directly setting PV-kernel, PV-ramdisk and PV-args works, which is basically what pygrub is supposed to do. But I stopped investigating as pvhgrub is a much better option which acually works.) You have 3 options copy kernel and initrd do dom-0 and configure xe vm-param-set uuid=... domain-type=pvh xe vm-param-set uuid=... PV-kernel=/dom-0/path/to/kernel xe vm-param-set uuid=... PV-ramdisk=/dom-0/path/to/initrd xe vm-param-set uuid=... PV-args="root=... ro console=hvc0 ..." xe vm-param-clear uuid=... param-name=PV-bootloader Not a very practical option, just PoC. use pvh-ovmf, but this requires UEFI-enabled VM (ie. GPT disk layout with EFI partition and some EFI bootloader or kernel directly in EFI with proper config (or as UKI) use pvhgrub. You need a recent grub2 to build the image for i386-xen_pvh target. Or just get the blob - this one is from Alpine package curl https://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/grub-xenhost-2.12-r8.apk | tar -xzf - --strip-components=3 usr/lib/grub-xen/grub-i386-xen_pvh.bin Save it to dom-0 (e.g. to /var/lib/xcp/guest/grub-i386-xen_pvh.bin) and configure the VM xe vm-param-set uuid=... domain-type=pvh xe vm-param-set uuid=... PV-kernel=/var/lib/xcp/guest/grub-i386-xen_pvh.bin xe vm-param-clear uuid=... param-name=PV-ramdisk xe vm-param-clear uuid=... param-name=PV-args xe vm-param-clear uuid=... param-name=PV-bootloader If the VM has valid grub2 config, it should work. Of course, you need a linux kernel with CONFIG_XEN_PVH enabled.

@ronan-a Thanks! I've installed the plugin, and configured it. Now to wait until the next power outage. (or until I get time this weekend to test it and annoy my family)

fixed in commit fcefa

Hello, I am asking XO team.

Yeah I remember it wasn't that easy

It's better to have it to get handy options like IP addresses displayed and so on.

@flakpyro i try to find a new version but site and search only found 3.3.0. When try to search again in a proxmon forum found the repo xD

@olivierlambert Dang ok. I waited a few minute then clicked the Connect in XOA for that host and it connected. Not sure what to do really.

Great!

@nathanael-h yeah, the installation finished, tho as mentioned above I would prefer to assign my ips via dhcp, so it's not perfect. (mind, I'm currently using a manually deployed cluster just fine, so I'm in no rush to really figure out why the automatic ups are failing) Unrelated, are there plans to eventually allow for up/down scaling the recipe later? With the CCM, setting up vm auto scaling should be possible if the recipe supports it right?

@lsouai-vates Duly noted. If amd when you do get a moment, could you have a look at https://xcp-ng.org/forum/post/94297 and offer up any guidance on how I can stop the debug log entries and also the double timestamp entries in the audit.log file? Thank you.

@olivierlambert, yes, thank you. I will open that ticket.