I had several reports from users that could not access fileshares. The server was up and responded to ping. But in AD there were duplicates of the Windows server. We found that an old Cont Repl job had left "garbage" VM's named {importing]. These VM's had everyting on (networking and AutoStart Enabled). We did not take notice ogf these(stopped) VM's until they auto-started after host-upgrade and restart.

Could there be a function in ContReplication jobs that turns off Auto-start right away when the cloned VM is created, in case the job stops AND the host late will reboot?

Usiong the latest patches (260117) for both xcp-ng and XenOrchestra (from sources)

Best regards Johan Uusijärvi

Re: Overview of a logical allocation of thin provisioned SRs

Hi, I wonder if it's possible to get , for each storage, a sum of PROVISIONED space ? I my environment I can abosultely not overprovision , users may suddenly start filling up space and storage would then be full.

Best regards Johan

Thanks for feedback. No success here. I will move docker instead to a new VM.

Johan

@olivierlambert
Thanks for the reply.
Yes, in VM-ware it is BIOS, same in XCP. Didnt try UEFI.

photonOS is a minimized and optimized from VM-ware and for containers. It probably needs some drivers to be able to run on XCP.

The installation ISO crashed directly if I try to install from scratch. Moving the VM results in a startscreen, then it stops reading from disk and processor is 100%, som very minimal network traffic and a black screen with a prompt stays on.

I will need to move Docker and all files instead ....?

/Best regards

I have tried to use import from VMWARE in XO (built from sources). The machine start up but only a black screen on console. Maybe photonOS is incompatible with xcp-ng? Anyone have any experience?