Fedora Account System
Red Hat Associate
Red Hat Customer
i have running all sdort of 6.5 F32 kernelson F31 asw ell as on F32 for prepare and test wireguard and i am not sure how serious this since all works: [ 3.317671] Unknown ioctl 1976 [ 3.317845] Unknown ioctl 1976 [ 3.375700] Unknown ioctl 1976 [ 3.376162] Unknown ioctl 1976 at least it's woth a notice
FWIW: that seems basicly "only" affect VMware guests on VMware Workstation as well es ESXi 6.5/6.7/7.0 but suddenly unknown ioctls are alarming
I noticed the same message, within a Fedora 32 on ESX 6.5 U2.
obviously open-vm-tools and with open-vm-tools-11.1.0 this appears not only at boot but regulary and only with Linux 5.6.x May 11 19:01:53 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:01:53 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:01:53 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:01:53 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:01:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:01:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:01:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:01:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:01:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:02:24 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:02:24 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:02:24 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:02:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:02:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:02:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:03:24 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:03:24 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:03:24 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:04:24 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:04:24 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:04:24 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:05:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:05:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:05:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:08:24 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:08:24 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:08:24 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:12:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:12:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:12:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:17:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:17:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:17:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:22:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:22:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:22:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:27:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:27:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:27:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:32:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:32:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:32:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:37:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:37:54 buildserver.thelounge.net kernel: Unknown ioctl 1976 May 11 19:37:54 buildserver.thelounge.net kernel: Unknown ioctl 1976
and that does *not* happen on a Fedora 28 with a custom linux 5.6.x and a recent open-vm-tools
Like dsouders suggested on https://github.com/vmware/open-vm-tools/issues/425, please make sure that the vmci and vsock modules are loaded: See https://github.com/vmware/open-vm-tools/blob/master/open-vm-tools/lib/include/vmci_sockets.h define VMCI_SOCKETS_DEFAULT_DEVICE "/dev/vsock" define VMCI_SOCKETS_CLASSIC_ESX_DEVICE "/vmfs/devices/char/vsock/vsock" if defined(linux) define VMCI_SOCKETS_VERSION 1972 define VMCI_SOCKETS_GET_AF_VALUE 1976 <--------- define VMCI_SOCKETS_GET_LOCAL_CID 1977 define VMCI_SOCKETS_UUID_2_CID 1991
the opposite is true, add the following lines to your existing blacklistfile in /etc/modprobe.d/ blacklist vsock_loopback blacklist vmw_vsock_virtio_transport_common install vsock_loopback /usr/bin/true install vmw_vsock_virtio_transport_common /usr/bin/true Vmware-HA and Vmware-DataProtection don't need all that stuff in the best case your lsmod looks like this and everything is fine [root@master:~]$ lsmod Module Size Used by xt_multiport 20480 7 ipt_REJECT 16384 16 nf_reject_ipv4 16384 1 ipt_REJECT xt_iprange 20480 4 xt_conntrack 16384 9 nf_conntrack 159744 1 xt_conntrack nf_defrag_ipv6 24576 1 nf_conntrack nf_defrag_ipv4 16384 1 nf_conntrack libcrc32c 16384 1 nf_conntrack iptable_filter 16384 1 crct10dif_pclmul 16384 1 crc32_pclmul 16384 0 ghash_clmulni_intel 16384 0 vmw_balloon 24576 0 vmxnet3 65536 0 vmw_vmci 86016 1 vmw_balloon ip_tables 32768 3 iptable_filter crc32c_intel 24576 3 vmw_pvscsi 32768 2
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.