diff --git a/overcloud-resource-registry-puppet.j2.yaml b/overcloud-resource-registry-puppet.j2.yaml
index fe892c33e9..3b6c4a455f 100644
--- a/overcloud-resource-registry-puppet.j2.yaml
+++ b/overcloud-resource-registry-puppet.j2.yaml
@@ -174,6 +174,7 @@ resource_registry:
   OS::TripleO::Services::NovaCompute: deployment/nova/nova-compute-container-puppet.yaml
   OS::TripleO::Services::NovaConductor: deployment/nova/nova-conductor-container-puppet.yaml
   OS::TripleO::Services::NovaLibvirt: deployment/nova/nova-modular-libvirt-container-puppet.yaml
+  OS::TripleO::Services::NovaLibvirtLegacy: deployment/deprecated/nova/nova-libvirt-container-puppet.yaml
   OS::TripleO::Services::NovaLibvirtGuests: deployment/nova/nova-libvirt-guests-container-puppet.yaml
   OS::TripleO::Services::NovaManager: deployment/nova/nova-manager-container-puppet.yaml
   OS::TripleO::Services::NovaMetadata: deployment/nova/nova-metadata-container-puppet.yaml
diff --git a/releasenotes/notes/nova_compute_el8_legacy-273fb004d090191a.yaml b/releasenotes/notes/nova_compute_el8_legacy-273fb004d090191a.yaml
new file mode 100644
index 0000000000..ede27f3c12
--- /dev/null
+++ b/releasenotes/notes/nova_compute_el8_legacy-273fb004d090191a.yaml
@@ -0,0 +1,10 @@
+---
+upgrade:
+  - |
+    For Nova computes that need to keep running EL8, you can replace
+    ``OS::TripleO::Services::NovaLibvirt`` service with
+    ``OS::TripleO::Services::NovaLibvirtLegacy`` in its role files to run the
+    monolithic libvirt. Unlike the modular deamons consumable with EL9
+    computes, that legacy service should only be used for Train to Wallaby
+    skip-level (fast-forward) upgrades, and should not be used in new
+    deployments.