March 11, 2010 - Sven Huisman

VMware View upcoming features

Today I joined the VMware communities podcast. The topic of this podcast was VMware View and John Dodge of VMware was on the phone. I’ve heard some interesting things today, which I think are worth sharing.

  • Win7 support? In the next release.
  • Next minor or next major release? Next release will be a major release.
  • Brand new UI for the View manager, more of an application but still a browser application.
  • When RTO software integration? RTO profiles integration in next release. Other RTO products will be released as seperate products.
  • VMware has been doing a lot of testing with the workload simulator (RAWC, available for VMware partners). Also IOPS testing. Results will be published in a new reference architecture whitepaper.
  • View portal will be replaced -> no more logon, only VMware View Client software download page.
  • Linux guests: not on roadmap yet.
  • When first release on CVP (Client Virtualization Platform)? CVP has gotten a lower priority because, according to VMware, the community wants the offline desktop (a client hosted desktop). There is less demand for the CVP. A lot of the people in the podcast disagreed.
  • Current planning of Offline desktop: production ready in next release.

Just to get some numbers on “offline VDI” and to see if VMware is right not to give CVP a higher priority, here is a quick poll:

[poll id=”3″]

Virtual Desktop VDI / View / VMware /


  • Duncan says:

    I really don’t understand why people would disagree. There are other things that just have a higher priority like for instance fully supported offline mode (check in / check out).

    It just makes me wonder how in touch with the real world those people are. Do you see a lot of need for CVP yourself at this point in time? I think VDI is just barely touching ground at the moment. I would say stabilize, and expand slowly but steadily.

    • Sven Huisman says:

      I think we both agree there is a use case for offline VDI. One way to achieve this is by the use of a client hosted hypervisor, where you would need an OS like Windows XP or Windows 7 to host the offline virtual desktop. Local resources will be used, so the user doesn’t have the disadvantages of the remote display protocol and the user is able to work at locations where he is unable to connect to the datacenter. One big disadvantage in this case is that the hosting OS still needs to be managed, updated, licensed, virusprotection, all in the “traditional” way.
      The other way is “bare-metal” client hypervisor, where you don’t need a “traditional” OS to be able to run the offline virtual desktop, and where the management of the client hypervisor will be as “easy” as managing a thin client. AND you have the advantage of “direct” access to the hardware, with more performance (graphics) for the applications.
      In an ideal world, I think a company has only one desktop image to manage, and that image will be used by users on thin clients (remote) and on fat hypervisor clients (local).
      I agree with you, real world examples are more complex than that. On the other hand, I won’t mind waiting for CVP if VMware releases it as fully supported from the beginning. The Offline-vDI feature in View is experimental for a while now, which is OK if you want to play with it, but not for production environments.

  • Louw Pretorius says:

    VMware View is currently pushed in smaller environments by enthusiasts, hence the need for CVP and its another feather in the cap of whoever can get it “out-there” as the Leader in the VDI field.

  • CVP is indeed essential!!