Edit with solution: I'm dumb. Just use the default quickemu settings and only change "-device virtio-gpu-gl " to "-device virtio-gpu " and "-display sdl,gl=on " to "-display sdl,gl=off ". Although qemu will have a lot of overhead at boot, the CPU usage when on the desktop should not eat your linux host's entire core. I also disabled Windows Defender, which I don't recommend if you run random stuff from the internet (or open .xlsm spreadsheets), but it helps. I ran CTT's windows debloat tool and removed edge because it was updating in the background for some reason. Even then Windows is still a last resort kind of machine when my desktop isn't available, not an actual work OS.
Edit with solution 2: The above still sucks compared to using RDP. Use the above to set up Windows Remote Desktop, then use for example Gnome Connections to RDP into it. I had to forward the RDP port to the Windows VM for it to work.
I changed the line
-netdev user,hostname=Quickemu,hostfwd=tcp::22220-:22,id=nic \
to
-netdev user,hostname=RDPWindows,hostfwd=tcp::22220-:22,hostfwd=tcp::3389-:3389,id=nic \
Then I just connected to 127.0.0.1 from Gnome Connections
=======ORIGINAL POST:
Hi, I have trouble running Windows 10 in QEMU on an old af thinkpad x200t. The issue is that it that my GPU only supports opengl 2.0, so virtio does not work. The best I could do is use these options:
-vga qxl \
-device virtio-gpu \
-display sdl,gl=off
and like 30 more which are part of the default quickemu configuration. The three mentioned are ones I changed.
With these options QEMU uses "just" 85% of my CPU so I can still do something on the linux host. The issue is that Windows is basically unusable because the one core it has is constantly occupied by rendering graphics even when just idle on the desktop.
At this point I have accepted my faith that this laptop ain't usable for Windows virtualization but I thought that I would ask here before closing this case. So does anyone have a secret hack which makes pre core i series intel GPUs work with Windows guests in QEMU?
thanks for any tips
It sounded like you got annoyed that I was guessing and it sounded like you tried to make it clear to me that the guess was not helpful to you with the use of sarcasm. I guess I misunderstood, sorry.
Regarding the actual questions: You asked how does it compare to Coreboot. Canoeboot is actually coreboot, just slightly modified to work with Free Software Foundation's rules but these rules are kind of absurd. See [1]. Libreboot is also modified Coreboot but one that's actually good. The difference between them is that Libreboot should be a bit easier to install and that they support different hardware.
In terms of battery life the same laptop with or without Coreboot should perform the same. Coreboot really only handles the booting. Battery life should depend on the "EC firmware", which is like a second chip on your motherboard that handles stuff like blinking LEDs or checking if your lid is opened or closed. It also depends on the OS itself so Linux vs Windows will make a difference. Canoeboot is an exception because it does not include "microcode updates" for ideological reasons. Microcode is code that runs on a "CPU inside of your CPU". Not updating it will A) make your CPU buggy and vulnerable to attacks like Spectre [2] and B) maybe even have worse battery life because Microcode can control the voltage your CPU runs at. More voltage -> more power (P ~ V^2)
[1] https://libreboot.org/news/policy.html
[2] https://en.wikipedia.org/wiki/Spectre_(security_vulnerability)