How to migrate VM's from Intel host to a new AMD Ryzen host

[jmasek1]

Hi "Workstation Pro Discussion" community !

hope I'm on the right forum for my request?

I read different threads on AMD  compatibility with VMware including the actual Hypertread issues,  with stacked virtualisation and problems with Windows11 hosts. in this forum.

As a result I'm more confused now then I was before !

So I ask for the recommended migration steps for following situation:

Source:  PC1  Intel based  Win7 host running WS pro 14.1.8

Destination: PC2 AMD Ryzen (7950x3d) Win11 host running WS pro 16.1.0  (actually)

Different (mostly Windows based)  VM's  running on the source should be migrated to run on the destination in the future!

Any  usefull hints how to migrate are wellcome!

best regards  Jiri

[CallistoJag]

We have had 0 issues migrating hundreds of Windows and linux VMs to AMD from Intel. The only preparation we have needed is with some MS SQL machines that needed to have a few settings checked first. As these machines will need to be powered off anyway to move, you meet the minimum requirement

[jmasek1]

Hi  CallistoJack

glad to hear you had no issus and that I meet the mininum requirements!

My Question is basically how to do the migration in a VMWorkstation Context (not  iESX!)

I can think of different options:

1) copy each VM's Directory to new Host HDD , run vmWS 16  to open the VM's *.vmx file

or

2) Use vCenter Converter  standallone V2V conversion Support 

or

3) Use VAMT (ADM's Vmware Architecture  Migration Tool)  maybe only for ESX?

Is Option All I need to do ?

Best regards  Jiri

[a_p_]

Unless you have some special configuration (e.g. linked clones, etc.), it's actually just the copy job (Option 1) which has to be done.

André

[BivasM]

workstation to workstation migrations should not pose any major issue regarding intel to ryzen.

[JAG7]

Hello; 

I am having an issues with a VM migration from Intel to AMD currently running in Workstation 16.x.  The VM seemed to have migrated fine and windows boots with no issues, however in the windows system information screen the "BaseBoard Manufacturer" states "Intel Corporation" and BaseBoard Product states "440BX Desktop Reference Platfform".  Both of these are clearly incorrect. 

Also, in device manager I see INTEL drivers loaded for Network and IDE.   I have tried to uninstall these however they keep getting installed on rescan of hardware. I believe it is to due with the incorrect Baseboard system information, nut I am not sure. 

Can anyone provide direction on how to correct this? Alternatively, is this an issue?  

Info from Powershell commands:

Get-ComputerInfo

CsManufacturer : LENOVO
CsModel : 21C50015US
CsName : *********
CsNetworkAdapters : {Local Area Connection, Ethernet, Ethernet3, Ethernet0...}
CsNetworkServerModeEnabled : True
CsNumberOfLogicalProcessors : 2
CsNumberOfProcessors : 1
CsProcessors : {AMD Ryzen 5 PRO 5675U with Radeon Graphics }
CsOEMStringArray : {[MS_VM_CERT/SHA1/27d66596a61c48dd3dc7216fd715126e33f59ae7],
Welcome to the Virtual Machine}

Get-CimInstance -ClassName Win32_BaseBoard

Manufacturer : Intel Corporation
Model :
Name : Base Board
SerialNumber : None
SKU :
Product : 440BX Desktop Reference Platform

[CallistoJag]

The vm has virtualized HW, it is not a match to your underlying system. The virtual network cards are either using the VMware specific virtual cards or they use the default intel based virtual interface. The processor will be displayed as the correct type, but the rest of the virtual HW will be generic. Hope this helps.

[RDPetruska]

---

@JAG7 wrote:

Hello; 

I am having an issues with a VM migration from Intel to AMD currently running in Workstation 16.x.  The VM seemed to have migrated fine and windows boots with no issues, however in the windows system information screen the "BaseBoard Manufacturer" states "Intel Corporation" and BaseBoard Product states "440BX Desktop Reference Platfform".  Both of these are clearly incorrect. 

Actually, that is 100% correct... that IS what the virtual hardware BIOS and motherboard chipset ARE in a VMware virtual machine.

[JAG7]

Thank-you for your replies.  The information provided is useful. 

I believe there is still something wrong with the migration of the VM from Intel PC to AMD PC. 

The INTEL based source PC VMware Workstation was set with 1 processor, 2 Cores and windows worked fine.  However, on the AMD VMware workstation I have more CPU capacity, but if I change the CPU settings to 1 Processor, 4 Cores for example then Windows Blue Screens on bootup with Stop Code: SYSTEM THREAD EXCEPTION NOT HANDLED. It does not do this every time, but 7 out of 10 times. For the other times, Windows goes through it's automatic repair/recovery process and eventually loads. However the times when Windows does boot up, I find Windows operationally is sluggish. IE. mouse clicks, typing delays, program loads. If I change the CPU settings back to  1 Processor, 2 Cores on the AMD PC VMware Workstation, windows boots and operates fine.

Is CPU settings something that cannot be changed in Workstation with this type of migration or is Windows the one not not working properly? 

Thanks