We hit the simillar issue with follow error in nova-compute log:
: libvirtError: internal error: process exited while connecting to monitor: 2021-01-15T02:26:20.537782Z qemu-kvm: -chardev socket,id=charserial0,host=192.168.33.67,port=10001,server,nowait,logfile=/dev/fdset/16,logappend=on: Failed to bind socket: Address already in use
2021-01-15 10:26:20.844 36347 ERROR nova.virt.libvirt.driver [req-11f3c907-ca7c-44fc-98f0-70d9cc01f9f0 650c5993a2d3498bbba3d62e6f338ca6 75767e74f09f4b4caf216f9bbd2a0832 - default default] [instance: e5595da6-0a21-4dcc-8463-cbb0b0dcfc65] Failed to start libvirt guest: libvirtError: internal error: process exited while connecting to monitor: 2021-01-15T02:26:20.537782Z qemu-kvm: -chardev socket,id=charserial0,host=192.168.33.67,port=10001,server,nowait,logfile=/dev/fdset/16,logappend=on: Failed to bind socket: Address already in use
The openstack version is Pike.
Is there any solution or workaround?
We hit the simillar issue with follow error in nova-compute log:
: libvirtError: internal error: process exited while connecting to monitor: 2021-01- 15T02:26: 20.537782Z qemu-kvm: -chardev socket, id=charserial0, host=192. 168.33. 67,port= 10001,server, nowait, logfile= /dev/fdset/ 16,logappend= on: Failed to bind socket: Address already in use libvirt. driver [req-11f3c907- ca7c-44fc- 98f0-70d9cc01f9 f0 650c5993a2d3498 bbba3d62e6f338c a6 75767e74f09f4b4 caf216f9bbd2a08 32 - default default] [instance: e5595da6- 0a21-4dcc- 8463-cbb0b0dcfc 65] Failed to start libvirt guest: libvirtError: internal error: process exited while connecting to monitor: 2021-01- 15T02:26: 20.537782Z qemu-kvm: -chardev socket, id=charserial0, host=192. 168.33. 67,port= 10001,server, nowait, logfile= /dev/fdset/ 16,logappend= on: Failed to bind socket: Address already in use
2021-01-15 10:26:20.844 36347 ERROR nova.virt.
The openstack version is Pike.
Is there any solution or workaround?