XCP-ng 8.2.0 RC now available!

_danielgurgel

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

xe host-list uuid=<host uuid> params=other-config

[13:01 CLI220 ~]# xe host-list uuid=e1d9e417-961b-43f4-8750-39300e197692 params=other-config
other-config (MRW)    : agent_start_time: 1604332891.; boot_time: 1604323953.; iscsi_iqn: iqn.2020-11.com.svm:cli219; rpm_patch_installation_time: 1604320091.898; last_blob_sync_time: 1570986114.22; multipathing: true; MAINTENANCE_MODE_EVACUATED_VMS_SUSPENDED: ; MAINTENANCE_MODE_EVACUATED_VMS_HALTED: ; MAINTENANCE_MODE_EVACUATED_VMS_MIGRATED: ; multipathhandle: dmp

[13:02 CLI219 ~]# cat /etc/iscsi/initiatorname.iscsi
InitiatorName=iqn.2020-11.com.svm:cli219
InitiatorAlias=CLI219

olivierlambert

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

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

xe host-list uuid=<host uuid> params=other-config

[13:01 CLI220 ~]# xe host-list uuid=e1d9e417-961b-43f4-8750-39300e197692 params=other-config
other-config (MRW)    : agent_start_time: 1604332891.; boot_time: 1604323953.; iscsi_iqn: iqn.2020-11.com.svm:cli219; rpm_patch_installation_time: 1604320091.898; last_blob_sync_time: 1570986114.22; multipathing: true; MAINTENANCE_MODE_EVACUATED_VMS_SUSPENDED: ; MAINTENANCE_MODE_EVACUATED_VMS_HALTED: ; MAINTENANCE_MODE_EVACUATED_VMS_MIGRATED: ; multipathhandle: dmp

[13:02 CLI219 ~]# cat /etc/iscsi/initiatorname.iscsi
InitiatorName=iqn.2020-11.com.svm:cli219
InitiatorAlias=CLI219

So the IQN was correctly "saved" during the upgrade, it sounds correct to me. Is that host in a pool? Can you check for the other hosts?

_danielgurgel

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

So the IQN was correctly "saved" during the upgrade, it sounds correct to me. Is that host in a pool? Can you check for the other hosts?

All others are correct and with other guests running.
I'll do some testing by removing the iSCSI connections altogether and replugging the host that has been updated.

If you have any tips on how to solve it, i appreciate your help.

olivierlambert

Frankly, I never saw that error before.

It's in there:

https://github.com/xapi-project/sm/blob/master/drivers/BaseISCSI.py#L143-L155

You have the field in XAPI, so I don't get why it fails with an error.

stormi

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

on first boot of the install ISO I got a nominal error of
Installer mode (UEFI) is mismatched with target boot mode (legacy)

I would expect this if you're booting the USB stick in UEFI mode but have your existing system configured to boot in legacy mode (though I don't know exactly how that is detected).

Maybe @beshleman would know.

Update: I think that's a message from the installer itself, actually. It detected that the existing XenServer system was installed in BIOS mode, not UEFI, so it refuses to go on.

gskger

Upgraded a three host homelab:

ISO upgrade from XCP-ng 8.1 fully patched to XCP-ng 8.2.0 RC
ISO upgrade from XCP-ng 8.2.0 beta fully patched to XCP-ng 8.2.0 RC
ISO fresh install of XCP-ng 8.2.0 RC

My quick-and-dirty setup of Let's Encrypt on one of the hosts survived the ISO upgrade - nice

Did a yum update on all hosts and tested:

Add/remove hosts to XO from source
Join/remove hosts to a pool.
Copy/Move of VMs (within and across pools)
Move VDI between local/shared SR
Create/Change VMs (Linux, Windows (but not UEFI))
Add, Remove, Re-add NFS shares (ISO and storage)

Rocky

@stormi yea, I wasn't concerned about it was just documenting how it's normal I guess. Actually it's a helpful error even because then I knew to boot the USB the legacy (non-uefi) way.

Rocky

Shared nothing windows 10 Live migrations working well in my 2 hosts 8.2RC pool. both uefi VM and BIOS vm.

Rocky

So one error I got was on a XO backup job from a VM I moved from an 8.1 pool to a my test 8.2RC pool.

Error: INTERNAL_ERROR((Failure "Expected string, got '{}'"))

Update: I get this error on a new backup job also. This is on XO from the sources, I'll test with XOA also.

Update: this is working from XOA, not sure why I got the error in XO (from sources)... and I got 86.73 MiB/s. Which I think is faster than 8.1.

Update: this is now working for XO (from the sources) after I updated to 5.70.0 / 5.74.0 thanks for the great products.

olivierlambert

Thanks for the feedback! It's very helpful

beshleman

@stormi The installer just checks for the existence of "/sys/firmware/efi/", which is created when the kernel EFI driver reads that EFI is enabled from the boot_params passed to it from GRUB2. This is how it detects the "Installer mode"

The "target boot mode" is UEFI if an EFI (ESP) partition is discovered on the target disk, otherwise it's determined to be legacy.

A mismatch between the two will cause this error. This system is a UEFI system, but doesn't appear to have a ESP on the target disk.

stormi

Important update about XCP-ng 8.2

There were several updates pushed to the repositories for XCP-ng 8.2 RC. More than planned, because we chose to sync with the latest Citrix Hypervisor 8.2 hotfixes before the final release.

So please update (yum update, see https://xcp-ng.org/docs/updates.html if needed), reboot the hosts, and give us your feedback.

You're not supposed to notice anything changed. These changes are under the hood.

This is the last sprint. If all goes well, XCP-ng 8.2 final will be released real soon.

gskger

@stormi did yum update on my three host homelab. So far everything is running as usual, but I did no real test others then starting/stopping/restoring some VMs and moving them around.

A Former User

This post is deleted!

KernelCrunch

I made a little project out of it and removed two of my servers from my pool to install 8.2 RC from scratch. There was a learning curve as I could not use the Windows XCP-ng Center for ANYTHING. So, I had to learn some more xe commands. Everything seemed fine at first. I migrated a handful of servers over. I hit a roadblock when I couldn't get my 2nd server to join the pool of the 1st. (This was never a problem when I used the XCP-ng Center in 8.1. Though I never tried using the xsconsole to join a server to a pool in 8.1 either.) I couldn't find log entries which would tell me why it was failing. I would love to troubleshoot this further but I want to get everything back to normal before Monday. The two servers were AMD TR 3960X and AMD Ryzen 3900X. I'm very curious if I was to just upgrade if there would have been any issues.

olivierlambert

You can rely on https://xcp-ng.org/docs/cli_reference.html#xe-cli-reference

There's also the command to add a host to a pool there. It's even better than using the text UI.

eg https://xcp-ng.org/docs/cli_reference.html#xe-command-reference

gskger

@kernelcrunch Deploying the Xen Orchestra Appliance (XOA) on one of the hosts will give you a UI to perform all required actions to create and manage a pool. It is really easy to install and use (and the recommanded UI for XCP-ng).

A Former User

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

Danp

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

A Former User

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

UPDATE:
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..