Best posts made by gskger

You could at least send the backup reports (requires backup-reports and transport-email plugin on XOA) to a Microsoft Teams channel of your choice (Channel - More options - Get email adress).

@gduperrey Updated my two host playlab without a problem. Installed and/or update guest tools (now reporting 7.30.0-11) on some mainstream Linux distros worked as well as the usual VM operations in the pool. Looks good

@stormi Did not even know the problem existed . Anyway, added a new (second) DNS server (9.9.9.9) to the DNS server list via xsconsole and rebooted the host (XCP-ng 8.2.0 fully patched).

Before update: DNS 9.9.9.9 did not persist, only the previous settings are shown
After update: DNS 9.9.9.9 did persist the reboot and is listed together with the previous settings

Deleting DNS 9.9.9.9 worked as well, so the xsconsole update worked for me.

@stormi Updated my two host playlab (8.2.0 fully patched, the third host currently serves as a Covid-19 homeoffice workstation) with no error. Rebooted and ran the usual tests (create, live migrate, copy and delete a linux and a windows 10 VM as well as create / revert snapshot (with/without ram) ). Fooled myself with a VM_LACKS_FEATURE error on the windows 10 VM until I realized that I forgot to install the Guest tools - I need more sleep. Will try a restore after tonights backup.

Edit: restore from backup worked as well

@gduperrey Rolling update of my homelab through Xen Orchestra worked flawlessly. Thanks!

@gduperrey Updated my playlab and did some basic tests (create, copy, snapshot, (life-) migrate VMs and disks). Looking good so far.

@gduperrey Update installed successfully on my 2 host playlab with shared NFS TrueNAS Core storage on a 10G network. Let's see how VM usage works during the next days.

@stormi Again more a regression test for the basic things. Tested Debian and Ubuntu VMs (create, live migrate with/-out guest tools (now at 7.20.0-9), start/stop/reboot, snapshot with/-out RAM and revert, storage migrate from/to shared and local SR). Imported Centos and Ubuntu VMs and restored a Windows 10 and a Debian VM from backup. No issues so far. Nice work.

@stormi Did the update on my two host playlab, which worked well. Do not use secureboot/UEFI or QNAP, so this is more a regression test for the usual stuff. I tested Debian, Centos and Ubuntu VMs (create, live migrate with/-out guest tools (now at 7.20.0-8), start/stop/reboot, snapshot with/-out RAM and revert, storage migrate from/to shared and local SR) and restored a Windows 10 and a Debian VM from backup. As for now, everthing is working. I will see how backup runs tonight.

Upgraded a three host homelab from XCP-ng 8.1 fully patched to XCP-ng 8.2 beta.
Things done/tested successfully:

• Upgrade process (via ISO)
• Copy/Move of VMs (even cross pool)
• Create/Change VMs (Linux, Windows (but not UEFI))
• Add/remove server to XO from source
• Create/Change networks
• Fresh install process (via ISO)
• Basic storage benchmark on dom0 and Debian VM using fio
• Add, Remove, Re-add NFS shares (ISO and storage)

This weekend I try to do some backup/restore (if time permits).
Nice work XCP-ng rocks

[edit: some more tests]

@stormi
Cannot test the bugfixes on my system but did an ISO update of my two host playlab (DELL Optiplex 9010, XCP-ng 8.2.0 fully pathed) with the updated installation images for XCP-ng 8.2. The update process went well, but this are pretty plain and identical systems with XCP01 being master and XCP02 being slave. The only thing different between the hosts was that I had to confirm the NIC setup steps on the slave XCP02 but not on the master XCP01 (which was updated and rebooted first)?
Apart from the update process, creating, starting, stopping and deleting (Linux) VMs does work as usual as well as taking snapshots and doing VM and storage migration. Will do a fresh install with the updated installation images the other day if time permits.

@stormi Updated my two host playlab (XCP-ng 8.2.0 fully patched) as per 1 and did a reboot of the hosts.

