User:Jack Palmadesso - Revision history

Jack Palmadesso at 05:47, 26 October 2011

2011-10-26T05:47:39Z

Jack Palmadesso at 05:14, 26 October 2011

2011-10-26T05:14:01Z

Jack Palmadesso at 05:12, 26 October 2011

2011-10-26T05:12:02Z

Jack Palmadesso at 04:53, 26 October 2011

2011-10-26T04:53:11Z

Jack Palmadesso at 04:49, 26 October 2011

2011-10-26T04:49:34Z

Jack Palmadesso at 04:47, 26 October 2011

2011-10-26T04:47:35Z

Jack Palmadesso at 04:23, 26 October 2011

2011-10-26T04:23:47Z

Jack Palmadesso at 03:24, 26 October 2011

2011-10-26T03:24:54Z

Jack Palmadesso at 03:06, 26 October 2011

2011-10-26T03:06:18Z

Jack Palmadesso at 02:25, 26 October 2011

2011-10-26T02:25:59Z

@@ Line 2: / Line 2: @@
 ==Intro==
-The following tutorial is a pretty advanced topic.  I will attemmpt to do my best in being as clear as possible but you need to be warned that if you have not worked with Linux for very long you might get lost.
+The following tutorial is a pretty advanced topic.  I will attempt to do my best in being as clear as possible but you need to be warned that if you have not worked with Linux for very long you might get lost.
 For a few years now the Linux kernel has had the ability to run virtual machines natively.  Most people think of Vmware or Virtual Box when they want to run virtual machines.   These are good products and have come a long way in making virtualization a reality.  While it is possible to get these products for "free" and use them there are drawbacks to using these products.  For the most part these mainstream products are streamlined and present a nice gui to an end user.  These usually do a good job in making the complex task of virtualizing a machine simple but there are drawbacks.  The "free" versions usually disable some really nice features like "snapshots" or they might restrict the amount of resources that can be assigned to a Virtual Machine.
@@ Line 70: / Line 70: @@
 ==Here We Go==
-Please make sure to follow these steps because you can blow away your system.   I have a space PC I am using for this so I am not worried about any data.
+Please make sure to follow these steps because you can blow away your system.   I have a spare PC I am using for this so I am not worried about any data.
 * First you have to fire up virt-manager.  This is a gui based tool and the following steps will all utilize the gui.  There are a ''ton'' more options in the cli but we are going to keep in simple here.

@@ Line 135: / Line 135: @@
 ==VM integration==
-Your VM will be assigned a private network address by KVM.  Normally its 192.168.22.X  This address will be NATed by default to the network the host is attached to.  In my case my host machine called KVM is on my network with my Amahi HDA as well as alot of other devices.  I assigned KVM a static address in the Amahi control panel just because its a server.  You don't have to if you don't want to.  Whats cool is that the VM uses all the network information from the Host.  This means that your new VM is effectivly on your network and will resolve all the home devices via the DNS server in Amahi.  You can also create an alias in the Amahi networking panel so its possible to reach the VM from anyplace.  It rounds things out nicely.  This is especially usefull if you are running another Amahi HDA for development because the separation of the networks means that the dev HDA will not interfere with the normal workings of the "production" home network.  I see this alot on IRC where guys are hesitant to test because it interferes with the setup.
+Your VM will be assigned a private network address by KVM.  Normally its 192.168.22.X  This address will be NATed by default to the network the host is attached to.  In my case my host machine called KVM is on my network with my Amahi HDA as well as alot of other devices.  I assigned KVM a static address in the Amahi control panel just because its a server.  You don't have to if you don't want to.  Whats cool is that the VM uses all the network information from the Host.  This means that your new VM is effectivly on your network and will resolve all the home devices via the DNS server in Amahi.  You can also create an alias in the Amahi networking panel so its possible to reach the VM from anyplace.  It rounds things out nicely.  This is especially usefull if you are running another Amahi HDA for development because the separation of the networks means that the dev HDA will not interfere with the normal workings of the "production" home network.  I see this alot on IRC where guys are hesitant to test because it interferes with their setup.
 ==Development==

