关于如何使用 Hyper-V 上的 Windows 2008 R2 服务器节省空间的想法？
这个问题我很久以前就有了，但仍然困扰着我。
我使用一些运行 Windows 2008 服务器的虚拟机，其中大部分是演示虚拟机和测试机。由于大多数开发人员都使用它们，因此我不喜欢到处进行单独的设置，而是维护导出的虚拟机和硬盘驱动器映像的目录。
由于并行程序集和 Windows 更新，每个服务器在并行文件夹 (winsxs) 和 Windows 更新中会产生大约 6 - 12 Gig 的开销。
假设我有 50 个导出的虚拟机（及其映像），每个虚拟机都有大约 3 G 的有效负载数据（操作系统、程序、数据）和大约 12 G 的共享开销，所有这些虚拟机的开销基本相同。然后我浪费了 2/3 的存储空间（总共约 600 Gig），更不用说当开发人员想要下载新的 VM 快照时在网络上推送这些冗余数据的网络开销。
所以我正在考虑一种跨多个VMS整合winsxs文件夹的方法。理想情况下，我想提出一些共享驱动器之类的东西。我什至愿意为此指定一个物理设备。
我意识到 Windows 服务器有最低要求，并且无法删除这些文件 (http://social.technet.microsoft.com/Forums/en-US/itprovistasetup/thread/9411dbaa-69ac-43a1-8915-749670cec8c3）。
我还在 移动winsxs文件夹，但它似乎不是一个可靠的解决方案。
这听起来可行吗？跨虚拟机整合资源的最佳实践是什么？
感谢全能的 stackoverflow 专家的及时关注；-)
I've got this question awhile ago, but it still bothers me.
I work with a few virtual machines running Windows 2008 server, mostly demo VMs and test machines. Since most devs use them, I prefer to not have individual setups here and there and maintain a catalog of exported VMs and hard drive images instead.
Thanks to side-by-side assemblies and windows updates each server carries an overhead of about 6 - 12 Gigs in side-by-side folder (winsxs) and windows update.
Suppose I have 50 exported VMs (with their images), each has about 3 Gigs of payload data (OS, programs, data) and about 12 Gigs of shared overhead, which is mostly the same for all these VMs. Then I waste 2/3 of my storage space (about 600 Gigs total), not to mention network overhead of pushing this redundant data around the network when a dev wants to download a new VM snapshot.
So I am thinking of a way of consolidating the winsxs folder accross multiple VMS. Ideally, I'd like to come up with some shared drive or something. I am even willing to designate a physical device for this.
I realize that Windows server has minimum requirements and these files cannot be deleted (http://social.technet.microsoft.com/Forums/en-US/itprovistasetup/thread/9411dbaa-69ac-43a1-8915-749670cec8c3).
I also found a post on moving winsxs folder, but it does not appear as a reliable solution.
Does this sound even remotely feasible? What are the best practices for consolidating resources across VMs?
Thank you almighty stackoverflow gurus for your prompt attention ;-)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
不要触摸 WinSXS 文件夹。
它并不像看起来那么大（其中很多是指向重复文件的硬链接）
如果您想拥有整合的空间，请使用差异磁盘 - 创建一个带有 Windows 的虚拟机，然后使用该磁盘作为其余磁盘的基础。每个磁盘仅存储原始磁盘与虚拟机之后所在位置之间的增量。
无法跨安装共享 WinSxS 文件夹。
如果您想了解有关 WinSxS 工作原理的更多信息，请查看我的博客文章：http://fearthecowboy.com/post/CoApp-FAQ-Can-you-explain-how-Side-by-side-%28WinSxS%29-works .aspx
Don't touch the WinSXS folder.
It's not as big as it looks (alot of it is hard links to duplicate files)
If you wanted to have consolidated space, use differencing disks--create one VM with Windows on it, and then use that disk as the basis for the rest. Each disk will only store the delta between the original and where that VM goes after that.
It is not possible to share WinSxS folders across installations.
If you want to know more about how WinSxS works, check out my blog post: http://fearthecowboy.com/post/CoApp-FAQ-Can-you-explain-how-Side-by-side-%28WinSxS%29-works.aspx