Let's Install Proxmox 8.0!

so you've built yourself a new server and you're anxious to get your home lab up and running with virtual machines and mass storage like all of your cool friends If This Were A choose your fighter screen my choices would be proxmox for the main OS and virtualizing true Nas for all of your storage needs today we're going to focus on installing proxmox 8.0 getting your first couple VMS set up and running and going over some of the need to know features and settings in this latest release let's get started foreign [Music] this is the captain Rett is there something going on down there I need to know about we're on UPS backup sir the main Paradigm couplers have come on a line routers are Tangled with the secondary Casino in English Mr right it's the bandwidth sir getting it down is not the problem it's getting it back up well do what you can but remember I've got a budget here I'm gonna have to call you back hosting your own servers also means you get to host all your own problems even the most skilled Chief Engineers will tell you you should decentralize your network so why not host your services with lenode if it runs on Linux it'll run on the Node they offer shared CPU plans for as little as five dollars per month and can scale as high as you need to go with dedicated CPUs S3 compatible object storage GPU hosting and vme block storage and more linod is also expanding at light speed with 12 new global data centers planned before the end of 2023 visit lenode.com craft Computing and get a 100 60 day credit just for signing up for a new account that's lenode.com craft Computing and again thanks to lenode for sponsoring today's video Welcome Back to craft Computing everyone as always I'm Jeff in my last video I went over the hardware selection for this bookshelf friendly Nas build and while I did run into a couple difficulties with fitment I did manage to get everything installed and running a quick recap for those that didn't see this video this is an 8 bay Server Chassis from odd hide which I loaded up with a full set of hgst he6 SATA Enterprise disks for the PC side of things we're running an eerieing Micro ATX motherboard fitted with an Intel I9 11800h mobile CPU which gives us a deadly combination of low power consumption and high end speed all while having 8 cores and 16 threads to take advantage of we've also got 32 gigabytes of ddr4 3200 memory along with a pair of silicon power a60 one terabyte nvme drives I did have a slight issue getting the as media 1064 SATA controller to fit properly as two of the SATA ports stick straight out of the top of the card luckily a couple Silverstone low profile cables allowed the card to fit and the top panel to properly close so now it'll look something about like that see it even screws down look at that [Music] you can fit so much home lab in this bad boy now there were a number of comments in the build video asking why I went with this particular SATA controller rather than going with a tried and true server HBA the answer comes down to how I wanted to use this card and the slots available on the motherboard see we're going to virtualize True Nas which means the VM needs bare metal access to all of the hard drives the easiest and most effective way to do this is using PCI Express passthrough giving the VM full access to the as media card the as media 1064 only requires a single 1X PCI Express slot whereas a typical server HBA requires an X4 or even an X8 since there's only one x-16 slot on this motherboard and I'd like to leave it reserved for 10 gigabit networking later on down the line I was forced to use a 1x card only now remember with servers and PCs and any kind of build there are literally an infinite number of Hardware combinations you can come up with and all of them likely have a use case this is the a combo that I decided on and even with 8X spinning drives I don't expect to be able to saturate the 10 gigabit bandwidth of the PCI Express 3.0 X1 Lane on the SATA controller and even if I could we're still going to be limited by the 10 gigabit network connection once I install the network card for my use case this is going to do everything that I want and helps keep cost as low as possible on literally every single component as this SATA controller was only about 55 dollars and a 10 gig network card would be around thirty dollars for this slot all in all for a one thousand dollar virtualization and storage server I think the results are going to be pretty fantastic with the hardware sorted let's go ahead and do what we came here to do install proxmox head on over to proxbox.com click on the downloads Tab and find the latest release of proxmox virtual environment or proxmox ve as it's known in the download links as a filming that would be version 8.0-2 once you have the ISO file you'll either want to create a bootable flash drive with tools like or in my case I'm going to copy it over to my iodd virtual disk manager and optical drive emulator that I reviewed last year there are a million and one ways to create a bootable ISO image and if you have any suggestions about one that I didn't mention I'm sure I'm going to hear about it for the first time ever down in the comments below with your media of choice inserted into the server it's going to be time to fire up the machine and boot into the proxmox installer if you're a proxbox veteran the installer really hasn't changed at all since at least version five so it's going to be all business as usual for you but this is a tutorial so we're going to walk through it all anyway the first step is to read the entirety of the end user license agreement which I'm sure all of you will take the time to do click the I agree button to continue assuming you actually agree and aren't just saying that so we can move forward the second screen is the one that needs your attention which is where we select the hard drives and raid setup you're going to install proxmox onto by default the installer will pick a single drive but as we have two installed in the system I'm going to want to set up a raid 1 so we have some redundancy next to the Target hard disk pull down menu click on the options button under file system you can select which multi-drive setup is right for you again with a two disk setup I prefer a raid 1 mirror there are two file systems to choose from in this particular setup whether we use Raid ZFS or butterfs my preference is usually to go with ZFS as it's the system that I know better and that's what my recommendation is going to be here so select ZFS raid 1. this will bring you back to the options screen where by default the installer thinks you want to use every disk that's currently installed in your server while I do appreciate its enthusiasm again we're only going to be using our two one terabyte nvme drives at the bottom of the window click the button to deselect all drives then I'm going to select my two nvme drives four Drive zero and drive one once you have everything set up the way you want click on OK to close the options menu and then select next in the main installer the rest the setup is going to be region selection setting up a root password and configuring your network all of which is going to be completely up to you now note proxmox will not work with the DHCP lease and needs to be assigned as static IP address I'll explain the network setup in a little bit more detail later on but for now enter an address that will work on your network and then click install so we can get everything set in stone once the installation finishes we're actually done working directly on the server with a keyboard mouse and monitor connected everything from this point out will happen through a web browser and proxmox's web interface open up Edge Netscape or whatever browser you prefer and enter https the IP address of your server that you configured just a second ago followed by a colon n8006. instead of hosting the web interface on Port 80 or 443 proxmox uses Port 8006 and the colon and port number allows your browser to make the proper connection to log in the username is root and the password is whatever you set up during the end installation if you forgot the password between four minutes ago and now you're quite literally boned start the installer again and join us back here when you're ready but I'm not waiting for you we'll dive into some of the features and settings inside proxmox that might be of interest to you shortly but why don't we start with creating your first virtual machine as that's really what most of you are probably here to watch this video for the only thing we need that we don't already have to make this happen is an ISO installer for whatever OS you want to run on your VM to keep things simple let's create a new VM and install Ubuntu Server head on over to ubuntu.com click on the downloads link and select Ubuntu server for this tutorial the most recent version is 22.04 R3 once you have the iso downloaded to your PC we'll need to upload a copy to proxmox so it can pass along the iso to your virtual machine on the left side of the proxmox main screen you'll see a data center icon this represents all of the proxmox servers you have managed together but since we're only running a single proxmox server and haven't clustered anything together yet the only thing you'll see under here is your single server we'll go over multi-server Management in a future video under your server icon you'll see three more icons one for local network one for local storage and another for local file systems click on the middle icon to access your local storage which is where we'll store any install isos that you want proxmox to have access to in the storage window click on the iso images tab and then click on the upload button in the upload window that pops up click on select file to browse and locate your version of Ubuntu Server ISO on your PC once you have it selected click on upload to make a copy onto your proxmox server if the upload is successful you'll see a confirmation window appear close that and you'll be taken back to the iso images tab which is where you should see all of your Linux isos in one convenient location and by this I actually mean Linux isos at this point you should be ready to create your first VM back on the left side of the screen you're going to want to right click on your local proxmox server not the data center icon and click create VM from the context menu this will bring up the VM wizard screen and walk you through the process of getting the VM configured for use if you're brand new to the world of virtual machines they're kind of exactly what they sound like software-based emulation of physical computers every aspect of a PC is recreated either through software emulation things like PC bios hard drives network interfaces to physical sharing of actual Hardware divvying up the resources from your CPU or physical memory to share between the host system in this case proxmox and your virtual or client system we'll go over this a bit in more detail later in the video for now let's get this virtual machine on the road proxmox assigns each virtual machine that it manages a unique identifier with an accepted range between 100 and an identifier that is nine digits long unless you plan on creating just shy of 1 billion virtual machines in a single managed cluster I'd recommend sticking with a three-digit ID the default is 100 but I hate starting with zero because I don't think in binary so I'll give my first VM an ID of 101. under name this is a human readable identifier so give it something that makes sense to you I'm going to name my virtual machine homelab Dash Ubuntu once you're done go ahead and click on next in the next tab we'll Define what operating system type the virtual machine will use and what install media will be mounted on the first power on under the iso image pull-down menu you can select the ISO file that you'd like to use and as you probably guessed I'll be installing Ubuntu server with the iso that we just downloaded a moment ago on the right side of the screen is the guest OS type by default proxmox assumes you'll be running a Linux based operating system with a modern V6 kernel in this case it's 100 correct so we're going to leave these settings alone however if you were to install a different OS either another Linux kernel or maybe a Windows based OS make sure to make the proper selections here this election helps determine which virtual Hardware to create for the client system ensuring compatibility of everything that you're going to need with all that done click on next to move on to the next step the system tab is where we start defining our virtual hardware for our virtual machine now the defaults for this seem to change depending on which version of proxmox you currently have or what Hardware boxmox itself thinks it's running on but I'll break the selection down into two options for you since around 2013 almost all modern PC Hardware is running UEFI based firmware where machines prior to that often use what we now refer to as Legacy BIOS whatever hardware and firmware you installed proxmox onto I'd recommend creating VMS with the same type of firmware unless you have a really good reason for switching it up mixing and matching between host and clients can lead to very odd and unexpected outcomes when it comes to memory allocation CPU instructions or Hardware sharing and pass-through there are two pull-down menus to pay attention to here which affect these settings machine and bios under machine i-440fx is your legacy biospace virtual hardware and Q35 is for UEFI we're going to be running proxbox on UEFI Hardware so select Q35 as your machine type under bios you'll also see two options one for C bios for legacy systems and OB vmf for running UEFI firmware again I'm going to select ovmf with UEFI based Hardware selected you'll also need to create an EFI storage device which is a tiny virtual disk for UEFI firmware to be stored on select your local file system storage pool for the disk location another quick note while we're on this page if your operating system requires a tamper protection module or TPM you can emulate one by checking the add TPM box here other than that you should be ready for the next step onto storage for your virtual machine where we're going to create a virtual hard drive image to connect to your VM it might sound a little odd but leave the bus device at its default scuzzy selection as a virtual scuzzy Drive is actually the fastest of all the virtual interfaces under storage you'll select the location on proxmox to store this virtual disk and just like the EFI disk we're going to select the local file system under disk size I'm going to increase the size from 32 gigabytes to 80 gigabytes all disks at least those created on a ZFS file system are created with thin provisioning which means even though we're creating an 80 gigabyte disk it won't actually use space in our storage pool unless the VM writes data to it giving it 80 gigabytes allows plenty of room for growth without resizing the virtual disk later on and as you'll see when the install is done the virtual disk is only going to take up around three gigabytes of space in our storage pool moving on to the CPU tab here the defaults are pitiful as just a single CPU thread is assigned to our virtual machine the setting you want to change here is cores with each number being a thread your virtual machine can use now this is where a lot of people have misunderstandings about what virtual machines are and how CPU allocation is performed assigning a thread to a virtual machine does not exclude that thread from being used Elsewhere on the machine either by proxmox or overhead use or buy another virtual machine itself you're also not limited on how many threads you can allocate based on the number of cores and threads in your actual Hardware in my case again I've got eight cores and 16 threads on my CPU but that doesn't mean I can only allocate 16 threads across every virtual machine on my entire server CPU performance allocation is handled dynamically by proxmox and by your Hardware either through Intel's VTX or amd's VT virtualization systems that are built into their respective CPU platforms what you're assigning with the number of threads or cores is the maximum performance you want to provide a single virtual machine not how many slices of the pie your virtual machine will outright own even if you've allocated more threads than your CPU physically has both Intel and amd's virtualization systems are designed to automatically balance loads between both the host and client systems for a basic virtual machine these days I recommend a minimum of four threads as a starting point you can always give a virtual machine more if you feel performance constraints are affecting you but I guarantee you're not going to want to allocate just a single thread unless you have a very specific reason for doing so CPU type is another thing we'll get into shortly and proxmox 8.0 introduced a new default type called x86 64 V2 AES for right now just leave this at the default as we can always come back and change it later after I explain some differences in CPU types and if you decide that your use case is a good fit next up is memory configuration which again is a big area that a lot of people get wrong through misunderstandings or misinformation in the community Through Intel VTX or AMD VT physical memory can be used by your host and client system in a shared pool the maximum amount of memory your VM can use is what you're defining with this option and my recommendation is to give each VM at least four gigabytes or 4096 megabytes of memory that it can use now right now this is the only time in this tutorial we're going to click on the advanced checkbox in the Wizard but a quick glance here shows that ballooning device is checked by default ballooning means that only Ram that has data written to it by a VM is considered allocated just like storage unless memory is allocated anything unused by a VM remains available to both the host and to other virtual machines on the server just like storage and CPU settings it is absolutely possible to over allocate your resources giving a pool of virtual machines a combined four terabytes of potential storage capacity when your physical storage capacity is only one terabyte or giving eight different VMS a total of four CPU threads for a total of 24 when your CPU only has 16 available or giving six individual virtual machines eight gigabytes of memory each for a total of 48 when you only have 32 gigabytes of memory installed in your server as long as the actual used storage memory or CPU Cycles doesn't exceed what your Hardware can provide the system should perform as expected now this is a slippery slope as some services or operating systems will use every available resource they have access to for things like Windows updates or ZFS pool caching so don't just give every VM you create more Hardware than you can actually use but assigning resources isn't denying resources Elsewhere on your system either it's a balancing act that you'll need to learn for yourself based on what services and resources you will actually be using on your server getting back to memory again I like assigning four gigabytes to even simple virtual machine means but with ballooning enabled to keep my allocated memory to a minimum and with that we have just one config left in the Wizard and that's your network setup there are only two things to check for here and one we haven't covered the background of yet the bridge is a network path between your virtual machine through proxmox and out to a physical network adapter on your server I'll explain this in slightly more detail shortly but by default proxmox creates a bridge called vmbr0 and for this tutorial that's what you'll want to use for the VM connection as well the model of network card will have different defaults based on your client system OS for Windows based VMS it will often use the virtual Intel E1000 Nic which will allow for gigabit speeds on a virtual machine Windows uses this because the drivers are installed by default on basically every modern version of Windows so out of the box your networking adapter will function the best performance is actually from a device called vert IO which is a para virtualized Network device that negotiates 100 gigabit connections between the virtual machine and the proxmox bridge Network device this means connections from one VM to another on the same Hardware will have 100 gigabit links between them as proxmox's Bridge serves as a virtual switch the downside to the vert I O Network device is it is a red hat developed virtual device and while most Linux or BSD Kernels have drivers built in Windows operating systems do not but you can add drivers to a Windows image or install drivers once your virtual machine is up and running but if you're looking for the maximum possible Network performance this is absolutely the route I recommend going and it's what I'll be selecting for our Ubuntu virtual machine today and with that the last screen is simply a confirmation of all the choices you made in the Wizard if everything looks good you can click on finish and finalize the creation of your first virtual machine the creation process typically takes less than a minute and once completed you should see your virtual machine appear with both the VM ID number and the human readable name that you gave the machine inside of the wizard once both those appear the virtual machine should be ready to start up for the first time double click on the virtual machine to bring up a virtual console this will serve as your monitor keyboard and mouse for interacting with the VM one thing you'll notice is once you click Start now and Power on your VM for the first time it loads into a typical PC bio splash screen this is because it's actually its own unique PC it's as if you just spent your time assembling a PC part by part and powered it on for the first time only this PC exists only through a combination of Hardware sharing and software emulation pressing delete or F2 will bring you into this virtual machine's bios screen where you can actually adjust settings just like on real Hardware every aspect of this virtual machine works as if it were real hardware and the reason I'm explaining it like this is because this is sometimes the most difficult part of understanding what virtualization actually is it's virtualizing every last individual component and part of a PC putting it all together and turning it on as if it were actually real Hardware if your new virtual machine boots into the Ubuntu Server installer congratulations you've started your very first virtual machine I'm not going to walk through the install of Ubuntu to right now just know it works exactly like it would on a real PC with real Hardware as I said I wanted to come back and cover networking because that's one area where people often stumble when it comes to learning virtualization not only are we virtualizing PC Hardware to create virtual machines on this server but proxbox's Network system acts as a virtual switch for all the virtual network interfaces on each individual virtual machine during the proxbox installer itself you were asked to create a static IP address for the server to be accessed on what you were actually doing is creating a virtual network bridge and here's where things start to get weird between physical network adapters like the one on the back of this server and virtual network adapters which exist only in software proxmox creates a network bridge and names it vmbr0 this virtual network adapter is what gets assigned the static IP address a network bridge is actually a bit self-explanatory it links two or more network adapters together whether they be virtual or physical in this case we have a virtual network bridge with an IP address of 10.0.0.215 linked to a physical network adapter which in and of itself has no IP address at all all it's doing is linking our virtual bridge to a physical cable so the bridge can communicate with the rest of your network the cool part about a network bridge is you can link it to multiple physical network devices to create redundant Pathways out onto your physical Network inside proxmox the virtual network adapters you create for each virtual machine are also connected to the network bridge which is how they are granted network access through the server's physical adapter through these virtual links you can operate the network bridge like a managed network switch assigning vlans to each virtual machine or adapter creating internal only networks so VMS can communicate among themselves but not to the outside world or link different VMS to different physical network connections the method of using a network bridge as a virtual switch is very common in hypervisors nowadays that you'll come across with hyper V xcpng VMware and many others using very similar configurations before we wrap this up I also wanted to touch on virtualized CPU types one of the biggest changes to default settings in proxmox 8.0 is arguably making x8664 V2 AES the default CPU type but what is a virtual CPU type what does it actually affect in Virtual machines and what settings should you use when speaking about CPU types we're actually talking about features available to a CPU things like microcode instructions for AVX or AES encryption for a very long time the default CPU type in proxmox has been the KVM 64 CPU which essentially gives your virtual machine access to CPU instructions from a Pentium 4 CPU that's a 20 year old CPU platform that means that a virtual machine wouldn't have access to Modern instruction sets for applications again things like ABX or AES have Specific Instructions and algorithms written into CPU Hardware but to take advantage of them your software needs to know that these CPUs are present and have these instruction sets available a virtual Pentium 4 era CPU is compatible with basically every host CPU you could ever install proxmox onto but it would also be missing those instructions to pass through to a VM the x8664 V2 AES virtual CPU type along having the worst possible name for a virtual CPU interface also has instructions for all CPUs up to Intel's 4th generation westmere parts and amd's opteron 64. this adds critical instructions for many modern applications like SSC 3 and SSE 4.2 and as long as your host CPU is from that generation or newer will give your virtual machine access to these instructions however the V2 CPU type still doesn't support ABX instruction sets if you are running a newer model CPU I'd encourage you to take a look at some of the more modern CPU types as well especially if the software that you want to virtualize takes advantage of newer instruction sets x8664v3 adds support for Intel Broadwell and AMD first generation ryzen and epic CPUs adding AVX and avx2 instruction sets among others x8664v4 is what I'd recommend for any modern platform that means Intel's 6th generation Skylake or newer and support all the way up to AMD Zen 4 and epic Genoa CPUs the CPU type adds support for AVX 512 instructions and ensures that if you are running a modern CPU your virtual machines can take advantage of all the latest features if you've had a problem I'm running an application like cinebench or Adobe Premiere in Virtual environments before it's likely because your virtual CPU didn't have access to instruction sets necessary for the program to run effectively while these apps will run without instruction sets like AVX the CPU basically has to Brute Force its way through each calculation tanking performance inside of the virtual machine now there are dozens of available CPU types and most of them are for specific Generations or single product lines of retail CPUs it's fine to select a matching architecture to a physical CPU you have installed but going with a more generic selection will make it easier to manage or migrate virtual machines between individual proxmox servers later on if that's something you're eventually going to set up virtual machines especially those running Windows don't like to have their CPU type changed at random so selecting a CPU like x8664v3 allows your VM to think it's running on the same physical CPU even if you move a VM from an Intel Skylake to an AMD epic rom-based server unless you have a specific need to define the exact CPU model generic CPU selections tend to keep everything happy for your client OS hopefully in this video you were able to install proxmox set up your first virtual machine and now have a handle on the basics of virtual networking CPU allocation and CPU types and the relationship between the host hardware and your virtual machines just like all server topics virtualization is a subject that is miles deep and I've got plans over the next couple months to dive as far down as I can go using proxmox I'm hoping to cover subjects like PCI Express passthrough private networking for isolated home lab or developer environments as well as looking at specific services that you can run in a virtualized environment if you have anything specifically you'd like to see me cover please drop me a line down in the comment section below I'm always looking for new ideas or subjects to cover in videos like this one thing I've always subscribed to is the idea that knowledge should be free which is why I publish these tutorials on YouTube at no charge if you liked this video learned something or want to help support making videos like this there are a number of different ways you can do that first off head on over to craft computing.store for some quality merch that is designed and made right here in house yes I personally etch every single one of these pint glasses and coasters myself out in my garage I get a couple of bucks to help support the channel and you get some quality glassware everyone wins second I do have a Discord server but it's an exclusive perk of joining the patreon it gives you the opportunity to chat with myself as well as the nearly 800 people who have joined the community we talk about the newest beers we've tried share knowledge around all aspects of PCS and home labbing there are community-led classes on topics like soldering and it's an all-around awesome place just to hang out follow me on the social medias at craft Computing make sure to hit that Thumbs Up Button And subscribe to craft Computing if you haven't done so already and as always I will see you in the next video cheers everyone not the beer to drink for a tutorial I'll tell you that much I don't know if this is the right beer to open for a tutorial but what the heck uh in honor of the 666th video posted to my Channel today we are opening Android theories all that I have learned which is a fantastic name but it's not the name alone that is getting the nod today it is the 16.66 ABV on the back of it there could not be a more appropriate beer right now and also one that I'm more terrified of advert theories all that I have learned Russian imperial stout age in Maple whiskey barrels this is Ghost 987 for those in the know and bottle number 55 of 2000. nice this smells like a very well aged bottle of Founders Canadian breakfast out CBS which I don't think they make anymore uh boy that Maple and whiskey it is so so right there that is a dangerous beer wow the maple is definitely much more present on the nose than it is in the flavor itself uh the flavor profile very very rich Stout with a very bitter dark chocolate and coffee back end and that whiskey is poking through a little bit as well with kind of some butterscotch and and charred charred wood kind of flavor to it uh not nearly as sweet as you'd be led to expect based on the smell alone that is super rich super complex ever evolving every flavor is there did I mention it was 16.6 percent good luck so this beer has warmed up quite a bit it's probably very close to approaching room temperature maybe just a couple degrees below it is also mellowed out a lot uh one thing about this when it was cold is it had this super harsh bite right at the front of the flavor profile and I mean really harsh like Jack Daniel's harsh uh not that it really detracted from the flavor but it was noticeable and it may be off-putting for some people now oh God it's just velvety smooth which of the 14 flavors I just experienced in six seconds do you want to hear about because they were all good ah it goes without saying this is an amazing beer maybe 12 ounces is too much for a single person but I also don't care

Channel: Craft Computing

Views: 147,387

Keywords:

Id: sZcOlW-DwrU

Length: 33min 30sec (2010 seconds)

Published: Tue Aug 22 2023