1. 6

  2. 2

    The fact that doing so will prevent you from running Virtualbox or the like I can see as a big problem for developers. I can’t think of any developer I know that doesn’t have some kind of virtualization running on their workstations. I can see the don’t put this evil on me please IT conversations.

    Does anybody know if with Hyper-V you can run any kind of generic virtual machines? Noooo idea how it works.

    1. 1

      Hyper-V works like Xen more than anything else. The host OS is actually a privileged VM.

      The big problem with client Hyper-V quite frankly, is that it sucks. Poor OS compatibility, and you need to use RDP in a VM to gain basic stuff like sound, or just decent GUI performance.

      1. 1

        But, I doubt they’d cripple Edge like that, right? So, presumably they have some new tricks for Hyper-V that will make the experience better?

        1. 1

          In this case, you’re not dealing with any of Hyper-V’s suck - that is, the whole experience with the paravirtual devices on the console. VT-d being a requirement also probably involves some voodoo to make it blend in.

          It’s worth noting LSASS got moved into a separate VM when possible on Windows 10 as well.

          1. 2

            Yeah, the article mentions that Windows 10 is Qubes like in some ways. But, I wonder how they do the rendering for these apps, and whether or not it’s exposed in a way that you could start a Linux VM, and show X11 in a window. If so, maybe that’d solve the poor GUI performance that you speak of?

            Also, this is kind of a perfect example of why X11 is great.. Being able to send graphics/interactions over a socket to be displayed seems like a much bigger win than effectively taking screenshots of the rendered screen like RDP / VNC. On a Linux machine, with Docker, I could effectively do the same thing being done with Edge by just exposing my X11 unix socket to each container that wants to display something. More info here.

            1. 1

              Windows has RemoteApp and RemoteFX, but I wonder with VT-d being involved, it might be using something different instead, with lower overhead.

              The big problem with X11 forwarding is that it won’t forward 3D acceleration, sound, or printing. RDP (with RemoteFX) can do this.

      2. 1

        You can nest hypervisors, so I’m not sure this is a problem in practice.

        1. 1

          Hypervision (is that a word?) in general can be nested, but “Type-1” or “bare-metal” hypervisors typically don’t like to coexist with other hypervisors.

          You can run Virtualbox and VMware Workstation next to each other (both Type-2, the app kind), but you cannot run Virtualbox under Xen.

          1. 1

            Inability to nest just means the virtualization is incomplete. VMWare can virtualize/emulate VT-x, running “bare metal” hypervisors inside. Hyper-V cheats in some way to allow itself to nest, but doesn’t provide access to VT to the VM. I might classify that as a bug, or at least a missing feature.

            1. 1

              VMWare can virtualize/emulate VT-x, running “bare metal” hypervisors inside.

              Case in point: This is how you’re supposed to test ESXi - you’re running VMware inside VMware, quite possibly to further nest turtles.