Skip navigation
McAfee Secure sites help keep you safe from identity theft, credit card fraud, spyware, spam, viruses and online scams
742 Views 3 Replies Latest reply: Mar 20, 2013 1:26 AM by skloepping RSS
dtomko Newcomer 11 posts since
Mar 15, 2013
Currently Being Moderated

Mar 15, 2013 6:22 AM

Virtual appliance best practices

What would be best options to configure virtual appliances. i.e. vmware virtual machine settings for MWG 7.x.

First, i would like to ask about type of networking adapter: is vmxnet3/2 supported by MWG 7? Will I get any performance gain changing adapter type?

What about virtual disk types?

Any other conderations(number of cores per socket, ....)?

  • prajoshgeorge Apprentice 66 posts since
    May 9, 2012
    Currently Being Moderated
    1. Mar 17, 2013 1:55 PM (in response to dtomko)
    Re: Virtual appliance best practices
  • skloepping McAfee SME 28 posts since
    Jan 17, 2013
    Currently Being Moderated
    3. Mar 20, 2013 1:26 AM (in response to dtomko)
    Re: Virtual appliance best practices

    Hey dtomko,


    for a general and supported setup you may want to cionsult our Product Guide:


    Web Gateway 7.3.1 Product Guide


    Requirements for setting up a virtual appliance

    To set up a virtual appliance, the following is required:

    • One of the following VMware types:

    • VMware ESX

    • VMware ESXi

    VMware Workstation version 5.5 or later is not supported, but can be used for testing purposes.

    • Virtual machine host system with the following specifications:

    • CPU — 64‑bit capable

    • Virtualization extension — VT‑x/AMD‑V

    • Virtual machine with the following specifications:

    • Memory — 4 GB

    • Hard disk space — 200 GB

    • CPU cores — 2 (minimum)


    Saying that i would have to say that the sizing really depends on your setup, needs, deployment, rule sets, used features (SSL Scanner) and so on. The only thing i would recommend is not to use web cache in a virtual environment which could(!) lead to I/O Performance issues. But as always, there is no general "do not do that" rule.


    Network cards: E1000 | VMXNET 3 are supported, say i would suggest to use vmxnet3 cause this drivers onloads a bit more of cpu usage from the VM to the hypervisor.


    Disk: BusLogic Controller (recommended) but LSI Logic Controller is also supported. Thin or Thick provisioning? Well, i would always go thin if your storage is capeable of doing the realy I/O work.


    Best Regards


More Like This

  • Retrieving data ...

Bookmarked By (1)


  • Correct Answers - 5 points
  • Helpful Answers - 3 points