Building a Homelab - Proxmox Hypervisor [Part 2]

Show Video

Hey everybody, welcome back to Jim's Garage. This is the second video in the new Homelab series where we're going to be deploying Proxmox onto our Homelab device and I'm going to talk you through all of the steps as well as some of the recommendations that I have for the device you might want to use and also the configuration of Proxmox itself. I'll also show you how to deploy your first virtual machine as well as an LXC and some of the other configuration options you might want to consider. Now in the previous video I gave you some options around some devices I recommend but I also spoke about some of the things that you should look for when creating a Homelab device, be it one that you've already got, i.e.

an old device, one that you may be building for new, a second-hand enterprise server or something off the shelf. Now the requirements for Proxmox are pretty lightweight anyway but obviously if you want to run more on this you want to have more provisioning, i.e. more cores, more RAM, more storage space. Some of the devices I showed in the previous video were very much bare bones so if you are using one of those devices do note that you might run out of some of those and it could limit what you can actually run on your Homelab server. Obviously something with

an upgrade path, more RAM slots, more storage space, more CPU etc you're going to be able to do more with your Homelab. But to prove a point I'm going to use what I would consider the sort of bare minimum. I'm going to use a Mele device that I've used in a previous video. It's only got four cores it's using the newest Intel N150, it's got 16 gigabytes of RAM and a one terabyte NVMe.

Ideally you'd probably want to get something with at least sort of eight cores or at least four cores and hyper threading. 16 gigs is okay to get you started but 32 is probably a good spot if you want to be hosting some additional services, additional virtual machines etc and I would recommend having two network interface cards. That can be really handy and it gives you the option to easily set up things like a virtual firewall and also having the ability to have more NVMe drives in there is pretty cool as well. You could either mirror your boot drive and use that single mirror to actually host the operating system for Proxmox itself as well as all the virtual machines. That does give you some redundancy because there isn't an official way to back up Proxmox albeit you will find unofficial ones with copying certain folder structures on the hypervisor itself. Now

there are a few ways to actually install Proxmox. There's an automatic installer where you can create a configuration file and it will automatically install it. That's good in a headless environment i.e where you don't have say a GPU or you need to have remote access to the system. You can also do it through a network boot as well but I'm going to take the easy option which is what I recommend and kind of what I'm aiming this series at and that'll be that more traditional method of downloading the ISO.

In this case it's going to be 8.4-1 from the official website we're going to hit download and download the ISO. You will need to burn this to a USB stick. Now there are other

ways to do this as I mentioned but they are more involved and I might cover that in a later video. You will also notice here that there is Proxmox backup server. I do have an existing video on that that is still relevant so I recommend you go and check that out if you want to be able to back up your virtual machines your LXCs etc after you've installed Proxmox. So once you've downloaded the ISO file we're going to need to burn that to a USB stick. Now there are

multiple ways to burn this ISO file to a USB stick. The tool that I like to use is called Rufus so you can just head to the Rufus website and download this but other alternatives include things like Etcher. It doesn't really matter which one you use just choose which one you like. Now the key thing is this is going to wipe the USB stick because it's going to need to partition it when it copies over the ISO file. So in my case I just simply need to click select, select the ISO file that I want, hit OK and then that's pretty much it. I should be able to hit start. Now it's going

to remind me again that it's going to destroy everything on this device and that's okay and then it's going to go away and actually install that onto the USB stick. Now whilst this is right in that image it's worth pointing out that Proxmox is not the only hypervisor that you can use. There are lots out there. For example you can actually use a hypervisor on your Windows machine. That's available on Pro and above I believe. I do have a video on that but if you're going down the home lab route I definitely recommend having something like a dedicated machine that you can install Proxmox on. Other

things to note are you can actually use things like Trunaz or Unraid as a hypervisor albeit I tend to use those just for storage. Another notable or at least it was notable was something like vSphere before it was bastardized by Broadcom. My understanding is that they are going to create another free tier for that but a lot of those bridges have already been burned within the community. So I generally recommend Proxmox. It's definitely the most popular one in the home lab space and I've had a great experience with it over the past few years. In fact I actually have three machines all running Proxmox in a cluster. I'll come on to that

later but if you want to skip ahead I've already got videos on that. Now once this has written it to the drive you're okay to close this down but you're probably thinking now well how do I actually get this onto the device what is it that I need to do? Well I'm going to assume that you've just got a bare-bones setup. What I mean by that is you've got your ISP router, you've got the machine like me that I'm recording this video on and then you've got another device that you're looking to install your first Proxmox onto. Now that device quite simply you

