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

Something worth noting is that when the server itself is booting (bios menu etc) there is output on the rack KVM, but as soon as the OS itself boots, there is nothing.

For some reason, as soon as XCP-NG boots, our Dell-branded rack KVM & Console has no output at all.

This is on XCP-NG 8.2.1, as well as the 8.3 installer (doing upgrade for 8.3 currently).

This shows on the rack KVM & Console as no input detected. It only affects the XCP-NG hosts as well as the installer image (via USB).

The physical servers are Dell R660 hosts.

When using the iDRAC Enterprise virtual console, there is output. I'm able to use the virtual console to interact with both the installer, and XCP-NG once it boots.

When troubleshooting issues at the server rack, we are unable to use the physical KVM at all.

Does anyone have thoughts on why this is, and why it only affects XCP-NG systems?

@olivierlambert Interesting.

When you say SSH disabled by default, are you talking about XCP-NG not supporting SSH connections out of the box? Or XOA?

@olivierlambert

Interesting.

Does XO connect to each of the servers via SSH to be able to manage the stuff via XAPI etc?

Couldn't you integrate a bash script via the SSH connection to do this when someone tries to rename an interface via the XO UI?

Perhaps I can work on one that could just be ran as a standalone for now.

@CodeMercenary Glad it worked out for you.

@CodeMercenary Try the toolstack reset on that host.

Maybe do a toolstack reset on the pool master as well - which doesn't affect running VM's.

If that doesn't work, try an emergency network reset on the host having trouble.

@CodeMercenary Have you restarted the toolstack now that it is doing what it needs to do?

That might make the console show what it needs.

Also try exiting out of the console and then starting it back up with xsconsole.

@olivierlambert

This section.

https://xcp-ng.org/docs/networking.html#renaming-nics

If we could go into a host and change the network interface status to disconnected and then click on the "device" name and change the interface - and then change the status to connected, that would make it a lot easier for users to rename interfaces on hosts that do not match the rest of the pool.

In my particular instance, the rest of the servers are using eth4 for the 10gb/s interface but this particular host has that interface as eth2, so it needs to be renamed to eth4 so that this host may be used with the pool without issues.

@olivierlambert I would like the ability to rename physical network interfaces for a host inside of XO.

To disconnect an interface (put it in a down state) and rename it instead of having to do it via the CLI.

This would help when trying to join new hosts to a pool that have different interfaces out of the box because the interfaces have to be renamed to be the same across the entire pool.

Where is the best place to submit a feature request for XO?