Please provide your domain xml and libvirtd configuration. And it's better to compare start time with previous libvirt versions...
On Fri, Feb 8, 2019 at 11:55 AM Sharath Kurudi <kurudishar...@gmail.com> wrote: > Hi, > > I have installed libvirt 4.9. libvirtd 4.9 takes a long time to come > up. I enabled debug prints and also put my own prints Logs are below > > > 2019-02-06 05:55:49.082+0000: 377: info : libvirt version: 4.9.0 > 2019-02-06 05:55:49.082+0000: 377: info : hostname: draco > 2019-02-06 05:55:49.082+0000: 377: info : virObjectNew:248 : OBJECT_NEW: > obj=0x558e782d8bb0 classname=virAccessManager > 2019-02-06 05:55:49.082+0000: 377: debug : virAccessManagerNewDriver:105 : > Initialized with stack > 2019-02-06 05:55:49.082+0000: 377: info : virObjectNew:248 : OBJECT_NEW: > obj=0x558e782cd870 classname=virAccessManager > 2019-02-06 05:55:49.082+0000: 377: debug : virAccessManagerNewDriver:105 : > Initialized with none > 2019-02-06 05:55:49.082+0000: 377: info : virObjectRef:382 : OBJECT_REF: > obj=0x558e782d8bb0 > 2019-02-06 05:55:49.082+0000: 377: info : virObjectUnref:344 : > OBJECT_UNREF: obj=0x558e782d8bb0 > 2019-02-06 05:55:49.082+0000: 377: debug : main:1200 : Decided on pid file > path '/var/run/libvirtd.pid' > 2019-02-06 05:55:49.082+0000: 377: debug : main:1213 : Decided on socket > paths '/var/run/libvirt/libvirt-sock', '/var/run/libvirt/libvirt-sock-ro' > and '/var/run/libvirt/libvirt-admin-sock' > 2019-02-06 05:55:49.082+0000: 377: debug : virFileClose:109 : Closed fd 5 > 2019-02-06 05:55:49.082+0000: 378: debug : virFileClose:109 : Closed fd 4 > 2019-02-06 05:55:49.082+0000: 378: debug : virFileClose:109 : Closed fd 4 > 2019-02-06 05:55:49.082+0000: 378: debug : virFileClose:109 : Closed fd 6 > 2019-02-06 05:55:49.083+0000: 379: debug : main:1255 : Ensuring run dir > '/var/run/libvirt' exists > 2019-02-06 05:55:49.083+0000: 379: debug : virFileMakePathHelper:3034 : > path=/var/run/libvirt mode=0777 > 2019-02-06 05:55:49.083+0000: 379: debug : virNetlinkStartup:137 : Running > global netlink initialization > 2019-02-06 05:55:49.083+0000: 379: debug : virNetlinkStartup:144 : Sharath > Returning from global netlink initialization > 2019-02-06 05:55:49.083+0000: 379: debug : main:1270 : Sharath > virNetlinkStartup done > 2019-02-06 05:55:49.083+0000: 379: debug : virNetDaemonNew:127 : Sharath > Running virNetDaemonNew > 2019-02-06 05:55:49.083+0000: 379: debug : virNetDaemonNew:131 : Sharath > virNetDaemonInitalize done > 2019-02-06 05:55:49.083+0000: 379: info : virObjectNew:248 : OBJECT_NEW: > obj=0x558e782ce1b0 classname=virNetDaemon > 2019-02-06 05:55:49.083+0000: 379: debug : virNetDaemonNew:136 : Sharath > virNetDaemonInitalize done > > The above logs loop till libvirtd comes up. It is also seen that more than > one instance of libvirtd runs simultaneously during delay. > > Any ideas on how to resolve? > > Thanks > _______________________________________________ > libvirt-users mailing list > libvirt-users@redhat.com > https://www.redhat.com/mailman/listinfo/libvirt-users -- Best regards, ----------------------------------- Han Han Quality Engineer Redhat. Email: h...@redhat.com Phone: +861065339333
_______________________________________________ libvirt-users mailing list libvirt-users@redhat.com https://www.redhat.com/mailman/listinfo/libvirt-users