@@ Line 23: / Line 23: @@
 *80 gb OS drive (Fedora 15 X64 Installed)
 *160 gb drive (to be used for the VM images)
 Nothing special about it right, but to take advantage of the 4gb or RAM you need 64 bit, especially if you have more RAM than I have here.  As I mentioned I am using Fedora which is what Amahi users are used to so this will be biased towards Fedora.
@@ Line 88: / Line 90: @@
 #*[https://lh5.googleusercontent.com/-6BlV30CaNLw/Tqd-V6ikVzI/AAAAAAAADA0/AsiEOpqx7Ng/s912/7disk_by_id.png Image7]
 #*This is where you need that ID.  Hit the browse button by '''"source path"'''and navigate to /dev/disk/by-id  From there pick the one with the filename that matches your number ID.  '''Don't screw this up or you can blow your host system away!!'''
 #*[https://lh3.googleusercontent.com/-9gk8Mbm4f4U/Tqd-WEc_4SI/AAAAAAAADBI/SpApMvZ-1sU/s912/8storage_final.png Image8]
 #*Once you pick the correct device you should have this.  Check the "build pool" box so the Volume group gets created on the device.
@@ Line 132: / Line 135: @@
 ==VM integration==
-Your VM will be assigned a private network address by KVM.  Normally its 192.168.22.X  This address will be NATed by default to the network the host is attached to.  In my case my host machine called KVM is on my network with my Amahi HDA as well as alot of other devices.  I assigned KVM a static address in the Amahi control panel just because its a server.  You don't have to if you don't want to.  Whats cool is that the VM uses all the network information from the Host.  This means that your new VM is effectivly on your network and will resolve all the home devices via the DNS server in Amahi.  You can also create an alias in the Amahi networking panel so its possible to reach the VM from anyplace.  It rounds things out nicely.
+Your VM will be assigned a private network address by KVM.  Normally its 192.168.22.X  This address will be NATed by default to the network the host is attached to.  In my case my host machine called KVM is on my network with my Amahi HDA as well as alot of other devices.  I assigned KVM a static address in the Amahi control panel just because its a server.  You don't have to if you don't want to.  Whats cool is that the VM uses all the network information from the Host.  This means that your new VM is effectivly on your network and will resolve all the home devices via the DNS server in Amahi.  You can also create an alias in the Amahi networking panel so its possible to reach the VM from anyplace.  It rounds things out nicely.  This is especially usefull if you are running another Amahi HDA for development because the separation of the networks means that the dev HDA will not interfere with the normal workings of the "production" home network.  I see this alot on IRC where guys are hesitant to test because it interferes with the setup.
 ==Development==

@@ Line 133: / Line 133: @@
 ==VM integration==
 Your VM will be assigned a private network address by KVM.  Normally its 192.168.22.X  This address will be NATed by default to the network the host is attached to.  In my case my host machine called KVM is on my network with my Amahi HDA as well as alot of other devices.  I assigned KVM a static address in the Amahi control panel just because its a server.  You don't have to if you don't want to.  Whats cool is that the VM uses all the network information from the Host.  This means that your new VM is effectivly on your network and will resolve all the home devices via the DNS server in Amahi.  You can also create an alias in the Amahi networking panel so its possible to reach the VM from anyplace.  It rounds things out nicely.
 ==Conclusions==

← Older revision		Revision as of 04:49, 26 October 2011
Line 1:		Line 1:
		+	==KVM Virtualization==
		+
	==Intro==		==Intro==
	The following tutorial is a pretty advanced topic. I will attemmpt to do my best in being as clear as possible but you need to be warned that if you have not worked with Linux for very long you might get lost.		The following tutorial is a pretty advanced topic. I will attemmpt to do my best in being as clear as possible but you need to be warned that if you have not worked with Linux for very long you might get lost.

