The Princetons & Harvards may not face the problem, but a lot of non-ivy league schools will. H1B sustains an entire academic ecosystem in the U.S. Any reform of the program should consider this aspect for there are entrenched interests in sustaining the status quo.
1. Get all the drivers from the OEM for the specific model.
2. Get the REAL windows product key (& OEM cert) of your pc. Google is your friend here.
3. Get a Retail windows copy from MSDN or some other legit site.
4. Format the PC, install windows and use slmgr tool to activate it.
5. Now install all the drivers & you are good to go.
No crapware now & it saves me disk space that the OEMs manage to steal in the name of recovery partition.
I have an inkling that Microsoft/OEMs will make the process more onerous going forward but I believe its worth the pain.
I had recently started poking around the lguest hypervisor. From my limited reading I believe 2 of the 3 memory subscription choices mentioned in the article are present in Linux. Existing linux based open source hypervisors like kvm etc use paging/swap mechanism (i,e, for x86 - the paravirt mechanism). Ballooning is possible using the virto_balloon. Kernel shared memory in linux allows dynamic sharing of memory pages between proceses - this probably doesn't apply to virtualization.
I couldn't find any CPU over-subscription thing in open-source hypervisors. It seems to be the only area where open-source hypervisors are lacking.
On an other note, established players like IBM tend to use Type-1 hypervisors (link) for enterprise servers, it would be interesting to see how this company fares against them.