the VM is a plain debian9 VM. Other VMs with identical setup are still working as expected. Only when I try to change System settings I got this behavior.. 6. Februar 2019 16:27, "Greg Sheremeta" <gshereme(a)redhat.com (mailto:gshereme@redhat.com?to=%22Greg%20Sheremeta%22%20<gshereme@redhat.com>)> schrieb: On Wed, Feb 6, 2019 at 6:04 AM <matthias.barmeier(a)sourcepark.de (mailto:matthias.barmeier@sourcepark.de)> wrote: Hi, after creating a VM from a template everything works fine. After a while I would like to increase memory and cpus. I changed the memory and virtual cpu settings in the "System" settings. I restarted the VM. From this moment on the VM hangs on boot with this messages filling the console: url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id (http://169.254.169.254/2009-04-04/meta-data/instance-id)' Connection to 169.254.169.254 timed out. Google says that's a special EC2 address. Does your VM do something with EC2 and now the network isn't coming up for some reason? Can you get a fresh Stretch VM working with networking that can ping out? This goes on for ever. What can I do to make the VM work again ? I tried to restore the settings to the values it has before but this does not help. The VM contains debian 9 (stretch) with cloud init. Ovirt version: 4.2.7.5-1.el7 Ciao Matze _______________________________________________ Users mailing list -- users(a)ovirt.org (mailto:users@ovirt.org) To unsubscribe send an email to users-leave(a)ovirt.org (mailto:users-leave@ovirt.org) Privacy Statement: https://www.ovirt.org/site/privacy-policy/ (https://www.ovirt.org/site/privacy-policy/) oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ (https://www.ovirt.org/community/about/community-guidelines/) List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/BCVGAAKBBX5... (https://lists.ovirt.org/archives/list/users@ovirt.org/message/BCVGAAKBBX5...) -- GREG SHEREMETA SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX Red Hat NA (https://www.redhat.com/) gshereme(a)redhat.com (mailto:gshereme@redhat.com) IRC: gshereme (https://red.ht/sig)

On 06. 02. 19 12:03, matthias.barmeier(a)sourcepark.de wrote: Hi Matthias, it is really strange that update of the VM memory or CPU settings would trigger this cloud-init behavior inside the VM. I would focus more on what's been happening with the VM after its creation and before the restart. Few ideas and questions: - Is it possible that the cloud-init has been installed or enabled later after the VM creation? - Is the VM from pool? If yes, were there some changes made to the template, e.g., new sub-versions created, before the VM was restarted? This means that the cloud-init service running on your VM is trying to reach the EC2 datasource[1]: https://cloudinit.readthedocs.io/en/latest/topics/datasources/ec2.html I am not familiar with cloud-init on Debian but there should be 120 seconds default timeout to wait for the 169.254.169.254 address to return something, it definitely should not wait forever. -- Pavel Novotny Red Hat Virtualization Quality Engineer Red Hat Czech