@@ Line 102: / Line 102: @@
 #Now just browse to the location where the ISO is located and select your OS type in the dropdowns
 #*[https://lh4.googleusercontent.com/-si2UbG9im60/Tqd-ZBEb_oI/AAAAAAAADB0/gmhjqG8BhEE/s912/14media_ostype.png Image14]
+#Enter the amount of RAM and number of CPUs you would like for this VM.  This is where the 64 bit OS becomes comes in handy.  Otherwise your VM would be starved for RAM right off the get go.

← Older revision		Revision as of 04:23, 26 October 2011
Line 64:		Line 64:
	What I will try to describe is a fairly advanced concept called LVM (Logical Volume Manager). There are many methods to create a volume group in Linux but as far as I know it is nessasary to use the KVM gui or cli tools to integrate them properly into KVM. I am not going to describe all the details of LVM because its just so much. Just know that it works well and is very well developed. KVM utilizes LVM and has some built in tools to create and use volume groups. KVM calls them storage pools for some reason, probably to make it easier for people migrating from ESX or others. It makes sense but it can get confusing when all these terms are being tossed around.		What I will try to describe is a fairly advanced concept called LVM (Logical Volume Manager). There are many methods to create a volume group in Linux but as far as I know it is nessasary to use the KVM gui or cli tools to integrate them properly into KVM. I am not going to describe all the details of LVM because its just so much. Just know that it works well and is very well developed. KVM utilizes LVM and has some built in tools to create and use volume groups. KVM calls them storage pools for some reason, probably to make it easier for people migrating from ESX or others. It makes sense but it can get confusing when all these terms are being tossed around.