Created a new Debian 10 VM from scratch, installed the new guest tools and did a reboot of the VM. IP addresses and Management agent are shown as expected. Clean shutdown and reboot is working (from XO from source and from the VM console). Live migration is working as well.

Did the same with a Debian 10 VM restored from backup and it basically works as well. I experienced some "blibs" along the way which I attribute to my impatience (e.g. I was unable to eject the new guest tools disk after a live migration and needed a toolstack restart). Can not reproduce this, so most likely nothing.

Edit #1: Exported a Debian 10 VM with the "old" guest tools installed from another pool and imported it to my playlab pool, installed the new guest tools, did a reboot and it works as expected.

Edit #2: Created a new Ubuntu 20.04 server VM and everything works as well.

@gduperrey Updating my playlab and all is good with some easy VM operations and VM/storage migration test. Now let's see how the next few days of normal tasks turn out.

@stormi All good with updating my playlab.

@gduperrey Updated my two host playlab (Dell Optiplex 9010, Intel i5-3550 CPU). Everything works as expected, but I doubt my CPUs are relevant for the update either.

I have a strange INTERNAL_ERROR((Failure "Expected string, got 'N'")) error with Xen Orchestra (from 3rd party script update to commit a1bcd) when creating a new Debian 11 VM as part of my test procedure, but I could continue with XCP-ng Center. Just found and will follow xoce INTERNAL_ERROR while trying to create VM.

@stormi Reinstalled my playlab from the test installation ISO and will do some testing tomorrow. Poking around with some imported VMs showed now errors so far, but real tests are pending for the weekend . Most likely much to early but looking good so far. Keep fingers crossed for the weekend

@stormi A lazy sunday morning, some coffee, a notebook and time for testing. Updated my two host playlab (DELL Optiplex 9010, 8.2 fully patched) and tested Debian VMs and Windows 10 VMs (create, live migrate with/-out guest tools, start/stop/reboot, snapshot with/-out RAM and revert, online-/offline storage migrate from/to shared and local SR). Restored a Windows 10 and a Debian VM from backup. All good so far for this regression test.

@benjireis Had some time for testing and installed the update on my two host playlab (DELL Optiplex 9010, XCP-ng 8.2.0 fully pathed). This are identical hosts with an onboard NIC (Intel 82579LM, eth0) and a dual port NIC (Intel 82571EB/82571GB, eth1 and eth2). Both are connected to a Synology as shared storage.

• Starting with the master, both hosts updated and rebooted without an issue.
• Live migration of Debian, Ubuntu, Centos and Windows 10 VMs works (with and without guest tools installed).
• Host evacuation over eth0 (Management network) without the new network-uuid parameter works as before.
• Host evacuation over eth1 (Storage network) with the new parametrer works at full gigabit speed.

Still working on 10G in my playlab, so i only have 1G available, but host evacuation over a non- management network works with the new network-uuid parameter.

@stormi Successfully updated my two host playlab (8.2.0 full patched, but with the new guest tools ISO). Rebooted both hosts and ran my usual test program (create, live migrate (without (only Debian) and with guest-tools installed (Debian 10 and Windows 10) avoiding the VM_LACKS_FEATURE error on Windows 10 - more sleep this time ), copy and delete as well as create / revert to snapshot (with/without ram) and (live/halted=shutdown) storage migration remote to local SR and back). Also restored a Debian 10 VM from a pre-update backup with no problem. Looks good . Will see how backup runs tonight, but I am confident that this will work as well.

Edit #1: typos

Edit #2: Thanks to Xen Orchestra, out-of-band management even for Optiplex 9010s, a notebook and a very nice evening on the balcony, I extended my tests to Ubuntu 20 LTS. And you might guess it - works as well

Edit #3: Deleted a subsequent post on an asyncMap is not defined error because it is not related to the security update.

@olivierlambert It is a pleasure to help. I highly appreciate your teams work on making XCP-ng better and more secure as well as the support you give.