Motherboard/CPU upgrade - reinstallation needed?

[bellocarico]

As per title I'm upgrading my old tyan motherboards to a more recent version but different  brand; Supermicro.

in both cases the CPU are opteron.

What would it be the best way (quicker) to move the ESXi 6.5 standalone installation from one motherboard to the new one?

The controller and RAID will still be the same untouched.

I guess reinstalling is a must e.g. doubt I just moe the disk and it will work as it is... if so can I just perform something like upgrade so without really touching the config?

Or do I really have to go through the pain to reinstall from scratch?

Thanks!

[Alex_Romeo]

Hi,

many times there is no need to reinstall, check the article within the post:

ESXi 5.5 - processor upgrade

(even if and for 5.5)

ARomeo

[bellocarico]

Thanks, if it was the CPUs only I would have concluded the same indeed!

Here though there's a new motherboard and different brand too, still supporting Opteron CPUs but I would expect some drivers to be different.. not sure?

[Alex_Romeo]

Hi,

The drivers will certainly be different. If you are patient to reinstall Esxi, it is safer.

If I were you I would do it, and if possible, with some more updated versions, even 5.5 or 6.0

ARomeo

[disheng222]

I recently had to replace motherboard for my laptop, and I noted that VMWare workstation 16 player cannot launch the VM guess machines (windows OS). My host is LInux.

I found another guy had the same issue: https://communities.vmware.com/t5/VMware-Workstation-Pro/Failure-to-start-VM-after-replacing-motherb...

But I can't see any solutions? 

Any ideas?

Thanks! 

[scott28tt]

@disheng222 

Other than changes in the BIOS settings, I can think of no other reason why Workstation would care that you swapped out your motherboard, it doesn’t have the same driver model as something like ESXi (which this thread was about).

[disheng222]

Thanks, scott28th!

I found the reason. 

That's because of 'virtualization technology' which was turned off by default in BIOS setting. 

After turning it on, the problem is solved. 🙂