qemu appears to be built without CONFIG_NUMA defined
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
qemu (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Utopic |
Fix Released
|
High
|
Unassigned |
Bug Description
=======
SRU Justification
1. Impact: openstack cannot use numactl to pin kvm to cpus
2. Test case: ldd /usr/bin/
3. Regression potential: this causes qemu to be build against libnuma. It should only enable users who wish to use numa to do so, though of course new code will be enabled so unepxected regressions are possible.
=======
When running
qemu-system-x86_64 -object memory-
I got the following error: "NUMA node binding are not supported by this QEMU"
Looking at the qemu code, it appears that this means that the package was built without CONFIG_QEMU being defined. The "host-nodes=
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: qemu-system-x86 2.1+dfsg-4ubuntu6.4
ProcVersionSign
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.1
Architecture: amd64
Date: Wed Feb 4 09:04:26 2015
KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.7.5-20140531_
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.
dmi.modalias: dmi:bvnSeaBIOS:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.
dmi.sys.vendor: QEMU
Changed in qemu (Ubuntu Utopic): | |
importance: | Undecided → High |
description: | updated |
It looks like it is mainly disabled because it is in Debian, see /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 758189
https:/
The reasons for disabling it in Debian don't strictly apply in
ubuntu, so it may be ok for us to enable it.
status: triaged
importance: high