Feeds:
Posts
Comments

Consider this.

You want to integrate Salesforce into your Outlook 2007. You went to salesforce.com and downloaded ‘Connect for Outlook’. Installed it and restarted Outlook several times but still not able to see the Salesforce Outlook buttons.

Outlook 2007 has a strange way to put the Salesforce plugin in the ‘Disabled items’ list. What you need to do is then, enable it from the menu. On the Outlook 2007 console, Go to Help-> Disabled Items -> Salesforce. Refer to the screenshot below.

Disabled items

Disabled items

Thanks,

Arun.PC

Problem

After installing VMware Tools, you are still having a bad experience interacting with your Win2k8 or Vista VM.

Firstly, it could be because you have not enabled full hardware accelaration. Please check you hardware acceleration settings to confirm that you have set it to the fullest.

To check for hardware acceleration, Right click on your desktop, Goto Settings-> Display Properties-> Troubleshoot-> Hardware Acceleration.

Make sure that you set this to the fullest.

Secondly, it could be because VMware Tools is incorrectly configured. To check this out, go to the event viewer and look out for error messages.

To get to the event viewer, type in the command ‘eventvwr’ at the ‘Run’. You might see error messages on the service called ‘InteractiveService Detection’.

Now you need to set this service to startup automatically. For that, Go to Windows ‘Run’ prompt, type in ‘services.msc’.Look out for the service called ‘InteractiveService Detection’. Select ‘Properties’, and set it to start ‘Automatically’.

Restart the VM to experience better performance.

Thanks,

Arun.P.C

“Some things, such as themes, sounds, or background settings may not work
correctly.” blah blah blah

There were several posts on the web but none of it could get me my Ubuntu working. What i suspect is that this is a very generic error message and this could come so many ways.

My scenario
—————-

Worked seemlessly till i configured wireless for my boreadband internet. What followed is a long delay in starting GNOME and it would eventually start after 10 minutes displaying the above message in a message box.

Problem/ Diagnosis
————————-
I suspect two problems,

1) Since i configured for Wirelss through the GUI tool that come with Ubuntu Hardy as default, the entry for my lo/loopback in my /etc/network/interfaces file got displaced.

Many client server processes which run on the same machine, like some of them which GDM makes use of, needs a loopback reply from the same machine to proceed. Since the entries in the /etc/network/interfaces got screwed up, they wait infinitely to startup and result in long delays for timeout.

2)The other problem i discovered is that i cant ping
- pluto(which is my hostname)
- localhost
- 127.0.0.1

This is because of the fact that interfaces ‘lo’ or ‘localhost’ was not configured in /etc/network/intefaces.

Please check the command
#ifup lo

When i did it i got the error message,
Ignoring unknown interface lo=lo
If you get this error make sure that you make sure that you configure your interface settings in your /etc/network/interfces file correctly before proceeding any further.

This clearly shows that the interface for lo is not configured.

Solution
————

1) The solution is to feed in entries in /etc/network/interfaces for localhost and loopback.
So there would be two configuration in your /etc/network/interfaces.
One is the configuration for localhost/loopback interface and other is your wireless broadband.

It should look like this.

#vi /etc/network/interfaces

# The primary network interface
auto lo
iface lo inet loopback

# Wireless interface
auto wlan0
iface wlan0 inet dhcp
wireless-key 123456789
wireless-essid Arun


2) The next step is to provide values in the hosts configuration file.
arun@pluto:~$ cat /etc/hosts
127.0.0.1 localhost lo pluto

3)Check whether lo is pingable.
arun@pluto:~$ ping lo
PING localhost (127.0.0.1) 56(84) bytes of data.
64 bytes from localhost (127.0.0.1): icmp_seq=1 ttl=64 time=0.039 ms
64 bytes from localhost (127.0.0.1): icmp_seq=2 ttl=64 time=0.040 ms

4) If the ping does not work,bringup the lo interface manually
#ifup lo

5) Restart the networking settings
arun@pluto:~$ sudo /etc/init.d/networking restart

Make sure that you run the networking services cron during the startup to get your wireless broadband connect.

Thanks,

Arun.PC

Do you expereince slow data trasfers between your guest operating systems? Is data transfer between the host and guest also very slow? Are you getting megabyte trasefer rates even though your network adpaters are of gigabit speeds? Here is the solution.

The slow trasfer rates between VMware guest operating systems could be due to VMware tools not being correctly installed. Please check whether VMware tools service is running correctly in your Guest OS. Other than mouse and SVGA features, this is what VMware tools does to your Guest OS.

