FYI - the merge itself would be complete, but while testing I found an issue
introduced in some former ubuntu delta that would now kill the configuration of
an already installed nis on update (bad handling of conffiles).
We will have to create a fix for this transition before we can go on with
Some initial analysis to support further decisions
Version check
Version upstream
4.2.8p4 2015/10/21
Latest versions in Ubuntu
1:4.2.6.p3+dfsg-1ubuntu3.6 | precise-security
1:4.2.6.p5+dfsg-3ubuntu2.14.04.5 | trusty-security
1:4.2.6.p5+dfsg-3ubuntu6.2 | vivid-security
** Changed in: nis (Ubuntu)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
** Changed in: nis (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
FYI - After a discussion I'll likely revamp the patches for wily and upstream
the next days.
Until then we will also decide if this is worth SRUs for trusty/vivid.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
** Patch added: "Fix for upstream"
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/525674/+attachment/4486128/+files/upstream_package.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Other MOTD plugins use caching, for example
/usr/lib/update-notifier/update-motd-reboot-required does:
if [ -f /var/run/reboot-required ]; then
cat /var/run/reboot-required
fi
Actually /usr/lib/update-notifier/update-motd-updates-available already uses
"caching" like the others.
It
** Patch added: "Fix for vivid"
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/525674/+attachment/4486126/+files/vivid_package.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
** Patch added: "Fix for trusty"
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/525674/+attachment/4486125/+files/trusty_package.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
** Patch added: "Fix for wily"
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/525674/+attachment/4486127/+files/wily_package.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
Here the bigger, but more architecturally complete solution for
wily (which is actually identical at this time).
Summary:
- move the actual updating part out of the pam based trigger completely (avoids
slowdown)
- pam based motd now only prints the cached info (if existing)
- hook into apt with
** Patch added: "Enhanced fix for Wily and Upstream"
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/525674/+attachment/4487279/+files/wily_and_dev_package.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the
** Patch added: "Enhanced fix for Wily and Upstream (version 3)"
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/525674/+attachment/4489492/+files/wily_and_dev_package.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Martin:
- I already removed one indirection with my former patch and love to remove one
more.
Simple code = good code - thanks for the good hint.
- I changed it slightly to use the existing variable so people recognize from
which code
it came and to avoid issues if one ever changes only one
snmp and snmpd are part of one source being: net-snmp
I could confirm that this still affects wily/upstream
The killall was introduced way back by
* debian/snmp.preinst, debian/snmp.prerm: kill any/all processes owned by
snmp user before install/uninstall, LP: #573391
-- Dustin Kirkland
** Patch added: "debdiff for wily and upstream"
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1245604/+attachment/4489741/+files/wily_and_dev_package.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
As described by Robie versions are:
precise: n/a
trusty: n/a
vivid: 1.53+2014.06.08.git.918
wily: 1.56-1
To reproduce the issue I installed the tool and wrote a minimal test
wrapper based on online examples - and hey it is fairly short (not even
worth an attachment).
#!/usr/bin/env python3
** Patch added: "backport of the fix that was upstream in python3-memcache 1.54"
https://bugs.launchpad.net/ubuntu/+source/python-memcache/+bug/1492604/+attachment/4484805/+files/fix-python3-memcache-str-handling-rebase1.53.diff
--
You received this bug notification because you are a member
I can confirm that with this as backport applied the testcase runs fine.
** Changed in: python-memcache (Ubuntu)
Status: New => In Progress
** Changed in: python-memcache (Ubuntu)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
--
You received this bug notification b
First of all thanks for checking the fix. and yes so far it is only
released for Xenial (16.04).
Given the time it was open and the amount of feedback we have got I
assumed it wouldn't be worth an SRU -
https://wiki.ubuntu.com/StableReleaseUpdates.
I'm still not sure if it is worth an SRU given
I looked into it more in detail - It is actually a bigger change than just
reusing what we did for Xenial.
Since for Xenial we did a lot of cleanup regarding upstart we can't just
"reuse" what we have for trusty.
--
You received this bug notification because you are a member of Ubuntu
Server
Public bug reported:
When building the test environment for subiquity I end up with an image I can
run with qemu/kvm.
And I realized that this works fine with the Trusty kernel (Host), but when
running on trusty+hwe-t (4.2.0-23-generic) it reliably crashes my host (not
only the guest).
On the
** Attachment added: "two of the bug on messages I found in dmesg after
restarting my system"
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1532571/+attachment/4547455/+files/subiquity-installer-triggers-kernel-bug
--
You received this bug notification because you are a member of
I can use cgm to do some getrecursive calls without issue, like this:
cgm gettasksrecursive freezer
With that I think my quick debugging has reached its end, but lets
assign to the proper components now that we know.
** Package changed: shadow (Ubuntu) => cgmanager (Ubuntu)
--
You received
I wanted to summarize that we addressed all MIR feedback.
Note: Also the merge to DPDK2.2 is done and in universe for a few days now.
So @Seth/Michael - does this qualify for your conditional ACK in post
#16 and we are fine to go now and promote it to main?
--
You received this bug notification
Regarding the State in Debian:
I filed an ITP offering joint effort work on it.
If someone in Debian cares about dpdk we would keep it "compatible" together,
if not we have no collision.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815760
Regarding Tests
As I mentioned multiple times the
I was working on a fix to bring it upstream first, but there our old discussion
with a wider scope got picked up again.
=> http://dpdk.org/dev/patchwork/patch/9088/
There are always tradeoffs to be made and we had quite some discussions on
so-versioning and such I don't want to go in to, but the
FYI - the linker script solution seems to be refreshed and picked up for
2.3 http://dpdk.org/dev/patchwork/patch/9088/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1546547
Title:
** Changed in: dpdk (Ubuntu)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1547517
Title:
libdpdk should link agai
Public bug reported:
With the recent merge to postfix 3 there were quite some changes to its
configuration.
Now postfix has a lot to handle those changes in a compatible way so that old
configurations should transfer to postfix 3 as good as possible.
In case any incompatibilities occur it
Hi,
I couldn't reproduce today.
The device stays in:
0:0:0:1074675728 sdb 8:16 active faulty offline
And when re-adding it comes back online just nice.
The way I configured was via chzdev like:
I used the z/VM approach with detaching the FCP adapter.
I used the multipath.conf as reported
After discussing on #ubuntu-devel it was decided that the tests should guard
themselves and skip the test if not appropriate.
Such specific HW need seems rare and there is no e.g. autopkgtest feature to
limit Architectures.
Note: it was considered a "regression" because the fact that before we
FYI - this started on Friday and while we were almost done right now it
is worth to document this for further reference e.g. from the
Changelogs.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
Public bug reported:
While adding further tests we realized that DPDK tests would fail on non
supported platforms.
While it makes perfect sense for them to fail, most involved people wondered
why it even ran there.
Long story short: The dpdk package builds packages for all platforms like
[...]
- Needs a team bug subscriber
=> FYI - Done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1492186
Title:
[MIR] dpdk
To manage notifications about this bug go to:
Public bug reported:
The upstream DPDK project does not keep sover's on their combined library.
There was some great work to properly version all the sublibraries going into
For now we have to live with the state as (deliver as sover 0) is and all its
implications like complex
More an openvswitch-switch-dpdk than a pure dpdk issue, but should be
tracked in both.
** Package changed: dpdk (Ubuntu) => openvswitch-dpdk (Ubuntu)
** Changed in: openvswitch-dpdk (Ubuntu)
Importance: Undecided => Medium
** Changed in: openvswitch-dpdk (Ubuntu)
Status: New =>
Public bug reported:
One might think it has no DPDK support when liiking at it as well as this is
kind of an exception of the usual library handling.
So for example openvswitch-switch-dpdk depends on libdpdk0 which seems right.
But in fact it would not have to as it is build with that library
Public bug reported:
Openvswitch has a nice security feature where one can drop privileges via
--user option.
Unfortunately due to the nature of DPDK it needs root permissions to initialize
most of its resources.
Thereby --dpdk and --user are mutually exclusive.
There are upstream discussions
Public bug reported:
As of today the vhost_user sockets created by openvswitch have root:root file
ownership.
In fact creation is actually done by code the DPDK lib, but the path is passed
to it from openvswitch.
The API called to DPDK has no notion of ownership/groups.
It just "inherits" what
** Changed in: dpdk (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1538664
Title:
Please enable ppc64el on dpdk
To manage notifications about
** Changed in: dpdk (Ubuntu)
Status: New => Triaged
** Changed in: dpdk (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1539775
Public bug reported:
See:
ldd usr/lib/x86_64-linux-gnu/libdpdk.so.0
linux-vdso.so.1 => (0x7ffc977e3000)
Public bug reported:
It all started out as a typical case of "something happened".
Looking at the CI history of openvswitch-dpdk at
http://autopkgtest.ubuntu.com/packages/o/openvswitch-dpdk/xenial/amd64/.
We weren't sure if the test machines or any other part of the execution changed.
But due to
On Fri, Feb 19, 2016 at 6:35 PM, Martin Pitt <martin.p...@ubuntu.com>
wrote:
> ChristianEhrhardt [2016-02-19 14:02 -]:
>
[...]
> > But later infinity pointed out if we shouldn't bump our scalingstack
> > machine configs as all underlying HW would support that. In
Sharing a few good statements from a chat with infinity with all participants
on this bug
And from me thanks Adam for these insights to part of Ubuntus build/test
history.
Quoting Infinity:
"We'd want scalingstack buildds and autopkgtest to match if we're changing
machine type. Having
** Also affects: autopkgtest (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1547528
Title:
How to handle specific HW needs for
** Changed in: dpdk (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1546565
Title:
Ownership/Permissions of vhost_user sockets for
** Changed in: dpdk (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1546556
Title:
Dropping privileges in openvswitch-switch via --user is
I still expected smb to do this, so I missed that - sorry.
Verifying:
1. verified the issue before proposed
2. updated to proposed
3. I see the mk missing issues gone:
e.g. those appear no more:
Makefile:39: /usr/share/dpdk/mk/rte.vars.mk: No such file or directory
Makefile:50:
I still expected smb to do this, so I missed that - sorry.
Verifying:
1. verified the issue before proposed
2. updated to proposed
3. I see the critical calls removed in the init script
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
It has to be noted that the steps-to-reproduce have other issues to
build the l2fwd as-is, but the issue addressed with this bug is indeed
fixed.
** Tags removed: removal-candidate verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a
** Tags removed: removal-candidate verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1516543
Title:
dpdk-init depends on executables
Public bug reported:
In System z one often has plenty of devices in the channel subsystem but
only a few of them configured.
Currently
/etc/sysconfig/scripts/hardware/hwup
/etc/sysconfig/scripts/hardware/functions
Print a log message like this:
Mär 14 09:30:43 s1lp5 systemd-udevd[1169]: Process
script, but actually even when mounting a
1G mountpoint it fails.
It needs to be debugged in what way it expects a non-default size hugepage
mount and then provided by dpdk init scripts OR fixed in dpdk code.
** Affects: dpdk (Ubuntu)
Importance: Medium
Assignee: ChristianEhrhardt
Check code
opens /proc/mounts
gets pagesz_str defining what the mountpoint has
if nothing is set assume default size
if something is set in the mp's options calculate the size
check if this is the mountpoint matching
=> not working for my mountpoint
Need to be run in gdb, to check where exactly
The detection failure was a false positive.
The following would provide a sufficient mount point.
sudo mount -thugetlbfs hugetlbfs /dev/hugepages-1G -o "pagesize=1G"
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
It seems we have to decide if we want to hardcode a directory path for
the non-default mountpoint or if we want to replicate dpdks logic to
parse and detect (including size recalculations).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
Hi,
I realized that bug seems dormant :-/
So I wanted to let you know that I keep this unread in my inbox all the
time.
It juts currently buried under other priorities.
But I really intend to take a closer look at a potential SRU as soon as I
can.
Christian Ehrhardt
Software Engineer, Ubuntu
I have working code, but found various other combinations - like if one
pages size isn't supported at all - that I have to take care of first.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
Thank you Hikari Kobayashi for reporting the issue and even doing the
work identifying the patch.
This was backported to 2.4.11 and therefore obviously is also in 2.4.18.
Thereby Xenial and Wily are not affected.
Note: This is a regression 2.2.22 (precise) -> 2.4.7 (trusty) since migrating
from
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
Hi,
you are right that default configurations should be sane.
I totally like your report on the potential DOS, by keeping a connection open
and so stalling the restart forever.
So I don't just want you or me to close it.
But then the GracefulShutdownTimeout being zero is the apache default - not
a remaining tr change o - to _ which is wrong,
see bug 1554214.
Both should be fixed, so that in case an admin or experiment unassigned
devices and wants to get back to normal by restarting the script would
not fail.
** Affects: dpdk (Ubuntu)
Importance: Medium
Assignee: ChristianEhrhardt
cal
Assignee: ChristianEhrhardt (paelzer)
Status: Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1559912
Title:
Openvswitch 2.5 + dpdk 2.2 totally failing for virtio
It was also reported in 1559408 that this also affects BNX2X_PMD
** Description changed:
*as a start same text as my reach for the involved project mailing
lists*
I was trying to replicate a setup that I have working on physical devices
(ixgbe) under kvm since there is a virtio pmd
ed in: dpdk (Ubuntu)
Importance: Undecided => Critical
** Changed in: dpdk (Ubuntu)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.laun
Since I consider the extra PMDs kind of "unsupported" upstream I have to
rate it low for now.
** Changed in: dpdk (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
Hi Thiago,
you were busy weren't you :-)
Thanks your further experiments and reports - I'll try to refer all the open
points.
Trying to summarize:
1. The vfio grouping issue is not a bug, just the vfio setup being more complex
in general. But you already handled that for your setup - great.
As an example what I meant to imply here the reason why it is disabled
by default as of now.
commit ce9b8bb8b99877026fcca00fdb253fa3ec3a7e06
Author: Thomas Monjalon
Date: Tue Jul 28 18:22:39 2015 +0200
config: disable bnx2x driver
This driver has too
** Also affects: openvswitch-dpdk (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1559912
Title:
Openvswitch 2.5 + dpdk 2.2 totally
Actually these might be good candidates to go to
http://dpdk.org/browse/dpdk-stable/.
Once my testing is done I should suggest that.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
Ok, I did the backport.
This package is somewhat scary old at some places (no patches, dh compatibility
level 1 - well undefined).
Yet I was able to keep changes minimal and the changes that went into
the Debian upgrade from .33 to .34 applied as is.
It is building fine in trusty.
I revived my
Since so many things changed since this - admittedly embarrassing old -
bug was reported I thought I retest it before the next LTS comes out.
I looked at the Xenial content and found stuff like:
Not only is it specified "After network.target", but on top there is
at least
some of them.
** Affects: dpdk (Ubuntu)
Importance: High
Assignee: ChristianEhrhardt (paelzer)
Status: Triaged
** Changed in: dpdk (Ubuntu)
Status: New => Triaged
** Changed in: dpdk (Ubuntu)
Importance: Undecided => High
** Changed in: dpdk (
Info on progress.
No feedback from communities so far.
After various other DPDK fixes took 3/4 of my day I set up a more thorough
debugging environment derived from my testing env, but the real debugging
itself has to start tomorrow morning.
--
You received this bug notification because you
Martin since I'm happy you work with that code base I'd recommend you create a
test setup based on virtio.
You will still be blocked on bug 1559912 for now, but I'm working on that this
week and stil hope to get some upstream support.
I'll reject this bug for the given reasons now, but please
I checked the other default disabled drivers.
To all some kind of incompleteness, non-support or being only stubs applies.
It could be said, that the same is true for the virtual ones we enable like
PCAP and XEN.
But there is a major difference in:
- nobody is "buying" the HW for pcap or XEN to
I had a focus on identifying:
- only patches to components that are enabled in our packaging
- issues that have a real chance to occur on the usage we expect for 16.04
timeframe
- patches that are small, so review is not overly complex
- apply without manual adaption (offset ok to some extend, no
Subscribing the ~ubuntu-sru Team to evaluate and consider this for a
Trusty SRU.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1204530
Title:
yppasswd results in a segmentation fault
** Patch added: "Debdiff for Trusty"
https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1204530/+attachment/4608491/+files/bug-1204530-SRU-nis_3.17-32ubuntu6-to-nis_3.17-32ubuntu7.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
[Impact]
* The bug is a segfault on yppasswd rendering users unable to change their
passwords
* justification for the SRU is the continued request by users and the fact
that it is a very minimal change
* the fix ensures that a lib accessing data unconditionally only gets called
if the
ok, code is ready I wait a few days for something else to be wrapped up in one
upload.
*beta release hanging over me*
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1557532
Title:
Hi,
in Xenial 2.7.2-4ubuntu1 got merged.
The issue that our delta solved by dropping of the systemd service, seems
solved in Debian >=2.7.2
The Debian Changelog part in 2.7.2-2 is:
* Add wrappers that check the MODE in /etc/nut/nut.conf to avoid starting
the daemons if nut is not
for the upstream discussion to finish and apply.
Then we will pick and apply those as backport patches in packaging.
** Affects: dpdk (Ubuntu)
Importance: Medium
Assignee: ChristianEhrhardt (paelzer)
Status: Triaged
** Changed in: dpdk (Ubuntu)
Status: New => Tria
One of the patches got an ack upstream, the other is still waiting for
attention.
None is committed yet.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1554009
Title:
use after free
ged
** Changed in: dpdk (Ubuntu)
Importance: Undecided => Medium
** Changed in: dpdk (Ubuntu)
Assignee: (unassigned) => ChristianEhrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.laun
Yeah we changed the dpdk piece to properly be linkable in bug 1547517.
And James did some great work on updating openvswitch to 2.5.
We just have forgot to update this one, I'll talk to James later if he agrees
that we can close it.
Thanks already Thiago for making me aware!
--
You received
instead of failing
3. add a comment about the need into /etc/dpdk/interfaces so people can read it
while configuring instead when failing
** Affects: dpdk (Ubuntu)
Importance: Medium
Assignee: ChristianEhrhardt (paelzer)
Status: Triaged
** Changed in: dpdk (Ubuntu)
St
Had a discussion with James Page today.
He will look into it (backporting, hack, other solution) in his work regarding
charming that stuff.
Big thanks for that!
We agreed that will discuss (or be happy about the fix) again in approx
10 days from now.
** Changed in: openvswitch-dpdk (Ubuntu)
FYI how it looks like in the log, for the next that might find it.
systemd[1]: Starting DPDK runtime environment...
dpdk-init[7467]: Reassigning pci::00:04.0 to uio_pci_generic
dpdk-init[7467]: Error - no supported modules(DPDK driver) are loaded
systemd[1]: dpdk.service: Main process exited,
Found an uploader, wrapping two more fixes before that.
Therefore removing the debdiff and sponsors subscription from this bug for now.
** Patch removed: "Updated revision of the debdiff"
Hi Thiago,
when running into the issue the bug is referring to it looked way different.
So I'd say the issue you are currently facing has nothing to do with the bug.
I've seen your mail on the List and will reply there with some
suggestions and by that keep the bug to the related things.
--
You
The root cause is very easy - the "-" to "_" conversion in the scripts.
I'll have to discuss why that was added as it is from before my time.
I'll let you know about a solution.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in
Hi - here a minor update
Regarding:
NOTE: To make it work manually, the module "vfio-pci" must be declared at
"/etc/modules" as well.
Yes it is required to load the module before dpdk_nic_bind, if running manually
you have to do it some way on your own e.g. /etc/modules.
If using the init
FYI - stalled on FCP setup in RT 89162
** Changed in: multipath-tools (Ubuntu)
Status: New => Triaged
** Changed in: multipath-tools (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: dpdk (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1551752
Title:
DPDK Testpmd failing with Xen specific gntalloc in
** Changed in: dpdk (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1551601
Title:
DPDK init scripts need some hardening against broken
** Changed in: dpdk (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1551767
Title:
DPDK hugepage config in /etc/dpdk/dpdk.conf should
We looked at it and could confirm that the merge to OVS 2.5 and DPDK 2.2
resolved that bug without us noticing :-/
So mark it properly as fix released.
** Changed in: dpdk (Ubuntu)
Status: Triaged => Fix Released
** Changed in: openvswitch-dpdk (Ubuntu)
Status: Triaged => Fix
** Changed in: dpdk (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dpdk in Ubuntu.
https://bugs.launchpad.net/bugs/1554397
Title:
dpdk-init fails due to missing modules in virt
1 - 100 of 153 matches
Mail list logo