Virtualization, in general, is a popular topic these days. It lets a single computer do more things more flexibly than running a single OS on a single piece of hardware. However, it has its downsides. Virtualization, as the name implies, is a software system that allows one piece of hardware or operating system pretend that it is a different piece of hardware or operating system. It’s a translation layer. It’s akin to (but simpler than) bi-directional automatic human language translation.
We all know Rhino makes heavy use of OpenGL. And our plan when we started revamping the OpenGL subsystem for Rhino 6 was to fully support virtualization. As we got further along in the process, it became clear that the translation layers for OpenGL just weren’t very good. VMWare does a pretty decent job; Parallels is pretty bad. OpenGL 4 was released in 2010. Parallels supports OpenGL 2 from 2006; VMWare supports OpenGL 3.3 from 2010. Rhino also doesn’t run on Windows 95 or XP because those old platforms don’t do what people expect from computers these days.
I guess it depends on what you mean by “supported”. Is it OK for Rhino to only show Wireframe? What about basic shaded mode? Rendered? Textures? Decals? Shadows? Arctic? Artistic?
At some point, various parts of those no longer work. It seems cumbersome to “partially support” something; it’s easier to say we don’t support it. Of course, Rhino still runs - so people can try it and see if they can get their work done. I’ll leave it as an exercise for the reader to create a detailed list of what works and what doesn’t for their specific platform, virtualization environment, and driver.
Virtualization wasn’t supported in V5, either. It worked OK, sometimes, because Rhino used a much older version of OpenGL. But people complained a lot about it even then. And V5 still runs - people who want to use it still can.