It will install the virtual network driver vmxnet instead of the default vlance. Network devices of the host machine communicates to the vlance driver just like the way it does to real hardware hence a lot of hardware overhead comes with this driver(it constantly checks whether the network is plugged etc..). But vmxnet is treated differently and differentiates itself as a virtual driver and hence a lot of unnecessary hardware checks are avoided.

This improves the network performance and gives you gigabit speeds.The following diagram tell you whether it is properly installed.

vmxnet Windows driver

But the more serious problem that most people face is the slow data trasfer between the host and the guest OS. Their complain always goes like this “I have gigabit network adapters for both my host and my guest OS. But why is that I still have only megabyte trasfer rates between host and guest?”.

After a lot of googling and consulting within the community, i am assuming that Vmware server is designed that way so that gigabit data trasfers are not possible(remember there is no thing as free lunch). In Vmware ESX, there is a straighforward option to configure the speed of the network adapter. Even if you set it as ‘automatic’, it would directly allot the speed of the pipe as gigabit if both your host and guest has that capacity.

However, you can always speed the transefer between your host and guest. One way is to turn off the unwanted checks done by your network adapter. If your host is Linux, you may use ethtool and for Windows, you can directly go to the advanced settings of the network adapter and turn OFF settings for TSO(TCP segmentation offload).Look below for the screenshot. What this setting does is to quicken the file transfer between the host and the guest.

 

Windows network adapter configuration

 

With so much Ga Ga over VMware and Xen, the industry overlooks the importance of dozen other players who play key roles in maintaining a thriving virtualization ecosystem.

Let me call the whole ecosystem a “jungle”. Like a jungle which contains all kinds of animals and each one playing a unique distinct role, virtualization ecosystem also has lots of players from thin-client companies to hypervisor companies to connection-brokers. Each of these roles is very critical for the sustenance of the ecosystem.The lion of this jungle is clearly VMware as it has the early mover advantage and also has a large chunk of the hypervisor market. Citrix is yet another lion from a different jungle who is trying to adjust to climatic change(from Server based computing to VDI) and is working desperately hard to establish himself under the new circumstances.

I have represented different components of a VDI solution as layers.The order of arrangement of layers needn’t be the same for all solutions that are deployed across the globe. Different solutions exist for different cases and this is a general approach to VDI. Please make a comment if there is anything that needs to added or modified.

Layers of VDI

As of today, there is NO SINGLE vendor is known to have a product which by itself is self sufficient to provide the entire VDI solution. There are many players like VMware, Provision, Microsoft and Citrix who have products in many layers of the solution but doesn’t yet cover the entire spectrum. Citrix, Microsoft and VMware have been on a buying spree acquiring startups for the getting more control over the VDI stack. This explains why recently Citrix bought Xen (Hypervisor Company) and VMware acquired Propero, a connection broker company.

Let me describe some of those components.

Thin clients or the End user machines :-P lenty of VDI solutions do not need any end point infrastructure except for broadband internet access.However,many vendors require a thin client infrastructure simply for generating a rich end user experience. This is the component which makes VDI experience a lot better than the existing Citrix or the terminal service experience. Thin clients do not have local storage or DLLs. They are just tools to find the remote virtual desktop hosted at the datacenter or the server farm. Most of them have inbuild extensions of connection brokers of Leostream, Provision or Vmware. Some of them even have IP phone capabilities and video accelerators to make use of the local graphic cards.Some of the popular thin clients are Wyse,Neostream, NEC etc..

Access and authentication layer is contacted immediately after a user provides his username and password. He is authenticated and permissions are granted using good old Kerberos, LDAP or Active Directory. This is the same for any client server application and VDI is no different here.

Display protocol is used to export the display from the server to the client.Mostly it is RDP,VNC or Citrix ICA. While the processing happens at the server the display is exported to the thin client.

Connection Brokering is the industry’s most competed layer. There are a dozen of vendors fighting all out to conquer this layer.This component connects the end client to the corresponding VM running on the remote server.It needs to consider things like 1) server load 2) traffic 3) latency 4) bandwidth 5) permissions etc..VMware recently acquired Propero and Citrix already has a brokering application.Some of the other players are Provision,Chip PC, Leostream,Sun etc..

Application Virtualization solutions from Microsoft SoftGrid,Symantec SVS and thinstall are the most popular ones. These virtualize registry, filesystem and everything thats needs for an application to run. The application is streamed to the client from the server and they execute it from the client sandbox present at the end point. The calls to the OS are smartly redirected through the sandbox.This way the client is completely unware of the application running on it.

