You will need to modify that patch (as it is particular to power) and
the need for this is across most archs. Particularly via ACPI APEI ERST
on Intel boxes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Does this include the changes/fixes that James Troup reported in bug
#1628750? Or do we expect an urgent update to this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1628809
Title:
[SRU] ceph
So jujud exercises the same code path as ceph-osd? curious
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568729
Title:
divide error: [#1] SMP in task_numa_migrate - handle_mm_fault
To
Does the trusty version (HWE) of the Xenial kernel automatically get
added to this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607404
Title:
Xenial update to v4.4.16 stable release
To manage
Stefan,
Can you add a trusty (Xenial HWE) version of this to the PPA? I'm trying a
rebuild of this as part of a Trusty PPA and getting a failure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568729
Public bug reported:
Stable release of Neutron 7.0.3 was tagged today. I'm not seeing a bug
tracking that so filing.
wily
UCA trusty
** Affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server
Public bug reported:
Stable release of Neutron 7.0.3 was tagged today. I'm not seeing a bug
tracking that so filing.
wily
UCA trusty
** Affects: neutron (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Serge we (Matt Fischer and myself) are using UCA Kilo with Trusty.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1432644
Title:
VM permanently tries to read /dev/shm/lttng-ust-wait-5
@serge this is a different path in Hammer that needs also to have a fix
similar to 1432644 so ANOTHER lttng issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1432644
Title:
VM
And since that was self-referential, maybe we just need a brand new bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1432644
Title:
VM permanently tries to read
So Mfischer said "reopening" I think the bug recurred in a slightly
different way. So maybe we need a new bug either way we'd like the
fix.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
So Mfischer said "reopening" I think the bug recurred in a slightly
different way. So maybe we need a new bug either way we'd like the
fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432644
Serge we (Matt Fischer and myself) are using UCA Kilo with Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432644
Title:
VM permanently tries to read /dev/shm/lttng-ust-wait-5
To manage
And since that was self-referential, maybe we just need a brand new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432644
Title:
VM permanently tries to read /dev/shm/lttng-ust-wait-5
To
@serge this is a different path in Hammer that needs also to have a fix
similar to 1432644 so ANOTHER lttng issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1432644
Title:
VM permanently tries
Public bug reported:
Unweighted OSDs (zero weighted), trigger another "MAX AVAIL 0" bug in
OSD pools.
Ref:
http://tracker.ceph.com/issues/13840
** Affects: ceph (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
Unweighted OSDs (zero weighted), trigger another "MAX AVAIL 0" bug in
OSD pools.
Ref:
http://tracker.ceph.com/issues/13840
** Affects: ceph (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
~mriedem looks like the above isn't the case, that you made fixes to
glance_store and rbd. Is there still suspicion that 0.80.10 is
contributing to the breakage.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
~mriedem looks like the above isn't the case, that you made fixes to
glance_store and rbd. Is there still suspicion that 0.80.10 is
contributing to the breakage.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Vivid issue.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-neutronclient in Ubuntu.
https://bugs.launchpad.net/bugs/1467272
Title:
python-neutronclient 2.4 is required for kilo, but not packaged
To manage notifications
Vivid issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1467272
Title:
python-neutronclient 2.4 is required for kilo, but not packaged
To manage notifications about this bug go to:
Verified in clean vivid.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479496
Title:
[SRU] python-neutronclient 1:2.3.11 +
Verified in clean vivid.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-neutronclient in Ubuntu.
https://bugs.launchpad.net/bugs/1479496
Title:
[SRU]
Public bug reported:
When upgrading from Juno to Kilo (with a system that was initially
installed with Icehouse) a middleware error crops up in Neutron.
It's easiest to show by showing what the dist sets in each of these
releases:
/etc/neutron/api-paste.ini (Icehouse)
[filter:authtoken]
Public bug reported:
When upgrading from Juno to Kilo (with a system that was initially
installed with Icehouse) a middleware error crops up in Neutron.
It's easiest to show by showing what the dist sets in each of these
releases:
/etc/neutron/api-paste.ini (Icehouse)
[filter:authtoken]
This is also true in Vivid (not just UCA).
vivid (python): client - Neutron is a virtual network service for Openstack
1:2.3.11-0ubuntu1: all
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1479496
As noted elsewhere, this is a remnant of:
https://bugs.launchpad.net/python-neutronclient/+bug/1422736
in the upstream openstack python-neutronclient library
which points to this commit:
https://git.openstack.org/cgit/openstack/python-
This is also true in Vivid (not just UCA).
vivid (python): client - Neutron is a virtual network service for Openstack
1:2.3.11-0ubuntu1: all
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to python-neutronclient in Ubuntu.
[DEV] root@bfd02-control-001:~# neutron --debug net-list
DEBUG: keystoneclient.session REQ: curl -g -i -X GET
http://bfd02-internal.os.cloud.twc.net:5000/v2.0/ -H Accept: application/json
-H User-Agent: python-keystoneclient
DEBUG: keystoneclient.session RESP: [200] content-length: 348 vary:
As noted elsewhere, this is a remnant of:
https://bugs.launchpad.net/python-neutronclient/+bug/1422736
in the upstream openstack python-neutronclient library
which points to this commit:
https://git.openstack.org/cgit/openstack/python-
[DEV] root@bfd02-control-001:~# neutron --debug net-list
DEBUG: keystoneclient.session REQ: curl -g -i -X GET
http://bfd02-internal.os.cloud.twc.net:5000/v2.0/ -H Accept: application/json
-H User-Agent: python-keystoneclient
DEBUG: keystoneclient.session RESP: [200] content-length: 348 vary:
Public bug reported:
python-neutronclient 1:2.3.11-0ubuntu1~cloud0
In a network with 80+ networks and routers
returns an error with:
[DEV] root@bfd02-control-001:~# neutron net-list
Request URI Too Long
See attached file for output from: neutron --debug net-list
A quick check with venv pip
Public bug reported:
python-neutronclient 1:2.3.11-0ubuntu1~cloud0
In a network with 80+ networks and routers
returns an error with:
[DEV] root@bfd02-control-001:~# neutron net-list
Request URI Too Long
See attached file for output from: neutron --debug net-list
A quick check with venv pip
[DEV] root@bfd02-control-001:~# neutron --debug net-list
DEBUG: keystoneclient.session REQ: curl -g -i -X GET
http://bfd02-internal.os.cloud.twc.net:5000/v2.0/ -H Accept: application/json
-H User-Agent: python-keystoneclient
DEBUG: keystoneclient.session RESP: [200] content-length: 348 vary:
[DEV] root@bfd02-control-001:~# neutron --debug net-list
DEBUG: keystoneclient.session REQ: curl -g -i -X GET
http://bfd02-internal.os.cloud.twc.net:5000/v2.0/ -H Accept: application/json
-H User-Agent: python-keystoneclient
DEBUG: keystoneclient.session RESP: [200] content-length: 348 vary:
At the top I see Affects for T, U, and V. Where do the Affects for
UCA show up? Ie, where's the patch for Juno on Trusty going to appear?
Is it being considered. (Filing this in one place but of course this
affects almost any T/U backport for I/J and now K OpenStack releases.
What's the right way
** Summary changed:
- [SRU] Memory leaks in librados.py
+ [SRU] Memory leaks in rados.py
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1425164
Title:
[SRU] Memory leaks in rados.py
** Summary changed:
- [SRU] Memory leaks in librados.py
+ [SRU] Memory leaks in rados.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425164
Title:
[SRU] Memory leaks in rados.py
To manage
Has there been any update on this?
(Iknow that's a sad pathetic update.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374109
Title:
epmd does not support binding to an IPv4 address anymore
To
Public bug reported:
minor typo in man uvt-kvm. Says --userdata instead of the proper
--user-data also uploading branch with patch
** Affects: uvtool (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Public bug reported:
minor typo in man uvt-kvm. Says --userdata instead of the proper
--user-data also uploading branch with patch
** Affects: uvtool (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
medberry@hob:~/launchpad/man-page-fix$ bzr push lp:~med/junk/uvtool-man-page-fix
Using default stacking branch /+branch-id/348568 at
chroot-73525584:///~med/junk/
Created new stacked branch referring to /+branch-id/348568.
--
You received this bug notification because you are a member of Ubuntu
** Patch added: lp1401749.patch
https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/1401749/+attachment/4279209/+files/lp1401749.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1401749
Public bug reported:
Please update this to at least 0.4 or 0.4.1
** Affects: python-openstackclient (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
By adding -p and -m to the start-stop-daemon call to enable glance-
control to function properly (ie, whether started via upstart or with
glance-control).
Needs to be added to both:
glance-api.glance-api.upstart
glance-registry.glance-registry.upstart
files in the ./debian/
Public bug reported:
By adding -p and -m to the start-stop-daemon call to enable glance-
control to function properly (ie, whether started via upstart or with
glance-control).
Needs to be added to both:
glance-api.glance-api.upstart
glance-registry.glance-registry.upstart
files in the ./debian/
Patch that fixes
** Patch added: amends upstart scripts for g-a and g-r
https://bugs.launchpad.net/ubuntu/+source/glance/+bug/1386906/+attachment/4247595/+files/glance.lp1386906.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
It does appear that this should be referring to 0.80.* based on:
http://ceph.com/download/ and
ppa:james-page/utopic
https://launchpad.net/~james-page/+archive/ubuntu/utopic
** Summary changed:
- [SRU] 0.86.7 stable update
+ [SRU] 0.80.7 stable update
--
You received this bug notification
It does appear that this should be referring to 0.80.* based on:
http://ceph.com/download/ and
ppa:james-page/utopic
https://launchpad.net/~james-page/+archive/ubuntu/utopic
** Summary changed:
- [SRU] 0.86.7 stable update
+ [SRU] 0.80.7 stable update
--
You received this bug notification
This issue still exists. At each boot it does an interface rename
(dl380p Gen8 with two 10G nics)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324558
Title:
[SRU] biosdevname returns identical
@jamespage when will this hit t-proposed?
--
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/1354159
Title:
[SRU] icehouse 2014.1.2 point release
To manage notifications about this bug
@jamespage when will this hit t-proposed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1354159
Title:
[SRU] icehouse 2014.1.2 point release
To manage notifications about this bug go to:
Is this SRU being MREd? Or are we just using the standard SRU process
for Icehouse-Trusty updates?
--
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/1328134
Title:
[SRU] icehouse
Is this SRU being MREd? Or are we just using the standard SRU process
for Icehouse-Trusty updates?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328134
Title:
[SRU] icehouse 2014.1.1 point release
** Summary changed:
- check and alarm on broken simplestreams data on cloud-images.ubunt.com
+ check and alarm on broken simplestreams data on cloud-images.ubuntu.com
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This likely needs to go into an SRU for Precise and get fixed in Trusty
and Utopic.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1247803
Title:
dnsmasq temporarily breaks DNS
This likely needs to go into an SRU for Precise and get fixed in Trusty
and Utopic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1247803
Title:
dnsmasq temporarily breaks DNS resolution when
Shang, as I understand it, yes, since 0.80 is going into trusty proper,
it should be supported as long as Trusty is. Per
https://wiki.ubuntu.com/Releases that is April 2019. (That's not to say
that Trusty won't update to an even newer version as part of that
support process--it certainly could.)
Shang, as I understand it, yes, since 0.80 is going into trusty proper,
it should be supported as long as Trusty is. Per
https://wiki.ubuntu.com/Releases that is April 2019. (That's not to say
that Trusty won't update to an even newer version as part of that
support process--it certainly could.)
Henrik, can you please reference the bugs fixed (mentioned above). I'm
looking through the git log and not seeing anything specifically
addressing this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
Henrik, can you please reference the bugs fixed (mentioned above). I'm
looking through the git log and not seeing anything specifically
addressing this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see two commits in the branch-1.4 that came after the release. I'll
build a version with those and re-run my GRE tests (with the problematic
quantal kernel) and see if it recurs. The 1.4 branch is basically end-
of-life from OVS upstream as far as I can tell. 1.9 is considered their
LTS.
--
I see two commits in the branch-1.4 that came after the release. I'll
build a version with those and re-run my GRE tests (with the problematic
quantal kernel) and see if it recurs. The 1.4 branch is basically end-
of-life from OVS upstream as far as I can tell. 1.9 is considered their
LTS.
--
Verified that the OOPS is a kernel bug (not the OVS packages) by re-running
with
3.5.0-42-generic #65-Ubuntu SMP Tue Oct 1 23:38:22 UTC 2013 x86_64 x86_64
x86_64 GNU/Linux
(3.5.0-44-generic generated the oops.)
Upgrade via quantal-proposed and code in OVS-1.4.6 works fine:
Verified that the OOPS is a kernel bug (not the OVS packages) by re-running
with
3.5.0-42-generic #65-Ubuntu SMP Tue Oct 1 23:38:22 UTC 2013 x86_64 x86_64
x86_64 GNU/Linux
(3.5.0-44-generic generated the oops.)
Upgrade via quantal-proposed and code in OVS-1.4.6 works fine:
Screencap of OOPS.
** Attachment added: Screencap of OOPS.
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1219788/+attachment/3931252/+files/ovs-oops.quantal.png
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
VMs with OOPS reproducer avail on request.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1219788
Title:
[SRU] Update openvswitch to 1.4.6 stable release
To manage
Hi James/Daviey,
I'm getting a kernel oops when I try this on Quantal. Christopher Arges
is debugging the OOPS but I can't verify on Quantal as a result. (Note:
I believe Quantal also oopses with the existing OVS so it's not
necessarily related to 1.4.6 or this specific version/upgrade/release.)
Hi James/Daviey,
I'm getting a kernel oops when I try this on Quantal. Christopher Arges
is debugging the OOPS but I can't verify on Quantal as a result. (Note:
I believe Quantal also oopses with the existing OVS so it's not
necessarily related to 1.4.6 or this specific version/upgrade/release.)
VMs with OOPS reproducer avail on request.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1219788
Title:
[SRU] Update openvswitch to 1.4.6 stable release
To manage notifications about this bug go
Screencap of OOPS.
** Attachment added: Screencap of OOPS.
https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1219788/+attachment/3931252/+files/ovs-oops.quantal.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It doesn't look like the Ubuntu version has synced with Debian in some
time. I can't tell by examining https://launchpad.net/ubuntu/+source
/live-build why that is the case. I think Ben marked it as fix-committed
for the build system (but not for the actual ubuntu package.)
--
You received this
Using the #1 work around, got my USB devices working again.
(Installed USBDeview in Windows to have a view of the USB tree in Windows
guest.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245251
@Serge
I was passing in specific devices all along and this just doesn't work
in Saucy.
medberry@handsofblue:~$ dpkg -l libvirt-bin qemu-system
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required
Oh, and I had been using kvm-qemu via the virtual machine manager.
Here's what my qemu command looks like:
medberry@handsofblue:~$ sudo cat /proc/3378/cmdline |xargs -0
qemu-system-x86_64 -machine accel=kvm:tcg -name Fitbit -S -machine
pc-i440fx-1.5,accel=kvm,usb=off -m 1024 -realtime mlock=off
xml for my domain
** Attachment added: virsh dumpxml Fitbit
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1245251/+attachment/3904462/+files/fitbit.xml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Updates should be made to:
https://help.ubuntu.com/community/KVM/Managing
for the USB Passthrough method.
(It also may have some errors--are we still limited to USB 1.1?)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Okay, opening a new bug with content from 2013-11-08
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju in Ubuntu.
https://bugs.launchpad.net/bugs/1149410
Title:
Stuck on Trying to connect to the Juju environment
To manage
Okay, opening a new bug with content from 2013-11-08
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1149410
Title:
Stuck on Trying to connect to the Juju environment
To manage notifications about
I've spent some more time with this and suspect OpenStack folks will be
moving to 1.10.x if seriously interested in this. Not sure how they
would go about that on raring officially but unofficially it works fine.
I don't have a case/cause for getting anything newer into Raring so
feel free to
I've spent some more time with this and suspect OpenStack folks will be
moving to 1.10.x if seriously interested in this. Not sure how they
would go about that on raring officially but unofficially it works fine.
I don't have a case/cause for getting anything newer into Raring so
feel free to
Public bug reported:
OpenVSwitch upstream treats 1.9.x as their LTS. They have fixed a number
of bugs that should also be fixed in raring's 1.9.x.
In particular, 46c9e8c1a833c77991257363b4bf1034f22e52ec fixes a
segfault.
It also appears they accepted one of James Page's patches so be aware of
Public bug reported:
OpenVSwitch upstream treats 1.9.x as their LTS. They have fixed a number
of bugs that should also be fixed in raring's 1.9.x.
In particular, 46c9e8c1a833c77991257363b4bf1034f22e52ec fixes a
segfault.
It also appears they accepted one of James Page's patches so be aware of
Public bug reported:
From Raring to Saucy, do-release-upgrade still omits a --download-only
(though there are some sketchy work arounds in Ubuntu Answers.)
Regardless, lack of this option is a bug.
Versions:
Ubuntu 13.04 - 13.10
ubuntu-release-upgrader-core 1:0.192.13
Expectations:
** Changed in: lansing
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210280
Title:
libgtop2 used by system monitor reporting incorrect number of
processors
we can probably close this after the meeting today. Marked as confirmed
after checking old and new repo
** Changed in: walinuxagent (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to walinuxagent
** Changed in: lansing
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/1193175
Title:
hv-kvp* needs to be included in default installation of Ubuntu
** Changed in: lansing
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1193175
Title:
hv-kvp* needs to be included in default installation of Ubuntu 13.10
on Hyper-V
we can probably close this after the meeting today. Marked as confirmed
after checking old and new repo
** Changed in: walinuxagent (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Apparently SuSE has patched there version (and is likely that disconnect
is what triggered the initial customer concern.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210280
Title:
libgtop2 used
** Changed in: lansing
Assignee: (unassigned) = David Medberry (med)
** Changed in: lansing
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1213282
Title
** Changed in: lansing
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210280
Title:
libgtop2 used by system monitor reporting incorrect number of
processors for
Thanks kernel folk.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1197526
Title:
Include Synthetic Fiber Channel and a few other storage patches in
Ubuntu 13.10
To manage notifications about
Marc,
I didn't see that GLIBTOP_NCPU was used anywhere else. I'll dig some more.
Yes, it will dramatically increase memory consumption in some tools.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
path to source:
kernel.git/tools/hv/hv_vss_daemon.c
Should be built similarly to hv_kvp_daemon.
** Also affects: lansing
Importance: Undecided
Status: New
** Changed in: lansing
Status: New = Confirmed
** Changed in: lansing
Importance: Undecided = High
** Changed in:
Public bug reported:
For hyper-v and azure, we need to support host initiated snapshot.
Please add hv_vss_daemon to linux-tools (similarly to hv_kvp daemon.)
** Affects: lansing
Importance: High
Status: Confirmed
** Affects: linux (Ubuntu)
Importance: Undecided
Hi Louis,
Thanks for the response (and I fully agree and went ahead after I was
convinced.)
My official writeup settled it this way (which works for even the smallest
instance on Azure):
WAS:
74 # add crashkernel option if we have the required tools
75 if [ -x /usr/bin/makedumpfile ] [
This appears to be a setting in glibtop/cpu.h:
https://developer.gnome.org/libgtop/stable/libgtop-cpu.html#GLIBTOP-
NCPU:CAPS which becomes an array size and only GLIBTOP_NCPU are
gathered.
From the source package: libgtop2:
cat -n
...
53 /* Nobody should really be using more than 4
Adding appopriate source package, libgtop2
** Package changed: ubuntu = libgtop2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210280
Title:
System monitor reporting incorrect number of
Currently Ubuntu supports 256 CPUs in a server config (ref:
http://askubuntu.com/questions/158555/how-many-maximum-cpus-does-ubuntu-
support-by-default) and that # is still valid for Saucy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
1 - 100 of 218 matches
Mail list logo
