XCP-ng 8.2.0 RC now available!

stormi

@jmccoy555 To test, you may try to give the VM more RAM and make sure to have dynamic min = dynamic max = static max.

jmccoy555

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

stormi

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

jmccoy555

@stormi When someone mentions you already 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.

stormi

@jmccoy555 Just to be sure, what's the output of rpm -q uefistored?

stormi

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

jmccoy555

@stormi

uefistored-0.2.5-1.xcpng8.2.x86_64

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.

stormi

Updates are available on the 8.2 repositories for the recent "Platypus" security vulnerability.

stormi

@jmccoy555 We think we managed to reproduce the issue. I'll let you know about the outcome.

jmccoy555

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

gskger

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 10 9 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

followed by

Gave up waiting for suspended/resume device

and

[***   ] 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 -l shows the expected drive/partition/swap. Most likely related to the somewhat different host?

gskger

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 .

stormi

XCP-ng 8.2 officially released https://xcp-ng.org/blog/2020/11/18/xcp-ng-8-2-lts/

stormi

@gskger said in XCP-ng 8.2.0 RC now available!:

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 .

We're still debugging this VM startup issue and will fix it as soon as possible.

stormi

@stormi said in XCP-ng 8.2.0 RC now available!:

XCP-ng 8.2 officially released https://xcp-ng.org/blog/2020/11/18/xcp-ng-8-2-lts/

And, of course, many thanks to all the pre-release testers!

r1

@jmccoy555 said in XCP-ng 8.2.0 RC now available!:

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

Were you not able to attach the pre-existing SR on CephFS? Accordingly, I'll take a look in the documentation or the driver.

jmccoy555

@r1 Good question, I don't know!!

I'll probably find out when I update my main host shortly.

stormi

@jmccoy555 said in XCP-ng 8.2.0 RC now available!:

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

An update candidate is now available that should fix that backup restore / VM copy issue.

Install it with:

yum clean all --enablerepo=xcp-ng-testing
yum update uefistored --enablerepo=xcp-ng-testing

I don't think a reboot is needed, maybe not even a toolstack restart. If you don't see a better behaviour with the update, then maybe try first a toolstack restart and then a reboot.

jmccoy555

@stormi said in XCP-ng 8.2.0 RC now available!:

yum update uefistored

I could only get it (uefistored-0.2.6-1.xcpng8.2.x86_64) to update by yum update uefistored --enablerepo=xcp-ng-testing

But it has done the trick. No toolstak restart or reboot needed either.

stormi

@jmccoy555 you're right, I've fixed my post.