just want to plug that into your ISP router that should pick up an IP address via DHCP and you should be good to go. Now you don't technically need to give it internet access to undo the installer but you're obviously going to need to have network access to get onto that device post installation. One thing that's important for doing it this route is to have a GPU or an iGPU hence why I gave it so much attention in the previous video. Now you can do it without a GPU. Sometimes certain devices have things like IPMI whereby it's able to send the output of the machine over the network and you can view that but having something like an integrated GPU is a great start because you can simply plug in an HDMI cable like you would normally do and you'll just get this as output to a monitor. If you're using something like an AMD system that you've built yourself a lot of the time those CPUs don't come with an iGPU so you will actually have to use a discrete GPU for that installation process but you can remove that post installation because you'll be connecting to this thing through the web browser anyway or backup via SSH.

So now with your machine plugged in it's time to boot it up and we want to enter the BIOS to begin with. This is important because we need to make sure that we've got the right boot option selected. By default it's probably going to boot to the hard drive that the device was set up or came pre-configured with. Now the BIOS for your machine is going to be different depending on motherboard manufacturer, feature set, chipset, CPU etc. There's a

myriad of things but there's some common things that we want to look out for. Now on an Intel machine we want to be looking for things like VTX and VTD. Those want to be enabled. So on my machine this was on the VTD section here you can see that that's enabled and I've also got VTX enabled as well in another section in the BIOS. The next thing really you want to have a look at is to go to the boot section and here you can see that I've got Ubuntu installed from when I tested this device and the boot option too is that UFE USB drive that I just installed Proxmox 2. So what we need to

do is basically swap these around so that the first boot device is actually the USB device. On some machines as well you also get the option to fast boot and you can boot that from a different device without having to change these settings. I'm just going to change this now just to make it easier and make it permanent. Do remember in the future though if you plug in a USB device it might try to boot off that so you might want to swap these around again but effectively all we need to do now is click save changes and exit.

That should save it, reboot the device and now hopefully as you can see it's now trying to boot into Proxmox. Now I'm going to talk you through sort of a beginner setup for Proxmox but do go and read the documentation. There's a ton of other options. This should be able to get you up and running without too many issues but once you do start to get down this path and get more familiar you might want to revisit it. If we have a look at the advanced options you can see that there's automated installations which I mentioned before. There's also

some memory testing and some firmware settings. If you've got say a secondhand server from eBay or something you may wish to run a memory test first to make sure that all of your memory is performing as expected otherwise you could get some crashes or bad behavior once you're going through it. Now we're going to go through the graphical output just because it's easier with a graphic interface. Now it's going to boot

actually into the installer and we're going to go through the setup wizard to get this up and running. Now once this is booted we have to agree to the Euler and then we need to choose which device we want to install it on. Now because this is a cheap device and it only has one NVMe slot you can see here that I've only got this one option. If you have more than one device you will be able to click on the option selection here and you'll be able to choose how you want this set up. So for example you can set this up as ZFS and you've got various different ways to do RAID and also BTRFS. This would then

give you the opportunity to configure and set up and install this to a RAID. That would mean that in my instance I've only got one drive if that fails I lose everything but if you have a mirrored drive a redundant pair if one of those drives failed it would simply be using the other drive and you could replace it and keep your data. That is definitely something to bear in mind but if you're just starting out in the homelab space and you've only got a small device with one drive you should be fine because by the end of this we are going to be setting up a 3-2-1 backup strategy. So worst case is you'll lose whatever it is between now and your last backup but to be honest if you're backing up regularly that should be less of an issue. In the

future you'll probably want to go and add another drive in here make a raid rebuild your cluster etc and we can discuss that later on in the video series. But for now I'm just going to use this hard drive here and I'm going to click next. It's automatically detected where I am just due to having this plugged in and then it's going to ask me to create a password to log in. This will be the actual administrative console password the one that we'll be logging into through the web browser in a moment. So with those details entered we should be able to click next and then it's asking us what do we want as our management interface. Now

again on most of these devices if you're just getting a bare-bones device or an old machine it's probably only going to have one network card one network interface. This one actually has the wired one the one that I'm using you see it's green and it also has a wireless one. Obviously don't recommend using wireless because of the dropouts etc interference which can make administration a pain and also connections between VMs and your network etc pretty flaky. But also I

