VMWare Linux anti-patterns. How VMware is kind of neglecting the Linux experience
I like VMware stuff a lot, and write about them regularly, usually in a positive way, so I write this list of VMware Linux anti-patterns with only good intentions.
Lately I've been feeling a bit bummed by VMware's deprecated Linux experience, and Windows-centric mentality. If VMware gets too Windows-centric, it'll only be competing with Microsoft. I
want VMware to do well against Microsoft! And I believe that to do so, it needs to deliver an experience that doesn't marginalaize Linux users.
Here's how VMWare can improve the Linux experience:
- Improve the vmware-tools install on Linux guests. (All VMware products, all host OS's)
On a Windows guest, you run a binary (by clicking it!), and you're done. On the Linux side, you run a binary (most likely via command-line), and then visually, you'd think you were done. but you're not. You installed it, now you configure it. Seriously, whenever I train or help users with this part, I feel guilty/embarrassed about how idiosyncratic it feels. The output of the rpm/install script never tells you "now you configure it." Sure the docs do. But on Windows you don't have to do all that. VMware, I won't hold you responsible for the command-line parts, that's (mostly) in Linux's hands. But you could longterm do away with the configure, and short-term, announce at the end of the install that, "Now it's time to configure."
- Make a Virtual Infrastructure client for Linux.
You made one for Windows. I think you love Windows more than you love Linux. (And yes, I am aware of the web client. I'll pretend you didn't suggest that.)
- VMware Converter is way more difficult with Linux than Windows.
- The VMware Converter program itself only runs on Windows
- Converting Linux physical-to-virtual VM's is a more burdensome process for Linux guests, with more rules and hoops than Windows guests have.
- I feel like you're slowly taking away ssh/ "service console"/ file system access to your ESX-based products. You've only done this to 3i so far. And there is a workaround. But the vibe I get (I hope I'm wrong) is that you're trying to wean us off of standards communications and file-system access to this stuff.
- Give VMWare Server 2.0 a Linux client.
I know you took away the non-web client from both Windows and Linux, but since Windows people can use the new VI client to access VMWare Server, I'm still counting this as a ding against Linux users.
Real talk.
Labels: linux, virtual infrastructure, virtualization, vmware, vmware converter, wishlist
