@flakpyro
I'm good now!

I'm on build d8370 and last night all my backups ran without issue.

All is well for me ...thanks for the hard work!

@olivierlambert Thanks!

@tjkreidl Thank you!!!

@olivierlambert
Trying to avoid doing the shared NFS/Iscsi thing.

FWIW: The XO Community edition backups don't work as of build 6b263. If you roll back to commit 19412 they work fine.

The longer error is:
"Error: The last argument to .catch() must be a function, got [object Object]"

" "result": {
"message": "The last argument to .catch() must be a function, got [object Object]",
"name": "TypeError",
"stack": "TypeError: The last argument to .catch() must be a function, got [object Object]\n at Promise.caught.Promise.catch (/opt/xo/xo-builds/xen-orchestra-202506201840/node_modules/bluebird/js/release/promise.js:130:19)\n at /opt/xo/xo-builds/xen-orchestra-202506201840/@xen-orchestra/fs/src/abstract.js:717:43\n at next (/opt/xo/xo-builds/xen-orchestra-202506201840/@vates/async-each/index.js:90:37)"
}"

Is it possible for a script on one host to check if a VM is running on another host?

Id like to have a cron task that runs every few minutes on host A to see if a VM is running on host B. If its not, I want it to start a VM on A, if it is I want it to either carry on or to shut down the VM on host A.

Trying to get around running Opensense and don't have multiple WAN IP addresses for HA.

@olivierlambert
I’ve got a few VM’s that lock up from time to time. There is no rhyme nor reason (different hosts, different storage, etc).

As a result, I just have a job that restarts them at 5:30 am every day. I’d like to have the software tool software restart them but, in the occasion wher the VM is locked up tight as Fort Knox, I’d like the hard reset to happen.

Make sense ?

@pdonias Tis will sound weird but is there any way to have it try going through the guest tools first and, if it doesn't work, then do the hard-reboot of the VM?

@pdonias Thanks!

@pdonias
One more...what does "timeout" do?
Thank you!

In the jobs function, there is a function to re-start a virtual machine called "vm.restart". It has a series of options. Is there anywhere that shows what the various options do?

The three options are shown below:

timeout
force (seems obvious but what if it not checked?)
bypassBlockedOperation

Thanks!

@flakpyro
I've found a similar issue with all VMs I update. After I update and reboot, it stays at "Management agent detected" with no version shown.

Once I reboot a second time, it stays at "Management agent detected" with "Management agent 9.4.1-160 detected"

@AshleyDe
In the last few days, I've had these same issues with a few Server2025 virtual machines (I assume are close ish to Win11 24h2).

I updated the master pool...all went well. I updated one of the other hosts. After it rebooted, I got lots of messages about "Async.VM.clean_shutdown: 8%" on the various VMs.

My bad....XO was a two builds behind and well as XO was not up to date.

I updated to commit 95e72 and updated XOA version to 5.106.2 and all is well.

User error on my part but I hope this helps someone.

@AtaxyaNetwork
I do!

@AtaxyaNetwork
BTW...how in the world did you add the guest tools? I messed around with that while watching two movies a few Sundays ago and finally gave up!

@flakpyro
I'd love to see what you did!
On the GRUB password thing, I cheated and opened it with another instance os SLES and jacked around with the menus from a working system. I tried a million things but could never get the tools installation to work!

3. Mount up basically any linux installer or system rescue ISO.

4. Boot into that (If using SLES, go to other options and select "RESCUE MODE" and wait).... get a shell...
   This will let you ssh into it
   sudo ssh-keygen -A
   sudo service ssh --full-restart
   ip addr # so I can know how to get in from putty
   cat $PATH
   passwd (makes a new password so you can ssh inot it)
   /sbin/sshd

lvdisplay
mkdir -p /mnt/sysimage/boot
mount /dev/xvda2 /mnt/sysimage/boot
mount /dev/OMCAppVG/LVRoot /mnt/sysimage
mount -t proc none /mnt/sysimage/proc
mount -o bind /dev /mnt/sysimage/dev
mount -o bind /run /mnt/sysimage/run
/mnt/sysimage
for x in sys proc run dev tmp; do mount --bind /$x /mnt/sysimage/$x; done
chroot /mnt/sysimage

I saw these instructions somone where but I coudl not figure out these steps ?

8 ) Enable root logins in /etc/ssh/sshd_config

9. Enable sshd via: systemctl enable sshd

10. Set a temporary password for root via passwd

11. Exit the chroot and the installer/rescue image... let it boot back into OME

12. Cache your ssh key in root's keystore via whatever method you like... my preferred is ssh-copy-id

13. Remove root's temporary password...

@olivierlambert
Since I'm having the same issue, can I give that suggestion a shot? If so, how do you do it from the command line (with xe CLI)?