yahoo-eng-team team mailing list archive

[Balazs Gibizer <1902516@xxxxxxxxxxxxxxxxxx>]

I'm marking this as invalid from nova perspective as this is more like a
deployment configuration error.

** Changed in: nova
       Status: New => Invalid

-- 
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/1902516

Title:
  [CI] Libvirt error "cannot set up guest memory 'pc.ram': Cannot
  allocate memory" cause failure while spawning instance

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  I saw at least couple of times recently that one of tests in scenario
  CI jobs was failing due to failure in spawning instance. In nova-
  compute's logs there is error like:

  Nov 02 09:13:24.954052 ubuntu-bionic-rax-ord-0021331595 nova-
  compute[23193]: ERROR nova.virt.libvirt.driver [None req-9c065faf-96c5
  -42fd-833c-e0c015457188 tempest-TrunkTest-649105798 tempest-
  TrunkTest-649105798] [instance: 69366a0b-6d15-4e8b-9f90-e9bec06ca126]
  Failed to start libvirt guest: libvirt.libvirtError: internal error:
  process exited while connecting to monitor:
  2020-11-02T09:13:24.490765Z qemu-system-x86_64: warning: TCG doesn't
  support requested feature: CPUID.01H:ECX.vmx [bit 5]

  For example in:
  https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_bb7/759852/4/check
  /neutron-tempest-plugin-scenario-linuxbridge-
  train/bb75daf/controller/logs/screen-n-cpu.txt

  Logstash query:
  http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22warning%3A%20TCG%20doesn't%20support%20requested%20feature%3A%20CPUID.01H%3AECX.vmx%5C%22

  From logstash it seems that it happens only in jobs which runs on
  Ubuntu Bionic.

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