The following errors always appear in the compute container log:

{"component":"virt-launcher","level":"error","msg":"internal error: Unable 
to get session bus connection: Cannot spawn a message bus without a machine-id: Unable to load /var/lib/dbus/machine-id or /etc/machine-id: Failed to open file “/var/lib/dbus/machine-id”: No such file or directory","pos":"virGDBusGetSessionBus:126","subcomponent":"libvirt","thread":"38","timestamp":"2024-12-29T08:44:16.323000Z"}

{"component":"virt-launcher","level":"error","msg":"internal error: Unable to get system bus connection: Could not connect: No such file or directory","pos":"virGDBusGetSystemBus:99","subcomponent":"libvirt","thread":"38","timestamp":"2024-12-29T08:44:16.323000Z"}


We need to find a way to resolve them 

All

100%

1. Launch a VM
2. Locate the virt-launcher pod
3. Observe the compute container log
4. You should see the errors