@cichy

You need to select a vm template.

Update - After shutting down the VM and removing the previous snapshot and creating new one. I left VM powered off after creating new snapshot. VM is migrating now.

Screenshots of VM settings and files...

I dont see a the file that it is looking for...

I am trying to complete my vmware migration and I have 2 more vm's to migrat. All have been successful until now...

This is the error message i get when trying to migrate the VM.

503 Service Unavailable https://192.168.1.125/folder/ArcDC01/ArcDC01-000001-sesparse.vmdk?dcPath=ha-datacenter&dsName=SSD_DataStore

Suggestions? I have since started the VM back up on vmware and the VM is working.

The only thing i did differently was take a snapshot from a shutdown state before removing the vmware tools. This server is our Primary Windows Active Directory.

@Danp said in XOA license issue:

@acebmxer It looks like you've resolved the first issue by binding the trial license. You haven't yet purchased support, so you won't be able to bind licenses to your XCP-ng hosts. This has no effect on the functionality of the hosts.

Ok thank you for the update that this is expected behavior. We do plan to pay for support just need to take care of a few things on our side before we do so.

@Greg_E

I know this is an old thread but just incase others come accross it. @Greg_E did you resolve this?

Did you install the UEFI certs into the new install - https://docs.xcp-ng.org/guides/guest-UEFI-Secure-Boot/

I had some issues and had to do them manually see here - https://xcp-ng.org/forum/topic/11129/xcp-ng-8.3-uefi-certs-wont-install

@kubuntu-newbie

Yeah i didnt do anything with disabling the vgpu. Just a standard Win 11 or ubuntu VM and attached the nivdia gpu.

I was able to get nvidia rtx 4070 passed through to a windows VM and Ubuntu server. Need to make sure you passing all the devices associated with the GPU, specifically the Audio controller on the GPU.

These were on AMD systems.

Just an FYI I currently only have 1 xcp-ng host as I am still in the vmware migration. I have 2 more vms to migrate which is scheduled for tomorrow. If no issues I will be able to being over the 2nd host to xcp-ng.

Thread created to move the conversation

@olivierlambert said in XOA fails after update to 5.106.0:

I don't think it's the same issue. Originally, you ended on a white page with "Cannot get /". It seems unrelated here, right?

Yeah i think i have moved passed the original issue onto this issue. That is why I stated you can move this to its own thread if need be. Or I can open a support ticket now that is usable.

@olivierlambert

I still belive this an issue unless i am missing something here. Just fired up my XOA 5.105 and updated to latest stable 5.108 and it broke. Updated to latest XOA 5.109.1 and broke still. Maybe I just from 5.105 to 5.109.1 it will work by skipping 5.108?

In this state i can not navigate any menu stuck at this screen.

EDIT:

Update. Feel free to move this to its own thread if need be.

Think I figured it out but still having an issue. The below screen shots are from 5.105. Is the error

@utopianfish & @AtaxyaNetwork - Maybe related to this bug noted here- https://xcp-ng.org/forum/topic/10798/xoa-fails-after-update-to-5.106.0/71

@DustinB

I was following the directions stated here - https://docs.xcp-ng.org/installation/migrate-to-xcp-ng/

Which states to remove tools then take a fresh snapshot.

VMFS 6 (6.7 and newer)
For VMFS 6, the VM needs to be shut down. Follow these steps:

Uninstall VMware tools before migration.
Remove all snapshots attached to the VM.
Ensure no ISO files are mounted to the VM.
Shut down the VM.
Take a fresh snapshot.
Start the migration process.

Also I am aware of the XO backups are not application aware. We use Veeam for that backup data. And i still have Veeam backups from the Servers to fall back onto. I just wasn't sure if there were any other precautions i should be taking or thinking about.

It seams after another restart or two of the server and repallying the latest update (same version that was installed) and restarting its services a few times. It appears to be working...

I now have a fear I might have issues when i go to migrate our Windows Active Directory master. I have moved over our backup dc (dc2) which runs our DHCP server and backup DNS. That appears to be working.

Is there any particular precautions i should be taking prior to moving that server? Previous steps followed were

1. remove vmware tools and reboot server.
2. once back up shut down server.
3. remove any old snapshots(none to remove)
4. take a snapshot
5. start the migration process.
6. adjust cpu topology.
7. start vm log in adjust date and time and IP address as needed.
8. shut down vm enable vm tools via windows update and attach iso made with management tools.
9. Power on vm let it reboot as needed for driver installs
10. install management tools (let windows update handle drivers).
11. Run windows updates until all updates applied.

Should I take the 1 / final snapshot prior to removing vmware tools? Incase of issue i can spin up old vm? Open to ideas and suggestions.

After migrating our windows server that host our Duo Proxy manager having an issue.

[info] Testing section 'radius_client' with configuration:
[info] {'host': '192.168.20.16', 'pass_through_all': 'true', 'secret': '*****'}
[error] Host 192.168.20.16 is not listening for RADIUS traffic on port 1812
[debug] Exception: [WinError 10054] An existing connection was forcibly closed by the remote host

After the migration I did have to reset the IP address and I did install the Xen tools via windows update.

Any suggestions? I am thinking I may have the same issue if i spin up the old vm as the vmware tools were removed which i think effected that nic as well....

@Andrew said in XOA fails after update to 5.106.0:

@acebmxer Did you activate your License?
Click on XOA then Licenses (at the top). Make sure you see This license is active on this XOA

Yes in 5.105.0 (fresh install) it worked. When i upgrated to 5.108.1 it stoped. I tried v5.109 and failed. same as @Lhoust

Using XO from sources for the moment.

I just installed XOA at work and after updating to latest stable 5.108.1 i am facing the same error.

This is a fresh install in preparation to migrate from vpshere.

@DustinB

That pic was taken from the host tab. But yes I removed from the settings tab and host 2 still shows under pool 1 and all looks ok.

Thank you.

@DustinB can you explain further? What is the proper procedure to adding a second host once you have 1st host and xo setup? Below are the steps i did. To follow what you said i should be able to click settings and just remove the host2? From first picture?

1. Click on settings and add connect 2nd host.
2. click into the pool and choose add host. Selected host 2 and it dropped it from itself selfcreated pool and added into pool1 with host1.

Now i see what I showed in pics above.

v6