Re: [libvirt-users] RLIMIT_MEMLOCK in container environment

On Thu, Aug 22, 2019 at 12:01 PM Laine Stump wrote: > > On 8/22/19 10:56 AM, Ihar Hrachyshka wrote: > > On Thu, Aug 22, 2019 at 2:24 AM Daniel P. Berrangé > > wrote: > >> > >> On Wed, Aug 21, 2019 at 01:37:21PM -0700, Ihar Hrachyshka wrote: > >>

Re: [libvirt-users] RLIMIT_MEMLOCK in container environment

On Thu, Aug 22, 2019 at 2:24 AM Daniel P. Berrangé wrote: > > On Wed, Aug 21, 2019 at 01:37:21PM -0700, Ihar Hrachyshka wrote: > > Hi all, > > > > KubeVirt uses libvirtd to manage qemu VMs represented as Kubernetes > > API resources. In this case, libvirtd is runn

[libvirt-users] RLIMIT_MEMLOCK in container environment

Hi all, KubeVirt uses libvirtd to manage qemu VMs represented as Kubernetes API resources. In this case, libvirtd is running inside an unprivileged pod, with some host mounts / capabilities added to the pod, needed by libvirtd and other services. One of the capabilities libvirtd requires for

Re: [libvirt-users] e1000 network interface takes a long time to set the link ready

On Fri, May 11, 2018 at 1:42 AM, Daniel P. Berrangé <berra...@redhat.com> wrote: > On Thu, May 10, 2018 at 11:53:23AM -0700, Ihar Hrachyshka wrote: >> Hi, >> >> In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, >> link on the interface becomes

Re: [libvirt-users] e1000 network interface takes a long time to set the link ready

On Thu, May 10, 2018 at 2:07 PM, Laine Stump <la...@redhat.com> wrote: > On 05/10/2018 02:53 PM, Ihar Hrachyshka wrote: >> Hi, >> >> In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, >> link on the interface becomes ready several seconds aft

Re: [libvirt-users] e1000 network interface takes a long time to set the link ready

On Thu, May 10, 2018 at 11:57 AM, Daniel Romero wrote: > Hi, > > try to use virtio instead... That is exactly what I tried, and indeed the link is ready almost immediately. But there are some issues with virtio, like missing drivers in default Windows images. Kubevirt

[libvirt-users] e1000 network interface takes a long time to set the link ready

Hi, In kubevirt, we discovered [1] that whenever e1000 is used for vNIC, link on the interface becomes ready several seconds after 'ifup' is executed, which for some buggy images like cirros may slow down boot process for up to 1 minute [2]. If we switch from e1000 to virtio, the link is brought