Virtualization infrastructure is the layer which manages the health of the virtual machines, their redundancy,load, maturity etc..VMware and Provision networks have tools in this layer.The tools act as a “mother” to the virtual machines monitoring them closely for their well being.The VMware product is called Virtual Center and there are also vendors like Veeam and Virtugo who offer similar solutions.

Virtualizd Guest OS remains our good old Windows XP/Vista which are hosted at the datacenter instead of local machines.

Virtualization Host:- This is the heart of the VDI solution. This is where the guest operating systems are hosted over bare metal boxes and managed like individual programs.This layer is dominated by Vmware with its flagship product ESX. But with the Citrix acquisition of Xen and Virtual Iron also doing very well, the status quo of Vmware may not be remain the same forever. But as of now, it looks like a smooth sail for some time to come for VMware.There are also other players like Parellels for Apple Mac users and KVM/Qemu for Open source enthusiasts. Of late a company called Qumranet has also developed a KVM based desktop virtualization solution.

Backup and Storage technology:- Companies like Veeam and Vizioncore sensed the opportunity for vm backup/storage operations and they have solutions in the areas for BC/DR and maintenance of Vms.

Storage:- IBM, Sun, Hitachi,EMC have been virtualizing SAN/NAS. To end users, storage appears as locally mounted disks while the storage is virtualised in the datacenter and managed through a storage management interface to the system administrator.

Thats all folks!. I ll keep you updated.

Your comments always rock!

Note:- This article is technical.May not be useful for people NOT working with virtual machines

Scenario

The Host machine runs Vmware Server on Linux and the guest also runs Linux virtual machine.

Problem Summary
When trying to ssh from the Host Linux box into the guest Linux box, it just stays with the command and fails to execute or throw an error.It just remains like this.

ssh user@192.168.X.Y
<nothing happens after this.No error thrown>

The logs(/var/log/ssh or /var/log/auth.log) also doesnt show anything useful.

Test
Host machine can ssh into other machines in the network.

Host machine cannot ssh into any Vms it carries.

Host machine can PING to all Vms aswell as the other machines on the network.

Diagnosis
The problem is with the ethernet card settings. We need to tune the ethernet card settings with a tool called ethtool.(see MAN ethtool pages for various options).

By executing the below given command we disable some kernel modules like Rx checksum and scatter gather which solves the problem.

ethtool -K eth0 sg off rx off tx off tso off

Hope some of you found it useful.

Thanks,

Arun.PC

What is VDI?

What is VDI?

VDI is Virtual Desktop Infrastructure.

In order to understand VDI, you need to understand what ‘virtual desktops’ are. Virtual Desktops are not real desktops but who cares? You don’t need to if you are an end user.

What i mean by that is, you interact with your virtual desktops just like the way you interact with real desktops. Nothing changes. Nothing.

Let us take an example.Assume that you are using your Windows XP/Vista desktop with all your favorite applications like Yahoo messenger, Photoshop, MS excel, PowerPoint etc….You also have picture of your dog as the wallpaper. This is the desktop you use at home.You love your desktop and you are so familiar and accustomed to it. You don’t want to change it because it works for you and it is very personal.

Imagine this desktop is accessible to you everywhere. ie..an omnipresent desktop. You can access your applications and data from a friend’s place, local bar, your in-law’s house, office or a different country altogether.This is possible through virtualization and virtual desktop infrastructure. Ubiquity of access is just one of the feature of VDI. There are numerous others like security, cost, backup etc..

From an end user’s perspective, nothing changes in terms of his interaction with his desktop. He just needs to login to the network and his desktop is click away. His desktop gets streamed to him wherever he is and whenever he needs it.He can always save the changes he make; his preferences of applications, and all the other desktop settings remain intact.The difference lies in the system administrator’s job.Desktops are no more deployed.They are hosted and delivered.The user has an individual virtual desktop on the server elsewhere and they are allotted to him as and when they are needed. These desktops are streamed over the network and user gets his desktop irrespective of his physical location.

The obvious constraint to this technology is that desktops always need to be connected to the network.With the increasing adoption of broadband and companies working on caching and offline technologies, this issue sure to be mitigated to a large extent.

If you find the whole idea confusing, foggy and abstract, don’t worry; you are not alone. This is a whole new technological shift.This trend is not an evolutionary or an incremental change in application and desktop computing but it is a radical shift.

I am also eagerly waiting to see the how the story will unfold and in the coming days, i will keep you posted on the intricacies and developments in this area.
See you.

Thanks,

Arun.PC

 

 

 

 

 

« Newer Posts

Follow

Get every new post delivered to your Inbox.