−	Please make sure to follow these steps because you can blow away your system. I have a space PC I am using for this so I am not worried about any ~~date~~.	+	==Here We Go==
		+
		+	Please make sure to follow these steps because you can blow away your system. I have a space PC I am using for this so I am not worried about any data.
		+	* First you have to fire up virt-manager. This is a gui based tool and the following steps will all utilize the gui. There are a ''ton'' more options in the cli but we are going to keep in simple here.
		+
		+	#Start virt-manager from the command line or menu or whatever
		+	#*[https://lh6.googleusercontent.com/-PqNshtWkxh4/Tqd-O13ZsKI/AAAAAAAADAM/KOamaJAGbYs/s912/1virt-man.png Image1]
		+	#Its going to bug you to authenticate as the root user. You can avoid this by starting virt-manager at the command line as root but anyway
		+	#*[https://lh5.googleusercontent.com/-JIjMnfk6Urc/Tqd-UJzhcQI/AAAAAAAADAU/x8ZJcie9GAU/s912/2virt-man.png Image2]
		+	#Once you are in you need to goto Edit --> Connection Details. It should bring up the following overview panel.
		+	#*[https://lh3.googleusercontent.com/-3Nm0v70_Y7A/Tqd-UjEJ50I/AAAAAAAADAo/-xLIzzc2dd8/s912/3conn_details.png Image3]
		+	#Goto the Storage tab so we can build our storage pool for the KVM VMs.
		+	#*[https://lh6.googleusercontent.com/-NVif9rgSGQA/Tqd-UXaQ78I/AAAAAAAADAY/ZpIC51VAd6A/s912/4storage.png Image4]
		+	#Once we are there we want to Add a Pool like so
		+	#*[https://lh6.googleusercontent.com/-4FgJvgcr4is/Tqd-U2Dyn_I/AAAAAAAADAk/cTzntzAuKdg/s912/5add_storage_pool.png Image5]
		+	#*Fill in a name that makes sense to you in the top field. Since this step is creating a volume group I start off with that and then use the underscore and name the volume group.
		+	#*In this case we are using LVM so follow along. As you can tell there are many other options including stuff used in the enterprise like iSCSI and others like LVM. You can also choose to just do a file like vmware to keep it simple.
		+	#At this point we are performing the steps of creating a Logical Volume Group. in the bottom left click the plus sign to add a new Volume group. The volume group will store all the logical volumes of the VMs to be created soon. You will also need that drive ID you recorded earlier. You do have that right?
		+	#*[https://lh6.googleusercontent.com/-BlVneEgyb7w/Tqd-VSDRgfI/AAAAAAAADA4/dsCgnjYs8B4/s912/6storage_target.png Image6]
		+	#After hitting the Forward button you will be presented with something like this
		+	#*[https://lh5.googleusercontent.com/-6BlV30CaNLw/Tqd-V6ikVzI/AAAAAAAADA0/AsiEOpqx7Ng/s912/7disk_by_id.png Image7]
		+	#*This is where you need that ID. Hit the browse button by '''"source path"'''and navigate to /dev/disk/by-id From there pick the one with the filename that matches your number ID. '''Don't screw this up or you can blow your host system away!!'''
		+	#*[https://lh3.googleusercontent.com/-9gk8Mbm4f4U/Tqd-WEc_4SI/AAAAAAAADBI/SpApMvZ-1sU/s912/8storage_final.png Image8]
		+	#*Once you pick the correct device you should have this. Check the "build pool" box so the Volume group gets created on the device.
		+	#Here is you final warning.
		+	#*[https://lh4.googleusercontent.com/-WX5UJn0ZOzU/Tqd-Wi2-N4I/AAAAAAAADBE/0JkLn5BXPR4/s912/9storage_you_sure.png Image9]
		+	#At this point our Volume group is created. You can also call this a storage pool. Inside this pool we want to create a new disk or Logical Volume. This will be used to store the VM itself. This will also give the VM direct access to the device just like a non virtualized PC. Select New Volume
		+	#*[https://lh5.googleusercontent.com/-utcIDf_w6WM/Tqd-XCmfCDI/AAAAAAAADBU/HCq6lx4y9ck/s912/10new_pool.png Image10]
		+	#Now give the LV a name. I fall back on my own naming standards which you really need to develop when you do alot of this. Otherwise this field is free form. I name it after the VM that will go on this volume.
		+	#*[https://lh5.googleusercontent.com/-utcIDf_w6WM/Tqd-XCmfCDI/AAAAAAAADBU/HCq6lx4y9ck/s912/10new_pool.png Image11]
		+	#*Notice the size fields. KVM has the ability to "thin provision" I won't go into too much detail about this. The first field is the ultimate size the volume will be allowed to grow to without an extension. The second field is what will be allocated intially. It will automatically grow to the max field setting over time.
		+	#Once you hit finish you'll have a nice new shiny volume to install whatever you like on it.
		+	#*[https://lh6.googleusercontent.com/-UCthw_ttdt4/Tqd-YKSWEWI/AAAAAAAADBk/_c8XUdCrKRc/s912/12volume_done.png Image 12]
		+	#At this point we are ready to install our new VM. You can safely close out the Host Details window and Click the New VM button in the original virt-manager window. Thats the button in the upper left corner of virt-manager. You will be presented with a wizard like interface.
		+	#*[https://lh5.googleusercontent.com/-kB4VdNkappI/Tqd-YgcYWGI/AAAAAAAADBo/JXC_YiK3Eh8/s912/13new_vm_name.png Image13]
		+	#*This is where the ISO we copied over earlier comes in handy. Select ISO as the local install media.
		+	#Now just browse to the location where the ISO is located and select your OS type in the dropdowns
		+	#*[https://lh4.googleusercontent.com/-si2UbG9im60/Tqd-ZBEb_oI/AAAAAAAADB0/gmhjqG8BhEE/s912/14media_ostype.png Image14]
		+	#

