@fx991 You cannot live-migrate between hosts with processors that have different instruction sets.

You would have to shut down the VM and then migrate it and then power it back on after migration completes.

The E5506 and E5620 have similar instruction sets but the E5506 does not support hyperthreading or AES instructions, so there are some differences here.

The E5-2643 v2 is completely different.

If you power off your VM and then migrate it, it should be fine. From what I understood from your post you tried to live-migrate it and then reboot it after it had migrated and run into issues, which I would expect to happen.

@BenjiReis Thanks! I was looking in host-view and couldn't find this.

@darkbeldin I believe that it was created in UEFI mode but I am not certain.

When starting the .VHD file in UEFI mode I get the following screen:

It doesn't detect the hard drive at all as far as I can see....

Attached via Windows

I have a Windows Server 2016 VM that gets stuck on Boot Device: Hard Disk -- Success.

Starting the VHD file from a UEFI or Secure UEFI bios config sends it directly to the bios shell prompt - the VHD file is not detected as a bootable media at all.

When set to BIOS, it gets hung up on the Boot Device: Hard Disk -- Success prompt.

Attaching the VHD image (as read-only) in Windows Disk Management from a Windows device displays all of the data so I don't think it is an issue with the .VHD file itself.

I had the same result when starting the VHD file from NFS remote storage as well as local storage.

What could cause this?

@olivierlambert Thanks for the reply. I'll change to the "master" branch. I thought you were on a release schedule because you have a "releases" tab with the releases.

I was on the XO website today looking through some of the news articles and noticed a few on recent releases of XO.

It seems that the latest github community edition release was 5.51.*.

Are the later releases not available in the Community Edition?

@fx991 Mostly fine means that you may run into issues. Just shut down your VM and restart it on the new host.

@BenjiReis Thanks! I was looking in host-view and couldn't find this.

@fx991 You cannot live-migrate between hosts with processors that have different instruction sets.

You would have to shut down the VM and then migrate it and then power it back on after migration completes.

The E5506 and E5620 have similar instruction sets but the E5506 does not support hyperthreading or AES instructions, so there are some differences here.

The E5-2643 v2 is completely different.

If you power off your VM and then migrate it, it should be fine. From what I understood from your post you tried to live-migrate it and then reboot it after it had migrated and run into issues, which I would expect to happen.

Is it possible to rename networks on XO Hosts?

For example, "Pool-wide network associated with eth2" is not very descriptive. Can we rename these to something friendly like "Vlan35" or "Storage Network"? If so, how would this be done?

Also, the (i) button at the bottom right corner under networks on a host redirects to a 404 page on XO-Server 5.51.1 / XO-Web 5.51.0. It points here.

X-O Server is 5.51.1 and XO-Web is 5.51.0.