group.of.nepali.translators team mailing list archive

[ChristianEhrhardt <1561019@xxxxxxxxxxxxxxxxxx>]

Given the (no) feedback and the fact that this actually is not part of
the virt cpu the old request is won't fix. Furthermore I spawned a task
to remove the patches that did add it in the past.

TL;DR:
- intentionally not enabled/added upstream
- long gone with a very low amount of people missing it
- still (and in future) available as opt-in by changing the config as outlined in comment #15
- will remove (disfunctional) related delta on next merge

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

** Changed in: libvirt (Ubuntu Wily)
       Status: New => Won't Fix

** Changed in: libvirt (Ubuntu Xenial)
       Status: New => 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/1561019

Title:
  copied cpu flags don't match host cpu

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

Bug description:
  Using wily (libvirt 1.2.16-2ubuntu11.15.10.3) in a AMD FX-8350 nested
  KVM doesn't work, unless in the definition of the vm the cpu is
  configured with  mode='host-passthrough', for other CPUs the
  manifestation could be different.

  Steps to reproduce:

  L0: wily

  $ uvt-kvm create --memory 2048 --cpu 2 vm-L1 release=wily arch=amd64  # the L1 guest can be trusty too, it doesn't really matter
  $ uvt-kvm ssh --insecure vm-L1
  (vm-L1)$ sudo apt-get install cpu-checker
  (vm-L1)$ sudo kvm-ok
  INFO: Your CPU does not support KVM extensions
  KVM acceleration can NOT be used
  (vm-L1)$ sudo modprobe kvm-amd
  modprobe: ERROR: could not insert 'kvm_amd': Operation not supported
  (vm-L1)$ dmesg | grep kvm | tail -n1
  [45890.075592] kvm: no hardware support

  Expected Result:

  kvm-ok says that virtualization is supported

  
  Workaround:

  1) Shutdown the VM (vm-L1)
  2) In the kvm host edit vm-L1 definition (sudo virsh edit vm-L1) and change the cpu definition to:
    <cpu mode='host-passthrough'></cpu>
  3) power on the VM

  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: libvirt-bin 1.2.16-2ubuntu11.15.10.3
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Wed Mar 23 11:20:11 2016
  InstallationDate: Installed on 2014-12-06 (472 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: libvirt
  UpgradeStatus: Upgraded to wily on 2016-03-08 (14 days ago)
  modified.conffile..etc.apparmor.d.usr.lib.libvirt.virt.aa.helper: [modified]
  modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf']
  modified.conffile..etc.libvirt.qemu.networks.default.xml: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu/networks/default.xml']
  mtime.conffile..etc.apparmor.d.usr.lib.libvirt.virt.aa.helper: 2016-03-14T13:22:07.751461

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