Topics created by MichaelCropper

Thanks @lawrencesystems - I've finally got around to watching that video, explains the content well, quite interesting to see that happening in real time when the RAM is being land-grabbed by other VMs when things are getting full based on the different configuration settings.

@MichaelCropper That's awesome! I'm glad the usual computer pixie dust fairies dropped by and fixed the issue for you.

Poor Windows though... you initially laid the blame at their feet, but it seems more like this was a Google Chrome issue. I've noted a LOT of peculiarities with Google Chrome as of late and have started to migrate away for that reason. Reading a lot of forums on Reddit and other IT sources, this seems to be something that is pretty wide-spread.

In any case, it's working for you now... until Google changes something again. LOL

I hope you have a great weekend!

There's no black magic 🙂 As @ronivay said, you need to tell the filesystem inside your VM that the disk grew.

On Cloudinit-enabled VM, there's an auto-grow parameter that is checking at each boot if the disk was extended, and will automatically do it for you. But again, that's inside the VM. Keep in mind: it's not the job of the virtualization system to deal with what's inside the VM 🙂

As stated in the big warning yellow box here in the official doc: https://xen-orchestra.com/docs/community.html#report-a-bug 😉

Closing then 🙂

@MichaelCropper said in XO Backup Failing - Possibly to due Local Disks and loopback issues?:

Job canceled to protect the VDI chain

This usually indicates that there are VDIs that haven't coalesced. Check the "unhealthy VDIs" section of Dashboard > Health.

@mathiashedberg try, with xo/xoa, toggeling autostart off and then on again for 1 of the vm on the new host so xo will also activate the autostart option at the (new) server if it was not already enabled