Virtualization - Revision history

Kamran: /* Why “not” Virtualization? */

2013-05-10T12:13:32Z

Why “not” Virtualization?

← Older revision		Revision as of 12:13, 10 May 2013
Line 239:		Line 239:
	** And someone said, less screw-drivers!		** And someone said, less screw-drivers!

-	== Why “not” Virtualization? ==	+	== Why “not” use Virtualization? ==
	* Administration of VMs, when more than a few, is more complicated, and sensitive than more than a few physical servers. The different VM interfaces, such as VMware's Virtual Infrastructure Center, and KVM's ovirt, try to address this.		* Administration of VMs, when more than a few, is more complicated, and sensitive than more than a few physical servers. The different VM interfaces, such as VMware's Virtual Infrastructure Center, and KVM's ovirt, try to address this.
	* For live migrations involving movement of a VM from one physical host to another, involves extra IPs, etc. Plus the shared storage, sometimes cluster file systems, etc.		* For live migrations involving movement of a VM from one physical host to another, involves extra IPs, etc. Plus the shared storage, sometimes cluster file systems, etc.

WikiChaudhry: /* Processor capability identification tips: */

2010-11-22T05:36:53Z

Processor capability identification tips:

← Older revision		Revision as of 05:36, 22 November 2010
Line 170:		Line 170:

	=== Processor capability identification tips: ===		=== Processor capability identification tips: ===
-	On linux, you can check the /proc/cpuinfo file and see if the flags line has "vmx" (for Intel) or ~~smx~~ (for AMD) in it. If the following line results in some text, then your CPU (irrespective of being Intel or AMD), has Hardware-Assisted Full Virtualization support.	+	On linux, you can check the /proc/cpuinfo file and see if the flags line has "vmx" (for Intel) or svm (for AMD) in it. If the following line results in some text, then your CPU (irrespective of being Intel or AMD), has Hardware-Assisted Full Virtualization support.

	<pre>		<pre>
Line 177:		Line 177:

	If the command above, does not return any results, or just returns to the command prompt silently, then your processor does not support Hardware-Assisted Full Virtualization. However, it should be noted that sometimes, this feature is turned off in the BIOS. Therefore you should check your BIOS settings first, to verify that.		If the command above, does not return any results, or just returns to the command prompt silently, then your processor does not support Hardware-Assisted Full Virtualization. However, it should be noted that sometimes, this feature is turned off in the BIOS. Therefore you should check your BIOS settings first, to verify that.
		+
		+	* svm = secure virtual machine (AMD)
		+	* vmx = virtual machine extensions (Intel)

	Also, if your CPU is an older model, and does not have Intel VT-x or AMD-V technologies, all hope is not lost. Check if your CPU provides PAE feature. If that is there, you can still use/create Para-Virtual virtual machines on this machine, using Xen. You can also use the emulation based full virtualization products such as Qemu, Bochs, Virtual Box, VMware workstation, etc. Here is how you can check for PAE for your CPU in Linux:		Also, if your CPU is an older model, and does not have Intel VT-x or AMD-V technologies, all hope is not lost. Check if your CPU provides PAE feature. If that is there, you can still use/create Para-Virtual virtual machines on this machine, using Xen. You can also use the emulation based full virtualization products such as Qemu, Bochs, Virtual Box, VMware workstation, etc. Here is how you can check for PAE for your CPU in Linux:

Kamran at 16:32, 3 May 2010

2010-05-03T16:32:53Z

← Older revision		Revision as of 16:32, 3 May 2010
Line 298:		Line 298:
	** Virtualization provided to support single application.		** Virtualization provided to support single application.
	** e.g. WINE is used to run Windows programs in Linux environment.		** e.g. WINE is used to run Windows programs in Linux environment.
