Offline
Right now updates are still being done in the V5 interface but I assume that will change once V6 is fully implemented...but wondering if the current version and maybe an update link which goes to the V5 interface in the meantime can be added?
Currently the version in the V6 settings page just shows as blank.
I am not sure this adds much to the discussion, but I am also experiencing this issue since the latest update a day or two ago.
xoa 5.80.0
xo-server 5.110.0
I have two hosts in a pool and a single backup location but some backups have completed (all under 5 minutes) and then others have failed at the 5 minute mark from both hosts - I was originally thinking maybe just one host but have success and failure form both to the same location.
@christopher-petzel Thanks for this information I've been coming across this issue on a few 2019 servers and this worked perfectly!
@Danp I get the same results. I do not have any errors in the logs, but I do notice that with the settings for the host, it says "Unknown pool" for the pool name although it does show the correct UUID if I hover over it...not sure if that is related?
It is certainly still working in so far as I can access all the VMs, the errors are specific to accessing the hosts which it shows, but I get that error message when I click on them, or SRs which I was wrong in that it does not even list it just gives the error when I click on the storage menu item.
My hosts and storage are all listed on their respective pages, but when I click on either a host or an SR to view more details I get "an error has occurred" in red displayed in the top left of the frame.
I have delta backups configured and working on my VMs and assumed that the data was going to the target remote - but when I look at the main SR it shows them there as an [XO Backup...] - is this just a pointer reference or are the backup files actually going onto the main SR?
If they ARE going onto the main SR then how do I change that as I obviously want me backups to not be on the same storage platform in case of failure of the SR...apart from the delta target remote I cannot see any reference to the location of backups?
Thanks!
Everything seems okay apart from it needing update which, as I said, fails.
Ran updates today and all went okay and then got an ! - says to run again but when I run again it fails with this message:
Command failed: npm uninstall -g --silent xen-orchestra-upload-ova
@capeschools Just as an FYI to complete the thread - VT is enabled by default on the HPE server.
@olivierlambert Actually everything is HVM so my guess is the server is configured just fine but I'll shut it down tomorrow and double check the bios anyway just to make sure.
I'll keep plugging away but its a pain when it takes over 24 hours to export the VM - not sure why but I've had mixed success using a backup/restore process but I'll keep going.
Thanks for everyone's thoughts on this.
@olivierlambert But it is not all of them - surely if that was a factor they would all exhibit that behaviour? I currently have a 2012 and 2019 server imported without issues (apart from the original issue of the XVA import not seeming to work) but an OVA and then VHD import worked. I also have half a dozen totally different linux systems running without issue so it is not everything at all.
@olivierlambert how exactly? When I search for XOA extensions I find a single article related to whether XOA can run on a host or not. Obviously in my case the host is running XCP perfectly fine but there are issue with VM imports?
@danp The problem I am having is with the XVA - works perfectly with anything Linux....with any Windows server I try the VM starts up and then within 5-10 seconds fails and shuts down.
So an XVA export from XenServer takes 1/4 the time of the OVA export but does not start up on XCP.........
@danp I know I can do an inplace upgrade but this is also replacing the entire system (host and storage) which are old so it made more sense to set up the new system and then migrate over to it.
I am migrating from XenServer to XCP-NG and export my VMs as OVA files. On the import however, it shows there is no attached disk so, for example, I am importing a VM with a 200Gb disk, and the OVA takes hours to import and shows 200Gb but the disk does not so I end up with an empty VM and have to then extract the OVA and import the VHD file separately.
This does not seem like correct behaviour as it would therefore seem to defeat the point of the OVA file being everything included? Is this a setting when I export from XenServer perhaps, even though it appears to create the OVA just fine and I can import the files - but have to one at a time.
