Hi this was a brilliant video; if I may please ask. I have a Mikrotik Hex being used as a Switch which has 5 ports. 1 port will be used as a trunk from Proxmox, and the other 4 as access ports which are connected to physical devices, like laptops, wifi ap etc. Here’s the question; I want to create 3 additional VLANs with will only have Containers / VM. Am I required to add these 3 new VLANs to the Tik even though these VLANs are only for the Containers / VMs, and not physical devices.
i didnt have any free space sadly so I just used : sysctl -w vm.swappiness=10 And fixed my issue of 100% swap usage for 2 vms on 96gb of ram 32 CPU 6tb of storage. very strange.
Love it. I struggle with keeping up with edits required on old proxmox version, but seemingly unnecessary on 8.0 or above. Catching up with those by doing lots of grunt work. On your last edit of the grub file, I found an “update-grub” saves you a reboot. But the back of mind still questioned it. Lots and lots of reboot in a new setup…one less was the selling point. BUT I still did the reboot…IT norms 101 law! 😊
I just bought this same laptop and I'm still faced with the same error message. I've gone into the bios and intel (vmx) virtualization technology is enabled. How do I solve this issue
Proxmox specifications are on the official site here: www.proxmox.com/en/proxmox-virtual-environment/requirements On the error, you may need to enable Virtualization Technology on the host as a guess. You are best off googling the error message.
You may wish to live migrate a VM in any clustered hypervisor environment if you have service level agreements that you need to comply with. Updates / reboots will impact on recorded SLA stats, so moving the service onto unaffected hosts helps to maintain this.
I love videos like this! I have watched many video tutorials where the user has edited out failed attempts to appear flawless. Showing failed attempts can sometimes reveal issues that a viewer might also be confronted with. You have a new subscriber!
Would you also make a video in which you use the Proxmox API key and the secret, because the ticket expires after 2 hours and I don't want to renew it permanently and haven't yet managed to build a working query with it in Hoppscotch (Postman alternative).
Thank you very much for your videos the content is great you are helping people understand and navigate an amazing piece of software thumbs up for your dedication to proxmox. 👍
Very good content, it's hard to find a lot of dedicated videos to proxmox and I think understanding multiple areas of it is important. These videos are what we need keep up the good work. Give thumbs up 👍 people
Please keep making videos I think your channel will grow, I love proxmox I am newer to it even things I'm familiar with I still watch your video, I'm going to like all of your vids and try to get the algorithm going come on people push the like 👍
The nice thing about Proxmox is that the compatibility list is pretty much most hardware that will run x64. For the best notebook, other than "the one you have", I would go for as much RAM as you can afford together with an SSD disk if possible. Notebook hardware typically doesn't get to benefit from RAID 0 (or other RAID config) IO parallelization where the disk cache can give you a bit of speed boost even on HDDs. As such, putting some money into an SSD will help the machine perform better, even if it is just for test lab stuff as I'm doing.
Aww... I only clicked, because I thought you were going to tell us which chassis you were using in the thumbnail. Just FYI the instructions are available on their website, so what's this video add to what is already available without helping advertisers destroy the internet? Just more noise cluttering up my search results and suggestions.
The user/group filter appears to use LDAP filter formatting. For example, a user filter: (&(!(sAMAccountName=*$))(!(useraccountcontrol:1.2.840.113556.1.4.803:=2))) should filter out machine names (ending with $) and disabled accounts
A nice addition would be to mention the command pveam update (so you have to go cli first) which refreshes the templates to their latest versions, or add new ones as well. Also none takes the time to mention at least the danger of creating privileged containers, since it is more close to host's resources than a VM and the possible hack could lead directly to proxmox.
Thanks - I will take a look at the pveam update command. I am aware of the dangers of privileged containers, but it is a bit outside the scope of a quickstart video. I might have a look at this in a "what not to do" video in future.
Yes thank you so much keep making proxmox videos I love videos related to proxmox I've been using it for a few months its my new favorite base OS, please keep up the great work
thank you for this video. I’m studying a CCNA guide while trying to set my homelab up and it’s really cool to see new ways to do things. Keep up the great videos (Also thanks for keeping your troubleshooting process in, I learned a lot.)
No specific reason - could just as easily be the other way around. It doesn't matter which way around you choose in a virtualized environment like in this demo, but may have an impact on some software licensing costs (per socket is a cost in some cases). The point is not to use a 1 core 1 socket CPU as most operating systems are designed for more than this.
I've used VMware's V2V converter previously, if this is what you mean. If you mean can you import via VMware's vCenter - I don't believe this is supported as you are mounting from the ESXi servers directly.
From a virtualization one, there isn't one in terms of performance - but the number of sockets vs cores can impact on some software licensing costs, so what you choose will be subjective or driven by what software you are running and how it is charged for. From an operating system perspective, most modern OSs are expecting to be more than a single CPU core (unlike back in the days of Windows 95!). I would always tend to set the sockets/cores to more than one, but not too high or it becomes difficult for the hypervisor to schedule the VM to run as it needs an available slot for each core. The more cores you have, the harder this will be for the VM to be scheduled, and in fact the slower the VM will be.
Fair point - poor terminology on my part. I've edited the previous response - I'm referring to operating systems running on more than one CPU core. Modern operating systems typically support more than one, so I prefer to set them as such. In virtualisation, it doesn't make a lot of odds in terms of performance whether you increase the socket or core count - there's some more info here: pve.proxmox.com/pve-docs/pve-admin-guide.html#chapter_virtual_machines
