Showing posts with label VMware. Show all posts
Showing posts with label VMware. Show all posts

what is the different between thick and thin disk in vmware Or, thick-provisioned and thin-provisioned disks


what is the different between thick and thin disk in vmware Or,  thick-provisioned and thin-provisioned disks 

thick-provisioned disks are created with the entire size of the disk pre-allocated on physical storage at the time the disk is created. This pre-allocation means that creating a 50GB virtual disk actually consumes 50GB of physical disk space on your drives.

 thin-provisioned disks are created with the amount of physical disk storage used by a virtual disk is equal to the amount of actual data on that disk. If you create a 100GB disk but only use 20GB of that disk, the actual disk consumption on your physical drives will be 20GB.

Note: Versions of ESX prior to 4.0 were only capable of creating thick-provisioned disks.

p2v(Physical to Virtual) of Windows System using VMware vConverter

Below are the processes to convert P2V using VMware vCenter Converter Standalone 4.0.1
I.       Download VMware vCenter converter Standalone client and install in your physical sysem.
II.    Convert Windows Physical system to Virtual (P2V).

Download VMware vCenter converter and install on physical system and install it on your physical system
Download VMware vCenter Converter Standalone client from below link. http://www.vmware.com/products/converter/
Note:We need  to register to download vCenter converter. Just register with your mail id, it is free to download.
Convert Windows Physical system to Virtual (P2V).
1. Open VMware vCenter Converter and Click on Convert Machine













2. Select Source type is “Powered-on machine” and “This local machine” then click on Next


3. Select Destination type “VMware Infrastructure virtual machine”  and give ESX server details at “VMware Infrastructure server details” and clink next





















4. Give Virtual Machine name and click Next



5. Under View/Edit Option select drive to convert and check the box of drive which you want to convert and  un-check the box if you do not want to convert them. Click on Next to continue.











6. Click Finish to start conversion process.











8.You can see the status in progress marked in red




8.And the completed












9.Exit VMWare vCenter Converter once the conversion process is completed. Go to you ESX sever and start the converted VM.

commands to check whether vmware tools installed or not in ubuntu guest & the version

# ps -ef | grep vmware-guestd
root     10213     1  0 15:33 ?        00:00:00 /usr/lib/vmware-tools/sbin32/vmw                                                             are-guestd --background /var/run/vmware-guestd.pid
root     10446 10429  0 15:44 pts/0    00:00:00 grep vmware-guestd

OR

# ps -ef | grep vmware-tools
root     10213     1  0 15:33 ?        00:00:00 /usr/lib/vmware-tools/sbin32/vmware-guestd --background /var/run/vmware-guestd.pid
root     10559 10429  0 15:52 pts/0    00:00:00 grep vmware-tools
# vmware-config-tools.pl -h
Use of uninitialized value $gSystem{"system"} in concatenation (.) or string at                                                              /usr/bin/vmware-config-tools.pl line 2421.
VMware Tools 4.0.0 build-171294 for  configurator
Usage: /usr/bin/vmware-config-tools.pl [[-][-]d[efault]] [[-][-]c[ompile]]
[[-][-]p[rebuilt]] [[-][-]t[ry-modules]] [[-][-]p[reserve]]
[[-][-]o[verwrite][[-][-]m[odules-only]] [[-][-]k[ernel-version] version]
. default: Automatically answer questions with the proposed answer.
. compile: Force the compilation of kernel modules.
. prebuilt: Force the use of pre-built kernel modules.
. try-modules: Try to load all the compatible modules . preserve: Always
preserve user-modified configuration files.
. overwrite: Always overwrite user-modified configuration files.from the VMware
Tools package.
. modules-only: Only build/install kernel modules, skip all other configuration
steps.
. kernel-version: Build/install modules for the given kernel version instead of
the running one, implies modules-only, skip-stop-start and compile.
Command line arguments:  The acceptable characters are:
        the letters A, B, C, ...,
        the letters a, b, c, ...,
        the numbers 0, 1, 2, ...,
        and the special characters '_' and '-' and '='.

# grep buildNr /usr/bin/vmware-config-tools.pl
  my $buildNr;
  $buildNr = '4.0.0 build-171294';
  return remove_whitespaces($buildNr);