Yes, I have not noticed any negative effects after making the change, I don’t think it prevents the service from being started if needed. I also don’t think the service is really used in Qubes OS, but I could be wrong.
It allows for non-native binary formats to be executed, e.g. if you mount a windows drive and tries to execute a .exe file it would be able to map the format to wine, if it’s installed, and it can do the same with emulators and such, but it probably also has other uses.
Hi @renehoj,
I noticed that you replaced your previous entry for your i9-13900k with 9950X. Just FYI, there’s no limit on how many entries a person can have, and it’s always helpful to have more data points.
Added the old entry back in the table, I removed it to make the list shorter, I can see why it makes sense to keep it.
The 2.9 is with my new PCIe 5.0 x4 drive, 14500 MB/s reads.
I was playing around with booting the template from a ram drive, it’s possible to get 2 sec boot time when booting template from memory, but it’s not very consistent.
I was considering using it for DVMs, the faster boot time would be nice, and it would also make them truly disposable.
Have you tried 4k sector size that @51lieal and @augsch used to push down their times even further? My gut feeling is you might get to 2.5 or less on your monster rig.
Also, is it possible to store a booted DVM-template in memory and just copy it whenever a DVM is needed? Is that what you were trying?
Came across an article on RPi boot optimization and had a thought–is it possible to specialize Linux VM’s boot procedure to its task? E.g. Optimized boots for sys-net, sys-firewall, etc.