VMware Virtual Machine(VM) Configuration File types
Introduction–
When you create VM (Virtual Machine) in VMWare based Virtualization platform. VMware creates few VM configuration files in folder with VM name in Datastore (Local Storage or NFS/SAN). Please find the table which describes files types in vmware…
| File | Usage | File Description | File Format |
| .vmx | .vmname.vmx | Virtual machine configuration file. | ASCII |
| .vmxf | vmname.vmxf | Additional virtual machine configuration files, available, for example, with teamed virtual machines. | ASCII |
| .vmdk | vmname.vmdk | Virtual disk file. | ASCII |
| .flat.vmdk | vmname.flat.vmdk | Preallocated virtual disk in binary format. | Binary |
| .vswp | vmname.vswp | Swap file. | |
| .nvram | vmname.nvram or nvram | Non-volatile RAM. Stores virtual machine BIOS information. | |
| .vmss | vmname.vmss | Virtual machine suspend file. | |
| .log | vmware.log | Virtual machine log file. | ASCII |
| #.log | vmware-#.log | Old virtual machine log files. # is a number starting with 1. | ASCII |
Thank you,
Arun Bagul
What is Virtualization and Types of Virtualization
What is Virtualization and Type of Virtualization?
In general there are different types of virtualization like Memory,CPU, Storage, Hardware and Network virtualization. Howver here we are going to talk about OS virtualization only.
1] What is Hypervisor –
Hardware virtualization or platform virtualization refers to the creation of a virtual machine that acts like a real computer with an operating system. Software executed on these virtual machines is separated from the underlying hardware resources.
The words host and guest are used to distinguish the software that runs on the physical machine from the software that runs on the virtual machine.
The software or firmware that creates a virtual machine on the host hardware is called a hypervisor or Virtual Machine Manager.
2] Type of Virtualization –
a) Para-virtualization –
-Guest OS has to be modified
-VM does not simulate hardware
-Use special API that a modified guest OS must use
-Hypercalls trapped by the Hypervisor and serviced
-Xen, VMWare ESX Server
b) Full-virtualization (Native) –
VM simulates “enough” hardware to allow an unmodified guest OS to be run in
isolation. Same Hardware and CPU/Memory, eg- Vmware,IBM VM family,Parallels,
Xen.
* Full virtualization with Xen Hypervisor requires:
i) Intel processor with the Intel VT extensions, or
ii) AMD processor with the AMD-V extensions, or
iii) an Intel Itanium processor
* Full virtualization with KVM hypervisor requires:
i) Intel processor with the Intel VT and the Intel 64 extensions, or
ii) AMD processor with the AMD-V and the AMD64 extensions
c) Emulation –
-VM emulates/simulates complete hardware
-Unmodified guest OS for a different PC can be run
-VirtualPC for Mac, QEMU
d) OS-level virtualization –
-OS allows multiple secure virtual servers to be run
-Guest OS is the same as the host OS, but appears isolated apps see an
isolated OS. eg: Solaris Containers, BSD Jails, Linux Vserver,OpenVZ and LXC (LinuX Containers)
e) Application level virtualization –
-Application is gives its own copy of components that are not shared
(eg: own registry files, global objects) – VE prevents conflicts, JVM
Thank you,
Arun Bagul