This should be fixed now, please re-open if it isnt.
** Changed in: nova (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
This bug was fixed in the package libvirt - 1.2.12-0ubuntu13
---
libvirt (1.2.12-0ubuntu13) vivid-proposed; urgency=medium
* 9038-qemu-fix-setting-of-VM-CPU-affinity-with-TCG (LP: #1439280)
-- Serge Hallyn serge.hal...@ubuntu.com Wed, 13 May 2015 10:48:53
-0500
** Changed in:
Matt, Tony, that's for the clarification. I'm still a bit confused as
to when the cloud archive used by trusty (http://ubuntu-
cloud.archive.canonical.com/ubuntu/dists/trusty-updates/) would be
updated to point to this new libvirt cloud level. (sorry for being a
newbie on this).
--
You
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu Vivid)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
@vanderwl No problem I'm new to cloud archive as well.
So the URL I have is:
https://launchpad.net/~ubuntu-cloud-archive/+archive/ubuntu/kilo-staging/+index
and that shows (for me) that 4 hours ago the (kilo-staging) cloud-archive PPA
got the fixed libvirt.
So in theory We're done here. Matt
I'm waiting until the package appears in the official cloud archive
repository.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
Title:
Libvirt CPU affinity error
To manage
When will this get fixed for Trusty? that's where it was originally
reported.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
Title:
Libvirt CPU affinity error
To manage
The cloud archive repository currently does not contain a fix for Kilo
on Trusty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
Title:
Libvirt CPU affinity error
To manage
@vanderwl: The original report was against the trusty cloud-archive
repo.
If you look at: https://launchpad.net/ubuntu/+source/libvirt You can
see that the version in trusty is NOT affected by this issue.
Only vivid and the could archive PPA
--
You received this bug notification because you
wont-fixing the nova side will leave it broken for quite some time
until the backport has made its way into all relevant distro images. I'd
prefer to add your patch into nova code as workaround for older libvirt
versions.
--
You received this bug notification because you are a member of Ubuntu
Hello Matt, or anyone else affected,
Accepted libvirt into vivid-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/1.2.12-0ubuntu13 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Description changed:
+ =
+ SRU Justification
+ 1. Impact: VMs fail to launch with TCG (non-kvm-accelerated)
+ 2. Stable fix: cherrypick a patch from upstream.
+ 3. Regression potential: this only slightly relaxes the check for multiple
cpus, and is
@j-rosenboom-j My fix for nova will never be accepted upstream. I
wont speak for the Ubuntu developers but I strongly suspect that they'll
be unwilling to diverge from upstream. Especially as they've already
shown the fix will land in vivid.
--
You received this bug notification because you
I can verify that installing 1.2.12-0ubuntu13 on vivid fixes the issue
for me.
Please forgive my ignorance but can that package be tagged into cloud-
archive once it's officially a vivid update?
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug
** Also affects: libvirt (Ubuntu Vivid)
Importance: Undecided
Status: New
** Also affects: nova (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: libvirt (Ubuntu)
Importance: Undecided =
For the record. Applying this patch to the cloud-archive libvirt
package should fix the problem.
http://libvirt.org/git/?p=libvirt.git;a=commit;h=a103bb105c0c189c3973311ff1826972b5bc6ad6
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
I was pointed at the v1.2.12-maint head in the libvirt git which contains this
fix already.
http://libvirt.org/git/?p=libvirt.git;a=shortlog;h=refs/heads/v1.2.12-maint
I suggest we close the nova issue with won't fix and get the correctly
backported patch into the libvirt package.
--
You
I found the root cause in my environment.
I use libvirt in LXC. And the lxc doesn't enable the cgroup w/ read and
write permission. I add/change the config file with following line.
lxc.aa_profile = lxc-container-default-with-nesting
And install `cgroup-lite` in lxc guest. The libvirt works
Hi all,
I encounter this issue on qemu at Ubuntu 14.04 as a Virtual Machine on Vmware
ESXi. Do you know how to fix it? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
Using the patch above (that basically hacks out qemu specifically), nova boot
work fine.
Same qemu environment as I noted in my 4-23 post.
Can we get this patch out for formal review by nova folks?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Thanks - the patch seems to make sense.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
Title:
Libvirt CPU affinity error
To manage notifications about this bug go to:
We're in discussions with the libvirt devs to work out if the fix is
correct and/or exposes a libvirt bug.
Once that discussion concludes there will the a nova patch posted (and
tagged for backport)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Summary of the libvirt discussion. current upstream works. the libvirt
team would like to identify the libvirt fixes required and get them
backported. to the maintenance releases.
With reference to:
https://launchpad.net/ubuntu/+source/libvirt ; and
@Tony
Yes. You are right. I am sorry that I make a wrong file diff. I hide my last
comment, and paste a correct one.
I meet this issue too. After applied following patch, it works. I think
in the ubuntu, the libvirt (1.2.12, from cloud-archive) doesn't support
numa.
diff --git
It seems that nova's libvirt driver is generating an invalid domain xml.
If I understand correctly specifyin a 'vcpu' node with a cpuset is
invlaid in TCG *unless* you also specify emulatorpin See:
https://libvirt.org/formatdomain.html#elementsCPUAllocation
--
You received this bug notification
This patch (which hasn't gone anywhere near upstream yet)
Forces the libvirt driver in nova to avoid generating a cpuset and there
fore no longer generates the invalid domain XML.
Next steps are to discuss my findings with upstream libvirt and nova
developers to see if I'm correct of I've just
The attachment 1439280.patch seems to be a patch. If it isn't, please
remove the patch flag from the attachment, remove the patch tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for
But that makes no sense. If you were changing
# While earlier versions could support NUMA reporting and
# NUMA placement, not until 1.2.7 was there the ability
# to pin guest nodes to host nodes, so mandate that. Without
# this the scheduler cannot make guaranteed decisions, as the
# guest
I meet this issue too. After applied following patch, it works. I think
in the ubuntu, the libvirt (1.2.12, from cloud-archive) doesn't support
numa.
`
diff --git a/nova/virt/libvirt/driver.py b/nova/virt/libvirt/driver.py
index 4e94b60..d3a37e5 100644
--- a/nova/virt/libvirt/driver.py
+++
The packages list of ubuntu-archive of kilo:
http://reqorts.qa.ubuntu.com/reports/ubuntu-server/cloud-archive/kilo_versions.html
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
The hostsystem is virtualbox, and the guest system is qemu without kvm, because
virtualbox doesn't support hardware acceleration.
The Problem is, that nova-compute generates an invalid xml for this combination.
The offending part is vcpu placement='static'4/vcpu.
This part is not accepted from
I'm a bit confused - what exactly is the bug? It is not that cpusets
inside the guests to not work right? It's that the qemu guest's vcpus
are not pinned to the specified cpus on the host? The host is a true
hardware host? The guest is running accelerated KVM? How is it being
verified that it
Thanks - so the solution is for nova to only drop the placement='static'
from that line, whenever it knows it is using tcg?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
Title:
On the same system (QEMU only) and same version of nova (Kilo), I can
launch an instance with Libvirt 1.2.2 (included with Ubuntu 14.04) but
receive this error with Libvirt 1.2.12 (included with the Kilo cloud-
archive repo). Either Libvirt 1.2.12 reports the wrong capabilities to
nova or nova
Can you show 'virsh capabilities' output with both packages?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
Title:
Libvirt CPU affinity error
To manage notifications about
Looks like a nova bug, I guess it will issue in virt_type=qemu,
libvirt=1.2.7 and compute host that supporting NUMA.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libvirt (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
I also see this is still an issue with http://ubuntu-
cloud.archive.canonical.com/ubuntu trusty-updates/kilo main
VERSION=14.04.1 LTS, Trusty Tahr
# virsh version
Compiled against library: libvirt 1.2.12
Using library: libvirt 1.2.12
Using API: QEMU 1.2.12
Running hypervisor: QEMU 2.2.0
I wasnt able to reproduce this on vivid.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
Title:
Libvirt CPU affinity error
To manage notifications about this bug go to:
Chuck,
What version of libvirt?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
Title:
Libvirt CPU affinity error
To manage notifications about this bug go to:
Nothing jumps out at me from the list of patches we have in the nova
package - most are working around testing challenges due to offline
build environments.
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Raising a libvirt task to get the libvirt maintainers attention - I'll
poke on irc as well.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
Title:
Libvirt CPU affinity error
@Matt V: I hacked an easy place in
/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py line 4720.
change
if CONF.libvirt.virt_type not in ['qemu', 'kvm']:
IN
if CONF.libvirt.virt_type not in ['kvm']:
the commit who changed the numa behavior is 945ab28.
I am not sure, does qemu without
My installation with packages uses the cloud archive repo that includes
libvirt 1.2.12. My installation from source uses the generic 14.04 LTS
repo that includes libvirt 1.2.2. Both installations use the same nova
code (RC1), but the older version of libvirt doesn't exhibit this issue.
Also, I'm
@Matt:
in line 359 in the driver.py is the minimum libvirt version definded for which
the numa code is activated.
MIN_LIBVIRT_NUMA_VERSION = (1, 2, 7)
Therfore you did not trigger the behavior with the source code
installation.
--
You received this bug notification because you are a member of
I have met the same issue:
root@openstack:~# virsh version
Compiled against library: libvirt 1.2.12
Using library: libvirt 1.2.12
Using API: QEMU 1.2.12
Running hypervisor: QEMU 2.2.0
-
root@openstack:~# dpkg -l |grep
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
Still an issue in the 2015.1~rc1-0ubuntu1~cloud0 packages. I built an
environment on hosts that support KVM and successfully launched an
instance, so this issue only affects QEMU. I built another environment
using upstream source and successfully launched an instance using both
QEMU and KVM, so
Any ideas on how one could workaround this?
How to disable affinity in nova, libvirt, or qemu config's?
Some easy place in the code to hack?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
@Matt: Since you're farily certain that this is specific to Ubuntu, then
I hope Ubuntu's Nova package maintainers will take a look. . .
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
I'm not testing NUMA. I am launching a basic CirrOS image using the
m1.tiny flavor, neither of which should trigger NUMA bits. In fact,
adding the hw:cpu_policy=shared to extra_specs in the m1.tiny flavor
has no impact on this issue.
--
You received this bug notification because you are a member
Matt, you're right, allow me to correct myself below. Short: I still
cannot reproduce it.
I just tested it below in a Single node DevStack with today's Nova
git with the Nova instance being QEMU emulated, but I cannot reproduce
the said failure in this bug description.
Test environment
I'm fairly certain this is specific to the Ubuntu packages, not upstream
nova or libvirt.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
Title:
Libvirt CPU affinity error
To
Yes, to test CPU pinning/NUMA with libvirt you ought to use Nested KVM.
Please report results after testing with that.
That said, some notes below.
Quoting Dan Berrange from a different review with a complete response on
*why*:
It is fundamentally impossible to test CPU pinning with TCG (aka
This guest XML would be expected to fail if the guest is running on a
host that is using qemu w/o kvm acceleration:
vcpu placement='static' cpuset='0-1'1/vcpu
...as qemu does not support pinning when kvm isn't available. What's not
clear to me is why the Ubuntu version would be adding this
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1439280
56 matches
Mail list logo
