{{Admon/tip|Update your Fedora Installation|It's a good idea to ensure that your Fedora installation is fully updated before proceeding. You can update your system with the graphical tool located on the menu at >System>Administration>Software Update (or type the command <code>gpk-update-view</code>), or by typing either of these commands: <code>pkcon update</code> or <code>yum update</code>}}

{{Admon/caution|Reboot your fedora host|There appears to be an issue with supplying your VM's with a dynamic IP unless the host is restarted after installing "Virtualization". '''Reboot now to avoid this problem.'''}}

{{Admon/tip|Using an Image instead of a Live Disc|If you do not have a Live Disc available, you can download the .iso image file from http://belmont.senecac.on.ca/fedora/releases/13/Live/x86_64/Fedora-13-x86_64-Live.iso and then use the iso image file in place of the physical disk.}}

# Confirm that you can ssh to your virtual machine from the host (your main Fedora installation): <code>ssh ''IPaddress''</code>

{{Admon/tip|Authenticate to the network|The rest of this lab uses network access. Be sure to authenticate to the network using your browser before proceeding.}}

It is possible to install Fedora entirely from the network. In this investigation, you will install Fedora from a webserver on Seneca's LAN.

# Complete the installation. Record the time taken to install, and compare this to the time taken by the previous installations.

When Fedora is installed using the techniques you have used so far, the user is asked a number of questions. In some situations, it is better to provide the answers to these questions in a file rather than answer them individually. This type of file is called a ''kickstart'' file.

# Boot the virtual machine and log in (use the user ID and password information from the previous step). Compare the experience to the first time you booted the other virtual machines.

# In each VM, run this command: <code>yum update</code>

|}

{{Admon/note|Manage virtual machines from the host|The commands used to manage virtual machines must be executed on the host (your disk pack) and not inside a virtual machine.}}

# List all of the virtual machines again, and note any changes.

# Shut down all of the virtual machines.

{{Admon/tip|Shutting Down the Host while Virtual Machines are Running|If you shut down your host system while virtual machines are running, they will be suspended, and will resume the next time you boot your host system.}}

{{Admon/tip|SSHD and Firewall|If you have restarted your virtual machine ''fedora1'', the sshd server you started in section 1-16 will no longer be running. In addition, the firewall will have reverted to its original state. In order to use ''scp'', below, you will need to restart ssh and adjust the firewall again.}}