Changes

From Amahi Wiki
Jump to: navigation, search
4,660 bytes added ,  04:47, 26 October 2011
no edit summary
#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.#*[https://lh3.googleusercontent.com/-NqOynJ2XrFs/Tqd-ZhwMCsI/AAAAAAAADB4/1_ZC1ZrKms4/s912/15vm_resources.png Image15]#At this point the VM wizard is asking for a disk to install the VM on. Select the managed storage and hit browse.#*[https://lh4.googleusercontent.com/-SsWFTpfeofc/Tqd-Z8cz2-I/AAAAAAAADCY/FAHOdLSqTqA/s912/16storage_browse.png Image16]#Notice the interface that is very similar to what we used earlier. Select the storage you created earlier and hit Choose Volume at the bottom right corner.#*[https://lh5.googleusercontent.com/-gEhcjng_GsY/Tqd-ae95ykI/AAAAAAAADCE/VSKmUTHkOHU/s912/17pick_storage.png Image17]#The selection should look similar to mine#*[https://lh4.googleusercontent.com/-llgEFbUDn1A/Tqd-aknJtLI/AAAAAAAADCI/cEYIZpvCKGc/s912/18storage_chosen.png Image18]#Now we are almost there check the box "customize configuration before install" also make sure the Architecture is correct. This tends to be wrong so double check the default.#*[https://lh5.googleusercontent.com/-65mjmA6RqPc/Tqd-bVYqg_I/AAAAAAAADCU/x3_VedvP79o/s912/19almost_done.png Image 19]#You will get an overview window. Fill in a description if you like. #*[https://lh5.googleusercontent.com/-RFQcUp0_dKM/Tqd-bz-TgKI/AAAAAAAADCo/S6XzZnr0HZM/s912/20overview.png Image20]#Select the Processor field on the left and open the "Configuration" by clicking the arrow. The hit "Copy Host CPU Configuration"#*[https://lh3.googleusercontent.com/-8ORfMfPEi38/Tqd-cUf_NTI/AAAAAAAADCk/k84IhCsr1tY/s912/21proc_values.png Image21]#*I am not even sure if this is nessasary but I do it.#Hit Begin Install at the top to start the VM installation.#*[https://lh3.googleusercontent.com/-qt0E0xXp9YE/Tqd-cy-bBgI/AAAAAAAADDE/5vEwUkizt50/s912/22begin_install.png Image22]#You should be off and running. Mine booted to the install screen and eventually Anaconda#*[https://lh4.googleusercontent.com/-yvxG62bAhqA/Tqd-dYMmyRI/AAAAAAAADC0/dUR1i9RBs1s/s912/23booting_vm.png Image23]#*[https://lh5.googleusercontent.com/-2thyMZrsoRE/Tqd-djTduMI/AAAAAAAADC4/o6kX2rdEWqM/s912/24anaconda.png Image24] ==Problems==Most of the problems I've run into are related to SELinux policy. Depending on your distro of choice you may or may not get these. Since Fedora uses SELinux by default you run a good chance of getting blocked by it. Don't panic. SELinux troubleshooting is pretty good. If you get an alert click the details and it will tell you exactly what to do. Run the commands and you should be good to go. I ran into a few myself but I ironed them out before I ran through this install. ==Don't forget to update your VM==First thing to do is to install all the updates to your new VM. This will close any holes that exist. ==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==Hopefully you guys get something out of this. KVM is a real alternative to any of the competing virtualization products. I prefer it because its already part of the OS. This is not an immature product. It will work well and "just works" No extra drivers or layers to install. The VM just knows what to do and acts correctly.  I have really just scratched the surface of whats possible. To get an idea as root on the host type in the command "virsh" Then type help. You will get a list of what is possible. Hardware additions, resource addidtions like RAM on the fly can be performed. Snapshots are possible thanks to LVM storage pools. Rollbacks can be performed and lots of things in between. My job as a Linux sysadmin has given me the knowledge to work with most of these things. Hopefully this writeup has passed on some of that knowlege. Its not difficult but you have to do it perfectly. You know its a computer and it does not forgive. CheersJack