mentioned in previous video that you might want to add in additional network interface cards. Now that's where it gets quite interesting you can choose then to have dedicated network cards just for the administration of Proxmox itself which in a more sort of production setup is what you would have. You would likely have a dedicated interface card that is specifically for the administration of Proxmox and then you would put all of your containers VMs etc onto different network cards. That also gives you

the ability to have different network cards i.e. different performance based upon the requirements. Just for administration of Proxmox you really don't need anything fancy a one gig is more than enough but you might wish to get a cheap say Mellanox card or something else a 10 gig card and assign that just for your virtual machine so all of your virtual machines get snappy access to your network. In this scenario here where I'm choosing the default what this means is it's basically going to bridge the Proxmox interface and all of my virtual machines on that same network host. Like I say fine for a home lab not very productiony but it's enough to get you guys started. So depending on what you've got you choose how you want to set this up just remember which interface card you're using. Now

you can also give this a fully qualified domain name so for example I could just call this Proxmox.jimsgarage.co.uk you could choose whatever you wanted on yours as well based upon what you've got. This will be useful in the future because you'll be able to identify your machine etc and you'll be able to use this in the future to actually access this through the web browser etc. Now the IP address here is actually picked up through DHCP on my router and you'll probably have a similar setup if you're plugging this into your ISP router. You can obviously create a static map as well on your router if you wanted to so reserve an IP address. I generally recommend for

things like a management interface that you do do that because you want to make sure that your network interface isn't always changing because often when you need to log in stuff it's always the time at which things change and it can be a pain to get back up and running. So for this demonstration I'm just going to be running this on 9.109 and I've also set up my DNS server here which is actually my piehole. This will probably be picked up if you're just using your ISP router as your ISP router's DNS resolver but you could put in here for example 1.1.1.1 for something like

Cloudflare but it's up to you. You can also change all of these settings at a later date. So if we hit next we should get into now confirmation and installation. So it's basically

confirming everything we've just set up in the wizard and we're going to automatically reboot after a successful installation. So I'm ready to hit install and now that should be going away, should be formatting the drives etc and then it should be installing Proxmox to that single NVMe drive I've got on the machine. Once this is done it's going to reboot and I'll see you back on the other side once it's booted Proxmox for the first time. One thing to bear in mind and this is probably a bit advanced at this stage but is to understand the kernel version that you're running on Proxmox. Now basically the higher the Proxmox version the newer the kernel and for the uninitiated the kernel is essentially the bit of the computer, the code that actually talks between the operating system and the underlying hardware. So it

gives things like the OS access to the graphics card. Now in my instance and from my testing in a previous video the actual iGPU in the N150 is too new for kernel 6.8. I believe you need kernel 6.11. It's not

so much an issue for Proxmox itself because we're not going to allow Proxmox to use the iGPU but when you're installing say a new virtual machine and I'll touch again on this later in case you skipped ahead. When you install say a version of Ubuntu don't use something like 2404 and expect it to work. You can use 2404 but you'll have to update to at least something like 6.11 kernel otherwise the GPU just won't be recognized and you can't use it for pass-through. I'll reference my previous video because that process is still relevant. I'm not going

to have time in this video to do iGPU pass-through but I will speak about the bits that you need to look out for. So now the machine is rebooting it should now start up and because I've unplugged the USB drive it should automatically fail over now to that second one. Here you go it's picked up Proxmox and in two seconds it should automatically start booting into Proxmox itself. Now as I

mentioned before Proxmox is command line interface when you just plug an HDMI in. We're actually going to be accessing this through the web browser on my current machine i.e. the one I'm currently recording this video on. So now here you can see that we've got the IP address, HTTPS 9.109.port 8006 and that's what we need to connect to now in the web browser. Now we can also log in via the command line interface and this is good to know in case ever you've got any issues you should be able to log into here and resolve anything. So for instance

if I log in with root and I put in the password that I set during the installation. If I hit return you can see that I'm now actually logged in and just like I mentioned before if ever you've used Linux Proxmox is just installed onto Debian 12 Bookworm. So now you've got basically all the things you would expect from a standard Linux installation. So I'm going to exit this and now we're going to navigate to the IP address at the top of the screen via our browser. So if we go back now to the browser that we actually downloaded the ISO from and we put in the address that we saw.

So in my instance that 9.109 colon 8006 remember it's HTTPS we should be able to reach the web interface for Proxmox. Now you're likely to get a certificate warning but don't worry about that it's because it's using a self-signed certificate but one that isn't valid i.e trusted. So we want to hit advanced and we want to click proceed and then we should get to the login for Proxmox. Now

