Increasing command timeouts in global parameters can work here. At least I met similar behaviour with VR.
вт, 12 июн. 2018 г., 14:39 Christoffer Pedersen <v...@vrod.dk>: > Hi Nicolas, > > I did a apt show qemu and it gave me this version: > > Version: 1:2.5+dfsg-5ubuntu10.29 > > So I guess tha would be version 2.5? > > On Tue, Jun 12, 2018 at 1:04 PM, Nicolas Bouige <n.bou...@dimsi.fr> wrote: > > > Hello Christoffer, > > > > > > Could you tell us wich qemu version are you using ? > > > > Nicolas Bouige > > DIMSI > > cloud.dimsi.fr<http://www.cloud.dimsi.fr> > > 4, avenue Laurent Cely > > Tour d’Asnière – 92600 Asnière sur Seine > > T/ +33 (0)6 28 98 53 40 > > > > > > ________________________________ > > De : Christoffer Pedersen <v...@vrod.dk> > > Envoyé : mardi 12 juin 2018 12:30:48 > > À : users@cloudstack.apache.org > > Objet : SSVM's not starting, timeout for libvirt python script in > agent.log > > > > Hi all, > > > > I have an issue regarding the system VMs. After deploying an advanced > zone, > > the system VMs are trying to be created but gets stuck in a "Starting" > > state, however the Agent state is "Up". I have these logs in the > agent.log > > (sorry for the formatting) > > > > 2018-06-12 12:22:06,354 WARN [kvm.resource.LibvirtComputingResource] > > (Script-8:null) (logid:) Interrupting script. > > 2018-06-12 12:22:06,355 WARN [kvm.resource.LibvirtComputingResource] > > (agentRequest-Handler-4:null) (logid:ea9cb55a) Timed out: > > /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.py > > -n > > v-1-VM -p > > %template=domP%type=consoleproxy%host=1.1.1.1% > > port=8250%name=v-1-VM%zone=1%pod=1%guid=Proxy.1%proxy_vm=1% > > disable_rp_filter=true%eth2ip=9.9.9.9%eth2mask=255.255.255. > > 0%gateway=9.9.9.1%eth0ip=169.254.3.159%eth0mask=255.255.0. > > 0%eth1ip=6.6.6.6%eth1mask=255.255.255.0%mgmtcidr= > > > 9.9.9.0/24%localgw=1.2.3.4%internaldns1=1.2.3.4%dns1=8.8.8.8%dns2=8.8.4.4 > > . Output is: > > 2018-06-12 12:22:06,355 ERROR [kvm.resource.LibvirtComputingResource] > > (agentRequest-Handler-4:null) (logid:ea9cb55a) passcmd failed:timeout > > 2018-06-12 12:22:08,914 WARN [kvm.resource.LibvirtComputingResource] > > (Script-4:null) (logid:) Interrupting script. > > 2018-06-12 12:22:08,915 WARN [kvm.resource.LibvirtComputingResource] > > (agentRequest-Handler-5:null) (logid:8e44093e) Timed out: > > /usr/share/cloudstack-common/scripts/vm/hypervisor/kvm/patchviasocket.py > > -n > > s-2-VM -p > > %template=domP%type=secstorage%host=1.1.1.1%port= > > 8250%name=s-2-VM%zone=1%pod=1%guid=s-2-VM%workers=5%resource=org.apache. > > cloudstack.storage.resource.NfsSecondaryStorageResource% > > instance=SecStorage%sslcopy=false%role=templateProcessor% > > mtu=1500%eth2ip=7.7.7.7%eth2mask=255.255.255.0%gateway=9.9.9.1%public. > > network.device=eth2%eth0ip=169.254.2.193%eth0mask=255. > > 255.0.0%eth1ip=10.120.0.61%eth1mask=255.255.255.0%mgmtcidr= > > 9.9.9.0/24%localgw=1.2.3.4%private.network.device=eth1% > > internaldns1=1.2.3.4%dns1=8.8.8.8%dns2=8.8.4.4%nfsVersion=null > > . Output is: > > 2018-06-12 12:22:08,915 ERROR [kvm.resource.LibvirtComputingResource] > > (agentRequest-Handler-5:null) (logid:8e44093e) passcmd failed:timeout > > > > I have seen this error around but did not really find a solution to it. I > > am not exactly sure whats "timing" out? I can ping both SSVM's on their > > private and public interface. > > > > I hope someone can help me out here. :) > > > > -- > > Thanks, > > Chris pedersen > > > > > > -- > Thanks, > Chris pedersen >
