Generic VM not starting after migration to different unraid, other similar VM works.

[KptnKMan]

Hi,

I have a pretty generic Win10 VM that I have migrated over to a different unraid server, and it refuses to start under the same generic settings.

THe VM works fine on the old system (AMD Ryzen) but on the new system (Intel 13900H) there is no dice at all.

 

After a few tries the Windows Startup Repair runs though, so it seems the VM is "booting" but starting actual Windows doesn't work.

 

Interestingly, ANOTHER VM does boot, a similar Windows 10 generic VM (Migrated from AMD Ryzen system to same Intel system) with Virtual GPU etc, and that seems to be fine.

 

I'm at a loss investigating on what might be the problem...

 

Does anyone have an idea?

[KptnKMan]

I still haven't got this VM to work, and I've been trying everytrhing I can find.

Is it possibly something to do with TPM, why it won't start?

 

Does anyone have advice on how to copy TPM from another Unraid?

 

Would really appreciate any ideas.

[KptnKMan]

This continues to be a confusing issue, especially as I have now migrated other Windows VMs between the same systems without issues.

THis particular VM just seems to refuse to start on the new system.

 

Also, it seems that I cannot delete THIS particular VM now, but I can create/delete other VMs.

When I try to delete it, I just see the spinning arrows to infinity.

I've rebooted enough times, cleared browser cookies cache, tried a different browser.

 

If anyone has even an idea, I'd really appreciate anything...

[SimonF]

Do you have any files in the domain/vmname directory.

 

virsh undefine vmname should remove the config.

[KptnKMan]

41 minutes ago, SimonF said:

Do you have any files in the domain/vmname directory.

If you mean the domain dir on the cache disk, no there is nothing there.
I have even deleted the vdisk and the VM refuses to go.

 

41 minutes ago, SimonF said:

virsh undefine vmname should remove the config.

That also doesn't seem to work, I get a message:
 

root@unraid2:~# virsh undefine VM1-WIN10-Q35-OVMF
error: Failed to undefine domain 'VM1-WIN10-Q35-OVMF'
error: Requested operation is not valid: cannot undefine domain with nvram

 

[KptnKMan]

I looked into the error and and this worked:

root@unraid:~# virsh undefine --nvram "VM1-WIN10-Q35-OVMF"
Domain 'VM1-WIN10-Q35-OVMF' has been undefined

 

 

Still very confused about trying to get this particular Win10 VM running...

[SimonF]

4 minutes ago, KptnKMan said:

I looked into the error and and this worked:

root@unraid:~# virsh undefine --nvram "VM1-WIN10-Q35-OVMF"
Domain 'VM1-WIN10-Q35-OVMF' has been undefined

 

 

Still very confused about trying to get this particular Win10 VM running...

Did you use tpm in the vm as there would be a file that needs to be copied also. If younpost xml i can take a look.

[KptnKMan]

vm1-win10-data0.xml

Here is the xml for the VM in question.

 

I did try migrating the "/etc/libvirt/qemu/nvram/b154af59-fe03-1020-2c56-1a5f76d10671_VARS-pure-efi.fd" file on line 31, but still no joy.

 

It's like this VM just doesn't want to be moved for some reason.

 

I know it "works" because the Windows Recovery runs after a few reboots, but the actual OS refuses, just black screen forever.

 

Oh, also I didn't use TPM BIOS just the normal OVMF.

Edited June 5 by KptnKMan