just like I logged into the CLI we'll use the same credentials so it will be root and then it will be the password during the installation. You can obviously opt to save the username and also just getting ahead of ourselves you can use different authentication servers if you want a more advanced setup we're not going to do that in this video. So we'll hit login it's going to complain that we don't have a valid subscription that's because Proxmox comes in two flavors basically the free version that we're using but there's also an enterprise one which gets regular patching and security updates we're going to hit okay you can also disable that warning if you want later on. So now the default as soon as we get in here we can see that we're on the data center tab and it's basically given us all the information about our Proxmox installation this is technically our cluster but we only have a cluster of one machine so this is basically a summary of just this one machine. If you look at my more

recent videos and stuff I've done on the channel you'll know that I actually have three of these machines in what's known as a cluster and that allows me to do cool stuff like move VMs between different machines the benefit of that is I can take down one machine for maintenance and then move all of my production stuff all of my VMs etc onto a machine that isn't being taken down and it also does that automatically not manually so again it makes the management of my systems pretty straightforward. So just looking through the data center itself you'll see a summary of the machine and what's on it at the moment you can see that we've got basically zero CPU usage it's using about 10% of my memory and pretty much 1% of the storage. Very lightweight very minimalist just to get Proxmox up and running and like I said before this is only a quad core CPU with 16 gigs of RAM. Now if we did have a cluster we could have a look at all the cluster things here and if you do want to add another machine in the future to join a cluster it's as simple as creating a cluster first and then getting the join information going on to that second machine and then adding it to that machine and once you've clicked join basically within a few minutes you should then be able to see both through one user interface. You can see my video around how I've got this configured I'll link that now also Ceph and this is very much aligned to setting up that cluster. Ceph

I've covered extensively on my channel where I run three MSO1s for my cluster. Ceph is the distributed storage that allows me to do that hot failover between my virtual machines. That's because all of the nodes that are in my cluster all share the same Ceph storage. This is kind of a decentralized storage each one has a replica of each of the other's data they all basically replicate in real time so that a machine doesn't really care where it is because it's got access to all the up-to-date data. You can also check out

the storage here and you can also add new storage it supports lots of different storages. You'll also notice here that we can have that Proxmox backup server so we can actually set that up as server. I've got a video on that as well if you want to go and check that out that's still valid. Other things that are probably more relevant to you when you're just starting out you may have a NAS I'll be covering that in a future video so some network attached storage. You can

actually mount NAS storage within Proxmox itself and even then assign that over to virtual machines etc and you can use that specifically for backing up virtual machines manually. To do backups you'd want to create a backup schedule in here and specify which storage you want to use. Most of the other things in here like replication for example need at least two nodes so we can't do that. High availability is

basically the same as well that's what's going to allow you to have multiple nodes within a cluster and then basically if you assign it as highly available it will try to make sure that if one of those nodes goes down it puts it onto the other node to make it highly available. Other things that are in here really we've got some software defined networking stuff which I've done a video on. I probably need to update that it's quite old now and I didn't really go and scratch the surface on that one but what that will allow you to do is basically create software defined networks within Proxmox itself basically like another virtual switch layer etc. There is a firewall as well software firewall within Proxmox that you can use to add some additional rules and security. Don't really find that I need it because I tend to basically route everything through my router but that is an option especially if you're going down sort of a more virtualized route. Other things that are useful but I'm not going to cover in this video are users so you can add multiple users to Proxmox. You could add somebody else so

you want to say be an admin. You can get API tokens as well for your cluster if you're going to plug this into something else. You can set up two-factor authentication, put users in groups, look at pools etc. Give people different roles so when you create a user you have to specify which roles that they've got on your cluster. Obviously this is very much more sort of in the production space not for a home lab but it's great that you get all of these tools to play with and learn from.

So enough of the overview of this let's have a look at the actual node we've got. Remember this is the data center so this is the specific machine that I actually installed Proxmox on and if we go to the summary we should now see that we've got that four times cause for the Intel N150 and we've got 16 gigs of RAM and it's showing 100 gigs of storage space that's the default that the partition size for Proxmox is but if we actually go down on the left here for the disks we should be able to click on the disks and we can see this one here. Actually it's only half a terabyte not a full terabyte but what that means is we've basically got about 400 gigs for all of our virtual machines and containers. So similarly if we have a

