Application Virtualization a Different Approach

I basically started working on multi layer virtualization. What does it exactly mean?

Well we have seen talked and discussed about application virtualization. But how we are deploying it using Thin App/Xen-App/V-App? How do you club it with your current VMware environment ?

How about this multi layer virtualization?

1. Xen-App which will allow you to publish application- Layer 1

2. MS App V which provide application virtualization – Layer 2

3. Then you have third layer which is server virtualization where your MS App V server is running.

How does it sound you are running MS application virtualization over VMware server virtualization. Well this is competitive age and if you want to survive you should learn to respect each other.

What I have learn so far with MS App-V is that it allow you to execute application locally on the PC unlike Citrix. App-V run application in its own bubble (address space) including dll and executable. What does it suppose to mean? Say for example dll which is stored in system/system32 and if it used for two different application then every application will try to overwrite it and try to put own version. But incase of App-V it runs all in its own virtual partition.

So benefits of such design are that you can have more control over deployment since you don’t have to do perform deployment on 1000 different server. Again you can have different methodology of deployment, once such which I am aware is HP RADIA but as I mention this is complete different approach of application virtualization.

You virtualize application and then publish it to your XenApp and then your application virtualization as well as XenApp running on ESX host. How does it sound ?

I am currently involved in learning this whole new application virtualization stuff . After SRM/ESX ,

App-V woo next Ubantu/DataONTAP.

A General Sstem Error occurred: Invalid Fault

I was trying to create a VM on a host and it was throwing following error message

We just have to restart hostd service on the host: service mgmt-vmware restart

VMControl error -999: Unknown Error

I was trying to register one virtual machine on one of the pathetic host (It was giving me hell lots of trouble and cannot reboot for some reason). It was also giving me message

 

So I decided to create a new VM using same vmdk file. I thought I will copy just vmdk file and delete rest of the directory and attach the vmdk to newly created vm. When I was trying to remove the folder it gave me message

 

After doing googling I found following way to remove the directory.

1. First I ran command vm-support –x to get all the available vmid on the host

2. Run vm-support –X <vmid>. It can also be killed using kill -9 <vmid>

This will keep running with different messages.

Once this is completed it will dump the core file inside the VM directory. You should be able to remove the vswmp file.

ESXTOP series 1

“ESXTOP” is very handy command to check host status from the performance point of view. I have decided to write series of ESX related tips.

In this series we will check network status

So if you press

1. esxtop

2. s - to have delay calculated in second

3. then 2 for two second delay

4. n to check nic status

esxtop s 2 n

Output will be

Fix sshd_config issue

Sometime “sshd_config ” get messed because of ILO flaky or if you are not good with VI. So here is what we have to do to get it fix

1. If “sshd_config” is under /etc/ssh/sshd_config got modified you may not be able to do ssh into ESX host.

2. If host is already connected to virtual center then upload the file using “Browse Database ” and upload it under /vmfs/volumes partition. From there move it to /etc/ssh folder. You can use sshd_config from any other host.

mv /vmfs/volumes /sshd_config /etc/ssh/

I usually do this only after I add the host into VC. Then restart ssh service

/etc/init.d/ssh restart.

This should fix the problem