I understand that those are best practices, but those specs are difficult or too costly for most who are building a homelab, remember that for most it's just a hobby or a learning tool, so the costs matter.
Yeah, that will be fine for the boot drive.
Not sure what system you'll be running the setup on, but for a homelab, you really want to be running the VM's / CT's guest on SSD or better NVMe drives, SATA drive are just too slow for anything...
Are you able to set the Buffalo as a PVE storage device? If so you can select which types of storage that is advertised as within the PVE environment. i.e. backup / OSO store / templates etc. A PVE storage device can use any of the common...
NAS system 'need' control of the complete disk. You therefore need to pass the drives (or better the controller) through to whatever NAS implementation you use, and then share the space to your servers/applications.
That is the correct method...
I have QTY7 Proxmox nodes running on single SSD/NVMe drives in my Homelab, for approx. 4 years now. I do keep meticulous triple PBS backups of the guests, and figure that if the Proxmox host drive fails it's simple enough to rebuild, with the...
Are you guys using the Realtek drivers for those USB NIC's?
The Debian / Proxmox OS defaults to the cdc network drivers. It's been a while but I understand that the Realtek drivers can be in installed via DKMS package.
I believe that the...
I suggest once again that people evaluate the Pulse monitoring app, which uses the Proxmox api to monitor not only the temps, but the CPU/RAM/Disk/Backups/hosts/docker apps etc. on a single pane of glass, right across your estate. They have made...
Hi everyone,
I updated ProxMox to version 9.1.2 today.
I was wondering if there was still a solution for my HD530 iGPU in my Intel Core i7 6700T CPU, which worked great up to ProxMox 8.x.x.
I've seen some solutions for N100 and N150 processors...
The helper scripts are great (I have approx. 20 running in my homlab), but they are susceptible to break on OS or the underlaying package updates.
If you are going with OMV I would highly suggest running it in a VM with the drives passed through...
Just to add some input into the conversation, I use the 'Pulse' monitoring app to keep an eye on Proxmox, it plugs into the Proxmox api to provide all the info you need, works with clusters, docker, hosts, PBS, the works, complete with user...
I use OMV (even though I have 2x TrueNAS installs) as it's light on resources and plays nicely with USB drives, they can be temperamental + I didn't want the overhead of the zfs file system. I would suggest that you ensure that you have a...
I just tested it and confirmed it was wrong, so I've corrected it.
Since pre-stop is not executed, it is maintained by vfio-pci, but it seems correct to say that “even if bound to vfio-pci, the VM boots normally, so no one cares.”
On my Proxmox...
I had the issue with both Windows and Linux. My revision also got it working smoothly with both.
Thanks for the link, I'll follow those steps should my revised hookscript stop working.
Oh, I'm sorry, I'm sure I read that as 3.1.
If you can connect to the web interface OK, are you able to perform the system updates? If not that might indicate an incorrect DNS setting, or the Repositories set incorrectly.
I had pfSense running...
In addition to the hookscript on Proxmox, you also need 'reset mod' inside the guest OS, that is the only way the the guest can reset the GPU prior to shutdown/reboot.
You've not stated if the guest is Windows or Linux but I found the following...
Not so confusing, your private subnet 192.18.1.0/24 addresses the IP range from 192.168.1.1 to 192.168.1.254, so if you fix the IP of the Proxmox node to 192.168.3.1 it is sitting outside of your IP range and thus unable to communicate with the...
Sorry for the delay, I need to make some downtime available to get the information requested as the TrueNAS running on that node is critical to multiple applications in my lab.
There is nothing about the bare metal & 10TB until I asked.
Therefore the post comes across as if you are trying to squeeze a Proxmox installation complete with VM stores, onto a single 60GB drive.!
That requirement is so very different from everything indicated in this threat. Why on earth are you trying to squeeze every MB out of a 60GB drive, if I were in your shoes I would only consider that drive for the root, and ignore whatever space...