Slowed down further (lmited to 2 cpus), startup of the guests takes minutes now.
Still no issue to be seen.
The socket is around and working, while in background the guests start slowly but surely.
The test is now:
# cat test-restart.sh
#!/bin/bash
set -uxe
#starts off
date
ls -laF /var/run/libvirt/libvirt-sock
sudo service libvirt-bin status
date
# start service
sudo service libvirt-bin start
date
# check if socket is available immediately
ls -laF /var/run/libvirt/libvirt-sock
sudo service libvirt-bin status
ls -laF /var/run/libvirt/libvirt-sock
# this might take a while as the dameon queues requests
virsh list
date
With 100 Guests shut down, but set to autostart on a 2 cpu system.
That takes about 5 minutes to start the guests, but the service is up and ready on the socket before doing all that.
Did you face something else?
@Ed / @Guessi
I know it is a long time, but I'd need to get something reproducible to go on fixing this for artful. If you can help me with examples that do please let me know.
@Guessi:
I tried with the degraded RAID but it worked for me as well, maybe it is just not the most reliable repro.
@Ed:
the original case lacks some details what actually failed e.g. what dependent services and how it was triggered in your case.
Keeping incomplete status on Trusty for now :-/
Log of the last test:
# ./test-restart.sh
+ date
Wed Sep 6 09:56:01 UTC 2017
+ ls -laF /var/run/libvirt/libvirt-sock
ls: cannot access /var/run/libvirt/libvirt-sock: No such file or directory
+ /bin/true
+ sudo service libvirt-bin status
libvirt-bin stop/waiting
+ date
Wed Sep 6 09:56:01 UTC 2017
+ sudo service libvirt-bin start
libvirt-bin start/running, process 9730
+ date
Wed Sep 6 09:56:03 UTC 2017
+ ls -laF /var/run/libvirt/libvirt-sock
srwxrwx--- 1 root libvirtd 0 Sep 6 09:56 /var/run/libvirt/libvirt-sock=
+ sudo service libvirt-bin status
libvirt-bin start/running, process 9730
+ ls -laF /var/run/libvirt/libvirt-sock
srwxrwx--- 1 root libvirtd 0 Sep 6 09:56 /var/run/libvirt/libvirt-sock=
+ virsh list
Id Name State
----------------------------------------------------
2 artful-test32 running
[...]
101 artful-test45 running
+ date
Wed Sep 6 10:01:41 UTC 2017
Slowed down further (lmited to 2 cpus), startup of the guests takes minutes now.
Still no issue to be seen.
The socket is around and working, while in background the guests start slowly but surely.
The test is now: libvirt/ libvirt- sock libvirt/ libvirt- sock libvirt/ libvirt- sock
# cat test-restart.sh
#!/bin/bash
set -uxe
#starts off
date
ls -laF /var/run/
sudo service libvirt-bin status
date
# start service
sudo service libvirt-bin start
date
# check if socket is available immediately
ls -laF /var/run/
sudo service libvirt-bin status
ls -laF /var/run/
# this might take a while as the dameon queues requests
virsh list
date
With 100 Guests shut down, but set to autostart on a 2 cpu system.
That takes about 5 minutes to start the guests, but the service is up and ready on the socket before doing all that.
Did you face something else?
@Ed / @Guessi
I know it is a long time, but I'd need to get something reproducible to go on fixing this for artful. If you can help me with examples that do please let me know.
@Guessi:
I tried with the degraded RAID but it worked for me as well, maybe it is just not the most reliable repro.
@Ed:
the original case lacks some details what actually failed e.g. what dependent services and how it was triggered in your case.
Keeping incomplete status on Trusty for now :-/
Log of the last test: libvirt/ libvirt- sock libvirt/ libvirt- sock: No such file or directory libvirt/ libvirt- sock libvirt/ libvirt- sock= libvirt/ libvirt- sock libvirt/ libvirt- sock= ------- ------- ------- ------- ------- ------- ---
# ./test-restart.sh
+ date
Wed Sep 6 09:56:01 UTC 2017
+ ls -laF /var/run/
ls: cannot access /var/run/
+ /bin/true
+ sudo service libvirt-bin status
libvirt-bin stop/waiting
+ date
Wed Sep 6 09:56:01 UTC 2017
+ sudo service libvirt-bin start
libvirt-bin start/running, process 9730
+ date
Wed Sep 6 09:56:03 UTC 2017
+ ls -laF /var/run/
srwxrwx--- 1 root libvirtd 0 Sep 6 09:56 /var/run/
+ sudo service libvirt-bin status
libvirt-bin start/running, process 9730
+ ls -laF /var/run/
srwxrwx--- 1 root libvirtd 0 Sep 6 09:56 /var/run/
+ virsh list
Id Name State
-------
2 artful-test32 running
[...]
101 artful-test45 running
+ date
Wed Sep 6 10:01:41 UTC 2017