Wow! Welcome guys! Great to see Vates is doing well and expanding. You guys have an excellent product!

@hvilches

I don't have any insider knowledge, but I gotta believe Vates will have to pull the plug on xcp-ng Center at some point. Its another source of bug entry (as we just witnessed) and requires extra manpower. I'd rather them throw more of their time into XOA since that is their "official" management software.

Why not just built XO for yourself from sources if you need to do more than the free version of XOA allows?

@S-Pam Literally the first post has a big bold headline that tells exactly how you go about upgrading by linking to the docs.

And then in the sixth post from the top Oliver says it’s reasonable to believe the final release will be in 2 months.

When this Crosstalk microcode update hit last week there was an issue with certain Intel CPUs where we coudn't boot after the patch was applied. I run Linux Mint on my laptop and I couldn't boot it after taking the microcode update. I had to boot into recovery and then apt remove intel-microcode to get it back to a working state. Later that day, Ubuntu (or whoever) released a new intel-microcode update that corrected the problem.

Not sure if this is even remotely close to the same issue but wanted to put this out there.

This truly is an amazing piece of work. You guys should be proud of yourselves!

@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.

I'm running XO from sources on Debian 9 (as the tutorial recommends) and running Netdata. Works fine.

When running XO from source, you don't have the option to enable Netdata from within XO. You have to install it on the host as per this post.

How hard is it to SSH in and manually create the folder? It's 10 seconds worth of work tops. And you probably will never have to ever touch it again.

@arvid I think I built it with 3GB last time I tried. I don’t think you can build it with less anymore.

@s-pam Yeah I assume it works just like linux top with IRIX mode on (Shift + I).

@mrbaz I don't think its been implemented yet. Its coming from what I've read though.

I thought you could deploy a new appliance, connect to your back remotes, and restore metadata/backups from the new appliance even without a registered version. Is this not the case?

@jgibbons You can run XO anywhere it will compile. So run as many as you want on multiple physical machines. It doesn’t have to be run in a VM on the actual xcp-ng hosts.

@olivierlambert Yup, I meant Citrix and whatever they call it now - XenServer.

There is also Oracle Linux which is another RHEL offshoot.

Will be interesting to see what Xen decides to do. Does xcp-ng forge ahead on their own and pick a distribution that Xen doesn’t?

@george5888 You can build XO from sources and have access to everything: https://xen-orchestra.com/docs/from_the_sources.html

I agree with these guys above. Having a tree view seems like a no-brainer. It feels like its the industry standard (it should be if its not) for management GUI for hypervisors/VMs to be honest.

Have you actually tried to mount the NFS share from another machine and see if you can read/write to it? This sounds like an NFS permissions issue.

With NFS, you don't usually have a username/password. You can restrict access, if you wish, via IP or other measures. I have a Synology NAS unit configured as a NFS Remote for XO to send backups to. I don't specify a user/password for the share. I just feed XO the path to the share and let it rip.