December 8, 20223 yr I had a hardware problem with a cache pool that I have now fixed. I am attempting to restore a windows 11 VM. I have restored the backup *.img file: -rwxrwxrwx 1 root root 69793218560 Dec 8 16:34 /mnt/user/VM/Windows\ 10/vdisk1.img* I have created a new VM, and restored all the *.xml settings from the backup *.xml, while retaining the new values of <uuid>... and <nvram>... I also copied my backed up *.fd file to the location and name specified by those parameters: -rwxrwxrwx 1 root users 131072 Oct 17 09:58 /etc/libvirt/qemu/nvram/5a177830-4640-6f85-fed8-c2d284bb8488_VARS-pure-efi-tpm.fd* When I start the VM and open a VM console from the unraid dashboard, this is what I see instead of windows booting: If I enter exit in the screen above, I get this: I don't know how to debug this further. Thanks in advance for help.
December 9, 20223 yr change your share or passthrough ssd or whatever you are using as your windows drive to boot order 1 in your vm settings
December 9, 20223 yr Author Solution 9 hours ago, shakinbacon said: change your share or passthrough ssd or whatever you are using as your windows drive to boot order 1 in your vm settings The ...vdisk1.img did have boot order 1, but the windows install *.iso did not have a boot order of 2. I also scrubbed through all of the settings in the forms view, and found a few things that were not the same as they previously were. I don't know if it is user error when I pasted in the prior xml, or if the mapping from xml to forms is not 100% complete or correct. In any case, windows is now booting.
June 12, 20233 yr So, it seems like you had a hardware problem with a cache pool, which you've managed to fix. Kudos to you! Now, restoring the Windows 11 VM can be a bit tricky. It looks like you've successfully restored the backup *.img file and created a new VM, retaining the necessary settings from the backup *.xml file. Nice work! However, when you tried booting the VM and opened the console, you encountered a screen that wasn't Windows booting. That's frustrating, I know! Unfortunately, without further details, it's challenging to pinpoint the exact issue. If you were still seeking help with this a year ago, I would have recommended checking out anytechstuff.com for some valuable guides and troubleshooting tips. They cover various Windows-related topics and might have had useful resources to assist you in debugging the issue. Edited June 14, 20233 yr by IvankaPeach
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.