Hi, first time user here.
So, I've got pfSense running in one VM, and that's working fine. I installed minimal CLI CentOS to the second VM. And something must be wrong there because sometimes the CPU gets up to 100%, memory usage get up to about 3.5 GB (I allocated 4). Performance and responsiveness in general are just atrocious.
Here are the details:
Core 2 Duo CPU (an oldie, I know, but it supports VT-x. has 2 cores)
I used all the default settings when creating the VM. I tried using both the 'kvm64' and the 'host' CPU settings, and only one core is allocated.
Again this is just bog standard clean slate CentOS, I have nothing special going on yet, though I did yum update and reboot.
The networking I was unsure about, and perhaps a possible culprit. (Although it does connect to the internet perfectly fine.) In the VM setup, I set the bridge to vmbr0, which is the same bridge that I use for proxmox. I have 3 NICs: one is for pfsense WAN (vmbr1) one is for pfsense LAN (vmbr2), and the other one (vmbr0) is for connecting directly to proxmox, so I have an IP address, subnet, gateway set for it. For CentOS, I set it to also use vmbr0, but I gave it a different IP address. Is that correct, or do I need to make another bridge for it? Or set it to the same one as the LAN? Again, the internet does work, but I didn't know if maybe the CPU and memory were skyrocketing because maybe the packets were getting confused or something? Or maybe it's something totally unrelated. When I look at 'top', the memory is all locked up in buff/cache, and the CPU just shows the normal system processes (or 'yum' if that's what I'm running at the time). ... I would blame it on the age of the CPU, but pfsense never gets above about 50% usage, and it's actually doing work.
So, I've got pfSense running in one VM, and that's working fine. I installed minimal CLI CentOS to the second VM. And something must be wrong there because sometimes the CPU gets up to 100%, memory usage get up to about 3.5 GB (I allocated 4). Performance and responsiveness in general are just atrocious.
Here are the details:
Core 2 Duo CPU (an oldie, I know, but it supports VT-x. has 2 cores)
I used all the default settings when creating the VM. I tried using both the 'kvm64' and the 'host' CPU settings, and only one core is allocated.
Again this is just bog standard clean slate CentOS, I have nothing special going on yet, though I did yum update and reboot.
The networking I was unsure about, and perhaps a possible culprit. (Although it does connect to the internet perfectly fine.) In the VM setup, I set the bridge to vmbr0, which is the same bridge that I use for proxmox. I have 3 NICs: one is for pfsense WAN (vmbr1) one is for pfsense LAN (vmbr2), and the other one (vmbr0) is for connecting directly to proxmox, so I have an IP address, subnet, gateway set for it. For CentOS, I set it to also use vmbr0, but I gave it a different IP address. Is that correct, or do I need to make another bridge for it? Or set it to the same one as the LAN? Again, the internet does work, but I didn't know if maybe the CPU and memory were skyrocketing because maybe the packets were getting confused or something? Or maybe it's something totally unrelated. When I look at 'top', the memory is all locked up in buff/cache, and the CPU just shows the normal system processes (or 'yum' if that's what I'm running at the time). ... I would blame it on the age of the CPU, but pfsense never gets above about 50% usage, and it's actually doing work.