Posts made by gskger

@stormi My first HP Elitedesk 600 G6 Mini arrived (i5-10500T, 6 cores, 12 threads, 2.3 GHz base clock, 64GB RAM, 256GB NVME) and XCP-ng 8.3 alpha installed and updated right away (but I have the efi: EFI_MEMMAP not enabled message with a boot delay).

The XTF test on this non-enterprise hardware returns

[M01]# ./xtf-runner selftest -q --host
Combined test results:
test-hvm32-selftest                      SUCCESS
test-hvm32pae-selftest                   SUCCESS
test-hvm32pse-selftest                   SUCCESS
test-hvm64-selftest                      SUCCESS
test-pv64-selftest                       SUCCESS

and

[M01]# ./xtf-runner -aqq --host
Combined test results:
test-hvm32-umip                          SKIP
test-hvm64-umip                          SKIP
test-pv64-xsa-167                        SKIP
test-pv64-xsa-182                        SKIP
[M01]# echo $?
3
[M01]#

Have not done anything else with this unit yet.

@stormi I am afraid my playlab host (Dell Optiplex 9010, Intel i5-3550 CPU) is to old to contribute to the XCP-ng 8.3 alpha testing, but I run the XTF test with this results:

[h01]# ./xtf-runner selftest -q --host
Combined test results:
test-hvm32-selftest                      SUCCESS
test-hvm32pae-selftest                   SUCCESS
test-hvm32pse-selftest                   SUCCESS
test-hvm64-selftest                      SUCCESS
test-pv64-selftest                       SUCCESS

followed by

[h01]# ./xtf-runner -aqq --host
Combined test results:
test-hvm32-umip                          SKIP
test-hvm64-umip                          SKIP
test-pv64-xsa-167                        SKIP
test-pv64-xsa-182                        SKIP
[h01]# echo $?
3
[h01]#

I have some HP Elitedesk 600 G6 mini coming in to test as a small virtualization lab (i5-10500T, 6 cores, 12 threads, 2.3 GHz base clock, 64GB RAM). Not the target infrastructure but will add to the range of hardware.

@stormi Both host of my playlab are happy with the 73 patches applied by yum update and reboot . I assume that a rolling updated with XO would have worked as well

@stormi Finally updated my two host playlab from 8.2.0 fully patched to 8.3.0-alpha2 using the ISO method followed by installing available patches using XO from source.

As boring as it is, I have nothing to report other than that the update of my low-tech hosts has worked (Dell Optiplex 9010, Intel i5-3550 CPU, 32GB RAM, Intel S3700 100GB SSD for boot, Samsung 860 EVO 500GB SSD for local SR, Intel X520-DA1 10G). You wouldn't believe it, but sometimes boring is good .

I'll report back if anything comes up in day-to-day operations .

Same on my playlab. Updated both hosts and no issues so far.

Updated my playlab and nothing to report. Looks good.

@Danp Thank you for bringing that discussion back to my mind. Read about it in the Xen Orchestra 5.76 release blog too. I just hope the icon becomes a little more inconspicuous

I just came accross this new (to me) symbol in the pool view, but can not find any information on what it means. Which functionality is not available?

• XO from third party script
• commit be623
• xo-server 5.105.0
• xo-web 5.106.0)

@Danp Same here. Have been running XO from script with 4GB since I ran into problems I think a year ago. No problems since than

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

@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

@olivierlambert I think the OP tried using the Phyton script, but the link in the documentation is broken. A quick search gives no good results, so hopefully someone on the forum has the script available.

@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 Can not help with the sm and sm-rawhba regression, but did the update anyway. Worked well and kicking some VMs around works as expected. Let's see how my playlab does during the weekend.

@stormi All good with updating my playlab.

@stormi The initial update worked fine on my playlab (two Dell Optiplex 9010, Intel i5-3550 CPU, Synology shared NFS storage), but I can not migrate VMs between hosts anymore. Neither XO from third party script (commit 395d8, xo-server 5.96.0, xo-web 5.97.2) nor XCP-ng Center 20.04.01 work.

Edit: After a complete (bare metal) restart of hosts and storage systems, everything works as expected (create, migrate, start/stop, snapshot of VMs), so I can only blame myself

@stormi Update worked fine and no problems so far. Did the usual tests to create, move, snapshot, backup and restored some Linux and Windows VMs.

@olivierlambert I get the same error on a XO from third party script (same script as OP, commit a1bcd, xo-server 5.93.1, xo-web 5.96.0). Can share the error log and more infos to reproduce the error if that helps.