VMware Workstation Player course

How to Specify Packet Loss Percentage in VMware Workstation Player

Configure incoming and outgoing packet loss for a VMware Workstation Player network adapter, test it with ping, interpret results, and restore normal connectivity.

What packet-loss simulation does

Packet loss occurs when packets sent across a network fail to reach their intended destination. Applications may then encounter delayed responses, retries, timeouts, incomplete transfers, or disconnected sessions.

VMware Workstation Player can deliberately drop a percentage of traffic associated with a selected virtual network adapter. This is useful for testing application reliability, retry logic, timeout handling, error messages, and connection recovery without waiting for an unreliable physical network.

Incoming packet loss affects traffic traveling toward the guest operating system. Outgoing packet loss affects traffic leaving the guest. The settings apply to the selected virtual adapter, not automatically to every adapter in the virtual machine.

Prerequisites

  • Basic familiarity with VMware Workstation Player and virtual machine hardware settings.
  • A guest operating system with a working network connection.
  • Access to a reachable test endpoint.
  • A way to run ping or another application-level connectivity test inside the guest.

For background, see Networking Configurations Overview and Virtual Machine Explained.

Open the network adapter settings

  1. Power off the virtual machine. VMware may require the VM to be powered off before virtual hardware configuration can be changed.
  2. In VMware Workstation Player, select the virtual machine you want to test.
  3. Open the VM's settings.
  4. Select Network Adapter from the virtual hardware list.
  5. Open the adapter's Advanced settings. The packet-loss controls are available in this area in supported product versions.

The configuration path is:

Virtual machine settings > Network Adapter > Advanced settings > Incoming Packet Loss and Outgoing Packet Loss

Configure incoming and outgoing packet loss

Enter a whole-number percentage in each field. Use values appropriate to the test condition, such as 0, 1, 5, or 50 percent. The exact labels can vary slightly between VMware Workstation Player versions.

Setting: Incoming packet loss
Traffic direction: Toward the guest VM
What the percentage simulates: The percentage of packets arriving at the guest that the simulation drops
Typical test use: Testing missing responses, incomplete inbound data, and recovery when traffic received by the application is unreliable

Setting: Outgoing packet loss
Traffic direction: From the guest VM
What the percentage simulates: The percentage of packets sent from the guest that the simulation drops
Typical test use: Testing lost requests, failed uploads, and behavior when the guest cannot reliably transmit data

Incoming packet loss

Set Incoming Packet Loss to the percentage of traffic traveling toward the guest that should be dropped. For example, an incoming value of 50% means that roughly half of the simulated inbound packets may be discarded before the guest processes them.

Outgoing packet loss

Set Outgoing Packet Loss to the percentage of traffic leaving the guest that should be dropped. An outgoing value of 50% causes roughly half of the guest's outbound packets to be discarded.

Different values create an asymmetric network impairment: inbound and outbound traffic have different simulated conditions. For example, incoming loss with outgoing loss set to zero is useful when testing whether an application handles missing responses while still being able to send requests normally.

Choose a packet-loss percentage

Loss percentage: 0%
Test severity: No intentional loss
Expected behavior: Normal connectivity, subject to real network conditions
Recommended use: Baseline and final verification

Loss percentage: Small percentage
Test severity: Moderate loss
Expected behavior: Most traffic succeeds, but occasional retries or timeouts may occur
Recommended use: Testing resilience to intermittent network problems

Loss percentage: 50%
Test severity: Severe loss
Expected behavior: Frequent failures and timeouts in the affected direction
Recommended use: Stress-testing retry, timeout, and recovery behavior

The configured percentage is a target rate for simulated dropping, not a promise that every short test will show exactly that percentage. Loss is probabilistic, so a test of only a few packets can produce a result well above or below the configured value.

A useful severe bidirectional configuration is:

Incoming Packet Loss: 50%
Outgoing Packet Loss: 50%

To test failures affecting traffic received by the guest while leaving outbound traffic unaffected, use:

