** Also affects: kernel-package (Ubuntu)
Importance: Undecided
Status: New
--
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/2018612
Title:
Guest kernel crashes
Public bug reported:
What?
-
Add a workaround config option (that will be disabled by default) that
will disable the version-checking of hypervisors during live-migration.
Why?
It can be useful for operators in certain scenarios when upgrading.
E.g. if you want to relocate all
** Changed in: nova
Status: Invalid => Triaged
** Changed in: nova
Importance: Wishlist => Medium
--
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/1852437
Title:
Public bug reported:
[This bug was originally reported by Lukas Bezdicka when testing Red
Hat's OpenStack (OSP); but this should be reproducible in upstream
context as well. I'm writing this report based on the root cause
analysis in the environment where the bug occcurred. Thanks to Daniel
This looks like your installation of QEMU is completely broken.
As confirmed on IRC:
/usr/bin/qemu-system-ppc64: relocation error: /usr/bin/qemu-system-
ppc64: symbol fdt_check_full version LIBFDT_1.2 not defined in file
libfdt.so.1 with link time reference
Please consult Ubuntu's guidance
** 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/1852437
Title:
Allow ability to disable individual CPU features via
So, the libguestfs files in /var/tmp/.guestfs-0/appliance.d are the
*cache* and libguestfs never removes those files.
(Double-checked with libguestfs maintainers.)
And Nova _shouldn't_ delete those files either; that's wrong.
Instead, we suggest to use a tool like `systemd-tmpfiles`; from its
** Project changed: nova => qemu
--
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/1829696
Title:
qemu-kvm takes 100% CPU when running redhat/centos 7.6 guest VM OS
Public bug reported:
Nova uses QEMU's disk image cache modes in two main areas:
(1) When decicding what cache mode to use for the target disk image when
converting (using `qemu-img convert`) images from one format to
another (qcow2 <-> raw).
See unprivileged_convert_image() in
libvirt == v.4.4.0
* * *
Broader context and background here:
https://lists.gnu.org/archive/html/qemu-devel/2015-02/msg00529.html
RFC: Universal encryption on QEMU I/O channels
** Affects: nova
Importance: Medium
Assignee: Kashyap Chamarthy (kashyapc)
Status: New
Public bug reported:
Background
--
QEMU supports two main variants of "machine type" (think of it as a
virtual chipset) for x86 hosts: (a) 'pc', which corresponds to Intel's
'i440FX' chipset; and (b) 'q35', which corresponds to Intel's 82Q35
chipset. (For AArch64 hosts, the machine type
Public bug reported:
In addition to the existing 'virt-ssbd', future AMD CPUs will have _two_
ways to deal with SSBD (Speculative Store Bypass Disable). To that AMD
will be introducing two more[1][2] CPU flags:
amd-ssbd
amdb-no-ssb
It is recommended to add the above two flags to the
** Changed in: nova
Status: In Progress => 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/1766208
Title:
Lift the restriction on choices for
Not to belabor this: FWIW, as you know, we intentionally restricted the
original feature. So now we're just fixing that "bad" implementation.
So personally, I'd prefer to track this item in this bug too. But if
you really insist, I can let it go.
** Changed in: nova
Status: Invalid => In
sing performance issue or other
nuisance, and if the Operator isolated the problem to _that_ specific
CPU flag, then she may want to remove the flag.
** Affects: nova
Importance: Undecided
Assignee: Kashyap Chamarthy (kashyapc)
Status: New
** Tags: libvirt
** Changed in: nova
Ass
Public bug reported:
Upstream Linux kernel has removed[*] the 'perf cqm' (Cache
Quality-of-Service Monitoring) from the following kernels onwards:
[linux]$> git tag --contains c39a0e2
v4.14
Impact for OpenStack / Nova
---
Quoting the summary from Dan Berrangé
huge pages with Haswell model as one use case for
extra flags (thanks: Daniel Berrangé, for mentioning this scenario):
cpu_model_extra_flags=Haswell
cpu_model_extra_flags="pdpe1gb"
** Affects: nova
Importance: Undecided
Assignee: Kashyap Chamarthy (kashya
08 MiB/s
generated 10 requests in 9.00 s, 40 KiB, 1 iops, 4.44 KiB/s
min/avg/max/mdev = 838.2 us / 956.9 us / 1.13 ms / 81.0 us
This goes back to an average of 200us again after shutting down and
starting up the instance.
Expected result
===
No I/O latency experienced on C
** Also affects: libvirt (Ubuntu)
Importance: Undecided
Status: New
--
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/1673483
Title:
libvirt:
[Looks like a Nova-related issue, since it is not requesting a volume
detach from Cinder -- so moved this bug to Nova component.]
** Project changed: cinder => nova
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack
pu_model
** Affects: nova
Importance: High
Assignee: Kashyap Chamarthy (kashyapc)
Status: New
** Changed in: nova
Assignee: (unassigned) => Kashyap Chamarthy (kashyapc)
** Changed in: nova
Importance: Undecided => High
--
You received this bug notification because you are a
Public bug reported:
Description
===
Booting an instance from snapshot (which is an instance booted from
Cinder volume) fails with:
ERROR (BadRequest): Volume is smaller than the minimum size specified in
image metadata. Volume size is 1073741824 bytes, minimum size is
Public bug reported:
There seem to be 17 occurrences of this error in the last 7 days
[starting 3DEC2015]:
message: "libvirtError: cannot read header" AND tags:
"screen-n-cpu.txt"
And, 195 occurrences of the below error message string when looked at
logstash, :
message: "session 2
Public bug reported:
Description of problem
--
Once DevStack is completed successfully, attempting to boot an instance
fails, resulting in:
$ . openrc admin
$ nova flavor-create eph 100 512 0 1 --ephemeral 10
$ nova boot --image cirros-0.3.3-x86_64-disk --flavor
Public bug reported:
Noticed this in 'check-devstack-dsvm-cells' job failure:
Specific errors from tracebacks in logs (screen-n-cell-region.txt.gz,
screen-n-cell-child.txt.gz:
[. . .]
2015-02-05 10:03:43.694 ERROR nova.cells.messaging
[req-140b752f-0e02-4fa3-a781-e3bc39018238 demo demo] Error
Public bug reported:
Booting a Nova instance successfully with hw:numa_nodes=0, with a Nova
guest XML like that[*]. This bug came out of this RDO bug --
https://bugzilla.redhat.com/show_bug.cgi?id=1154152.
But, talking with Daniel Berrnage and Nikola Dipanov on IRC, they suggest we
should
Public bug reported:
Description of problem
--
From the proposed Nova specification Virt driver large page allocation
for guest RAM[*], if you set the Nova flavor extra_spec for huge pages
as 'any' ('nova flavor-key m1.hugepages set hw:mem_page_size=any',
it means: leave
Closing this bug per comment #3.
Please reopen it (with more verbose details) if you encounter it again.
** 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).
Public bug reported:
I encountered this as part of check-neutron-dsvm-functional test job
failure from Jenkins.
Contextual log snippet (from console.html)[1]:
.
.
.
2014-07-01 03:31:05.323 | 2014-07-01 03:31:05.304 | Command: ['sudo',
:00:07 node2-compute nova-compute[1529]: 2014-01-08 07:00:07.200
1529 TRACE nova.openstack.common.threadgroup
[reply] [−]
Private
Comment 1 Kashyap Chamarthy 2014-01-08 09:21:17 EST
More contextual trace from compute.log:
[. . .]
2014-12-10 22:12:38.789 1429 TRACE
]: 2014-01-08 07:00:07.200 1529
TRACE nova.openstack.common.threadgroup
[reply] [−]
Private
Comment 1 Kashyap Chamarthy 2014-01-08 09:21:17 EST
More contextual trace from compute.log:
[. . .]
2014-12-10 22:12:38.789 1429 TRACE nova.virt.libvirt.driver
2014-12-10 22:12:39.319 1429 ERROR
31 matches
Mail list logo
