This is running on *minimized* images, with linux-kvm kernel; so there might well not be CONFIG_DMI. This is however not the issue (or most likely not). Tests are done in qemu, to simulate running the images in openstack for now (but they are meant to start in openstack without issues). It's simply more convient to test quickly.
An important point is that if I add a qemu RNG to the VM, the cloud-init 'init' steo takes only 2.071 seconds. It appears as though some part of the initialization might depend on sufficient entropy being available. I will attach the log tarball shortly. ** Attachment added: "cloud-init.log.2" https://bugs.launchpad.net/cloud-init/+bug/1727358/+attachment/4995638/+files/cloud-init.log.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727358 Title: cloud-init is slow to complete init on minimized images To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1727358/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
