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.
Some VMware Server 2.0 Beta screenshots
...wanted to upload a couple of screenshots from VMware Server 2.0. As I mentioned yesterday, VMware Server 2.0 beta update 1 only has a web-gui. As you can see below, in a "read-only" way, this doesn't interfere too much. When you actually start to interact with the page, it gets a little more annoying, and you can feel the chug of the thinking and the rendering. I'll repeat that I appreciate that it isn't a draining Java applet doing all of this on the client side. But it's still pretty slow and painful. Aside from performance, the interface and navigation is inconsistent and confusing. I'll try to post about that tomorrow.
Now below you can see the web-ui get even more inconvenient when you want "console." By default, when you select a console view of a guest, you get only a partial view of it, ensconced in scrolly bars. You do have a fullscreen option, but nothing in between, let alone the "fit to screen" option available in the VMWare Server 1.x console client.
1 night with VMware Server 2.0 beta: It sure is web-based.
VMware Server 2.0 beta came out today, and I've had a couple of hours to play with it tonight. As suggested at VMworld, this is a really different product from VMware Server 1.x. Some changes good, some bad. I don't have the same opinion that virtualization.info, that VMware Server is becoming a less relevant product, but I do agree that there's something lackluster here.
VMware Server 1.x felt whole, right off the bat. With VMware Server 2.0, I have this "well, this is just the beta, surely there will be radical improvements" vibe.
While there are a million good and bad features here, what will save us both a lot of time is for you to know that as of now, VMware Server 2.x administration is totally web-based, and that is almost all you can think about or notice when you're working with this tool. I will give to credit to VMware, they've enabled a lot of functionality (rebooting, creating VM's, etc) on a web-client that somehow doesn't involve a giant, slow Java applet. That said, there are many situations when you feel the web pain. The web page has to "think" and rebuild itself a lot. Console access requires a plugin in your browser (which kinda kills the whole "all-you-need-is-a-web-browser" spirit). People in the forums are missing the fit-to-screen feature you got with the "regular" console in VMware Server 1.x, as am I.
VMware is taking a big risk here. The next version of the (regular) VI client will be able to manage VMware Server guests, somewhat softening the blow of not otherwise having one. But this will only help people who have the (not free) VI. I see the "strategy" here... entice VMware Server users to jump up to VI. However I don't believe it will work, and will actually turn people off of VMware.
Despite supporting more OS's and architectures, I feel VMware Server 2.0 is "less" of a product than VMware Server 1.x.
First post-Leopard VMware Fusion release is out, plus new tool: VMware Importer for moving Windows VM's from Parallels to VMware FusionJust saw a tweet from VMware Fusion developer Ben Gertzfield:
VMware Fusion 1.1 and VMware Importer (Parallels to VMware) beta are out!
Looking over the release dates, it looks like this is the first post-Leopard release of VMware Fusion, so if you have Leopard, you especially want to grab this.
Then there's VMware Importer, a new, beta tool for converting your Parallels guests to VMware (Fusion) guests. The docs say it works with Windows guests (Windows 2000, XP, 2003, and Vista), and that because enough info about your (virtual) hardware will change during the conversion process (just in terms of identifiers I assume, not actual profile), you'll probably need to reactivate you Windows license upon conversion.
While we're talking about Macs, VMware Fusion, and Ben Gertzfield, I might as well link to a pretty cool (video) Google TechTalk Ben gave about VMware Fusion. It's about an hour, and the first 10 minutes are the standard talking points VMware gives about "it's about apps," etc, etc. But at about minute 11 it gets very interesting as Ben talks about how VMware approached certain Mac-specific problems.
JayZ vs. Nas; VMware vs. Parallels. VMware answers Parallels Coherence with Unity. Mac virtualization gets competitive (No they didn't. No they did not just use C&C Music Factory in this video. They did. )
Aside from the ridic soundtrack, this video is compelling.
Yes, VMware Fusion is already available for free (in Beta). But this video shows features not currently available in the beta that you can download right now. Most notable is that VMware Fusion has responded to and one-upped Parallels Desktop's ability to have each Windows application be its own little window in OS X, rather than have one "parent" window host all guest applications.
Parallels calls this "coherence." VMware Fusion calls this "unity." They're pretty much the same, except that VMware Fusion can have each window appear individually in OS X's Expose feature, something Parallels does not.
That said, Parallels is fully released, and VMware Fusion is not. And the unity feature doesn't exist in the beta that's out. Add to that the fact that VMware hasn't announced how much/ if it will charge for VMware Fusion (its features are positioned between the free VMware Player, and $189 VMware Workstation).
Miguel de Icaza on Groklaw's over-the-top analysis of Novell's support of OpenXML in OpenOffice (it's true, Groklaw has demonstrated a bit of ignorance here. Almost every distro's interpretation of a project can be a little unique)
Last week was Ubuntu Open Week, where newbies, the curious, and the besotted could meet up in different irc channels and talk about specific topics. Here are the logs.
Wowza... So... Parallels for Mac OS X has been out a for a bit. But it's previously been best described as "...like VMware Workstation for a Mac." In other words, cool, but nothing beyond VMware, and if VMware actually had a product out for OS X, then you'd probably grab that.
But last Friday Parallels released a new feature that is pretty compelling, and raises the bar for the concept of "abstraction." Rather than having a parent window that hosts all of the guest OS's windows, there is a "coherence mode" option that has each window of the guest OS appear as an individual window in the host OS, making itSO the experience of using an application in the either guest OS or host OS, is pretty darn similar. Certain keyboard commands and drag and drop is supported between the two environments. The video above demonstrates this better than all these words. Check it out!
VMware Fusion video! (More) virtualization for Mac OS X is close.VMworld, virtualization software company VMware's big conference was a few weeks ago. Among the stuff presented was VMware Fusion. Even though it's not the first virtualization product for Mac OS X , it's definitely the one people have been most excited about.