Also worth noting is that Center isn't adding the name-description string, whereas XOA is. No... XOA is defaulting to the name-description (as expected.) and Center is asking for one, and I left it blank... No issue here.

@Biggen Thanks!

Oh ok.. I know why... mount.ceph came in nautilus release. I have edited the post to install nautilus. Unlike RBD, CephFS gives browsable datastore + thin disks and is super easy to scale up/down in capacity with immediate reflection. I'd spend some time later to implement "Scan" and have a proper SR driver. Thanks for testing and feel free to raise if you come across further issues.

I did the manual installation via the XVA. It worked for me.

It's already in closed beta at various places It will already work as fully manual install, because Gluster packages are available inside 8.1 directly

Thanks for the suggestion, but don't you think we never thought to that before? I start to think you are considering us as 2 people in a garage. We are crunching numbers on a regular basis, and it never computes with those models. Proxmox is here since a long time, with a strong and "large" use base allowing to use this model. This is not the case for us now. So on short term, this is not doable. But be assured we are continuously working on testing various models to see what's the best fit.

You should use GitHub and create an issue. This will be taken into account for XO 6 web UI

@rkelley You nailed it for item 2. Was driving me crazy! Ok, that does make sense for item #1 and was kinda what I was thinking. But it does lead one to believe you can't live migrate anything with a single host even if you have shared/remote storage available unless you poke around and experiment with different buttons like i did.

@johanb7 I had the same problem in the past with FTDI-based USB device. I could see it in Xen host, but not in VM. I've spent many evenings trying to make it visible in VM, but with no luck though. I don't know why, but seems that some USB devices won't attach to VM.

Feedback/tests is REALLY vital for the community We might have spotted this, or not. So we spared bundling another ISO/upgrade after the release Thanks again!

That's "normal" if you are running XO (from the sources) and not XOA (the pre-built appliance)

@olivierlambert Yes, and its also so simple and fast to deploy another Raspianclient client for testing purposes.

@Danp Thanks for pointing me in the right direction. I was following an older howto where --global was not specified. That was my first problem - now fixed! Second problem was that I had installed into the root directory of Centos7 so the paths for creating the links were different. Once I had found the correct paths and created the links all was good. Thanks again. Frank.

@fx991 the SR scans can and have been helpful in detecting storage issues for me. Sometimes when my ISO library goes offline but XCP-ng has not detected the failure and still shows it as connected I usually notice it from the long running SR scans that get stuck. The "Connection to VM console..." task is when you have a console window open to a VM or Host...hence the reason why you can't cancel/end it...if you want to get rid of it then close all open console windows

Please open a support ticket on xen-orchestra.com

I already opened one: https://github.com/vatesfr/xen-orchestra/issues/4882. pdonias created this issue in vatesfr/xen-orchestra open [VM] Network: show IP addresses in front of their VIFs #4882

@x-rayd If you have 3 VMs that each have a 5TiB disk and you want to back up all of them you need at least 3x5=15TiB on the SR for the initial snapshots. Then you also need some extra GiBs or TiBs for the deltas. The workaround is to set up the SR as EXT, instead of LVM. Then it's using thin provisioning, meaning that the snapshot only uses as much space as you have data in each 5TiB disk. So if your VMs are only using 1,3 and 4 TiB of actual disk space then you only need an SR that's 1+3+4=8 TiB + the extra space for the deltas.