[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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 assumption that all VFs have PFs assigned (LP: #1771662) -- Christian Ehrhardt Thu, 31 Jan 2019 12:45:18 +0100 -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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 assumption that all VFs have PFs assigned (LP: #1771662) -- Christian Ehrhardt Thu, 31 Jan 2019 12:29:37 +0100 ** Changed in: libvirt (Ubuntu Cosmic) Status: Fix Committed => Fix Released ** Changed in: libvirt (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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 net_enP2p1s0f4_1c_1b_0d_0d_52_d9 net_enP2p1s0f5_1c_1b_0d_0d_52_da cosmic verification: ubuntu@seuss-FLAKYMEMORY:~$ dpkg -s libvirt-daemon-system | grep ^Version Version: 4.6.0-2ubuntu3.3 ubuntu@seuss-FLAKYMEMORY:~$ sudo virsh nodedev-list | grep ^net net_enP2p1s0f1_40_8d_5c_ba_cd_c4 net_enP2p1s0f2_40_8d_5c_ba_cd_c5 net_enP2p1s0f3_40_8d_5c_ba_cd_c6 ** Tags removed: verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic ** 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/1771662 Title: [bionic] libvirtError: Node device not found: no node device with matching name To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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 https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libvirt (Ubuntu Cosmic) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-cosmic ** Changed in: libvirt (Ubuntu Bionic) Status: Triaged => Fix Committed ** Tags added: verification-needed-bionic -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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: [bionic] libvirtError: Node device not found: no node device with matching name To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
@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 ^Version Version: 4.0.0-1ubuntu8.7~ppa1 $ sudo virsh nodedev-list | grep ^net net_enP2p1s0f1_42_ca_74_64_88_75 net_enP2p1s0f2_42_ca_74_64_88_76 net_enP2p1s0f3_42_ca_74_64_88_77 ** 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 + * 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 to be accepted upstream -and those we'd want to backport to Bionic and Cosmic + * Dannf helped some patches initially from Linaro to be accepted upstream + and those we'd want to backport to Bionic and Cosmic [Test Case] - * Use VF passthrough to a KVM guest on Cavium thunderX + * Verify that virsh nodedev-list shows the onboard NICs: +$ sudo virsh nodedev-list | grep ^net +net_enP2p1s0f1_42_ca_74_64_88_75 +net_enP2p1s0f2_42_ca_74_64_88_76 +net_enP2p1s0f3_42_ca_74_64_88_77 - * This needs plenty of setup and special HW, but Jason Hobbs & Dannf are -willing to do the verification in our test lab. + * This needs plenty of setup and special HW, but Jason Hobbs & Dannf are + willing to do the verification in our test lab. [Regression Potential] - * Review hasn't spotted any issues, but in theory there could be negative -effects to PF/VF pass-through cases. There is some code cleanup -associated that should not, but might cause issues on that. -I'd ask Jason to also run PF/VF workload on the PPA/SRU with other -Hardware as well (like our x86 test environment) to be sure of that -being ok. + * Review hasn't spotted any issues, but in theory there could be negative + effects to PF/VF pass-through cases. There is some code cleanup + associated that should not, but might cause issues on that. + I'd ask Jason to also run PF/VF workload on the PPA/SRU with other + Hardware as well (like our x86 test environment) to be sure of that + being ok. [Other Info] - - * n/a + + * n/a --- After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like: 2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2' In my /var/log/nova/nova-compute.log I'm not sure why this is happening - I don't use enP2p1s0f1 for anything. There are a lot of interesting messages about that interface in syslog: http://paste.ubuntu.com/p/8WT8NqCbCf/ Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/ The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms. This thread has some related info, I think: https://www.spinics.net/linux/fedora/libvir/msg160975.html This is with juju 2.4 beta 2. Package versions on affected system: http://paste.ubuntu.com/p/yfQH3KJzng/ -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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 when pushed as SRU b) our plan to verify the actual by your testing SRU will work In addition I'll push these PPAs through the automated regression tests for qemu/libvirt. [1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3620 [2]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3621 -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
** 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 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
** 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 to be accepted upstream +and those we'd want to backport to Bionic and Cosmic + + [Test Case] + + * Use VF passthrough to a KVM guest on Cavium thunderX + + * This needs plenty of setup and special HW, but Jason Hobbs & Dannf are +willing to do the verification in our test lab. + + [Regression Potential] + + * Review hasn't spotted any issues, but in theory there could be negative +effects to PF/VF pass-through cases. There is some code cleanup +associated that should not, but might cause issues on that. +I'd ask Jason to also run PF/VF workload on the PPA/SRU with other +Hardware as well (like our x86 test environment) to be sure of that +being ok. + + [Other Info] + + * n/a + + --- + After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like: 2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name 'net_enP2p1s0f1_40_8d_5c_ba_b8_d2' In my /var/log/nova/nova-compute.log I'm not sure why this is happening - I don't use enP2p1s0f1 for anything. There are a lot of interesting messages about that interface in syslog: http://paste.ubuntu.com/p/8WT8NqCbCf/ Here is my bundle: http://paste.ubuntu.com/p/fWWs6r8Nr5/ The same bundle works fine for xenial-queens, with the source changed to the cloud-archive, and using stable charms rather than -next. I hit this same issue on bionic queens using either stable or next charms. This thread has some related info, I think: https://www.spinics.net/linux/fedora/libvir/msg160975.html This is with juju 2.4 beta 2. Package versions on affected system: http://paste.ubuntu.com/p/yfQH3KJzng/ -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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: #1811198 - remove arbitrary limit on socket_id/core_id
Remaining changes:
- Disable libssh2 support (universe dependency)
- Disable firewalld support (universe dependency)
- Set qemu-group to kvm (for compat with older ubuntu)
- Additional apport package-hook
- Autostart default bridged network (As upstream does, but not Debian).
In addition to just enabling it our solution provides:
+ do not autostart if subnet is already taken (e.g. in guests).
+ iterate some alternative subnets before giving up
- d/p/ubuntu/Allow-libvirt-group-to-access-the-socket.patch: This is
the group based access to libvirt functions as it was used in Ubuntu
for quite long.
+ d/p/ubuntu/daemon-augeas-fix-expected.patch fix some related tests
due to the group access change.
+ d/libvirt-daemon-system.postinst: add users in sudo to the libvirt
group.
- ubuntu/parallel-shutdown.patch: set parallel shutdown by default.
- Update Vcs-Git and Vcs-Browser fields to point to launchpad
- Xen related
- d/p/ubuntu/ubuntu-libxl-qemu-path.patch: this change was split. The
section that adapts the path of the emulator to the Debian/Ubuntu
packaging is kept.
- d/p/ubuntu/ubuntu-libxl-Fix-up-VRAM-to-minimum-requirements.patch: auto
set VRAM to minimum requirements
- d/p/ubuntu/xen-default-uri.patch: set default URI on xen hosts
- Add libxl log directory
- libvirt-uri.sh: Automatically switch default libvirt URI for users on
Xen dom0 via user profile (was missing on changelogs before)
- d/p/ubuntu/apibuild-skip-libvirt-common.h: drop libvirt-common.h from
included_files to avoid build failures due to duplicate definitions.
- Update README.Debian with Ubuntu changes
- Enable some additional features on ppc64el and s390x (for arch parity)
+ systemtap, zfs, numa and numad on s390x.
+ systemtap on ppc64el.
- d/t/control, d/t/smoke-qemu-session: fixup smoke-qemu-session by making
vmlinuz available and accessible (Debian bug 848314)
- d/t/control, d/t/smoke-lxc: fix up lxc smoke test isolation
- d/p/ubuntu/ubuntu_machine_type.patch: accept ubuntu types as pci440fx
- Further upstreamed apparmor Delta, especially any new one
Our former delta is split into logical pieces and is either Ubuntu only
or is part of a continuous upstreaming effort.
Listing related remaining changes in debian/patches/ubuntu-aa/:
+ 0001-apparmor-Allow-pygrub-to-run-on-Debian-Ubuntu.patch: apparmor:
Allow pygrub to run on Debian/Ubuntu
+ 0003-apparmor-libvirt-qemu-Allow-read-access-to-overcommi.patch:
apparmor, libvirt-qemu: Allow read access to overcommit_memory
+ 0007-apparmor-libvirt-qemu-Allow-owner-read-access-to-PRO.patch:
apparmor, libvirt-qemu: Allow owner read access to @{PROC}/*/auxv
+ 0017-apparmor-virt-aa-helper-Allow-access-to-tmp-director.patch:
apparmor, virt-aa-helper: Allow access to tmp directories
+ ubuntu-aa/0020-virt-aa-helper-ubuntu-storage-paths.patch:
apparmor, virt-aa-helper: Allow various storage pools and image
locations
+ 0021-apparmor-virt-aa-helper-Add-openvswitch-support.patch:
apparmor, virt-aa-helper: Add openvswitch support
+ 0029-appmor-libvirt-qemu-Add-9p-support.patch: appmor,
libvirt-qemu: Add 9p support
+ 0030-virt-aa-helper-Complete-9p-support.patch: virt-aa-helper:
add l to 9p file options.
+ 0031-virt-aa-helper-Ask-for-no-deny-rule-for-readonly-dis.patch:
virt-aa-helper: Ask for no deny rule for readonly disk (renamed and
reworded, was virt-aa-helper-no-explicity-deny-for-basefiles.patch)
+ 0032-apparmor-libvirt-qemu-Allow-reading-charm-specific-c.patch:
apparmor, libvirt-qemu: Allow reading charm-specific ceph config
+ 0033-UBUNTU-only-apparmor-for-kvm.powerpc-LP-1680384.patch: allow
commands executed by ubuntu only kvm wrapper on ppc64el
(LP 1686621 LP 1680384 LP 1784023)
+ 0034-apparmor-virt-aa-helper-access-for-snapped-nova.patch:
apparmor, virt-aa-helper: access for snapped nova
+ d/p/ubuntu-aa/0050-local-include-for-libvirt-qemu.patch,
d/libvirt-daemon-system.postinst: provide a local apparmor include
for abstraction/libvirt-qemu (LP: 1786019)
- d/rules: enable build time self tests on all architectures
- dnsmasq related enhancements
+ run dnsmasq as libvirt-dnsmasq (LP: 1743718)
+ d/libvirt-daemon-system.postinst: add libvirt-dnsmasq user and group
+ d/libvirt-daemon-system.postrm: remove
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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 notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
** 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] libvirtError: Node device not found: no node device with matching name To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
** 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 about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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 Disco) Importance: Undecided Status: In Progress ** Also affects: libvirt (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: libvirt (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu Disco) Status: In Progress => Triaged ** Changed in: nova Status: New => Invalid ** Changed in: libvirt (Ubuntu Cosmic) Status: New => Triaged ** Changed in: libvirt (Ubuntu Bionic) Status: New => Triaged -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
** 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 with matching name To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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 influence on functionality. -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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 backported to Ubuntu. -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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] libvirtError: Node device not found: no node device with matching name To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
@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 found: no node device with matching name To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
@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 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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, this issue is triggered by one of ThunderX SOC devices, VNIC network device to be exact. It's PF does not expose netdev which makes trouble for libvirt code. It means there is no interface name at which PF device can be found under /sys or pointed out using RTM_SETLINK message (there are some alternatives to that but more over this latter). >From information which I have at hand, there is no requirement from SRIOV >standard (nor any other) that PF has to have the same functionality as their >VF, by what IMHO all assumptions in libvirt code about VF->PF->VF mapping >using interface names are false. Basically that's why the proper fix for that >is hard as it requires a lot of rework in virtnetdev layer of libvirt. Someone >might argue that Intel cards expose such interfaces but this does not mean >that libvirt should assume that it is a "standard" behavior. I started to working on those [2] but ended up with quite invasive fixes which for sure requires some discussion on libvirt-dev list (comments for [2] more than welcome, I will also start RFC on libvirt-dev for that). The simple fix for this issue should: - suppress the initialization error (more less this is what Dann Frazier does in his patch [3] or I'm doing in first patch of the series of [2]) - fix some NULL reference bugs in libvirt (third and fourth patch in the series [2]) so libvirt will not crash in case of config is given for VNIC VF netdev, but just throw an error, that due to missing HW support it is not able to configure the interface (I didn't introduced proper error messages yet in my patch set). That's the fast fix which I should be able to extract from my fixes quite easily and it should be upstreamable. --- Beside the libvirt, the for full fix the ThunderX VNIC kernel driver need to be enhanced, as it currently does not support VLAN's and VF MAC setting, which is essentially needed to make ThunderX VNIC a fully supported device under libvirt. In fact this is the major part of the work. The true fix need: - fix libvirt wrong assumptions about SRIOV netdevs and handling of VF->PF->VF mapping by netdev names (instead pci BDF should be used in whole virtnetdev layer or some non-netdev name, just generic dev related addressing scheme) - fix libvirt PF VLAN and MAC handling code to use global port number instead of PF name for RTM_SETLINK - ThunderX VNIC driver need to support VLAN's per VF (MCAM) possibly with dynamic VF creation as well as switchdev functionality (currently VF are created basing on active port count read from BGX) --- @dann I understand the idea in your patch (filtering out the incompatible NIC's), but can You take a look at [4]? Not sure what was exactly the intention of the code inside virNetDevSwitchdevFeature(), but if you look at following line: pci_device_ptr = pfname ? virNetDevGetPCIDevice(pfname) : virNetDevGetPCIDevice(ifname); It might suggest that the intention of author was that switch functionality will be handled either by VF or PF. Therefore I'm rather for option that the fix should ignore errors from virNetDevGetPhysicalFunction(), which will leave pfname = NULL. At the end (also in case of ThunderX which doe's not support ESWITCH) it will give the same result as your patch (return 0) without introduction of additional check/filtering function. --- [1] https://bugs.linaro.org/show_bug.cgi?id=3778 [2] ssh://g...@git.linaro.org/people/radoslaw.biernacki/libvirt.git wip_thunder_fix6 [3] https://launchpadlibrarian.net/390574937/libvirt-no-thunderx-switchdev.debdiff [4] https://git.linaro.org/people/radoslaw.biernacki/libvirt.git/commit/?h=wip_thunder_fix6=a73772938cec6de16f14e9031bdbf42fe02e0faa -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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 expect they take it as-is but who knows, and vice versa they might spot an issue doing it that way in reviewing it. No matter what submitting it upstream would help to ensure the patch is good and to know if we need more (or not) to eventually bring it upstream. Please CC me on that upstream submission so I can stay in the loop. FYI: I'm out a week after today, but there is no libvirt upload in flight for cosmic. I checked the PPA [2] and found no issues with it (and it should be the same for 18.10, although I haven't tested it), so after you got a generally positive upstream reply feel free to upload to Cosmic next week if you want. Otherwise I'll take a look when I'm back. [1]: https://www.redhat.com/archives/libvir-list/2018-March/msg01383.html [2]: https://launchpad.net/~dannf/+archive/ubuntu/test -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
** 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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 I'd still be in favor of merging the existing patch to unblock running Ubuntu OpenStack on these systems in the short term. -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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. ** Patch added: "libvirt-no-thunderx-switchdev.debdiff" https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+attachment/5193615/+files/libvirt-no-thunderx-switchdev.debdiff -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
@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 GNU/Linux Will also now validate on bionic-queens -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
@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 kernel is lacking a lot of ACPI support, and maybe libvirt has grown to expect more. -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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 network connectivity to the tenant network, as the guest instance just drops to an initramfs prompt. https://pastebin.canonical.com/p/N2JQPvfsGv/ -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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 that bothers me is that if there is a fix to something else than libvirt (e.g. the cavium kernel driver) then the workaround will block the usage still. The test on the ppa is great, but eventually I wonder if we could make this part of one of the conffiles and use like virConfGetValueStringList [3] which might by default in the config have 0x177d:0xa034 but entries could be added/removed by an administrator. It might even default to an empty list if that is more acceptable upstream, but allow installations to mask broken devices as needed. Unfortunately none of the existing configs is used in the scope that we'd need it, which implies it would likely be a new config file [4] that is needed. There is a lot of the usual overhead (check paths, permissions, ...) to be added just for that, but maybe it would make the hack upstreamable. Hmm, OTOH maybe it would be over-engineering and we just use the simple change you suggested which would declare this network card not supporting switchdev offloads (even if fixed int he kernel driver, it is unlikely to reach Bionic trivially other than maybe HWE kernels) But for now lets see what result the test on your ppa delivers [1]: https://libvirt.org/git/?p=libvirt.git;a=commit;h=71d56a397925a1bd55d3aee30afdbdcd1a14f9a8 [2]: https://git.linaro.org/people/radoslaw.biernacki/libvirt.git/commit/?h=wip_thunder_fix=da79ade2f18bec11d1436dc12980f32b12fbad3c [3]: https://libvirt.org/git/?p=libvirt.git;a=blob;f=src/util/virconf.c;h=e0a3fd12c04f9df0ae2a3a7054292f1093ab8693;hb=HEAD#l936 [4]: https://libvirt.org/git/?p=libvirt.git;a=blob;f=src/util/virconf.c;h=e0a3fd12c04f9df0ae2a3a7054292f1093ab8693;hb=HEAD#l746 -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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(): virNetDevGetPhysicalFunction() However, virNetDevSwitchdevFeature() is stubbed out at build time unless HAVE_DECL_DEVLINK_CMD_ESWITCH_GET is defined. In bionic, this is defined in /usr/include/linux/devlink.h, which didn't exist in xenial. Since all of our OpenStack/arm64 testing on bionic is blocked because our test systems all happen to be impacted by https://bugs.linaro.org/show_bug.cgi?id=3778 , I'm wondering if there's some kind of temporary hack we can carry to detect these devices, disable some set of (currently broken) features, and allow our testing to proceed until this problem is addressed upstream. My understanding is that our testing succeeds with xenial, but fails with bionic, while the source version of libvirt remains constant. I therefore wonder if virNetDevSwitchdevFeature() is the (only) thing causing this to escalate to nova failure. In that case, could we e.g. compare vendor/device ids, and add a hack to return 0 if they match? I've pushed a libvirt build to ppa:dannf/test with such a hack, if someone w/ a full arm64 openstack setup can try it to see if it would be able to unblock us. -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
@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] libvirtError: Node device not found: no node device with matching name To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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 watch added: Linaro Bug Tracking System #3778 https://bugs.linaro.org/show_bug.cgi?id=3778 -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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 /sys/devices/pci\:00/\:00\:03.0/\:01\:00.1/sriov_totalvfs 63 # cat /sys/devices/pci\:00/\:00\:03.0/\:01\:00.1/sriov_numvfs 0 # ls -l /sys/devices/pci\:00/\:00\:03.0/\:01\:00.1/virtfn* ls: cannot access '/sys/devices/pci:00/:00:03.0/:01:00.1/virtfn*': No such file or directory While on a system with the Cavium Thunder X card: cat /sys/devices/pci0002\:00/0002\:00\:02.0/0002\:01\:00.0/sriov_totalvfs 128 # cat /sys/devices/pci0002\:00/0002\:00\:02.0/0002\:01\:00.0/sriov_numvfs 18 # ls -l /sys/devices/pci0002\:00/0002\:00\:02.0/0002\:01\:00.0/virtfn* lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn0 -> ../0002:01:00.1 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn1 -> ../0002:01:00.2 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn10 -> ../0002:01:01.3 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn11 -> ../0002:01:01.4 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn12 -> ../0002:01:01.5 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn13 -> ../0002:01:01.6 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn14 -> ../0002:01:01.7 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn15 -> ../0002:01:02.0 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn16 -> ../0002:01:02.1 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn17 -> ../0002:01:02.2 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn2 -> ../0002:01:00.3 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn3 -> ../0002:01:00.4 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn4 -> ../0002:01:00.5 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn5 -> ../0002:01:00.6 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn6 -> ../0002:01:00.7 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn7 -> ../0002:01:01.0 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn8 -> ../0002:01:01.1 lrwxrwxrwx 1 root root 0 Jun 29 08:24 /sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn9 -> ../0002:01:01.2 # cat /sys/devices/pci0002\:00/0002\:00\:02.0/0002\:01\:00.0/virtfn0/net/enP2p1s0f1/phys_port_id cat: '/sys/devices/pci0002:00/0002:00:02.0/0002:01:00.0/virtfn0/net/enP2p1s0f1/phys_port_id': Operation not supported And this is on by default, without a operator having enabled the virtual functions. libvirt finds the virtual functions this way: https://github.com/libvirt/libvirt/blob/0b86e23d25696c08234d4b73c90cef9515befe84/src/util/virpci.c#L2688 -- 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 this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
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/
drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c:.ndo_get_phys_port_id =
cxgb4_mgmt_get_phys_port_id,
drivers/net/ethernet/broadcom/bnx2x/bnx2x_main.c: .ndo_get_phys_port_id
= bnx2x_get_phys_port_id,
drivers/net/ethernet/mellanox/mlx4/en_netdev.c: .ndo_get_phys_port_id =
mlx4_en_get_phys_port_id,
drivers/net/ethernet/mellanox/mlx4/en_netdev.c: .ndo_get_phys_port_id =
mlx4_en_get_phys_port_id,
drivers/net/ethernet/sfc/efx.c: .ndo_get_phys_port_id = efx_get_phys_port_id,
drivers/net/ethernet/emulex/benet/be_main.c:.ndo_get_phys_port_id =
be_get_phys_port_id,
drivers/net/ethernet/qlogic/qlcnic/qlcnic_main.c: .ndo_get_phys_port_id
= qlcnic_get_phys_port_id,
drivers/net/ethernet/intel/i40e/i40e_main.c:.ndo_get_phys_port_id =
i40e_get_phys_port_id,
or you fall back to the "default behaviour" in net/core/dev.c:
/**
* dev_get_phys_port_id - Get device physical port ID
* @dev: device
* @ppid: port ID
*
* Get device physical port ID
*/
int dev_get_phys_port_id(struct net_device *dev,
struct netdev_phys_item_id *ppid)
{
const struct net_device_ops *ops = dev->netdev_ops;
if (!ops->ndo_get_phys_port_id)
return -EOPNOTSUPP;
return ops->ndo_get_phys_port_id(dev, ppid);
}
EXPORT_SYMBOL(dev_get_phys_port_id);
--
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 this bug go to:
https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771662] Re: [bionic] libvirtError: Node device not found: no node device with matching name
** 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. https://bugs.launchpad.net/bugs/1771662 Title: [bionic] libvirtError: Node device not found: no node device with matching name To manage notifications about this bug go to: https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
