4 ms·

from the github wiki: Rough VM size estimates: IE7: 13GB IE8: 8.4GB IE9: 13GB Currently, the script will leave the compressed RAR files in place, which means

from the github wiki: Rough VM size estimates: IE7: 13GB IE8: 8.4GB IE9: 13GB Currently, the script will leave the compressed RAR files in place, which means you're looking at something like 45 freaking GB if you don't prune them manually (in ~/.ievms/vhd/). This wasn't a big deal for me on my company workstation, but kinda sucks on my Macbook Air, so I'll be adding a cleanup option shortly. You probably don't need to keep the compressed files around anyway since we take a snapshot like you mentioned.

aninteger 15y ago
I know you aren't the creator of those VMs but, any idea why they are so big? What's weird is that there's a jump from 8.4 GB to 13 GB on Windows 7. What is on the IE9 vhd that isn't on the IE8 vhd? Edit: Nevermind, from the official link the IE9 vm comes with additional tools.
- pointyhat 15y ago
  On Win7, the jump is due to WinSxS. Every DLL several times and several versions. DLL hell solved.
  - MarkSweep 15y ago
    DLL hell solved indeed. How many versions do you keep? For what it's worth, the DLLs in System32 are projected out of WinSxS with hardlinks, so they should not take up extra space. You still have the multiple version thing, however that can be somewhat mitigated by making service packs permanent[1]. [1] http://blogs.technet.com/b/joscon/archive/2011/02/15/how-to-reclaim-space-after-applying-service-pack-1.aspx http://blogs.technet.com/b/joscon/archive/2011/02/15/how-to-...
    - pointyhat 15y ago
      That quantity of hard links takes up quite a bit of space though!