Incoming Packet Loss: 50%
Outgoing Packet Loss: 0%

Save the settings and test from the guest

  1. Save or apply the virtual machine configuration.
  2. Start the guest operating system.
  3. Open a terminal or Command Prompt inside the guest.
  4. Send multiple connectivity probes to a known reachable endpoint.
  5. Review the number sent, received, lost, and the calculated loss percentage.

On Windows, this command sends ten ICMP echo requests:

ping 8.8.8.8 -n 10

Ping is a diagnostic utility that sends ICMP echo requests and reports replies, latency, timeouts, and packet-loss statistics. A Linux guest commonly uses:

ping -c 10 8.8.8.8

When loss is enabled, output may contain successful replies mixed with timeout messages. On Windows, a missing reply commonly appears as Request timed out. These timeouts are expected when the simulation drops packets.

Example interpretation

Suppose both directions are set to 50%. A short run might report 10 packets sent, 4 received, and 6 lost, or it might report a different split. That result does not mean the setting was ignored; the sample is small and the drops are probabilistic.

For more representative results, send more packets or repeat the test several times. For application testing, also record request duration, retry count, timeout errors, and whether the connection recovers.

Interpret ping results correctly

Distinguish between the configured packet-loss target and loss measured during one test run. The configured value controls intentional simulation on the selected adapter. The measured value is the outcome of a particular sample and can also include other causes of failure.

  • The external network may already be unstable.
  • The destination may be overloaded or unreachable.
  • A firewall may block ICMP.
  • The destination may deliberately ignore ping requests.
  • The guest may have an invalid address, gateway, route, or adapter connection.
  • Different application protocols may respond differently from ICMP.

Because ping uses ICMP, a ping failure does not always prove that application traffic is failing. Use an application-specific test or a controlled local endpoint when consistent measurements are important.

Restore normal connectivity

  1. Power off the VM if required to edit its virtual hardware.
  2. Return to Network Adapter > Advanced settings.
  3. Set both fields to zero:
Incoming Packet Loss: 0%
Outgoing Packet Loss: 0%
  1. Save the configuration and start or restart the guest as needed.
  2. Repeat a connectivity test and confirm that intentional packet loss is no longer applied.

Document the VM, adapter, inbound percentage, outbound percentage, test endpoint, packet count, guest operating system, and test results. This makes QA runs reproducible.

Troubleshooting

No packet loss appears after entering a nonzero value

  • Verify that the settings were saved or applied.
  • Confirm that you edited the intended VM and the correct network adapter.
  • Restart the guest or disconnect and reconnect the virtual adapter if the changed configuration has not taken effect.
  • Run a longer or repeated test; a very short test may not make random loss obvious.

The observed percentage does not match the configured percentage

  • Use more packets and compare multiple runs.
  • Treat the configured percentage as a target rate rather than an exact result for every short sample.
  • Test against a controlled local endpoint to reduce unrelated network loss.

Ping reports complete loss with a low setting

  • Test a known reachable endpoint or an internal host.
  • Check the guest's IP address, gateway, route, DNS where relevant, and adapter connection state.
  • Check whether a firewall or destination policy blocks ICMP echo requests.
  • Verify that neither packet-loss field was accidentally set very high.
  • Temporarily set both values to 0% to separate intentional loss from an underlying connectivity problem.

Only some application operations fail

  • Review whether inbound and outbound percentages are different.
  • Test symmetric and asymmetric configurations separately.
  • Collect application logs, timeout data, and retry behavior; application protocols do not necessarily react to loss like ping does.

Exam-relevant notes

  • Incoming loss means traffic toward the guest; outgoing loss means traffic leaving the guest.
  • The settings affect the selected virtual network adapter.
  • Packet loss is simulated probabilistically, so a short measurement may not equal the configured percentage.
  • Use 0% in both directions for a normal-connectivity baseline and after the experiment.
  • Ping relies on ICMP, which may be filtered independently of other network traffic.

For related virtual networking tasks, see How to Limit Network Bandwidth for a VM and Networking Configurations Overview.