XCP-ng 8.2.0 RC now available!
I currently have a problem with XOA and XCP-NG Server where there cannot be made a connection to my XCP-NG host. I noticed the problem this morning as I wanted to create a new VM, when I did that it said that there was 'no host available'
Then I saw something on a forum where they said 'try restarting the toolstack', so I did that and now some other things came up as well.
Now this error is gone for some reason, but I keep seeing this error:
I have no idea what this could be, does someone have an idea? It says that I need to disconnect the XCP-NG server to let it update something, but I have no idea what it wants to update.
I am getting these problems on XCP-NG 8.2.0 RC
@appollonius Have you tried going to Settings > Servers in XO and clicking the button under to Status column? You should be able to toggle the connection status there.
@danp Yeah it says that it is enabled but when I want to start a newly created VM it says this:
Now when I restart the toolstack I get this as well:
This is the 'Servers' page:
I have these issues since I upgraded from XCP-NG 8.1 to 8.2.0 RC. And somehow I have no idea why it cannot connect to the host via 192.168.3.100:443 while I never had that error before...
It simply says that there is NO HOST AVAILABLE while the hosts 'status' is enabled...
So after a few hours of research and trial and erroring I found the issue why my newly created VM could not be started. For some reason the iso_sr has had an error:
Which occurred after the upgrade of yesterday... So in other words, I had to recreate the ISO SR in order to get it to work. Now it works again 'haha', but I have no idea in why it says 'no hosts available' when I try to startup the VM. Shouldnt it be somekind of SR error message? Because I got send the wrong way here..
Just a quick reference to my update to this post. I got the same poor upload speeds with 8.2 RC as I did with 8.1 with (all) latest updates. I was able to get my full speeds back by installing my server from scratch with 8.1 and no updates. (I used the same exact VM backup to test all three of these installs) I've yet to identify the exact update that's causing the slow uploads.
Just update my test host via iso and all patched.
CephFS is working nicely, but the update deleted my previous secret in /etc and I had to reinstall the extra packages and recreate the SR and then obviously move the virtual disks back across and refresh; something to be aware of in the future I guess, or maybe using the yum method would have avoided this?
Tried to restore a Windows 10 UFEI from backup, but it fails to boot. Just get the spinning dots and can hear the host fans ramp up. Tried a forced restart but no change. Will try and copy the same VM rather than restore from backup and see if that works.
@jmccoy555 The yum update method would have avoided this. In exchange for that, you lose the ability to revert the upgrade.
Note that the contents of
/etcwas not entirely lost: it was copied to the backup partition.
What version of XCP-ng was the Windows 10 backup made with?
@stormi It was no big issues as it was only my test host so proves its always worth testing! Plus I wanted to ensure the previous storage drivers / changes we put back etc.
The backup (from April) was made with 8.1.
@jmccoy555 what kind of backup is it?
@jmccoy555 To test, you may try to give the VM more RAM and make sure to have dynamic min = dynamic max = static max.
@stormi Hummm strange I didn't get a notification.
Anyway, the Copy worked, it booted, updated some drivers and all is good.
Back to the backup / restore..... Its a backup made and restored with XO, if that's that you mean??
dynamic min = dynamic max = static max were all changed and set to 6GB so don't think that would be an issue.
I will try a new backup (on XCP-ng 8.1, xo-server 5.70.0, xo-web 5.74.0) and restore of the VM that I used for the Copy and see if that works.
I have no idea of the XO versions used to make the previous backup, but they would have been up to date at the time in April.
edit: The recent backup restored fine. It's not an issue for me but I guess if older backups don't work it could be for others.
@jmccoy555 the forum software defaults to not notifying users by e-mail. I dislike that default but I think it may be related to GDPR and such. You can change that setting in your profile.
When someone mentions youalready set to Notification and email..... odd.
Right just as a double check I restored the same backup to XCP-ng 8.1 and it boots fine. Restored it again to XCP-ng 8.2 and it doesn't boot. Copy the same VM from 8.1 to 8.2 and its fine. So it looks like there's something funny going on with restoring backups on 8.2 made with 8.1.
@jmccoy555 Just to be sure, what's the output of
rpm -q uefistored?
@jmccoy555 And also can you detail the backup setup so that we can try to reproduce? Not sure if it matters, but is it a plain backup, CR, DR, etc.
Yep, the backup is just a 'backup'.
I will try creating a new back up of the same VM on 8.1 and then restoring on that 8.2 but it might take a while as the disk is 64GB.
Updates are available on the 8.2 repositories for the recent "Platypus" security vulnerability.
@jmccoy555 We think we managed to reproduce the issue. I'll let you know about the outcome.
@stormi Just tried a restoring a backup from yesterday and still no luck. Also I can not reproduce the successful copy I thought happened the other day so I can only assume I booted a VM that was on the host prior to the upgrade to 8.2 last time when I thought it worked. At least it appears to consistently not work
Ping something across if you want it testing.
I am a bit out of my knowledge zone here, so please excuse me if I post something unrelated or obvious.
EDIT - it looks like only this VM has a problem when restored from the 8.1 pool to the 8.2.0RC pool (good pick ). Did some more restores and those restored fine .
Restored the plain backup of a Debian
109 VM (based on the Debian 9 Template) from my homelab (DELL R210 II, Xeon E3-1270 V2, 32GB RAM, 8.1 fully patched) to my playlab (DELL Optiplex 9010, i5-3550, 16GB RAM, 8.2.0RC fully patched). My homelab and playlab have different (Synology) NFS SRs connected. I am using XO from source (xo-server 5.70.0, xo-web 5.74.0) to manage my homelab and playlab pool.
Restore was sucessfull and the VM does spin up after about 2min, but with some issues during boot:
[ 0.764806] vbd vbd-5696: 19 xenbus_dev_probe on device/vbd/5696
Gave up waiting for suspended/resume device
[*** ] A start job is running for dev-disk-by\x2duuid-7b8f0998[uuid like string].device (8s / 1 min 30s)
and finally (after 1min 30s)
[ TIME ] Timed out for dev-disk-by\x2duuid-7b8f0998[some uuid, see above] [DEPEND] Dependency failed for /dev/disk/by-uuid/[some uuid, see above] [DEPEND] Dependency failed for SWAP.
The VM finally starts and is fully working but does the above after every reboot.
fdisk -lshows the expected drive/partition/swap. Most likely related to the somewhat different host?
Just a quick follow-up on my last post on restoring backups from a 8.1 to a 8.2.0RC pool.
Successfully tested restoring Linux VMs (Debian 9/10) and Windows 10 VMs (but no UEFI) from 8.1 to 8.2. Tried newly created ("plain") VMs and production VMs (but not all). So apart from that one odd VM, backup and restore works on my homelab / playlab .