Posts made by Biggen

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

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

Have to wonder what the use case of something like this is other than "it can be done". Your cell phone has more processing power and memory than the RPi has.

The bug/security patches upstream never seem to end. Seems like since April all you guys have had time for is this...

Do you see the new drive when you do an lsblk in the xcp-ng host?

Option 1 is also what I do. I can't stand having to set static IPs in individual VMs (or any physical machine for that matter). Much easier to do it inside the router GUI where all the MACs are stored.

I'm waiting for the same feature. I have a surveillance camera VM with a 20TB array that I don't want to back up. I created an Ansible playbook to recreate just the OS in the event I needed to since I can't backup the VM but that is kinda a hack. I'd rather exclude the video footage array and backup the OS.

@antoniolfdacruz

Perhaps it was fixed. The bug report doesn’t show it: https://github.com/xcp-ng/xcp/issues/379

I uninstalled it back in April and haven’t retested.

biggen1684 created this issue in xcp-ng/xcp

open Netdata not showing Virtual Network Interfaces for VMs #379

Doe the netdata update not actually fix the missing network interfaces or virtual drives?

Did you have more cores/less cores assigned at some point to the VM? I noticed something similar some time ago. It took a host reboot to flush the RRDs which got XO(A) reporting CPU utilization accurately again for me.

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.