alturismo Posted December 17, 2017 Share Posted December 17, 2017 hi, just wanted to ask if thats possible, switched from Intel GPU to Nvidia and have some issues now, and as my my other VM running the nvidia was OVMF i guess it could help ... i think i saw a guide howto do that, but cant find it anymore ... may someone has a tip ? its my main VM and setting all new up would be a pain ... should be last solution if possible Link to comment
alturismo Posted December 18, 2017 Author Share Posted December 18, 2017 ok, figured a solution for me, just in case someone else needs an tip 1st, make a backup of your vdisk file ... just in case in windows 10 (1703+) there a new tool added, mbr2gpt so, i used powershell in admin mode mbr2gpt /validate /allowFullOS <-- if ok then mbr2gpt /convert /disk:0 /allowFullOS now your win10 VM disk is prepared for EFI boot,.shut the VM down. create a new win10 VM with your same settings (exept use OVMF instead seabios), pointing to your existing and edited vdisk1.img (or whatever name it has). That was it ... enjoy when all is good your can remove your backup from your vdisk .. Link to comment
Joseph Posted February 6, 2018 Share Posted February 6, 2018 On 12/18/2017 at 11:32 AM, alturismo said: mbr2gpt /validate /allowFullOS <-- if ok then Hi alturismo, I'd like to do the same thing... however I got these results: mbr2gpt : The term 'mbr2gpt' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1 + mbr2gpt /validate /allowFullOS + ~~~~~~~ + CategoryInfo : ObjectNotFound: (mbr2gpt:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException Any thoughts much appreciated. Link to comment
Joseph Posted February 6, 2018 Share Posted February 6, 2018 6 hours ago, Joseph said: Any thoughts much appreciated. Nevermind... updating to 1709 UPDATE: The VM Updated, but now it won't boot. QEMU shows the UEFI shell and then exits to a Shell> prompt. Unless there's a simple fix, I'm thinking its just going to be easier to reinstall Win10 from scratch with the OVMF settings in the VM config. Link to comment
alturismo Posted February 7, 2018 Author Share Posted February 7, 2018 What happens when you exit the shell ?Gesendet von meinem SM-G950F mit Tapatalk Link to comment
Joseph Posted February 7, 2018 Share Posted February 7, 2018 7 hours ago, alturismo said: What happens when you exit the shell ? Gesendet von meinem SM-G950F mit Tapatalk Got it figured out. For some reason you have to go into the bios and change the boot order. Seems to me the VM should do that automatically. Link to comment
alturismo Posted February 8, 2018 Author Share Posted February 8, 2018 ok, i had this too when i was changing the existing VM xml instead creating a new VM setup pointing to the existing img. Nice you got it working. Link to comment
Rudder2 Posted December 6, 2018 Share Posted December 6, 2018 On 12/18/2017 at 11:32 AM, alturismo said: ok, figured a solution for me, just in case someone else needs an tip 1st, make a backup of your vdisk file ... just in case in windows 10 (1703+) there a new tool added, mbr2gpt so, i used powershell in admin mode mbr2gpt /validate /allowFullOS <-- if ok then mbr2gpt /convert /disk:0 /allowFullOS now your win10 VM disk is prepared for EFI boot,.shut the VM down. create a new win10 VM with your same settings (exept use OVMF instead seabios), pointing to your existing and edited vdisk1.img (or whatever name it has). That was it ... enjoy when all is good your can remove your backup from your vdisk .. You are the man! It still works perfectly!! Link to comment
alturismo Posted December 6, 2018 Author Share Posted December 6, 2018 Thank youGesendet von meinem SM-G950F mit Tapatalk Link to comment
administrator Posted January 21, 2019 Share Posted January 21, 2019 On 12/18/2017 at 12:32 PM, alturismo said: ok, figured a solution for me, just in case someone else needs an tip 1st, make a backup of your vdisk file ... just in case in windows 10 (1703+) there a new tool added, mbr2gpt so, i used powershell in admin mode mbr2gpt /validate /allowFullOS <-- if ok then mbr2gpt /convert /disk:0 /allowFullOS now your win10 VM disk is prepared for EFI boot,.shut the VM down. create a new win10 VM with your same settings (exept use OVMF instead seabios), pointing to your existing and edited vdisk1.img (or whatever name it has). That was it ... enjoy when all is good your can remove your backup from your vdisk .. Thanks for this information. Helped out a lot. Link to comment
alturismo Posted January 21, 2019 Author Share Posted January 21, 2019 3 hours ago, administrator said: Thanks for this information. Helped out a lot. u welcome Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.