group.of.nepali.translators team mailing list archive

[ChristianEhrhardt <1621121@xxxxxxxxxxxxxxxxxx>]

I'm passing through old bugs, lacking further discussion and any
"forcing" argument why that would be needed in Xenial (which would be
feature enablement in SRU, so that would have to be a very good
argument) I'm closing the Xenial task to clean up.

Also if needed users have the option to get this in Xenial by using the
Cloud-Archive Ocata or Pike.

** Changed in: libvirt (Ubuntu Xenial)
       Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1621121

Title:
  VM fails to start when vcpu placement='auto'

Status in libvirt package in Ubuntu:
  Fix Released
Status in libvirt source package in Xenial:
  Won't Fix

Bug description:
  ---Problem Description---
  VM fails to start when vcpu placement='auto'
   
  ---uname output---
  Linux ltc-test-ci1 4.4.0-9134-generic #53-Ubuntu SMP Thu Aug 18 05:21:43 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = power 8 ppc64le 
    
  ---Steps to Reproduce---

  1. Define the VM with xml attached
  virsh define vm.xml
  2. Start the VM
  virsh start virt-tests-vm1
  error: Failed to start domain virt-tests-vm1
  error: unsupported configuration: numad is not available on this host

   
  Userspace tool common name: ii  libvirt-bin                          2.1.0-1ubuntu3                      ppc64el      programs for the libvirt library 
   
  The userspace tool has the following bit modes: both 

  Userspace rpm: ii  libvirt-bin                          2.1.0-1ubuntu3
  ppc64el      programs for the libvirt library

  
  ii  numad                                0.5+20150602-4                      ppc64el      User-level daemon that monitors NUMA topology and usage

  attached debug log by enabling flag, export LIBVIRT_DEBUG=1

  Not much info on qemu vm log
  cat libvirt/qemu/virt-tests-vm1.log
  2016-08-29 16:09:19.092+0000: shutting down
  2016-08-29 16:16:08.378+0000: shutting down
  2016-08-29 16:16:37.811+0000: shutting down
  2016-08-29 16:16:45.579+0000: shutting down
  2016-08-30 05:35:21.199+0000: shutting down
  2016-08-30 05:40:28.999+0000: shutting down
  2016-08-30 05:41:15.155+0000: shutting down
  2016-08-30 05:44:04.427+0000: shutting down
  2016-08-30 05:44:16.099+0000: shutting down
  2016-08-30 05:49:12.327+0000: shutting down
  2016-08-30 05:53:19.455+0000: shutting down
  2016-08-30 05:53:56.171+0000: shutting down

  
  service numad status
  ? numad.service - numad - The NUMA daemon that manages application locality.
     Loaded: loaded (/lib/systemd/system/numad.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2016-08-22 04:12:30 CDT; 1 weeks 0 days ago
       Docs: man:numad
   Main PID: 3563 (numad)
      Tasks: 2 (limit: 12288)
     Memory: 1.5M
        CPU: 6min 43.046s
     CGroup: /system.slice/numad.service
             ??3563 /usr/bin/numad -i 15

  Aug 22 04:12:29 ltc-test-ci1 systemd[1]: Starting numad - The NUMA daemon that manages application locality....
  Aug 22 04:12:30 ltc-test-ci1 systemd[1]: Started numad - The NUMA daemon that manages application locality..

  looks more like a configuration issue, suspecting that libvirt package
  is configured without numa support

  Can Canonical confirm if the libvirt package provides numa support?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1621121/+subscriptions