KVM Virtualization - Revision history

Bigfoot65 at 22:45, 14 September 2015

2015-09-14T22:45:01Z

Bigfoot65 at 14:23, 29 March 2015

2015-03-29T14:23:06Z

Bigfoot65 at 14:22, 29 March 2015

2015-03-29T14:22:52Z

Bigfoot65 at 16:31, 5 April 2014

2014-04-05T16:31:51Z

Bigfoot65: /* Conclusions */

2012-12-02T22:35:29Z

Conclusions

Cpg at 00:20, 13 July 2012

2012-07-13T00:20:02Z

Jack Palmadesso at 00:38, 3 November 2011

2011-11-03T00:38:33Z

Jack Palmadesso at 00:38, 3 November 2011

2011-11-03T00:38:01Z

Bigfoot65: /* You will need the following information which will be used later on */

2011-10-26T23:33:13Z

You will need the following information which will be used later on

Bigfoot65: /* You will need the following information which will be used later on */

2011-10-26T23:31:57Z

You will need the following information which will be used later on

← Older revision		Revision as of 22:45, 14 September 2015
Line 1:		Line 1:
−	~~{{MessageBox\|backgroundcolor = #FBB\|~~
−	~~image =Warning.png\|~~
−	~~heading =WARNING\|~~
−	~~message = [[Amahi 7]] is the latest stable release.}}~~
−	~~----~~
−
−
	{{NeedsUpdate}}		{{NeedsUpdate}}

← Older revision		Revision as of 14:23, 29 March 2015
Line 4:		Line 4:
	message = [[Amahi 7]] is the latest stable release.}}		message = [[Amahi 7]] is the latest stable release.}}
	----		----
−

@@ Line 1: / Line 1: @@
-{{MessageBox|
+{{MessageBox|backgroundcolor	= #FBB|
 image	=Warning.png|
 heading	=WARNING|
-message = This is recommended only for advanced users, proceed with caution.}}
+message = [[Amahi 7]] is the latest stable release.}}
 {{NeedsUpdate}}

@@ Line 4: / Line 4: @@
 heading	=WARNING|
 message = This is recommended only for advanced users, proceed with caution.}}
 ==Intro==
 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.

← Older revision		Revision as of 22:35, 2 December 2012
Line 154:		Line 154:
	*[[KVM]]		*[[KVM]]
	*[[Virtualization]]		*[[Virtualization]]
		+
		+	[[category:virtualization]]

@@ Line 138: / Line 138: @@
 ==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.  It rounds things out nicely.  This setup 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.
+Your VM will be assigned a private network address by KVM.  Normally its 192.168.122.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.  It rounds things out nicely.  This setup 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 9: / Line 9: @@
 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.
-There are also the problems.  The guis can be a bit buggy and not always work correctly.  Of course support is not going to be possible so you will have to live with the problems until the next update.  With Vmware and Virtual Box there are also some packages that need to be installed in the guest to make them work "properly".  This is usually some form of driver that makes the Virtual Machine aware its being virtualized or presents a layer to trick the Virtual Machine into thinking its on some real hardware.
+There are also the problems.  The GUIs can be a bit buggy and not always work correctly.  Of course support is not going to be possible so you will have to live with the problems until the next update.  With Vmware and Virtual Box there are also some packages that need to be installed in the guest to make them work "properly".  This is usually some form of driver that makes the Virtual Machine aware its being virtualized or presents a layer to trick the Virtual Machine into thinking its on some real hardware.
 I am not knocking these products.  There are quite a few out there now and its really amazing how far they have come.  I actually remember around the year 2000 when Vmware was giving away its product for free with Suse Linux.  They were the only one in the space at that time.  Now there are dozens of products and most of them work pretty well.  At this point in time virtualization is just a fact so the various OS vendors are now building vitualization into thier product.  Microsoft has Hyper-V, Oracle has Virtual Box and Solaris Zones, and all Linux distros have the ablility to run either Xen, or KVM based virtual machines.  Xen is on the decline in favor of KVM now.
@@ Line 149: / Line 149: @@
 Cheers
-Jack
+jackpal
 Other guides on this Wiki regarding Virtualization:
 *[[KVM]]
 *[[Virtualization]]

@@ Line 35: / Line 35: @@
 #*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 !! If you get a new kernel its best to reboot.
-#*{{Code|su -c yum -y update}}
+#*su -c yum -y update
 #Install the needed Packages
-#*{{Code|su -c yum -y install kvm virt-manager qemu-kvm.x86_64 qemu-kvm-tools.x86_64 qemu.x86_64}}qemu-common.x86_64 qemu-kvm.x86_64 qemu-kvm-tools.x86_64 sheepdog.x86_64 virt-v2v.x86_64 mc nmap
+#*su -c yum -y install kvm virt-manager qemu-kvm.x86_64 qemu-kvm-tools.x86_64 qemu.x86_64}}qemu common.x86_64 qemu-kvm.x86_64 qemu-kvm-tools.x86_64 sheepdog.x86_64 virt-v2v.x86_64 mc nmap
 #*This might take some time so take a break or something
 #Your Drive ID or model number.
 #*You can get this by installing the "sdparm" package
-#*{{Code|sdparm /dev/sdb}}
+#*sdparm /dev/sdb
 #*Copy down the model number
 #*In my case: sudo -c sdparm /dev/sdb
@@ Line 49: / Line 49: @@
 #Once all the packages are installed you need to check some things.
 #*Make sure the kernel modules are loaded
-#**{{Code|lsmod |grep kvm}}
+#**lsmod |grep kvm
 #**Should give
 #***kvm and either kvm_intel ''or'' kvm_amd
@@ Line 56: / Line 56: @@
 #***kvm                   317840  1 kvm_intel
 #Next you need to make sure to start libvirtd.
-#**{{Code|service libvirtd start}}
+#**service libvirtd start
 #*Also make sure it starts at boot
-#**{{Code|chkconfig libvirtd on}}
+#**chkconfig libvirtd on
 #Finally you need to get the ISO source of your selected Linux distribution onto your Host.  Its probably easiest to just copy it from someplace or download it to the host.  In my case since we are geting ready for the Amahi release on Fedora 16 I downloaded the beta DVD to my host.  The important thing is to make sure that the ISO is easy to get at.  Don't bury it.