# Troubleshooting

## General Troubleshooting

For any issues related to HVM network plugin, view the HPE Morpheus appliance logs. For details, see [Viewing plugin logs](https://support.hpe.com/hpesc/public/api/document/sd00008058en_us/render?page=GUID-48D8879A-1DFF-404F-BF15-E78FDA70A07F.html#GUID-48D8879A-1DFF-404F-BF15-E78FDA70A07F__SECTION_N4X_GCF_3JC).

## New Host Does Not Receive Networks

A new host may fail to receive networks if Morpheus has not completed host discovery or if required interfaces are not yet available for propagation.

Morpheus must discover the host interfaces before it can propagate network definitions. If bond interface discovery remains incomplete, Morpheus cannot complete network mapping for the host.

Perform the following:

- Check for pending **AddWorker** jobs.
- Confirm that Morpheus has discovered all required bond interfaces on the host.
- Verify that the host inventory reflects the expected network interfaces before propagation begins.

If the issue persists, check the following:

- Check whether the **AddWorker** workflow has reached the retry limit.
- Review Infrastructure > Activity for related alarms, retry exhaustion events, or propagation failures.

## SR-IOV PCI Device Reports “In Use by Driver QEMU”

This issue usually indicates stale virtual function tracking in libvirt.

Libvirt can lose accurate VF tracking after:

- VM clone
- VM backup
- VM restore

When this happens, libvirt may continue to report that a PCI device remains in use even though the device should be available.

## SR-IOV Network Fails to Create During Initial Setup

A new SR-IOV network usually fails to create when one or more host prerequisites remain incomplete.

- Verify that the host BIOS or UEFI enables **SR-IOV**.
- Confirm that you set `sriov_numvfs` on the correct physical function.
- Ensure that AppArmor allows **VFIO** device access on each host.
- Confirm that the physical function exposes SR-IOV capability on each host:

  ```
  ```
  /sys/class/net/*/device/sriov_totalvfs
  ```
  ```

## Data Network Jumbo Packets Fail

A network MTU change does not automatically update the guest operating system. Jumbo packet traffic also fails if any segment in the end-to-end path uses a lower MTU value.

Jumbo packet failures usually result from inconsistent MTU settings across the VM, guest operating system, and physical network path.

Perform the following to resolve the issue:

- Stop and start the VM after changing the MTU.
- Set the MTU on the guest interface manually:

  ```
  ```
  ip link set <iface> mtu 9000
  ```
  ```
- Verify that the connected switch port also uses MTU `9000`
