yahoo-eng-team team mailing list archive

[Takashi Kajinami <1450465@xxxxxxxxxxxxxxxxxx>]

Xen support was removed from nova multiple cycles ago and we have no
plan to fix this issue.

** Changed in: nova
       Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1450465

Title:
  vif name too long when libvirt driver trying to create XEN HVM domain

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  kilo-rc3

  Using library: libvirt 1.2.11
  Using API: Xen 1.2.11
  Running hypervisor: Xen 4.5.0

  network_api_class=nova.network.neutronv2.api.API

  According to http://xenbits.xen.org/docs/unstable/misc/xl-network-configuration.html "If the domain is an HVM domain then the associated emulated (tap) device will have a "-emu" suffice added."
  Neutron API and libvirt VIF using network_model.NIC_NAME_LEN which is 14. After XEN scripts adds "-emu" suffix vif can't be handled by xen-hotplug script:
  ++ ip link set vif1.0 name tap08205d6b-0a-emu
  Error: argument "tap08205d6b-0a-emu" is wrong: "name" too long

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1450465/+subscriptions