VM Junkie

December 10, 2009

View 4 & PCoIP – a few problems

Filed under: view, vmware, vSphere — Justin Emerson @ 9:15 pm

So I’ve been doing my first customer deployment of View 4 lately, and there have been quite a few gotchas that I’ve noticed so far…

The first, and biggest, is that I just can’t get View Composer to reliably clone machines. About 50% of the time, the VM will have an Error in View Manager that says “View Composer agent initialization state error (6): Unknown failure (waited 0 seconds) and the only way to fix it is to reset the VM manually or refresh it. I ran into similar issues during the Beta and what I’m seeing here is pretty nasty. It’s a very similar issue to what is outlined in this VMware KB article. However, the resolution in the KB article has so far not fixed the issue for this customer. The error will not clear on its own, and can even reoccur after a reset.

We’ve also had several issues with PCoIP so far. The most critical is we’ve had virtual machines lock up so bad after trying to connect to them with PCoIP that I had to kill the VM from the service console with kill -9. Other issues are that PCoIP doesn’t work with ThinPrint (so you get no printer redirection except through USB redirection), no folder redirection (which was to be somewhat expected since that’s provided by RDP), and the biggest issue is no tunneled connections. Much like RGS connections, PCoIP connections go directly to the VM. This has important implications, such as the Security Server is now useless except for RDP.

While I definitely think View 4 is a HUGE step forward from View 3, it still has a lot of things I think are pretty rough edges. Add that to a lot of the issues with vSphere Update 1 (well documented by Mike Laverick) and it looks to me like View 4 really was released too soon. That said, I think it’s a great start and bodes really well for the direction VMware is headed.

View Composer agent initialization state error (6): Unknown failure (waited 0 seconds)

December 9, 2009

Fix for LSI Logic Issue

Filed under: view, vmware — Justin Emerson @ 8:00 am

It appears that those having the issue I described in my previous blog post (myself included) were experiencing this issue because we were using a newer, unsigned driver for the LSI Logic controller. VMware actually recommends (in this KB article) that you use the WHQL driver which is available here. Doing so fixes the issue. Thanks to several folks in this VMware Communities thread for the resolution!

Create a free website or blog at WordPress.com.