I might have hard time to give you a confirmation, but worth checking on the VMware side, yes

@stormi Thank you for your reply.

@Cygace XO is not directly tied to XCP. So the versions have nothing to do with each other. You can look at the XO master commits and pick one that lists feat: release 5.xxx.x and that will line up with a XOA release. You can pick a version that is the same as the current XOA release and it will be the same tested base code.

Thanks, that's very useful info! @florent will take a look when he can!

I don't think that's going to be an issue with Vates, they have ppl in different parts of the world and they're very helpfull. Reach out to them and link this forum thread, im sure they will be able to get you going even tho you're in Australia.

@ph7 said in Error starting network UPS tools (NUT) driver for TrippLite USB-passthrough: @waveguide I used the PCI passthrough for my zigbee USB Dongle and it has been working perfectly since I installed it 2½ month ago [image: 1738063996972-c349c774-c4bb-4dde-97f9-887521e2a871-bild.png] Interesting idea. I am running on a Dell R710 and the USB controller is not listed as an available PCI device that I can passthrough to the guest VM. It does come up on the host as a PUSB device. The ESXi server was also an R710. [image: 1738113146366-525ece0c-93c4-4cd0-8ce5-c001961959c2-image.png]

@TheLastOtter Strange. I think you touch nothing on your side?

You can deploy multiple XOA if it's your question, one to export in OVA, one to import the OVA.

Not looking to revive this topic but wanted to post this documentation I found in case anyone else searching for answers stumbles here like I did. There are too links on this site that address some limitations that are not readily documented in the standard migration documentation. https://help.vates.tech/kb/en-us/37-import-export-migration

@Don-Gould-NZ I wonder if this system got cloned as intended. I see 2 devices in XO, that will be xvda and xvdb. Yet earlier you listed it was one device with two partitions. The 512M size of the 2nd device makes me wonder if the migration turned the disk partitions into devices with partition/swap signature and nothing else. As such since the system looks for xvda's 2nd partition for root, there's no partitions so naturally it fails. You could get SystemRescueCD, boot off that and investigate the devices.

@Andrew I did not see a serial port listed. I'll just get a USB version and plug in to server and see if I can pass thru it. If it works, I can get rid of another Destop server and be fully virtual. Thanks for your hellp.

@Danp @olivierlambert so I'm going to build this out next week and how can I do the build out with the trials and after that how much would a 4 node xoa managed HCI with XOSTOR run for licensing? Also are there any guides for best practices for deployment of above configuration? IE what type of network configs for the XOSTOR and the pools. Also the vmware has a citrix deployment on it so do you have a connection aspect for citrix to interface with the pool same as vmware has? My R730 servers have 8 10gb fiber ports each so take that into consideration for the xostor configuration.

The workaround I have found at this point is to rebuild grub after migrating to XCP-NG. Adds a few minutes to each VM but I don't have that many. Boot to live iso in UEFI mode (I used Debian12 given it was a Debian12 vm) sudo su - mount /dev/mapper/????? /mnt mount /dev/xvda2 /mnt/boot mount /dev/xvda1 /mnt/boot/efi for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done mount --bind /sys/firmware/efi/efivars /mnt/sys/firmware/efi/efivars chroot /mnt grub-install /dev/xvda update-grub exit shutdown now I'm using LVM so adjust the first mount to match your root partition. I shutdown so that I can remove iso and boot when I'm ready. Hope this saves somebody a bunch of frustration in the future.

So....................... it is dynamic memory causing me problems. I have have set the min/max and static memory to the be same. The system stays up fine. Now to figure our how/if I need dynamic memory to work on a Windows VM. I do not seem to be having problems with linux based workloads.

I recommend indeed Warm migration that doesn't need any 3rd party vendor tooling that are pushed by some shady accounts

A few things you could do -- Share the full error message (see entry in Setting > Logs) Switch to the "latest" release channel to see if issue also occurs there Review our Vmware migration checklist -- https://help.vates.tech/kb/en-us/37/133 HTH, Dan

Ok, Thank you!

@thomas-dkmt Our Hyper-V servers have no GUI and the process I use is: RDP to the Hyper-V host Open PowerShell Get a list of the VMs on the host Get-VM Stop the VM STOP-VM -Name <name of VM> Identify the VM's disk(s) for conversion Get-VMHardDiskDrive -VMName <name of VM> Convert the VHDX to VHD (destination file extension sets the type so use ".vhd") Convert-VHD -Path <source path> -DestinationPath <destination path> -VHDType Dynamic To transfer the newly created .vhd files to xcp-ng we use Putty via the cli

Hi! What's great is the fact we have -at the bottom of each doc page- a link to contribute to the documentation ("Edit this page"). That would be awesome if you can submit a change request and we could review it and finally merge it, so you'll have a better documentation that will help everyone