# DPAA Passthrough to VM

**URL:** <https://community.solid-run.com/t/dpaa-passthrough-to-vm/752>\
**Category:** NXP LX2160\
**Created:** [November 1, 2023, 1:21pm UTC](https://community.solid-run.com/t/dpaa-passthrough-to-vm/752 "2023-11-01T13:21:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![matta](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@matta](https://community.solid-run.com/u/matta)\
**Post date:** [November 1, 2023, 1:21pm UTC](https://community.solid-run.com/t/dpaa-passthrough-to-vm/752/1 "2023-11-01T13:21:18Z")

</div>

Utilizing the linux-qoriq kernel along with the qemu-qoriq from NXP, I seem to be having issues with DPAA resource passthrough. I’m able to add network interfaces to the hypervisor and use, but once I pass the resources in a DPRC to a VM, the interfaces become unusable. I’m able to see frames hitting the interfaces with restool but no traffic is being sent. What seems odd is that there’s no errors being thrown in the guest, hypervisor, or MC firmware.

Any feedback or paths to chase down about how to identify where the issue is?

---

<div class="post-metadata">

**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\
**Post date:** [November 3, 2023, 6:25am UTC](https://community.solid-run.com/t/dpaa-passthrough-to-vm/752/2 "2023-11-03T06:25:35Z")

</div>

> [@matta](#):
>
> qemu-qoriq

Which tag release are you using of qemu-qoriq?

---

<div class="post-metadata">

**Author:** ![matta](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@matta](https://community.solid-run.com/u/matta)\
**Post date:** [November 3, 2023, 11:58am UTC](https://community.solid-run.com/t/dpaa-passthrough-to-vm/752/3 "2023-11-03T11:58:29Z")

</div>

Not using a tagged released, but I am using commit `14fda5a42df6c72e890d6a97ff88c5852172604b` from the `qemu-4.2` branch with the `lf-5.15.y` branch of linux-qoriq as paired in NXP’s kirkstone branches of their Yocto SDK.