quick look through the user interface here you'll see that when we click on one of our machines we get this log down here this is going to show us everything that's going on on the Proxmox host. So for example when you create a virtual machine when you start it up when you shut it down all of that you'll get a nice log here and you can also display more granular detail if you click on the system log here it will show you basically everything that's going on. The cool thing with Proxmox as well is that you can actually have a shell into that machine so before we actually dialed in physically to the machine but here we're using a SSH connection over onto that machine so we can do that as well. You'll also notice now that we have all of the system settings so for example here we'll see the network if you remember back to the installation we had that EMP1S0 that's the physical RJ45 port on this machine and we also had that wireless over here as well which isn't enabled. Now what happens when you install this is it creates a virtual bridge to that physical NIC and when we actually install virtual machines by default it will install it to that VMBR0. We can create additional bridges so we could create another one it automatically enumerates it one higher we can then specify basically the IP address and all of that sort of stuff and then we can assign it to a bridge port we can make it VLAN aware etc. Now you do

need to assign each VMBR each virtual bridge to a physical bridge so we can't actually add another one to this and do note that if you are going to be doing anything with VLANs and I'll come on to that in future videos you will need to make this VLAN aware. If you don't make it VLAN aware when you try and put a virtual machine onto a VLAN the actual VLAN tags won't get passed on it won't understand it and thus you won't get a valid network address you won't get any networking on that device. Certificas are basically where we can add certificates to this machine this is most handy for when you're doing SSH connections to this some of my videos where I've used Ansible to deploy two proxmocks it will use a certificate to connect to it for security reasons and you can here basically specify your own certificate if you want to. DNS is that DNS that I set up during installation you can edit this add more DNS servers if you want to. The host file again similarly is going to show you the host file on this machine you may have to change this if you have some network changes. The updates tab is important and this is basically where you update this machine so if we actually click refresh for the first time and click ok it's going to go away to the Debian repository as well as the proxmocks ones and once that's completed it should show us all the packages that are available for us.

Now as I've just installed this hopefully there aren't too many but even with a fresh install you can see that we've got these packages that are available. To upgrade it's as simple as just hitting the upgrade do bear in mind that a lot of these you will have to restart your hypervisor i.e. proxmocks so if you are running something do bear in mind that it might need to reboot.

Also if you go down the route of installing something like a virtual firewall which I've got videos on as well when you do reboot your hypervisor you're obviously going to be rebooting your firewall as well so that will knock out your network. If we go down to the disks you'll see the disks in here like I mentioned earlier and then you can also see sort of the virtual partitions you've got on there the lvm's the different directories which you can create as well and also zfs if you created that earlier but we know that we didn't. So now that we've gone through the quick summary of our device itself let's go ahead and let's create our first virtual machine. Now the eagle-eyed amongst you probably noticed up here quite handily we've got createvm and we've got createct create a container. We've also got some handy

buttons along the top for rebooting this host, shutting down, accessing the shell etc and also some bulk actions. Now you'll also when we create this virtual machine pay note to what you've actually got selected here if you have the node in this instance selected and you hit shutdown it will shut down the node and all the vms obviously if you want to shut down just the vm make sure you've got the vm selected and then click shut down. Now to create a vm you probably think you hit the createvm button well you do but first of all you need to download an iso file so just like we did for Proxmox itself let's go and pick an iso file let's download that let's get it running. So just say we've got

something to look at here i'm going to download Ubuntu desktop i'll download 2504 just in case we wanted to pass through our iGPU just because this comes with the latest kernel version that does support the iGPU. Most of you will probably be downloading the server version which will just be the command line interface and that's what i predominantly use in my home lab for all of my things like my docker server kubernetes etc. Now what you can do here is just click the download button itself that will obviously download the iso locally and then when you go over to your Proxmox host you can go to where it says local on the left this is local storage and then you can click iso images and then you'll be able to upload it or you might notice this download from url which will cut out one of those steps. So if we click this to start the download that should start if it doesn't we can actually just right click this copy the link address we can cancel the one we've got coming down head over into Proxmox download from the url paste it in hit query and then you can see here it's got that 5.85 so if we hit download

that should now go away and begin that download process i'll see you once that's completed. So now that's completed we should be able to close this down and now we can see here that we've got this iso file available. So now we can click create a virtual machine and we're ready to start the wizard. I recommend you turn on the

