<div dir="ltr"><div>Hi,<br><br></div>try to use virtio instead...<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature">Atte.<br>Daniel Romero P.<br><br></div></div>
<br><div class="gmail_quote">On Thu, May 10, 2018 at 3:53 PM, Ihar Hrachyshka <span dir="ltr"><<a href="mailto:ihrachys@redhat.com" target="_blank">ihrachys@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
In kubevirt, we discovered [1] that whenever e1000 is used for vNIC,<br>
link on the interface becomes ready several seconds after 'ifup' is<br>
executed, which for some buggy images like cirros may slow down boot<br>
process for up to 1 minute [2]. If we switch from e1000 to virtio, the<br>
link is brought up and ready almost immediately.<br>
<br>
For the record, I am using the following versions:<br>
- L0 kernel: 4.16.5-200.fc27.x86_64 #1 SMP<br>
- libvirt: 3.7.0-4.fc27<br>
- guest kernel: 4.4.0-28-generic #47-Ubuntu<br>
<br>
Is there something specific about e1000 that makes it initialize the<br>
link too slowly on libvirt or guest side?<br>
<br>
[1] <a href="https://github.com/kubevirt/kubevirt/issues/936" rel="noreferrer" target="_blank">https://github.com/kubevirt/<wbr>kubevirt/issues/936</a><br>
[2] <a href="https://bugs.launchpad.net/cirros/+bug/1768955" rel="noreferrer" target="_blank">https://bugs.launchpad.net/<wbr>cirros/+bug/1768955</a><br>
<br>
Ihar<br>
<br>
______________________________<wbr>_________________<br>
libvirt-users mailing list<br>
<a href="mailto:libvirt-users@redhat.com">libvirt-users@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/libvirt-users" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/libvirt-users</a><br>
</blockquote></div><br></div>