← Older revision		Revision as of 03:24, 26 October 2011
Line 56:		Line 56:
	==You are Ready==		==You are Ready==
	Hopefully all that went well. Make sure to reboot if the system update installed a new kernel. Otherwise you should be good to go.		Hopefully all that went well. Make sure to reboot if the system update installed a new kernel. Otherwise you should be good to go.
		+
		+	Here is gets a bit complicated again so make sure to follow the steps exactly. But you already know that I'm sure. Most of the work is done for you already with KVM once its installed but as with most software you usually don't want to run with the defaults. After all anybody reading this is definitely a tweaker. Just be careful here because you can blow away everything on this machine. We will be messing with the storage. Specifically we will be adding a "storage pool" to be used by the VM. Obviously we need to set this up before installing the VM.
		+
		+	====Storage Pool Concepts====
		+	If you have used Vmware or Virtual Box or others you probably are familiar with the VM being stored in a big file. Usually its a vmdk or somthing. While these are fine and work well when using this method you sacrifice some performance because of all the layers being presented to the hypervisor. As a matter of fact the biggest problems with VM perforance can be traced back to how the disk is accessed. Simpler is always better and is almost always more direct. KVM offers direct disk access. In other words it is possible to connect directly to a physical disk in the host to install and run the guest. This offers the best performance because well its the most direct and native way to interact with any block device.
		+
		+	What I will try to describe is a fairly advanced concept called LVM (Logical Volume Manager). There are many methods to create a volume group in Linux but as far as I know it is nessasary to use the KVM gui or cli tools to integrate them properly into KVM. I am not going to describe all the details of LVM because its just so much. Just know that it works well and is very well developed. KVM utilizes LVM and has some built in tools to create and use volume groups. KVM calls them storage pools for some reason, probably to make it easier for people migrating from ESX or others. It makes sense but it can get confusing when all these terms are being tossed around.
		+
		+	Please make sure to follow these steps because you can blow away your system. I have a space PC I am using for this so I am not worried about any date.

@@ Line 27: / Line 27: @@
 #Enable Virtualization in your BIOS !! Don't overlook this !!
 #*If there is no virtualization options in your bios then either your board or cpu do not support it.  If that is the case then stop here because your experience will be poor at best.
-#Update your System !!
+#Update your System !! If you get a new kernel its best to reboot.
 #*su -c yum -y update
 #Install the needed Packages
@@ Line 48: / Line 48: @@
 #***kvm_intel              44819  0
 #***kvm                   317840  1 kvm_intel

@@ Line 17: / Line 17: @@
 This is going to take some time so get yourself comfortable.  Maybe get some music going in the background and get a drink or something,  seriously.  For this example I am using the Host or Hypervisor is running on Fedora 15 x64.  Do yourself a favor and make the Host 64 bit because you really need to take advantage of the RAM.  Here are my Host/Hypervisor specs:
-Dual core 3ghz proc
+*Dual core 3ghz proc
-gb RAM
+*4gb RAM
-OS drive (Fedora 15 X64 Installed)
+*80 gb OS drive (Fedora 15 X64 Installed)
-gb drive (to be used for the VM images)
+*160 gb drive (to be used for the VM images)
-Nothing special about it right but to take advantage of the 4gb or RAM you need 64 bit, especially if you have more RAM than I have here.  As I mentioned I am using Fedora which is what Amahi users are used to so this will be biased towards Fedora.
+Nothing special about it right, but to take advantage of the 4gb or RAM you need 64 bit, especially if you have more RAM than I have here.  As I mentioned I am using Fedora which is what Amahi users are used to so this will be biased towards Fedora.
 =====You will need the following information which will be used later on=====
 #Enable Virtualization in your BIOS !! Don't overlook this !!
-#*If there is not virtualization options in your bios either your board or cpu do not support it.  If that is the case then stop here because your experience will be poor at best.
+#*If there is no virtualization options in your bios then either your board or cpu do not support it.  If that is the case then stop here because your experience will be poor at best.
 #Update your System !!
 #*su -c yum -y update
@@ Line 40: / Line 40: @@
 #*You want the stuff in bold recorded somplace
 #*You can also get this same info from the "Disk Utility" app which is gui based.
+#Once all the packages are installed you need to check some things.