This article is created to discuss on handling error arises whenever Virtual Machine Manager has already successfully installed. It is actually happened when further editing process of a configuration file has already done to define nested virtualization.
The configuration file is edited in order to aim nested virtualization where in the Guest Machine runs inside Virtual Machine Manager, it will create another Guest Machine. That is where the ‘nested virtualization’ comes. See the article titled ‘Configure KVM for Nested Virtualization‘.
After configuring Host Machine which is responsible for running Guest Machine using Virtual Machine Manager, there is an error starting instance or Guest Machine in Virtual Machine Manager shown as follows :
Below is the alternative solution which is executed to solve the above problem by starting virtlogd.socket :
systemctl start virtlogd.socket
user@hostname:~# systemctl start virtlogd.socket You have new mail in /var/mail/root user@hostname:~#
Since the error message which is displayed above concerning the error of starting a domain involves virtlogd.socket specifically it cannot be found anywhere, the actual solution executed above is performed by starting the virtlogd.socket again.
To check whether the virtlogd.socket has already activated, the following command can be typed in the command line in order to look for it :
systemctl status virtlogd.socket
root@hostname:~# systemctl status virtlogd.socket ● virtlogd.socket - Virtual machine log manager socket Loaded: loaded (/lib/systemd/system/virtlogd.socket; enabled; vendor preset: enabled) Active: active (running) since xxx 2016-xx-xx xx:xx:xx xxx; xh ago Listen: /var/run/libvirt/virtlogd-sock (Stream) Okt 27 23:34:34 hostname systemd[1]: Listening on Virtual machine log manager socket. root@hostname:~#
Try running the virtual machine again from Virtual Machine Manager after starting and activating virtlogd.socket.
It can be done by selecting menu Run from the Virtual Machine Manager in the Right Click on the virtual machine which is going to be started shown below :
The process of starting the virtual machine if it is succeed, the status of the virtual machine will be changed from shutoff into running as shown below :