I am rebuilding my TW OS and have lost all the vm image files. I have the VM set up and Network connections correct but I am struggling to get past the booting of the VM because I have a dual boot setup on the machine and forget how to get past this.
I cannot find the link to the guide so if some kind soul could remind me it would be much appreciated please.
Budgie2
For example, when I am using the windows 10 settings>system page I want to change the screen resolution to give me a better fit with my screen but the option to change this is greyed out. How can I get this to work so I can select the resolution from options?
I now know I am getting senile as I remember once reminded by you and recognise what I did earlier but have absolutely no recollection of the detail. I have installed the virtio-driver and have it at /usr/share/virtio-win/virtio-win.iso but then I am lost. The instructions I am trying to follow are different from what I find on my machine. I need an idiots guide please and forgive me if I am repeating myself!
@Budgie2 In the VM settings add the iso image as another CDROM device so it’s seen in Windows.
Then in the Windows Device Manager right click on the video adapter, properties and upgrade the driver. In the next settings select custom(?) then select the CDROM (D: or E: drive) and make sure the box is check to browse sub directories and it should find and add…
Hi Malcolm,
Thanks for the reminder but…
I have Red Hat QXL controller shown in my system but with an exclamation mark on the driver concerning lack of digital signature. Bottom line is that I cannot change my display resolution. How do I sort this please?
Further questions. When I start the VM on my Leap 15.6 machine I have a prompt for root pw. I do not get this on the new TW build. Is this related to certification/authorities?
I recall that once the vm has been built the real downloaded files, ie Win 10 iso and Virtio-driver iso and cd-rom devices can be removed from machine build details. Is that correct?
But try as I might I couldn’t save the revised file. I therefore rebuilt the win10 VM from the start but avoid the signed virtio-driver I had to ensure the windows system started in insecure mode and the only way I found to be able to do this was when building, Under Firmware, select UEFI x86_64: /usr/share/qemu/ovmf-x86_64-smm-code.bin.
NOT a Secure Boot firmware (e.g., /usr/share/qemu/ovmf-x86_64-smm-ms-code.bin).
That enabled me to boot win10 with no secure boot.
I had forgotten what I had done and suspect that I was just lucky last time and selected the “wrong” firmware so I have posted this for ignorant souls like me.