To Reproduce Steps to reproduce the behavior:

1. Deploy an OSP17.1 cluster using OSP director operator. The OSP17.1 cluster has one compute node enabled for SR-IOV networking and one compute node enabled for DPDK based networking
2. Create one test VM for SR-IOV networking and one test VM for DPDK networking. Ensure that the VMs can be pinged
3. Adopt the OSP17.1 cluster to RHOSO 
4. Once control plane and data plane have been adopted (including the FFU procedure for data plane nodes), ensure that the existing VMs can still be pinged
5. Once control plane and data plane have been adopted (including the FFU procedure for data plane nodes), try to create new VMs with SR-IOV and DPDK networks
6. Failed to create either VM for SR-IOV or DPDK based networking
7. For the VM with DPDK networking, I see the following error
   1. 2025-03-10 18:06:12.609 2 ERROR nova.compute.manager [None req-0dd9b949-3bc1-4b2e-ac69-748da6a6d67a d433ff847a994572a63ff8c6c2743584 1766542687974d2696958f56f7aa084b - - default default] [instance: df9f3d34-9dda-4c12-ae9a-02bb4066b22a] Failed to build and run instance: libvirt.libvirtError: Failed to connect socket to '/run/libvirt/virtlogd-sock': Connection refused 2025-03-10 18:06:12.609 2 ERROR nova.compute.manager [instance: df9f3d34-9dda-4c12-ae9a-02bb4066b22a] Traceback (most recent call last):
8. The SR-IOV VM also fails to create. Will file a different bug for that

Expected behavior

• VM with DPDK based networking should be successfully created

Bug impact

• Cannot create new virtual machines after adoption to RHOSO

Known workaround

• None