The past year 2022 was again an exciting year with numerous innovations in XCP-ng and Xen Orchestra as well as good and helpful discussions in the forum. I am excited about what the new year brings and wish everyone a good start for 2023.

I second that! While not a commercial user, I really like the community and the active participation of the Vates team helping novice homelab user with patience and commercial user with in-depth knowledge alike. Keep rocking!

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

A great and happy new year 2022 to everybody! Another year has passed and the XCP-ng community continues to rock! Stay optimistic and healthy (never hurts ).

Updated my playlab and nothing to report. Looks good.

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

@Gadende Did you check the ISO integrity with the hash or a bare metal install to verify that the ISO is working?

@gduperrey Updated my two host cluster (HP ProDesk 600 G6) and no issues so far.

@olivierlambert Thanks Olivier and I hope it's okay to post some fun stuff from time to time despite the high level of professional discussion on the forum. I enjoy tinkering with low- or fun-tech when not busy with enterprise IT at work.

I couldn't resist a deal for an ACE-T8PRO from Ace Magician. This palm sized x86 computer comes with an Intel Celeron N5095, 8GB RAM, 256GB SSD, dual RTL8111/8168/8411 1Gbit NIC and a RTL8821CE 802.11ac Wireless card.

It idles around 7W with XCP-ng 8.3-beta installed, goes up to 11W during a VM copy or moderate load (3 VM runing fio) and up to 18W when under heavy load. iperf3 is 940 Mbits/sec with about 60 retries, probably due to the Realtek NICs but it has two NICs which is cool.

Nothing to get serious about, but not bad either, and it's still fun to play with. I bought it to test pfSense on a low power platform. Keep fingers crossed for the Realtek NIC performance on FreeBSD.

@stormi Did a clean ISO install of XCP-ng 8.3 beta on my three host playlab pool and imported some VMs to play around with. All went well on my aging lab. Next step is to connect to a TrueNAS 13.0-U4 shared storage.

@stormi Great news ! I will free up my playlab as a dedicated testbed. Keep up the good work (and speed to 8.3 final )

@stormi No problem with a rolling pool update of my two playlab host. Pool reports up-to-date and healthy (XO from source). Basic VM and VDI tasks work as expected. Looking good

@brodiecyber Ok, that makes sense.

I once run XCP-ng on a HP T620 PLUS Thin Client with some lightweight Debian VM for a test. The HPs AMD GX-420CA has a bit higher CPU Mark compared to the j1900 (1787 vs. 1148), but the single thread performance is more or less the same.

Nothing to run major workloads on, but should be ok for testing HA and general XCP-ng operations at low speed. No idea how XOSTOR will be performing on that platform, so please update us on your findings.

@brodiecyber Personally, I think that the setup is very limited in terms of performance with RAM being the greatest challenge from the beginning.

While I understand your initial idea of a low hardware and cost micro XCP-ng cluster to check out HA and learning runX/XOSTOR, you might be paying some good money for a low performance setup with little head room.

Probably not an option, but if it is about learning and testing, you could go for a used mini pc (i10500t, 64GB RAM, 1TB boot and ISO drive, 2TB VM drive) and setup everything as a nested virtualization XCP-ng cluster? That would allow for snapshots and backups to make testing and rollback a breeze. My HP ProDesk 600 G6 is at an 20W average with 16 VMs running. Going for a physical XCP-ng cluster is much more fun though .

@Darkbeldin Mh, in the SMlog it is ls /tmp/nfs -1 --color=never. Thats the number one but should that be the letter l? With the number one, lsreturns.

[17:31 h01 ~]# ls /tmp/nfs -1 --color=never
test
textfile