KKwang Posted July 20, 2022 Share Posted July 20, 2022 (edited) I got a issue that vm crash and no reponse for everything. At this moment, I can't open the unraid webui --> VM, no response for the browser. Other papge is OK at the same time. So I go to setting and stop the VM function. And then, I start VM function again. But I can't manager the VM in the webui which show as the screenshop. Libvrit service can't start. The only way to fix is reboot the unraid. What's the problem? How can I fixup without reboot the whole server. I try to restart the libvirt but fail. root@AIO:~# /etc/rc.d/rc.libvirt restart error: failed to connect to the hypervisor error: Operation not supported: Cannot use direct socket mode if no URI is set error: failed to connect to the hypervisor error: Operation not supported: Cannot use direct socket mode if no URI is set error: failed to connect to the hypervisor error: Operation not supported: Cannot use direct socket mode if no URI is set error: failed to connect to the hypervisor error: Operation not supported: Cannot use direct socket mode if no URI is set error: failed to connect to the hypervisor error: Operation not supported: Cannot use direct socket mode if no URI is set error: failed to connect to the hypervisor error: Operation not supported: Cannot use direct socket mode if no URI is set error: failed to connect to the hypervisor error: Operation not supported: Cannot use direct socket mode if no URI is set error: failed to connect to the hypervisor error: Operation not supported: Cannot use direct socket mode if no URI is set error: failed to connect to the hypervisor error: Operation not supported: Cannot use direct socket mode if no URI is set Stopping libvirtd... error: failed to connect to the hypervisor error: Operation not supported: Cannot use direct socket mode if no URI is set /etc/rc.d/rc.libvirt: line 179: kill: (15808) - No such process Stopping virtlogd... Stopping virtlockd... Starting virtlockd... Starting virtlogd... libvirt is already running... Here is the log for libvirt. 022-07-18 11:26:44.634+0000: 15812: info : libvirt version: 8.2.0 2022-07-18 11:26:44.634+0000: 15812: info : hostname: AIO 2022-07-18 11:26:44.634+0000: 15812: error : qemuDomainAgentAvailable:8610 : Guest agent is not responding: QEMU guest agent is not connected 2022-07-18 11:26:44.707+0000: 15810: error : qemuDomainAgentAvailable:8610 : Guest agent is not responding: QEMU guest agent is not connected 2022-07-18 11:26:44.818+0000: 15810: error : qemuDomainAgentAvailable:8610 : Guest agent is not responding: QEMU guest agent is not connected 2022-07-18 11:27:39.142+0000: 15812: error : qemuDomainAgentAvailable:8610 : Guest agent is not responding: QEMU guest agent is not connected 2022-07-18 11:27:39.216+0000: 15809: error : qemuDomainAgentAvailable:8610 : Guest agent is not responding: QEMU guest agent is not connected 2022-07-20 06:43:26.971+0000: 15813: warning : qemuDomainObjBeginJobInternal:909 : Cannot start job (query, none, none) in API remoteDispatchDomainGetBlockInfo for domain MGMT; current job is (query, none, none) owned by (15809 remoteDispatchDomainGetBlockInfo, 0 <null>, 0 <null> (flags=0x0)) for (221s, 0s, 0s) 2022-07-20 06:43:26.971+0000: 15813: error : qemuDomainObjBeginJobInternal:944 : Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo) 2022-07-20 06:43:56.972+0000: 15810: warning : qemuDomainObjBeginJobInternal:909 : Cannot start job (query, none, none) in API remoteDispatchDomainGetBlockInfo for domain MGMT; current job is (query, none, none) owned by (15809 remoteDispatchDomainGetBlockInfo, 0 <null>, 0 <null> (flags=0x0)) for (251s, 0s, 0s) 2022-07-20 06:43:56.972+0000: 15810: error : qemuDomainObjBeginJobInternal:944 : Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo) 2022-07-20 06:44:05.707+0000: 15811: error : qemuDomainAgentAvailable:8610 : Guest agent is not responding: QEMU guest agent is not connected 2022-07-20 06:44:05.789+0000: 15813: error : qemuDomainAgentAvailable:8610 : Guest agent is not responding: QEMU guest agent is not connected 2022-07-20 06:44:35.833+0000: 15811: warning : qemuDomainObjBeginJobInternal:909 : Cannot start job (query, none, none) in API remoteDispatchDomainGetBlockInfo for domain MGMT; current job is (query, none, none) owned by (15809 remoteDispatchDomainGetBlockInfo, 0 <null>, 0 <null> (flags=0x0)) for (290s, 0s, 0s) 2022-07-20 06:44:35.833+0000: 15811: error : qemuDomainObjBeginJobInternal:944 : Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo) 2022-07-20 06:45:05.834+0000: 17689: warning : qemuDomainObjBeginJobInternal:909 : Cannot start job (query, none, none) in API remoteDispatchDomainGetBlockInfo for domain MGMT; current job is (query, none, none) owned by (15809 remoteDispatchDomainGetBlockInfo, 0 <null>, 0 <null> (flags=0x0)) for (320s, 0s, 0s) 2022-07-20 06:45:05.834+0000: 17689: error : qemuDomainObjBeginJobInternal:944 : Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo) 2022-07-20 06:45:35.855+0000: 15812: warning : qemuDomainObjBeginJobInternal:909 : Cannot start job (query, none, none) in API remoteDispatchDomainGetBlockInfo for domain MGMT; current job is (query, none, none) owned by (15809 remoteDispatchDomainGetBlockInfo, 0 <null>, 0 <null> (flags=0x0)) for (350s, 0s, 0s) 2022-07-20 06:45:35.855+0000: 15812: error : qemuDomainObjBeginJobInternal:944 : Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo) 2022-07-20 06:45:40.855+0000: 15811: error : qemuAgentSend:761 : Guest agent is not responding: Guest agent not available for now 2022-07-20 06:46:05.856+0000: 15810: warning : qemuDomainObjBeginJobInternal:909 : Cannot start job (query, none, none) in API remoteDispatchDomainGetBlockInfo for domain MGMT; current job is (query, none, none) owned by (15809 remoteDispatchDomainGetBlockInfo, 0 <null>, 0 <null> (flags=0x0)) for (380s, 0s, 0s) 2022-07-20 06:46:05.856+0000: 15810: error : qemuDomainObjBeginJobInternal:944 : Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo) 2022-07-20 06:46:10.855+0000: 15811: warning : qemuDomainObjBeginJobInternal:909 : Cannot start job (modify, none, none) in API remoteDispatchDomainShutdown for domain MGMT; current job is (query, none, none) owned by (15809 remoteDispatchDomainGetBlockInfo, 0 <null>, 0 <null> (flags=0x0)) for (385s, 0s, 0s) 2022-07-20 06:46:10.855+0000: 15811: error : qemuDomainObjBeginJobInternal:944 : Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo) 2022-07-20 06:46:35.858+0000: 15810: warning : qemuDomainObjBeginJobInternal:909 : Cannot start job (query, none, none) in API remoteDispatchDomainGetBlockInfo for domain MGMT; current job is (query, none, none) owned by (15809 remoteDispatchDomainGetBlockInfo, 0 <null>, 0 <null> (flags=0x0)) for (410s, 0s, 0s) 2022-07-20 06:46:35.858+0000: 15810: error : qemuDomainObjBeginJobInternal:944 : Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo) 2022-07-20 06:47:05.859+0000: 15811: warning : qemuDomainObjBeginJobInternal:909 : Cannot start job (query, none, none) in API remoteDispatchDomainGetBlockInfo for domain MGMT; current job is (query, none, none) owned by (15809 remoteDispatchDomainGetBlockInfo, 0 <null>, 0 <null> (flags=0x0)) for (440s, 0s, 0s) 2022-07-20 06:47:05.859+0000: 15811: error : qemuDomainObjBeginJobInternal:944 : Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo) 2022-07-20 06:47:53.637+0000: 15816: error : virProcessKillPainfullyDelay:470 : Failed to terminate process 16226 with SIGKILL: Device or resource busy 2022-07-20 06:47:53.637+0000: 15812: warning : qemuDomainObjBeginJobInternal:909 : Cannot start job (query, none, none) in API remoteDispatchDomainGetBlockInfo for domain MGMT; current job is (query, none, none) owned by (15809 remoteDispatchDomainGetBlockInfo, 0 <null>, 0 <null> (flags=0x0)) for (488s, 0s, 0s) 2022-07-20 06:47:53.637+0000: 15812: error : qemuDomainObjBeginJobInternal:944 : Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo) 2022-07-20 06:48:23.637+0000: 15816: warning : qemuDomainObjBeginJobInternal:909 : Cannot start job (destroy, none, none) in API remoteDispatchDomainDestroy for domain MGMT; current job is (query, none, none) owned by (15809 remoteDispatchDomainGetBlockInfo, 0 <null>, 0 <null> (flags=0x0)) for (518s, 0s, 0s) 2022-07-20 06:48:23.637+0000: 15816: error : qemuDomainObjBeginJobInternal:944 : Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo) 2022-07-20 06:48:23.638+0000: 25653: warning : qemuDomainObjBeginJobInternal:909 : Cannot start job (query, none, none) in API remoteDispatchDomainGetBlockInfo for domain MGMT; current job is (query, none, none) owned by (15809 remoteDispatchDomainGetBlockInfo, 0 <null>, 0 <null> (flags=0x0)) for (518s, 0s, 0s) 2022-07-20 06:48:23.638+0000: 25653: error : qemuDomainObjBeginJobInternal:944 : Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo) 2022-07-20 06:48:53.642+0000: 15811: warning : qemuDomainObjBeginJobInternal:909 : Cannot start job (query, none, none) in API remoteDispatchDomainGetBlockInfo for domain MGMT; current job is (query, none, none) owned by (15809 remoteDispatchDomainGetBlockInfo, 0 <null>, 0 <null> (flags=0x0)) for (548s, 0s, 0s) 2022-07-20 06:48:53.642+0000: 15811: error : qemuDomainObjBeginJobInternal:944 : Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainGetBlockInfo) 2022-07-20 06:48:54.288+0000: 15808: warning : virNetDaemonRun:886 : Make forcefull daemon shutdown Edited July 20, 2022 by ChuckPeng Quote Link to comment
JorgeB Posted July 24, 2022 Share Posted July 24, 2022 Probably can only solve that by rebooting. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.