hi just passing by (am new to qspice, my apportation might help in a way that it fixed my ultra poor proteus simulation success rate, i wasnt able to simulate a lm317 with a variable resistor or even analog leds since it droped random spice errors… until now, now i can run it like i did run it on windows 98 and if the year were 2004.. flawless.)
from archlinux i did got snippets of my current qemu vm where i emulate a windows 10 (nope, i dont need keys, i am an old legend i guess… my legacy is gonna be: "he stop using keys bc he was too lazy to write and keep them in a safe place, and too esquizho he did chattr -i && rm -fr to this kind of files: ./DO_NOT_DELETE_FILES_HERE/win.key.dont.delete.me.plz just moments before needing them for the first time in months or even years… but lets go further:
not activated, running with penalties derived from windows protective licence environment… so its a non friendly environment, right? yeap… but it is not the problem, software must run ok here, as well as in correct windows instalations as well…
i explain: it checks if qemu with window identifiable as that win 10 w proteus is running… if so, abort… else lets run it… it uses a layer after a main setup where it derivates into its own disk and sistem version separated from others.. like in vmware u had the snapshots… well its a snapshot Win10.64.sh.4.qcow2 the rest of the line: try and fix or change and see… well with this line properly setup (i7 + 16gb ram sata hdd if u had that i guess u practically have what i do have on my system)
if u run it and the os behaves as a pretty cute windows 10 without no lag/slow/errors/ugliness, nor qemu tells u it droped or failed doing something… well… i am 99% sure u will run proteus complex stuff without any trouble… and since i was able to run the spice from n.i. even when proteus was unbeareable.. i think qspice would run like a pretty charmin toilet paper in the comfortable wide space of ur display screen *(u know like a bear in the boshes, but this is a charmin bear, it doesnt drop gifts for u =) )
##This:
ps aux|grep -v grep|grep “Windows 10 With Proteus” && (echo “Running!!!” && exit 0) || (echo “Not Running!!!” && /usr/bin/qemu-system-x86_64 -machine type=q35,accel=kvm,kernel-irqchip=split -device intel-iommu -smp 4 -m 8192 -action shutdown=poweroff -action panic=shutdown -action watchdog=shutdown -drive id=disk0,file=/home/usrnameforgottorm/VMs/Win10.64.sh.4.qcow2,if=none -device ahci,id=ahci0 -device ide-hd,drive=disk0,bus=ahci0.0 -cdrom /dev/null -boot once=c,menu=on -display gtk,gl=es,show-menubar=on,window-close=off -device virtio-gpu -vga virtio -nic none -usbdevice tablet -name “Windows 10 With Proteus” ) &
##isthewaytodo.
PS: i was supposed to run gpu server to provide gpu emulation slices into qemu, but i am kinda adhd or well u know… so i never did that part, i thnk my asus efi with mostly all default setings dont add any level of complexity/incompatibility… so… simply run the " -display gtk,gl=es,show-menubar=on,window-close=off -device virtio-gpu -vga virtio " in a linux where u did the steps to have a vga virtio, a virtio-gpu and gtk gui which can handle gl=es and that is… the computer has intel-nonfree drivers for the gpu (intel’s gpus inside the processor device unit) and… yea.. well hope that craft cmd line help somebody who uses qemu to achieve good old display experiences like the ones that vmware workstation used to give… long long time ago.
cheers.
PS: am kinda bussy right now but… dont forget to use this in ur kernel’s boot arguments:
i915.modeset=1 i915.enable_psr=0 kvm.ignore_msrs=1 i915.enable_fbc=0 i915.fastboot=1 i915.enable_guc=0 i915.enable_gvt=1 intel_iommu=on iommu=soft
in my computr, guc=2 (or was 3?) did provided weird good speed accelerations but not really the ones that one would love, also most of the time guc!=0 makes kernel taint or panik at boot so.. well, guc=0 is safe, simpler and makes this qemu thing behave pretty great.
if u have questions or if i forgot something dont worry, just ask or tell, also note i am kinda sleeping and my keyboard is in its last terminal state… so, sorry for the misspelings.
Cheers.
Adolf - Engineer