Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress

On Tue, Jan 3, 2017 at 6:23 AM, Clark Boylan wrote: > I don't have any answers but my first thought was maybe it is related to > https://bugs.launchpad.net/nova/+bug/1643911; however, that affects > libvirt 1.3.1 on Ubuntu Xenial and there is at least one instance of > that

Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress

<openstack-dev@lists.openstack.org> Date: Monday, January 2, 2017 at 3:37 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress XEN

Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress

On Tue, Jan 3, 2017 at 6:37 AM, Michał Jastrzębski wrote: > XEN doesn't work well with nested kvm. We need to change nova config to > pure qemu without kvm. I thought we did that in gates? ​In the gate, kolla is using qemu all the time[0]. So this should be not related. [0]

Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress

XEN doesn't work well with nested kvm. We need to change nova config to pure qemu without kvm. I thought we did that in gates? On Jan 2, 2017 2:25 PM, "Clark Boylan" wrote: > On Sun, Jan 1, 2017, at 09:13 PM, Jeffrey Zhang wrote: > > Checked more failed gate, here is the

Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress

On Sun, Jan 1, 2017, at 09:13 PM, Jeffrey Zhang wrote: > Checked more failed gate, here is the more info: > > 1. only rax-iad has such issue > 2. the failed and successful gates have the same rpm installed. > > So the only difference between failed gate and successful gate is the xen >

Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress

y Zhang <zhang.lei@gmail.com> > *Reply-To: *"OpenStack Development Mailing List (not for usage > questions)" <openstack-dev@lists.openstack.org> > *Date: *Friday, December 30, 2016 at 12:41 AM > *To: *OpenStack Development Mailing List <openstack-dev@lists.

Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress

lists.openstack.org> Date: Saturday, December 31, 2016 at 6:22 AM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress I checked

Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress

*OpenStack Development Mailing List <openstack-dev@lists. > openstack.org> > *Subject: *Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed > during launching qemu progress > > > > Found this nova bug[0] and another talk in openstack-dev[1]. > > > >

Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress

mber 30, 2016 at 12:41 AM To: OpenStack Development Mailing List <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress Found this nova bug[0] and another talk in openstack-dev[1]. The quest

Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress

Found this nova bug[0] and another talk in openstack-dev[1]. The question is: why this happens now and then? sometimes the gate is OK. and others not. [0] https://bugs.launchpad.net/nova/+bug/1649527 [1] http://lists.openstack.org/pipermail/openstack-dev/2016-December/109401.html On Fri, Dec

[openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during launching qemu progress

Recently, centos 7.3 is release. libvirt is upgrade to 2.0 version. But in kolla's gate. the nova_libvirt container failed now and then. What i found is: 1. Simple start nova_libvirt container is OK. 2. When launching a new instance, libvirt is killed without any logs in libvirtd.log file. 3.