advance just so you can see all of the options and you will need this available if you're going to be doing some additional things like adding through hardware etc. Now a good option that it opens up is obviously the startup boot so this means that if ever you reboot your Proxmox server this virtual machine will automatically restart. If you're using something like a firewall virtualized it's a really good idea to have that on otherwise your network's not going to come up automatically. So for this one i'm just going to call this one Ubuntu desktop and we're ready to move on to the next stage. So

for the OS i'm going to choose the one that we just downloaded that's that Ubuntu image there the storage is local later on you can choose different storages for what you want you can also use things like a network share for example and then we get on to the type of operating system it is. So obviously with Ubuntu being a Debian based system as well that's of type Linux and the kernel version is 6.x which it is. You can also choose on here different ones so Microsoft Windows and Solaris kernel. So if you are using something like Windows for example make sure you change the type of guest OS to Microsoft Windows and that'll give it better performance through better emulation. So if we click next we get on to some of the system settings. Now

this is where it can get a little bit tricky and i'll reference again my video for device pass through where i go into this in detail. Basically the default is going to work but the default is not going to give you the best experience especially when you're passing through hardware. In fact when you're passing through hardware you actually want to change this to a q35 device and you also want to change the bios over to a c bios. Now people will say and i've tested it myself things like the i440fx will still work for pass through but it is recommended per the documentation for q35. Because we're not going to be doing any pass through again check my video if you want to go and do that we're going to keep everything as default because i think this is the best way to get this up and running. Do note as well that if you go down the q35 route so things like windows 11 for example it will ask you to start adding tpms and enrolling keys and you probably want to go and read up on that. The best

thing to do really is to kind of add a tpm add some storage but don't auto enroll the key and that usually avoids most of the problems you're going to face. The virtio scuzzy single is going to be fine for this installation. Again if you're using a windows vm if you want to create that it'll often complain about the virtio drivers not being available so typically you're going to have to attach say a usb stick or something like that to your virtual machine when you go through that installation process and have the virtio drivers available. So we're going to click next and then it's going to ask us about the actual disk we want. So i'm going to leave this

as scuzzy in position zero i'm going to create the storage on local lvm which is this one over here. The disk size for this installation 32 gigs is going to be fine for this demonstration but obviously choose something that's going to work for you. You can also expand this later if you start to run out of space so don't worry about that. Now some important settings you want to be able to put on a discard but i believe discard only works when you've got ssd emulation on and what that basically means is it enables smart things like trim which allows it to basically claw back unused space from the virtual machine. So by default the virtual machine will try and claim all of that space but if it's not using it it can actually give it back to the hypervisor or back to another vm if that's also configured in this way. Everything else

we're going to leave as default and we're going to move on. Do note that there are bandwidth settings as well that you can specify for a virtual machine so if you've got say minimum levels of performance that you want for a virtual machine you could obviously go in there and tweak the bandwidth per device per vm. If we hit next we get onto the cpu. Now again there's a lot to take in here but let's try and keep it simple.

For a machine like mine and basically anything that is an enterprise your sockets are always likely to be one i.e you've got one socket on your machine and it has one cpu in it. On enterprise servers you can often get two three or four or even more these days on a motherboard and so as you scale that up you'll notice that you'll have more cores available. So i'm going to put this up to

two just to demonstrate a point. Here you can see that i've got one socket one core and one core available but if i actually put that up to two cores you can see that two cores are now available to that virtual machine. So what that means is it would take one core from each cpu but we know that we only have one cpu so make sure that you actually increase the cores and not the cpu. Now

you need to understand the notion of provisioning through a hypervisor. Now you know that we only have four cores on here so you might be surprised that i could actually set four cores for this virtual machine and you might think well how does the actual hypervisor still have any cores left? Well it's because it's a bit like a timeshare really it tries to allocate and reserve that much cpu or that much compute time and if it's available it will give it to it. It doesn't kind of hard carve that out and say only this virtual machine can use this core. You can actually pin

it and do things like that but by default it's not going to behave like that. One thing if you do have an enterprise server with multiple sockets and you're going to actually use cores from different sockets you probably want to make it numa aware and that's to do

2025-05-16 23:07

Show Video

Other news

【离限户外】巅峰对决 2025！vivo X200 Ultra、OPPO Find X8 Ultra 、小米 15 Ultra 户外综合体验 2025-06-03 01:19

The Engine of Our Dreams Exists. It's a Clean, Powerful, Supercharged and Rotary Valved Two Stroke 2025-06-01 10:00

Nvidia CEO Slams US Chip Rules, Trump’s AI Action Plan | Bloomberg Technology 2025-05-26 20:00