MAC address is removed with tainted VirtualBox modules on Fedora 29

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












0















I am getting crash reports. net/mac80211/driver-ops results in drv_remove_interface. My network interface is removed and I can't connect to the WiFi.
I can recover this by shutting down or going in and out of flight mode. It looks like it crashes once I unsuspend it.



I can't report this. My kernel is tainted. It's VirtualBox modules: vboxpci, vboxnetadp, vboxnetfit and vboxdrv.



  • Is VirtualBox causing the issue or is it just restricting me from sending the report?

  • Do I need to reinstall VirtualBox after the upgrade?

  • Is there a bug in Fedora with VirtualBox and the network interface?

  • Is this message misleading and completely unrelated to VirtualBox?


Regardless, I uninstalled it. As most sites referred to the removal in lower case, I just want to highlight that it is title case in Fedora.



sudo dnf remove VirtualBox-5.2.24-1.fc29.x86_64
sudo dnf remove VirtualBox-kmodsrc-5.2.24-1.fc29.noarch
sudo dnf remove VirtualBox-server-5.2.24-1.fc29.x86_64
sudo dnf remove virtualbox-guest-additions-5.2.24-1.fc29.x86_64









share|improve this question

















  • 1





    If you do not have a specific use for VirtualBox (such as bridging wireless without masquerading or something), you might could give QEMU/KVM a shot, perhaps with one of several front-ends.

    – Kenneth B. Jensen
    Feb 8 at 6:25






  • 1





    Thanks, much appreciated. I will look into that as an alternative.

    – cbillowes
    Feb 8 at 6:31















0















I am getting crash reports. net/mac80211/driver-ops results in drv_remove_interface. My network interface is removed and I can't connect to the WiFi.
I can recover this by shutting down or going in and out of flight mode. It looks like it crashes once I unsuspend it.



I can't report this. My kernel is tainted. It's VirtualBox modules: vboxpci, vboxnetadp, vboxnetfit and vboxdrv.



  • Is VirtualBox causing the issue or is it just restricting me from sending the report?

  • Do I need to reinstall VirtualBox after the upgrade?

  • Is there a bug in Fedora with VirtualBox and the network interface?

  • Is this message misleading and completely unrelated to VirtualBox?


Regardless, I uninstalled it. As most sites referred to the removal in lower case, I just want to highlight that it is title case in Fedora.



sudo dnf remove VirtualBox-5.2.24-1.fc29.x86_64
sudo dnf remove VirtualBox-kmodsrc-5.2.24-1.fc29.noarch
sudo dnf remove VirtualBox-server-5.2.24-1.fc29.x86_64
sudo dnf remove virtualbox-guest-additions-5.2.24-1.fc29.x86_64









share|improve this question

















  • 1





    If you do not have a specific use for VirtualBox (such as bridging wireless without masquerading or something), you might could give QEMU/KVM a shot, perhaps with one of several front-ends.

    – Kenneth B. Jensen
    Feb 8 at 6:25






  • 1





    Thanks, much appreciated. I will look into that as an alternative.

    – cbillowes
    Feb 8 at 6:31













0












0








0








I am getting crash reports. net/mac80211/driver-ops results in drv_remove_interface. My network interface is removed and I can't connect to the WiFi.
I can recover this by shutting down or going in and out of flight mode. It looks like it crashes once I unsuspend it.



I can't report this. My kernel is tainted. It's VirtualBox modules: vboxpci, vboxnetadp, vboxnetfit and vboxdrv.



  • Is VirtualBox causing the issue or is it just restricting me from sending the report?

  • Do I need to reinstall VirtualBox after the upgrade?

  • Is there a bug in Fedora with VirtualBox and the network interface?

  • Is this message misleading and completely unrelated to VirtualBox?


Regardless, I uninstalled it. As most sites referred to the removal in lower case, I just want to highlight that it is title case in Fedora.



sudo dnf remove VirtualBox-5.2.24-1.fc29.x86_64
sudo dnf remove VirtualBox-kmodsrc-5.2.24-1.fc29.noarch
sudo dnf remove VirtualBox-server-5.2.24-1.fc29.x86_64
sudo dnf remove virtualbox-guest-additions-5.2.24-1.fc29.x86_64









share|improve this question














I am getting crash reports. net/mac80211/driver-ops results in drv_remove_interface. My network interface is removed and I can't connect to the WiFi.
I can recover this by shutting down or going in and out of flight mode. It looks like it crashes once I unsuspend it.



I can't report this. My kernel is tainted. It's VirtualBox modules: vboxpci, vboxnetadp, vboxnetfit and vboxdrv.



  • Is VirtualBox causing the issue or is it just restricting me from sending the report?

  • Do I need to reinstall VirtualBox after the upgrade?

  • Is there a bug in Fedora with VirtualBox and the network interface?

  • Is this message misleading and completely unrelated to VirtualBox?


Regardless, I uninstalled it. As most sites referred to the removal in lower case, I just want to highlight that it is title case in Fedora.



sudo dnf remove VirtualBox-5.2.24-1.fc29.x86_64
sudo dnf remove VirtualBox-kmodsrc-5.2.24-1.fc29.noarch
sudo dnf remove VirtualBox-server-5.2.24-1.fc29.x86_64
sudo dnf remove virtualbox-guest-additions-5.2.24-1.fc29.x86_64






fedora kernel virtualbox kernel-modules






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 8 at 3:38









cbillowescbillowes

1012




1012







  • 1





    If you do not have a specific use for VirtualBox (such as bridging wireless without masquerading or something), you might could give QEMU/KVM a shot, perhaps with one of several front-ends.

    – Kenneth B. Jensen
    Feb 8 at 6:25






  • 1





    Thanks, much appreciated. I will look into that as an alternative.

    – cbillowes
    Feb 8 at 6:31












  • 1





    If you do not have a specific use for VirtualBox (such as bridging wireless without masquerading or something), you might could give QEMU/KVM a shot, perhaps with one of several front-ends.

    – Kenneth B. Jensen
    Feb 8 at 6:25






  • 1





    Thanks, much appreciated. I will look into that as an alternative.

    – cbillowes
    Feb 8 at 6:31







1




1





If you do not have a specific use for VirtualBox (such as bridging wireless without masquerading or something), you might could give QEMU/KVM a shot, perhaps with one of several front-ends.

– Kenneth B. Jensen
Feb 8 at 6:25





If you do not have a specific use for VirtualBox (such as bridging wireless without masquerading or something), you might could give QEMU/KVM a shot, perhaps with one of several front-ends.

– Kenneth B. Jensen
Feb 8 at 6:25




1




1





Thanks, much appreciated. I will look into that as an alternative.

– cbillowes
Feb 8 at 6:31





Thanks, much appreciated. I will look into that as an alternative.

– cbillowes
Feb 8 at 6:31










0






active

oldest

votes











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f499395%2fmac-address-is-removed-with-tainted-virtualbox-modules-on-fedora-29%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f499395%2fmac-address-is-removed-with-tainted-virtualbox-modules-on-fedora-29%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown






Popular posts from this blog

How to check contact read email or not when send email to Individual?

Bahrain

Postfix configuration issue with fips on centos 7; mailgun relay