Proxmox VE Installation Lab

IP Addressing

You will be assigning static IPs to your systems in this lab. Please use these settings:

  • Subnet Mask: 255.255.255.0

  • Default Gateway: 192.168.1.1

  • DNS Server 192.168.1.1

System IP FQDN Hostname

HV-A

192.168.1.10

proxmoxA.podX.itc2300.campus.ihitc.net

HV-B

192.168.1.11

proxmoxB.podX.itc2300.campus.ihitc.net
Replace podX in the hostname with your pod ID letter such as proxmoxA.podA.itc2300.campus.ihitc.net

Instructions

  1. You will be installing a Proxmox VE server on the two hypervisor (HV) VMs assigned to you (so do all these steps, unless otherwise indicated, on each computer). If you are unsure about how to do something try checking the Proxmox Wiki site first.

    Be sure to use a unique hostname on each Proxmox server, otherwise you will have issues connecting them together in a future lab.

  2. Two hypervisor VMs (labeled HV-A and HV-B) have been provided for you which you will be installing ProxMox VE on, each has:

    • 24GB RAM

    • 300GB Hard Drive

    • 2 CPUs

    • Enabled VTi/VTx Virtualization for the processors

  3. VMs are located on the https://netlab.ihitc.net Netlab system, be sure you are signed in to the ITC Passport site through D2L before attempting to access this system

    You will need to make a reservation for the Proxmox Labs in this class before you are able to access the VMs. Changes will be saved between your reservations so you will be able to make multiple reservations over several days as needed to complete labs.
    If you need to split your work up across multiple reservations be sure to safely shutdown your Proxmox VMs before ending your Netlab reservation. Otherwise when your reservation ends Netlab will simply power off your VMs (without shutting them down first) which could cause data corruption.
    If you make a mistake and need to have one or both of your HV VMs erased so you can re-install Proxmox you will need to access the ITC Passport interface and select the "View and manage Netlab pods assigned to your account" link. Click on the pod number for your "Virtualization Basics" pod and then click the link to erase the hard disks on the systems you want to reinstall.

  4. The Proxmox VE installer ISO file has been pre-loaded into the CD drive of each of your HV VMs

  5. Start the Proxmox VE installation (on both VMs) making note of these options:

    • Either graphical or console installation method can be used, they do exactly the same thing just look different. You could try the graphical mode on HV-A and the console mode on HV-B.

    • Set the Country to United States and Timezone to America/Chicago

    • Record the administrative password for future use, it is strongly suggested you use "itc2300" as the administrative password so that you can reference it here and your instructor can assist with issues in your lab.

    • Set the IP address for each Proxmox system using table above

    • Make sure the hostname is different on each Proxmox VE server and is set as identified in the table above

  6. Once the installation is finished log on to the console on each Proxmox Hypervisor as the root user and run the apt update and apt install open-vm-tools commands. Because we are running your Proxmox systems inside of our own virtual machines (called nested virtualization) this will improve performance and reliability. .Now you can use a web browser on PC-C to access the Proxmox VE server’s web interface at the IP address of the hypervisor and login as the root user (username root) and password set during the installation

    The password for the "Netlab User" account on PC-C is "netlab"

  7. Add a second user account to Proxmox VE and set it up with administrative access. Set the second account up as a Proxmox VE Authentication Server realm account meaning it will only be available in Proxmox and not on the underlying Linux system.

    You may want to read up about objects and paths for user accounts in Proxmox you will need to set a path for the account in order to get administrative permissions working. This is a bit trickier to get right than it may seem at first.
    Other students have used the power of Internet searching to find this site about users, groups and permissions in Proxmox VE which they have found helpful.

  8. Log out of the root account and login to the Proxmox web administrative interface using the secondary account you just created

  9. Use PC-C to upload Windows 10 and Linux Mint ISO files to the Proxmox VE server using the web interface

    • You may have problems uploading the ISO files with the Edge browser so Firefox or Chrome is suggested if you have issues uploading

    • The ISO files can be found on internal website http://172.17.139.70:8080 which you can access from PC-C.

  10. Try creating both a Windows 10 and Linux Mint VM (only on Proxmox VE server A!) and complete the installation.

    It is recommended that you disconnect/disable the virtual network interface on the Windows 10 VM before installing so that you will not need to sign in with a Microsoft account. Don’t forget to re-enable the network interface after completing the installation.
    Choose that you don’t have a product key when installing Windows, we’ll just use the trial version of Windows 10 Education
    If you do not see a hard drive to install Windows to it’s possibly your hard drive controller is a model which does not have a driver built in to Windows 10. When you create the VM in Proxmox one of the wizard screens asks what OS you will be installing on the VM. Most virtualization software does this as it will automatically select virtual hardware which is supported by that guest operating system. It is like you did not select Windows (or version 10 of Windows) when creating the VM. While you could manually change all of the VM virtual hardware to devices supported by Windows 10 (or add drivers to Windows 10 which support the virtual hardware you are using) it is probably easier to delete the VM you created and create a new one with the correct guest OS selected. For example, Windows 10 does not have VirtIO drivers built in by default so it can’t see any drives attached to a VirtIO controller. In this case you’ll need to pick a different controller (which Windows does have built-in drivers for) to get Windows installed.

  11. Install the "VirtIO Drivers" on your Windows guest system which will improve performance ad compatibiity with some of the virtual hardware.

  12. Install the "qemu-guest-agent" on both your Windows and Linux guest systems so that you can shut down and monitor the systems from Proxmox.

  13. Safely shut down your Windows and Linux Mint guest systems

  14. Safely shutdown your Proxmox VE servers

  15. End your Netlab Reservation

Document Build Time: 2024-10-30 23:55:42 UTC
Page Version: 2024.08
Creative Commons License
This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License