using ubuntu cloud archive gets a version of libvirtd which doesn't do nested virtualization

Bug #1689370 reported by Amrith Kumar on 2017-05-08
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Amrith Kumar

Bug Description

Sean helped me figure out an issue which has to do with the use of Ubuntu Cloud Archive in devstack.

With this new code in, we get libvirtd (2.5.0) and the old one used to be 1.3.1.

With version 1.3.1, vmware running with VT-X extensions enabled allows me to launch a trove guest successfully. With 2.5.0, and VT-X enabled, if I used virt_type of kvm, the VM won't boot. It hangs with a GRUB line, doesn't go any further. The same image, with virt_type of qemu works fine.

So, the incompatibility is now that if I use virt_type = kvm (required for Trove to successfully boot within a reasonable time), I can't launch a guest if I use libvirt 2.5.0.

Fix proposed to branch: master

Changed in devstack:
assignee: nobody → Amrith Kumar (amrith)
status: New → In Progress

Submitter: Jenkins
Branch: master

commit bb436d3373715253a17b6e1fd9211c2bc110a96f
Author: Amrith Kumar <email address hidden>
Date: Wed May 10 08:21:04 2017 -0400

    Make use of Ubuntu Cloud Archive switchable

    The trove development environment is typically a linux VM within which
    openstack is installed, and trove launches guest vm's within that
    environment. To make it possible for these vm's to launch in one human
    lifetime, one must set vt/x and enable nested hypervisors to use with
    kvm; qemu emulation will take way too long.

    The new libvirtd (v2.5.0) in Ubuntu Cloud Archive doesn't handle
    nested hypervisors well and if you use it, you end up with a guest
    hanging on the GRUB line.

    To enable that use-case, we provide ENABLE_UBUNTU_CLOUD_ARCHIVE which
    the trove developer can set (to False) before running devstack.

    Change-Id: Ia0265c67bb7d2a438575a03c0ddbf2d9c53266ed
    Closes-Bug: #1689370

Changed in devstack:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers