You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2022-05-06 03:38:51,501: vrnetlab INFO Unable to connect to qemu monitor (port 4000), retrying in a second (attempt 1)
2022-05-06 03:38:52,502: vrnetlab INFO Unable to connect to qemu monitor (port 4000), retrying in a second (attempt 2)
2022-05-06 03:38:53,503: vrnetlab INFO Unable to connect to qemu monitor (port 4000), retrying in a second (attempt 3)
Please help.
The text was updated successfully, but these errors were encountered:
Always include the complete command you ran and the full log output.
It seems you have some issue with KVM, so that is what you should troubleshoot. That the launch script cannot connect to qemu monitor is completely natural if the virtual machine is having some KVM related problem and thus won't start.
I was running vrnetlab on Rocky Linux 9.2, so my problem was vrnetlab couldn't find qemu-system-x86 which is qemu-kvm in Rocky Linux, I solved by creating a symbolic link.
While creating a "vr-vmx" from repo "https://github.com/vrnetlab/vrnetlab" and using Juniper KVM image - 18.2, I received the following Error
failed to initialize KVM: Device or resource busy
2022-05-06 03:38:51,501: vrnetlab INFO Unable to connect to qemu monitor (port 4000), retrying in a second (attempt 1)
2022-05-06 03:38:52,502: vrnetlab INFO Unable to connect to qemu monitor (port 4000), retrying in a second (attempt 2)
2022-05-06 03:38:53,503: vrnetlab INFO Unable to connect to qemu monitor (port 4000), retrying in a second (attempt 3)
Please help.
The text was updated successfully, but these errors were encountered: