No worries, I am/was interested from the technical perspective. I would say it is not recommended anyway, but that is just my opinion. Especially if you are considering some of more "advanced" cloud antivirus that caused world wide outage in the past.I need to install antivirus software on PVE unless I can provide evidence that it's not possible or recommended. Sorry I can't be more specific.
Search the form if your one find a statement.Hi,
Is there an official statement from Proxmox regarding the installation of antivirus software on PVE?
Does this installation affect the license and support provided?
Thanks!
I am not convinced of the supreme benefit of adding an antivirus to a hypervisor; it is really more a question of ticking a box, yes.In order to answer this question seriously, we would need to know exactly which antivirus product OP intends to install.
@NPK If you're talking about a classic AV scanner like ClamAV:
I’d consider that mostly useless on a virtualization host, because normally you wouldn’t upload random files to the host itself. And if you do upload untrusted files to the host, then you’re already in unsupported territory, and the activities that lead you to believe you need antivirus on the host are probably the much bigger issue.
If by “antivirus” you actually mean general security hardening or third-party security tools, they'd likely need to know which specific software you’re referring to. In that case, it would probably be best to open a support ticket and ask the Proxmox team directly whether they support the tool you want to use — or consider proper security consulting for Proxmox and Linux in general.
Long story short: Your question is too vague to answer with a simple “yes” or “no.” And if I had to guess, I’d say this is more about checking some compliance boxes for management than about actual security.
I can't imagine ClamAV being a problem for Proxmox or their support, as it is a standard Debian package.
Saying what?Is there an official statement from Proxmox regarding the installation of antivirus software on PVE?
I have no idea what that means, an anti virus is only applicable to its host operating system especially if monitoring RAM. a windows av is of no purpose if you're running PVE and vice versa- there is no such thing as "antivirus platform"Linux is an inferior antivirus platform. If you want to run your antivirus really well, the best bet is to install Windows.
Windows is a largest virus platform. Therefore it is also the largest anti-virus platform. Even Linux anti-virus products mostly check for Windows viruses. Which makes sense if you're serving files to Windows users. On a Linux-based hypervisor it is just useless overhead.I have no idea what that means, an anti virus is only applicable to its host operating system especially if monitoring RAM. a windows av is of no purpose if you're running PVE and vice versa- there is no such thing as "antivirus platform"
If you're asking to add AV into the scope of PVE, say so. if you're not, what possible reason would the devs have to even have a position? like you pointed out, its just Debian- if you can run it on debian you can run it on PVE.The question whether this is supported can only be answered by Proxmox Server Solutions GmbH.
Anything monitoring memory in real time is going to have a significant impact on performance. no way around that. just understand and prepare for that if your use case requires that level of intrusion. it may also have unintended consequences.Another question is whether running Antivirus on PVE is a good idea
@Johannes S was not the one asking this question.If you're asking to add AV into the scope of PVE
You don't need antivirus software on a virtualization host at all. Unless you grant the trainees, the receptionist, and the CEO root access to your production hosts. ;-)Anything monitoring memory in real time is going to have a significant impact on performance. no way around that. just understand and prepare for that if your use case requires that level of intrusion. it may also have unintended consequences.
I dont monitor in memory for the above reason. instead I have strict adherence rules to Lynis and an active IPS/IDS. more then one way to skin a cat.
We use essential cookies to make this site work, and optional cookies to enhance your experience.