somwhere around 1-2 years ago that messages started with a kernel-update on any Fedora guest running on VMware ESXi, it does not happen when the host is VMware Workstation given that all this guests are installed 2008 and in the past even hat "nobar" in the kernel params it starts to become annoying when you grep for "failed", "error" and "warning" after reboot machines since all is running fine waht is the purpose of this messages and why they just don't disappear? currently: 4.5.3-200.fc23.x86_64 [ 0.631273] pci 0000:00:15.3: BAR 13: failed to assign [io size 0x1000] [ 0.631566] pci 0000:00:15.4: BAR 13: failed to assign [io size 0x1000] [ 0.631842] pci 0000:00:15.5: BAR 13: failed to assign [io size 0x1000] [ 0.632128] pci 0000:00:15.6: BAR 13: failed to assign [io size 0x1000] [ 0.632419] pci 0000:00:15.7: BAR 13: failed to assign [io size 0x1000] [ 0.632698] pci 0000:00:16.3: BAR 13: failed to assign [io size 0x1000] [ 0.632987] pci 0000:00:16.4: BAR 13: failed to assign [io size 0x1000] [ 0.633267] pci 0000:00:16.5: BAR 13: failed to assign [io size 0x1000] [ 0.633548] pci 0000:00:16.6: BAR 13: failed to assign [io size 0x1000] [ 0.633823] pci 0000:00:16.7: BAR 13: failed to assign [io size 0x1000] [ 0.634108] pci 0000:00:17.3: BAR 13: failed to assign [io size 0x1000] [ 0.634388] pci 0000:00:17.4: BAR 13: failed to assign [io size 0x1000] [ 0.634684] pci 0000:00:17.5: BAR 13: failed to assign [io size 0x1000] [ 0.634989] pci 0000:00:17.6: BAR 13: failed to assign [io size 0x1000] [ 0.635264] pci 0000:00:17.7: BAR 13: failed to assign [io size 0x1000] [ 0.635540] pci 0000:00:18.2: BAR 13: failed to assign [io size 0x1000] [ 0.635815] pci 0000:00:18.3: BAR 13: failed to assign [io size 0x1000] [ 0.636100] pci 0000:00:18.4: BAR 13: failed to assign [io size 0x1000] [ 0.636377] pci 0000:00:18.5: BAR 13: failed to assign [io size 0x1000] [ 0.636658] pci 0000:00:18.6: BAR 13: failed to assign [io size 0x1000] [ 0.636937] pci 0000:00:18.7: BAR 13: failed to assign [io size 0x1000] [ 0.637227] pci 0000:00:18.7: BAR 13: failed to assign [io size 0x1000] [ 0.637502] pci 0000:00:18.6: BAR 13: failed to assign [io size 0x1000] [ 0.637784] pci 0000:00:18.5: BAR 13: failed to assign [io size 0x1000] [ 0.638071] pci 0000:00:18.4: BAR 13: failed to assign [io size 0x1000] [ 0.638346] pci 0000:00:18.3: BAR 13: failed to assign [io size 0x1000] [ 0.638621] pci 0000:00:18.2: BAR 13: failed to assign [io size 0x1000] [ 0.638898] pci 0000:00:17.7: BAR 13: failed to assign [io size 0x1000] [ 0.639183] pci 0000:00:17.6: BAR 13: failed to assign [io size 0x1000] [ 0.639458] pci 0000:00:17.5: BAR 13: failed to assign [io size 0x1000] [ 0.639735] pci 0000:00:17.4: BAR 13: failed to assign [io size 0x1000] [ 0.640018] pci 0000:00:17.3: BAR 13: failed to assign [io size 0x1000] [ 0.640297] pci 0000:00:16.7: BAR 13: failed to assign [io size 0x1000] [ 0.640579] pci 0000:00:16.6: BAR 13: failed to assign [io size 0x1000] [ 0.640856] pci 0000:00:16.5: BAR 13: failed to assign [io size 0x1000] [ 0.641142] pci 0000:00:16.4: BAR 13: failed to assign [io size 0x1000] [ 0.641418] pci 0000:00:16.3: BAR 13: failed to assign [io size 0x1000] [ 0.641693] pci 0000:00:15.7: BAR 13: failed to assign [io size 0x1000] [ 0.641977] pci 0000:00:15.6: BAR 13: failed to assign [io size 0x1000] [ 0.642252] pci 0000:00:15.5: BAR 13: failed to assign [io size 0x1000] [ 0.642527] pci 0000:00:15.4: BAR 13: failed to assign [io size 0x1000] [ 0.642803] pci 0000:00:15.3: BAR 13: failed to assign [io size 0x1000]
I have been having the same issue. Does anyone suspect that this may be related to server crashes? I see this often before issues with one of my VMs.
that is at *early boot* - see the timestamps
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs. Fedora 24 has now been rebased to 4.7.4-200.fc24. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 25, and are still experiencing this issue, please change the version to Fedora 25. If you experience different issues, please open a new bug report for those.
unchanged behavior on F24 with latest 4.7.x kernels
that's really annyoing when you call scripts on 30 servers from a admin-infrastructure which grep for failed/warn/error on all machines after kernel updates and reboot all nodes
still the same on F24 w/ 4.8.12-200.fc24.x86_64 #1 SMP Fri Dec 2 18:45:50 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux cheers
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There are a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs. Fedora 25 has now been rebased to 4.10.9-100.fc24. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
besdies the text "Fedora 25 has now been rebased to 4.10.9-100.fc24" is wrong the same issue with 4.10.9-100.fc24.x86_64 and that log flooding exists *for years* now
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.
[root@master:~]$ uname -r 5.16.10-100.fc34.x86_64 [root@master:~]$ dmesg | grep BAR [Mon Feb 21 15:04:03 2022] pci 0000:00:15.0: BAR 15: assigned [mem 0x20000000-0x201fffff 64bit pref] [Mon Feb 21 15:04:03 2022] pci 0000:00:16.0: BAR 15: assigned [mem 0x20200000-0x203fffff 64bit pref] [Mon Feb 21 15:04:03 2022] pci 0000:00:15.3: BAR 13: no space for [io size 0x1000] [Mon Feb 21 15:04:03 2022] pci 0000:00:15.3: BAR 13: failed to assign [io size 0x1000] [Mon Feb 21 15:04:03 2022] pci 0000:00:15.4: BAR 13: no space for [io size 0x1000] [Mon Feb 21 15:04:03 2022] pci 0000:00:15.4: BAR 13: failed to assign [io size 0x1000] [Mon Feb 21 15:04:03 2022] pci 0000:00:15.5: BAR 13: no space for [io size 0x1000] [Mon Feb 21 15:04:03 2022] pci 0000:00:15.5: BAR 13: failed to assign [io size 0x1000] [Mon Feb 21 15:04:03 2022] pci 0000:00:15.6: BAR 13: no space for [io size 0x1000] [Mon Feb 21 15:04:03 2022] pci 0000:00:15.6: BAR 13: failed to assign [io size 0x1000] [Mon Feb 21 15:04:03 2022] pci 0000:00:15.7: BAR 13: no space for [io size 0x1000] [Mon Feb 21 15:04:03 2022] pci 0000:00:15.7: BAR 13: failed to assign [io size 0x1000] [Mon Feb 21 15:04:03 2022] pci 0000:00:16.3: BAR 13: no space for [io size 0x1000] [Mon Feb 21 15:04:03 2022] pci 0000:00:16.3: BAR 13: failed to assign [io size 0x1000] [Mon Feb 21 15:04:03 2022] pci 0000:00:16.4: BAR 13: no space for [io size 0x1000] [Mon Feb 21 15:04:03 2022] pci 0000:00:16.4: BAR 13: failed to assign [io size 0x1000] [Mon Feb 21 15:04:03 2022] pci 0000:00:16.5: BAR 13: no space for [io size 0x1000]
According to: https://access.redhat.com/solutions/3144711 you should get in touch with VMware
This comment was flagged a spam, view the edit history to see the original text if required.
why should i get in touch with VMware when a kernel update introduced that and everything works fine?
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. 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 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
... [ 4.439929] e1000: ens33 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 6.612497] SELinux: initialized (dev binfmt_misc, type binfmt_misc), uses genfs_contexts [ 30.157957] SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs [ 1332.129864] IPv6: ADDRCONF(NETDEV_UP): ens33: link is not ready [ 1332.130528] e1000: ens33 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None [ 1332.131460] IPv6: ADDRCONF(NETDEV_CHANGE): ens33: http://vmstaging.lcibs.ac.bw/
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
for the sake of god can someone lock this bugreport until someone else is able to keep out spammeers?
"The device in question may not be fully compatible with the virtual hardware presented to the virtual machine by ESXi" is pure onsense and you need to be smarter to get clicks on your spam-link
I frequently play Run 3 after every working hour because it is an exceptionally intriguing and attractive endless runner game, https://run3online.io