This bug was fixed in the package libvirt - 4.0.0-1ubuntu8.7
---
libvirt (4.0.0-1ubuntu8.7) bionic; urgency=medium
* d/p/ubuntu/lp-1811198-utils-Remove-arbitrary-limit-on-socket_id-core_id
.patch: fix arm servers with high core_id (LP: #1811198)
* d/p/ubuntu/lp-1771662-*: fix
This bug was fixed in the package libvirt - 4.6.0-2ubuntu3.3
---
libvirt (4.6.0-2ubuntu3.3) cosmic; urgency=medium
* d/p/ubuntu/lp-1811198-utils-Remove-arbitrary-limit-on-socket_id-core_id
.patch: fix arm servers with high core_id (LP: #1811198)
* d/p/ubuntu/lp-1771662-*: fix
bionic verification:
ubuntu@seidel-FLAKYMEMORY:~$ dpkg -s libvirt-daemon-system | grep ^Version
Version: 4.0.0-1ubuntu8.7
ubuntu@seidel-FLAKYMEMORY:~$ sudo virsh nodedev-list | grep ^net
net_enP2p1s0f1_1c_1b_0d_0d_52_d6
net_enP2p1s0f2_1c_1b_0d_0d_52_d7
net_enP2p1s0f3_1c_1b_0d_0d_52_d8
Hello Jason, or anyone else affected,
Accepted libvirt into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libvirt/4.6.0-2ubuntu3.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Thanks in advance for all the help to everybody involved!
All prechecks ready and uploaded to the SRU queue waiting for approval.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771662
Title:
@Christian: both verify fine for me:
$ dpkg -s libvirt-daemon-system | grep ^Version
Version: 4.6.0-2ubuntu3.3~ppa1
$ sudo virsh nodedev-list | grep ^net
net_enP2p1s0f1_40_8d_5c_b1_e4_44
net_enP2p1s0f2_40_8d_5c_b1_e4_45
net_enP2p1s0f3_40_8d_5c_b1_e4_46
$ dpkg -s libvirt-daemon-system | grep
FYI - the fix for this bug as an SRUs is ready and testable from a PPA for
Cosmic [1] and Bionic [2].
Since the verification of this bug requires special hardware, I'd appreciate if
you could precheck these PPAs if they fix the issues. That would ensure that:
a) the fix is most likely to work
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/362544
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/libvirt/+git/libvirt/+merge/362545
--
You received this bug notification because you are a member
** Description changed:
+ [Impact]
+
+ * Libvirt has had the assumption that every VF (virtual function) will
+have a PF (physical function) assigned, but that does not hold true on
+some special Hardware like the Cavium ThunderX
+
+ * Dannf helped some patches initially from Linaro
This bug was fixed in the package libvirt - 5.0.0-1ubuntu1
---
libvirt (5.0.0-1ubuntu1) disco; urgency=medium
* Merged with Debian unstable
Among many other new features and fixes this includes fixes for:
LP: #1754871 - 1799446 zPCI passthrough support for KVM
LP:
Thank you Dann for finishing this!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771662
Title:
[bionic] libvirtError: Node device not found: no node device with
matching name
To manage
** Merge proposal linked:
https://code.launchpad.net/~libvirt-maintainers/ubuntu/+source/libvirt/+git/libvirt/+merge/361960
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771662
Title:
[bionic]
** Tags added: libvirt-19.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771662
Title:
[bionic] libvirtError: Node device not found: no node device with
matching name
To manage notifications
Fixes have now landed upstream:
04983c3c6a util: Fixing invalid error checking from virPCIGetNetname()
8fac64db5e util: Fix for NULL dereference
10bca495e0 util: Code simplification
6452e2f5e1 util: fixing wrong assumption that PF has to have netdev assigned
** Also affects: libvirt (Ubuntu
** Changed in: libvirt (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771662
Title:
[bionic] libvirtError: Node device not found: no node device
Thank you Dann.
Those fixes should unblock startup of libvirt on ThunderX. Keep in mind that
only hostdev config will work on this platform as is
not supported.
In case you find and issues keep me informed.
I will send v3. Changes for v3 are about where to report error and should not
Thanks Radoslaw! I've created PPAs for the rocky & queens ubuntu cloud
archives w/ your v2 patches integrated for testing.
ppa:dannf/queens-arm64
ppa:dannf/rocky-arm64
I plan to keep this up to date as your patch set iterates, as well as
rebasing on latest QEMU until merged in mainline and
Hi Dann, just sent the patches.
I decided also to share some fixes but the first one in series is the one you
looking for.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771662
Title:
[bionic]
@rbiernacki I just wanted to check - do you still have plans to propose
your "fast fix" upstream?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771662
Title:
[bionic] libvirtError: Node device not
@rbiernacki: Thanks for commenting here - and sorry for my delayed
response as I was out on PTO. While I haven't tested it in our setup, I
agree that your [4] is likely a better/more generic "fast fix" solution
than what I prepared. Feel free to CC me on your RFC.
--
You received this bug
As this is my first post, I would like to say Hello to everybody.
Seems that you are trying to fix the same issue as we in Cavium/Linaro [1] and
therefore I would like to share with you with some findings, which I hope you
will find helpful. It's a rather long explanation ;)
So first of all,
I'd not go the "implement the perfect thing" route without strictly
requiring it.
I only meant to get upstreams thoughts on it.
They don't have to accept it "that way" to consider it for us as a fix.
But suggesting it there on the old thread [1] that is dead since then would
help.
I would not
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771662
Title:
[bionic] libvirtError: Node device not found: no node device with
matching name
To manage notifications about
My original intent was to just carry it until there's a proper fix
upstream, and we can evaluate that for backporting. But, if you think
generic black-listing is a desired feature upstream (but w/ e.g.
configurable ids), I can take a look at implementing that. However,
that'll take some time, so
Nice, did you intend to propose that upstream?
Or was the intention to carry this sort of forever in Ubuntu only?
The Linaro bug was sort of "we keep it for ourselve" I wonder if we
should try to get upstream feeback?
--
You received this bug notification because you are a member of Ubuntu
Now that testing is looking good, here's a cleaned-up debdiff that is
hopefully more suitable for carrying. It is as used in the cosmic build
in ppa:dannf/test. This is still just the simple hack though (vs. a new
config) - just with improved function name/return type and w/ a DEP-3
header.
**
@Dann - good news, I am able to deploy a bionic guest using the non-uefi
image (still tagged as such) and connect to it with bionic-rocky:
Result of running uname -a on 10.245.172.3: Linux bionic-101103
4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:22:18 UTC 2018 aarch64
aarch64 aarch64
@Andrew: thanks. Hard to tell what the root cause is there - might need
more logs. The only obvious concern I see here is:
[0.062805] acpi PNP0A08:00: Bus :00 not present in PCI namespace
Would you mind trying a newer guest (bionic/cosmic) and seeing if that
is any better? The xenial GA
Have tested libvirt-bin from dann's PPA re comment 45 with partial
success.
This results in hypervisors being listed via openstack hypervisor list,
and instances can be launched.
https://pastebin.canonical.com/p/pDDmYQsvSr/
However, the instance build is not really successful - there is no
Nice find Dann!
There are examples of excluding some devices of that check already.
E.g. in libvirt 4.1 non-PCI devices were excluded [1]
I like your change even being only a workaround so far.
Linaro has adopted a much more aggressive temp fix [2] with more compatibility
issues.
The only thing
I tracked down why libvirt generates the message "internal error: The PF
device for VF XXX has no network device name" on startup when built in
bionic, but not in xenial. When populating device capabilities, we see:
virNetDevGetFeatures():
virNetDevSwitchdevFeature():
@mahmoh
Thanks for the reference - yes we believe this is the same issue and
we're not seeing it on other platforms.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771662
Title:
[bionic]
Hey guys,
This looks a lot like a problem Linaro reported [1] and if so it's a
Cavium driver bug that I believe they're working on.
Have you tried this on any other Arm hardware platform to see if you hit
the same problem?
[1] https://bugs.linaro.org/show_bug.cgi?id=3778
Thank you.
** Bug
That is interesting indeed.
The difference being on other systems the virtual functions are by
default disabled which I guess is why no one is running into this
problem with other hardware.
An example from a system with the ixgbe driver:
# cat
Actually the -EOPNOTSUPP error is the default behaviour, unless your
driver implements the .ndo_get_phys_port_id() callback, and at the
moment (4.18-rc3) only 7 drivers (out of several hundreds) implement
that:
linux$ grep -ri do_get_phys_port_id drivers/net/
** Summary changed:
- libvirtError: Node device not found: no node device with matching name
+ [bionic] libvirtError: Node device not found: no node device with matching
name
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
36 matches
Mail list logo
