![]() ![]() Number Start End Size File system Name Flagsġ 1049kB 473MB 472MB ntfs Basic data partition hidden, diagĢ 473MB 790MB 317MB fat32 EFI system partition boot, espģ 790MB 119GB 118GB ntfs Basic data partition msftdata *edit: Getting inconsistent results, so I don't think this is actually working for me.Sector size (logical/physical): 512B/512B This has worked for me, the VM is rebooting without issues now. If it doesn't boot, shutdown the vm, compress 1a8fdacb-aad4-4bbb-71ea-732b0ea1051a_VARS-pure-efi-tpm.fd and share it hereīefore shutting down the vm check if you have the double entry 'Windows boot manager' Once done, modify the vm template, deleting and adding to the nvme block (let's try the traditional way first). Rename the extracted files to OVMF_CODE-pure-efi-tpm.fd and 1a8fdacb-aad4-4bbb-71ea-732b0ea1051a_VARS-pure-efi-tpm.fd ![]() usr/share/qemu/ovmf-圆4/OVMF_CODE-pure-efi-tpm.fd Just decompress the zip, backup your original files: Why do I have two windows boot managers, why can't I delete them, why can I boot fine directly from my NVMe when I am in the OVFM BIOS and launch there, why can't I use boot order in my xml and boot more than once? Here is my entire current xml that boots: I have to go back to the xml, remove boot order and restore boot dev=hd. ![]() But as stated, once I shutdown Windows and reboot I will only get the first "Windows Boot Manager," OVFM will not respond to esc, and it just freezes there. On my first boot with an xml containing I get the exact same above screen and can enter the OVFM Bios with esc. However, every time I go back into the OVFM BIOS all the boot options are back as if I never deleted or reordered them □. I have tried removing the TWO windows boot managers that are in there and put the NVMe as the first boot device and saved (I've done this like 20 times). I can also press esc and enter the OVMF BIOS. If I shut down or restart Windows, OVMF will freeze and I cannot boot again until I go back, edit the xml to remove the boot order line, and restore the ?!? ![]() Only on the first boot after doing this will OVMF finish loading and boot Windows 11. When I do that, there is no line generated by the template. I have assigned the NVMe to boot order 1 which adds the line for boot order in the xml file I have completely removed the VM (not the VM and disk, just the VM) and started over. hvm /usr/share/qemu/ovmf-圆4/OVMF_CODE-pure-efi-tpm.fd /etc/libvirt/qemu/nvram/1a8fdacb-aad4-4bbb-71ea-732b0ea1051a_VARS-pure-efi-tpm.fd With this line in my xml file the VM will boot properly every time, the key line being With the release of unRAID 6.11.2 and 6.11.3 I have encountered the problem all over again. This is the thread where I sort of sorted it out or at least got my VM working again: However, after I did that I could no longer get my Windows 11 VM to boot properly or consistently. I then upgraded to Windows 11 and eliminated the need for spaces_win_clover.img (I think it was not compatible with Windows 11 or maybe I just didn't want to use it anymore because it was no longer needed in unRAID). Originally I had a Windows 10 VM setup to run on my NVMe bare-metal using spaces_win_clover.img. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |