在VMware 中运行VMware？
我们有一台运行 VMware 的物理机并托管我们用于 SharePoint 部署测试的虚拟机。 那台机器已经很旧了，快要死了，而我雇主的网络沙皇正在大力推动托管虚拟机作为过时物理服务器的替代品。 我很好奇是否可以在 VMware 内部运行 VMware，如果可以，是否会产生严重的性能影响。 我们并不要求此设置具有极高的性能，因为它仅用于 SharePoint 测试，并且关联的 SQL Server 位于不同的机器上。 我的猜测是，我们不能只使用主要托管虚拟机进行测试，因为我们希望偶尔回滚，或者对它有更多的控制权，而网络人员不太可能接受这一点。 有人对这个有经验么？
编辑：我知道这种嵌套当然不是首选选项，但是（1）我们希望能够随意使用 VMware 快照的灵活性，以及（2）网络人员不允许我们任意回滚到之前的点及时，因为可能会删除强制安全更新。 我的猜测是，运行 VMware Workstation 的本地桌面计算机可能是最佳选择。 如果托管选项可行的话，它看起来很有吸引力，因为它对我来说需要处理的机器维护工作较少。
We have a physical machine that runs VMware and hosts a VM we use for SharePoint deployment testing. That machine is old and dying, and my employer's network czars are heavily pushing hosted VMs as a replacement for outdated physical servers. I was curious about whether it's possible to run VMware inside VMware, and if so, whether there are severe performance implications. We don't require extreme performance from this setup, since it's just used for SharePoint testing and the associated SQL Server is on a different box. My guess is that we can't just use the primary hosted VM for our testing because we'll want to roll back occasionally and otherwise have more control over it, and getting buy-in for that from the network folks is unlikely. Does anyone have any experience with this?
edit: I know this nesting certainly isn't the preferred option, but (1) we want the flexibility of being able to use VMware snapshots at will and (2) the network folks will not allow us to arbitrarily roll back to a previous point in time because of the potential for removing mandated security updates. My guess is that a local desktop machine running VMware Workstation might just be the way to go. The hosted option seems attractive if it will work though since it's less machine maintenance for me to deal with.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（14）
在 VMware 内部运行 VMware 的技术限制是 VMware、Virtual PC 等利用虚拟化功能 存在于现代 CPU 中。
如果您有两个或多个虚拟机管理程序都试图控制Ring 0，那么就会出现问题，这是我在尝试在桌面上同时运行 VMware 和 Virtual PC 时遇到的情况 - 其中一个会出错/崩溃。
如果您的虚拟机管理程序可以与“父”虚拟机管理程序交互，那么您就可以了。 或者，如果子虚拟机管理程序不尝试使用 CPU 虚拟化功能，或者完全模拟 CPU（例如 QEMU），那么您也应该没问题。
基本上，旧CPU上的旧式虚拟机管理程序使用完全虚拟化（速度慢），它能够嵌套性能受到严重打击。 现代虚拟机管理程序/CPU 使用硬件辅助虚拟化（接近本机性能），您会很难迫切需要找到一个专为嵌套虚拟机设计或能够嵌套虚拟机的虚拟机管理程序。
最后，我强烈建议不要在运行生产虚拟机的同一台物理服务器上运行开发/测试虚拟机。 有太多的错误和安全隐患 - 您需要管理开发/测试环境，但听起来您不应该访问生产环境。 同样，您可能不希望运营团队扰乱您的测试环境。
更新： ESXi 4 现在支持虚拟化本身。 有关详细信息，请参阅本文
The technical limitation with running VMware inside VMware is that VMware, Virtual PC, etc takes advantage of the Virtualization features present in modern CPUs.
If you have two or more hypervisors are both trying to control Ring 0 then there will be problems, this is something that I've encountered while trying to run both VMware and Virtual PC simultaneously on my desktop - one will error out/crash.
If your hypervisor can interact with the 'parent' hypervisor, then you'll be OK. Alternatively if the child hypervisor doesn't try to use the CPU virtualization features, or entirely emulates the CPU (such as QEMU) then you should also be OK.
Basically old-style hypervisors on old CPUs use Full virtualization (slow) which would be capable of nesting with a heavy, heavy performance hit. modern Hypervisors/CPUs use hardware assisted virtualization (near native performance) and you'd be hard pressed to find a hypervisor that is designed or capable of nested virtual machines.
Finally, I'd really advise against running dev/test VMs on the same physical server that is running production VMs. There's just too much to go wrong and security implications - you need to manage the dev/test environment and it sounds like you shouldn't have access to production environment. Likewise you probably don't want the operations team messing about with your test environment.
UPDATE: ESXi 4 now supports virtualizing itself. See this article for more information
我从来没有在VMware中运行过VMware，但是我在VirtualBox中运行VirtualPC没有任何问题，所以我想没有根本原因它不应该工作......
在我看来，这更像是你的系统不灵活有问题 。 “网络沙皇”比任何技术沙皇都重要。 如果您是开发人员或质量检查人员，您需要一个测试环境，可以在其中使用过时（且可能不安全）版本的操作系统和应用程序，而不会让公司网络的其他部分面临风险。
I've never run VMware in VMware, but I've run VirtualPC inside VirtualBox without problems, so there's no fundamental reason it shouldn't work I suppose...
It sounds to me more like you have a problem with the inflexibility of your "network czars" than any technical one. If you're a developer or QA you need a testing environment where you can fool around with outdated (and potentially insecure) versions of the OS and applications, without putting the rest of the company network at risk.
这里是 VMware 前员工。
首先，当您说 Nested VMware 时，我会假设您指的是 Nested ESXi。 （您也可以指工作站、Fusion 或播放器）。
嵌套 ESXi 环境不受支持，不应用于生产。 这些场景未经 QA 测试，不保证有效。 简而言之，如果您遇到任何类型的问题，VMware 将不会帮助您进行嵌套 ESXi 设置。
话虽如此，是的，你可以做到，而且它确实有效。 许多人在实验室中使用嵌套 ESXi，但不在生产中使用。 以前，嵌套 ESXi 需要进行特殊的配置文件编辑才能正常工作。 我见过甚至有 3 层嵌套 ESXi 服务器的环境（物理 ESXi 主机上的 ESXi 虚拟机和 ESXi 虚拟机）。 最近出现的 ESXi 设备使这变得更加容易。
看看这里：
http://www.virtuallyghetto.com/2015/12/deploying-nested-esxi-is-even-easier-now-with-the-esxi-virtual-appliance.html
Ex-VMware employee here.
Firstly, when you say Nested VMware I will assume you mean Nested ESXi. (You could also mean Workstation, Fusion, or Player).
Nested ESXi environments are unsupported and should not be used for production. These scenarios are not tested in QA and not guaranteed to work. In short, if you experience any kind of problem, VMware will not help you with this Nested ESXi setup.
With that said, yes you can do it and yes it does work. A lot of people use nested ESXi in their labs but not in production. Previously there were special configuration file edits that were necessary for nested ESXi to work. I have seen environments with even 3 layer nested ESXi servers (ESXi vm on and ESXi vm on a physical ESXi host). More recently there is the ESXi appliance which makes this much easier.
Have a look here:
http://www.virtuallyghetto.com/2015/12/deploying-nested-esxi-is-even-easier-now-with-the-esxi-virtual-appliance.html
我遇到了同样的问题。 我在一家大公司工作，我们的整个基础架构都是虚拟的，因此如果您需要服务器，您可以获得 VMware 虚拟机。 因此，我有几个基于 Windows 2003 Server 标准版的来宾 VM，它们具有 6GB 内存和 200GB 磁盘空间，但我想在它们上运行 Linux 和 LAMP 堆栈。 因此，我尝试在一台计算机上安装 VMware Workstation，但收到一条错误消息，指出无法在虚拟机中安装它。 我也尝试过 Microsoft Virtual PC，并收到类似的错误消息。 我安装了 Sun 的 VirtualBox 并且安装得很好，但是我无法让网络在访客 Ubuntu 操作系统。 我的下一步是尝试 QEMU，尽管性能可能会成为一个问题。
I ran into this same problem. I work at a large company where our entire infrastructure is virtual, so if you need a server you get a VMware VM. So I had a couple of Windows 2003 Server Standard Edition based Guest VM's that had 6GB of memory and 200 GB of disk space, but I wanted to run linux and a LAMP stack on them. So I tried to install VMware Workstation on one and I got an error message saying it couldn't be installed within a VM. I also tried Microsoft Virtual PC and got a similar error message. I installed Sun's VirtualBox and that installed fine, but I couldn't get the networking to work w/in the guest Ubuntu OS. My next step is to try QEMU although performance might become an issue.
您应该看看大型机 - 它们从一开始就是虚拟化的：
硬件 - 运行虚拟机管理程序类型 1 - 级别 1
对此，您有 zVM - Type 2 Hypervisor - Level 2
在此你有 zOS - 你的主要大型操作系统 - 第 3 级
和/或
在此你有 zLinux - Level 3
和/或
在此您可以使用 zVM 来测试下一个版本 - 级别 3
和/
在这一点上，您可以在下一个版本中使用 zOS 来测试 zVM 和 zOS - 级别 4
因此，下降到级别 4 是很常见的
请注意，在大型机上，您可以同时运行 1000 个虚拟机 - 大多数开始使用 zVM/CMS 和 zVM/Linux 的站点通常都会这样做。
You ought to have a look at Mainframes - they are Virtualised from the word go:
Hardware - runs Hypervisor Type 1 - Level 1
on this you have zVM - Type 2 Hypervisor - Level 2
on this you have zOS - your main big operating system - Level 3
and/or
on this you have zLinux - Level 3
and/or
on this you have zVM for testing next version - Level 3
and/
on this you have zOS for testing zVM plus zOS both at next version - Level 4
So going down to level 4 is pretty common
Mind you on a Mainframe you can have 1000's of VMs running at the same time - and most sites who start using zVM/CMS and zVM/Linux usually do.
我可以看到两种解决方案（如果将虚拟机算作虚拟机内的虚拟机，则为三种解决方案，这太疯狂了）。
新硬件，应该足够强大，可以处理专门用于测试的多个虚拟机（Sharpoint 等）。 在这种情况下，您的团队可以在不影响非测试虚拟机的情况下获得更多权限。
Sharepoint 测试虚拟机已移至主虚拟机池，需要访问的用户可以检出/部署/回滚测试资源。 这可以直接通过 VMWare 工具或通过 VMWare API 工作的内部项目来实现。
这应该是网络/开发/测试之间的共同决定。
I can see two solutions for this (three if you count a VM inside a VM which is just crazy).
New hardware, which should be robust enough to handle several VM's used specifically for testing (sharpoint, etc.). In this situation your team could be given more rights without affecting non-testing VM's.
Sharepoint test VM's are moved to the main VM pool and those who need access are given the ability to checkout/deploy/rollback testing resources. This could be direct through VMWare tools or through an internal project that works through a VMWare API.
This should be a joint decision between Network/Dev/Testing.
JFYI：
我尝试将 VMware ESXi 服务器主机（子 ESXi 服务器）作为虚拟机（在父 ESXi 服务器上）安装和运行，并且它可以运行，但是您无法在子 ESXi 服务器下运行任何虚拟机。
JFYI:
I tried installing and running VMware ESXi server host(child ESXi server) as a virtual machine(on parent ESXi server) and it runs however you can not run any VMs under child ESXi server.
我正在单个物理机上进行 VMware vSphere 数据中心虚拟化实践。 Windows 8操作系统上安装了VMware Workstation。 在VM Workstation中，我安装了Windows Server 2008操作系统、VMware ESXi操作系统并创建了VMware数据中心实验室。 LAB中有虚拟机在运行，确认我们可以在VMware中使用VMware。 但这取决于您的需求以及选择的产品。
I am doing practice of VMware vSphere Data center virtualization on single Physical machine. There is VMware Workstation installed on Windows 8 OS. In VM Workstation, I have installed Windows Server 2008 OS, VMware ESXi OS and created the VMware Data center LAB. There is VMs running in LAB, and its confirm that We can user VMware in VMware. But it depends on your need, and Products which is chosen.
你可以在VMware Workstation上安装ESXi，学习ESXi很有用，所以没有理由在VMware中运行VMware。
You can install ESXi on VMware Workstation, it's usefull to learn ESXi, so there in no reason run VMware in VMware.
是的。 您可以在VMWare 中运行VMWare。 尽管未得到官方支持，但您可以在子 ESX 中部署虚拟机。 我已经检查了诸如 PassThrough the HBA 卡之类的高级功能，但该功能在子 ESX 中不可用，因此我无法从阵列提供 LUN。
所以在生产中最好不要使用它。
但对于培训和实践来说，可以使用它。
Yes. You can run VMWare inside VMWare. Though its not officially supported, You can deploy VMs in the child ESX. I have checked for an advanced feature like PassThrough the HBA card but which was not available in child ESX, hence I could not provide a LUN from array.
So in production its better to not use this.
But for training and practices this can be used.
你可以这么做。
您可以在另一个 vmware esxi 的虚拟机中安装 vmware esxi。
但性能会很差。
You can do that.
You can install vmware esxi inside virtual machine of another vmware esxi.
But the performance will be very bad.
完全有效..除了某种测试或某种教育目的之外，完全无法做到这一点，因为你不会得到支持。 从我有限的经验来看，它的表现并不是那么好。
Totally works.. totally can't do it other then for some kinda testing or some kind of educational purpose, because you won't get support. and from my limited experience it doesn't perform that well.
是的，您可以，VMware 甚至可以检测它是否在另一台 vmware 机器内运行，并警告您 VMception 会导致性能下降。 相信我，它会尝试让虚拟机在物理机中运行得最好，以获得尽可能多的性能。
Yes, you can, VMware can even detect if it's running inside of another vmware machine and warn you that VMception will cause worse performance. which it will, trust me, just try to get the version the virtual machines work best in a physical machine, as to get as much performance possible.
“是否可以在VMware内部运行VMware”什么？
我可以在托管于某处的 VMWare 计算机中使用 Sharepoint 运行 Windows。
或者，我可以在 WMWare 计算机中运行带有 Sharepoint 的 Windows，该计算机实际上是托管在某处的 VMWare 计算机。
我到底为什么要添加一层嵌套？ 为什么不直接使用在某处托管 Sharepoint 的 Windows？
您可以在单个主机上运行任意数量的 VMWare。 很多不同的版本做很多不同的事情。
嵌套它们没有意义。
"whether it's possible to run VMware inside VMware" What?
I can run Windows with Sharepoint in a VMWare machine that's hosted somewhere.
Or, I can run Windows with Sharepoint in a WMWare machine that's actually a VMWare machine that's hosted somewhere.
Why on earth would I add a level of nesting? Why not just go with Windows with Sharepoint hosted somewhere?
You can have any number of VMWares running on a single host. Lots of different versions doing lots of different things.
Nesting them doesn't make sense.