-	==[[Virtualization-XEN]]==	+	==[[Virtualization-XEN]] (Moved to separate page of it's own)==

Kamran at 16:29, 3 May 2010

2010-05-03T16:29:53Z

← Older revision		Revision as of 16:29, 3 May 2010
Line 298:		Line 298:
	** Virtualization provided to support single application.		** Virtualization provided to support single application.
	** e.g. WINE is used to run Windows programs in Linux environment.		** e.g. WINE is used to run Windows programs in Linux environment.
-	==[[Virtualization-XEN]~~XEN~~]==	+	==[[Virtualization-XEN]]==

Kamran at 16:29, 3 May 2010

2010-05-03T16:29:38Z

← Older revision		Revision as of 16:29, 3 May 2010
Line 298:		Line 298:
	** Virtualization provided to support single application.		** Virtualization provided to support single application.
	** e.g. WINE is used to run Windows programs in Linux environment.		** e.g. WINE is used to run Windows programs in Linux environment.
-	==[[Virtualization-~~XEN~~ XEN]]==	+	==[[Virtualization-XEN]XEN]==

Kamran at 16:29, 3 May 2010

2010-05-03T16:29:17Z

← Older revision		Revision as of 16:29, 3 May 2010
Line 298:		Line 298:
	** Virtualization provided to support single application.		** Virtualization provided to support single application.
	** e.g. WINE is used to run Windows programs in Linux environment.		** e.g. WINE is used to run Windows programs in Linux environment.
-	==[[Virtualization-XEN]]==	+	==[[Virtualization-XEN XEN]]==

Kamran: /* [Virtualization-XEN]:XEN */

2010-05-03T16:24:12Z

[Virtualization-XEN]:XEN

← Older revision		Revision as of 16:24, 3 May 2010
Line 298:		Line 298:
	** Virtualization provided to support single application.		** Virtualization provided to support single application.
	** e.g. WINE is used to run Windows programs in Linux environment.		** e.g. WINE is used to run Windows programs in Linux environment.
-	==[Virtualization-XEN]~~:XEN~~==	+	==[[Virtualization-XEN]]==

Kamran: /* Virtualization-XEN:XEN */

2010-05-03T16:23:34Z

Virtualization-XEN:XEN

← Older revision		Revision as of 16:23, 3 May 2010
Line 298:		Line 298:
	** Virtualization provided to support single application.		** Virtualization provided to support single application.
	** e.g. WINE is used to run Windows programs in Linux environment.		** e.g. WINE is used to run Windows programs in Linux environment.
-	==[[Virtualization-XEN]]:XEN==	+	==[Virtualization-XEN]:XEN==

Kamran: /* Virtualization-XEN:XEN */

2010-05-03T16:22:58Z

Virtualization-XEN:XEN

← Older revision		Revision as of 16:22, 3 May 2010
Line 298:		Line 298:
	** Virtualization provided to support single application.		** Virtualization provided to support single application.
	** e.g. WINE is used to run Windows programs in Linux environment.		** e.g. WINE is used to run Windows programs in Linux environment.
-	==[[Virtualization-~~XEN:~~XEN]]==	+	==[[Virtualization-XEN]]:XEN==

Kamran at 16:21, 3 May 2010

2010-05-03T16:21:48Z

← Older revision		Revision as of 16:21, 3 May 2010
Line 6:		Line 6:
	More at [http://wbitt.com, http://wbitt.com]		More at [http://wbitt.com, http://wbitt.com]

-	<b>This document is broken into smaller chunks.~~</b>~~	+	<b>Note:</b> This document is broken into smaller chunks. Virtualization with XEN is here: [[Virtualization-XEN]]
-	Virtualization with XEN is here: [[Virtualization-XEN]]	+

	== Why this document ? ==		== Why this document ? ==
Line 299:		Line 298:
	** Virtualization provided to support single application.		** Virtualization provided to support single application.
	** e.g. WINE is used to run Windows programs in Linux environment.		** e.g. WINE is used to run Windows programs in Linux environment.
-	==[[Virtualization-XEN,XEN]]	+	==[[Virtualization-XEN:XEN]]==