If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
The release is not identical to the RC, but it only differs by a few commits.
We removed DKMS support because it is not supported everywhere. We were already providing nearly the same functionality where it is not supported, and decided there are really better ways we can use our limited developer time than maintaining two kernel module build solutions, and we got quite a few bug reports which turned out to be because DKMS had got confused and stopped working. I don't really care whether it was their fault (if it is maintained at all) or ours, but it was a time drain. DKMS relies on a hook mechanism to be notified when an new kernel is installed so that it can rebuild its modules. We added hooks too, so this should still work. Obviously anything which worked before and does not now is a regression, and merits a bug report if you can reproduce it. If it is not important enough for you to reproduce of course then it may not be important enough to be worth investigating.
I understand that 3D is an important area for Phoronix readers, but it is not likely to get dramatically better (especially in X11 guests<1>) in the near future. Sorry.
I am not one of the core virtualisation performance people on the team, but it might still be worth mentioning, other than 3D, any particular and specific performance pain points. Perhaps as particular use cases (or perhaps not).
And other than that, I hope that many people enjoy the new release!
it might still be worth mentioning, other than 3D, any particular and specific performance pain points. Perhaps as particular use cases (or perhaps not).
I know that it's probably asking for a pony, but... what happened to VGA/PCIe passthrough? It's experimental since forever.
Also, another very nice pony I ask you to provide me asap is the passthrough of BIOS/UEFI IDs and keys and whatever else is needed that should THEORETICALLY allow me to run a legit windows inside a VM running in a Linux host on a PC with a windows OEM license.
I tried this some time ago but was like black magic and didn't work.
Also, another very nice pony I ask you to provide me asap is the passthrough of BIOS/UEFI IDs and keys and whatever else is needed that should THEORETICALLY allow me to run a legit windows inside a VM running in a Linux host on a PC with a windows OEM license.
I tried this some time ago but was like black magic and didn't work.
Not even sure exactly what Windows needs there. What we have on offer:
We haven't had much demand for more (any that I can recall in fact), but feel free to investigate what is needed. I can't promise or even say it is likely that we will do anything with the results, but if no one investigates it is extremely likely that nothing will happen.
I don't see where to specify SLP or SLIC (ACPI), there are tools to extract that like SLIC toolkit. SLIC 2.0 (Vista) and SLIC 2.1 (7) are not used anymore with 8+, there the used serial is stored in the firmware. Up to XP the SLP variant was used, basically just a string at a defined position. For Vista/7 you need to install the correct cert and an OEM key (both are extracted with the toolkit), funnly the OEM keys are exchangable between vendors and as the version was never defined in the vendor SLIC you could use those keys for "Anytime Upgrade" to switch from Starter to Ultimate on the cheapest netbooks too
Comment