@taghjichte Try importing the OVA files using XOA (Import > VM).

@yann-lebris I did, however. I cant assign more than 1 VM to the VLAN. When I migrate a 2nd VM and assign it to the same VLAN it takes the IP from the first vlan.

This is under Pools-Network
1003cd1c-4d92-4ce9-b961-4241f0f8199a-image.png

This is under Hosts-HostName-Network
9c61e2d3-74e0-46be-9e54-38324a0703e0-image.png

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 😉

@ricardowz
No Warning. Updates are from 2. April. I attached the Screenshot.

Can someone confirm that we could just "upgrade" to XCP-NG 8.3 and the VMs will run?

Greetings

9fca47c9-1a1d-4b02-9679-9acf0f58e121-image.png

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 🙂

@McHenry

Hey

Whatever happened to this? Have you solved it?

After looking at your comment I found this https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/manage-hyper-v-integration-services which explains how to disable those. I haven't done this before.

@McHenry +1. Never found how to do it....

@BenjiReis

Got it, thank you.

That's a possibility. Can you try and report after rename?

On which XOA release channel were you when you imported it? Are you up to date? I think we recently fixed the memory settings doing VMware imports.

@vaewyn another reason for leaving vmware 😉 in would go for robocopy then.