VBoxClient (seamless): failed to start. Stage: Setting guest IRQ filter mask Error:...

Connection Between Knot Theory and Number Theory

What do the positive and negative (+/-) transmit and receive pins mean on Ethernet cables?

Sort with assumptions

What is the tangent at a sharp point on a curve?

Derivative of an interpolated function

Showing mass murder in a kid's book

Can you describe someone as luxurious? As in someone who likes luxurious things?

Offset in split text content

How to split IPA spelling into syllables

1 John in Luther’s Bibel

Why would five hundred and five same as one?

Reason why a kingside attack is not justified

A seasonal riddle

"Marked down as someone wanting to sell shares." What does that mean?

Strange behavior in TikZ draw command

Highest stage count that are used one right after the other?

Capacitor electron flow

Do native speakers use "ultima" and "proxima" frequently in spoken English?

When is the exact date for EOL of Ubuntu 14.04 LTS?

Not hide and seek

Error in master's thesis, I do not know what to do

Can a Knock spell open the door to Mordenkainen's Magnificent Mansion?

Taking the numerator and the denominator

Would this string work as string?



VBoxClient (seamless): failed to start. Stage: Setting guest IRQ filter mask Error: VERR_INTERNAL_ERROR


vboxclient seamless failed to start setting guest irq filter maskHaving trouble installing guest additions for a Xubuntu 13.10 guest OS in Virtualbox 4.2.10Unable to have full screen Ubuntu in VirtualBoxVBoxClient: Failed to connect to the VirtualBox kernal service, rc = VERR_ACCESS_DENIED error. Unable to get past login screenVirtualbox guest additions installed but not working - version conflictVBoxManage guestcontrol permission errorMouse and keyboard input ignored after installing virtualbox-guest-x11Cannot install Ubuntu 16.04 Desktop on VirtualboxBoot VirtualBox guest from USBvboxclient seamless failed to start setting guest irq filter maskResolution stuck 1024x768 VirtualBox 6 VboxSVGA driver on guest Lubuntu 18.04













32















I'm trying to get an Ubuntu VM to run well in the latest VirtualBox (5.2.2), which I installed by running sudo ./VboxLinuxAdditions.run. The problem is I keep getting this error message when the VM starts:




VBoxClient (seamless): failed to start. Stage: Setting guest IRQ filter mas Error: VERR_INTERNAL_ERROR




Ubuntu on Ubuntu in VirtualBox is extremely frustrating



The host is Ubuntu 16.04.3. I've tried two Ubuntu 17.10 distros (Lubuntu and Budgie). Both failed with the same error.



Being unable to run Ubuntu on Ubuntu should be a P0 critical issue for Oracle. What am I doing wrong?










share|improve this question




















  • 1





    How did you install the guest additions?

    – George Udosen
    Dec 13 '17 at 10:58











  • @GeorgeUdosen: that was it. Updated the Q and added an answer. Thanks!

    – Dan Dascalescu
    Dec 13 '17 at 20:58
















32















I'm trying to get an Ubuntu VM to run well in the latest VirtualBox (5.2.2), which I installed by running sudo ./VboxLinuxAdditions.run. The problem is I keep getting this error message when the VM starts:




VBoxClient (seamless): failed to start. Stage: Setting guest IRQ filter mas Error: VERR_INTERNAL_ERROR




Ubuntu on Ubuntu in VirtualBox is extremely frustrating



The host is Ubuntu 16.04.3. I've tried two Ubuntu 17.10 distros (Lubuntu and Budgie). Both failed with the same error.



Being unable to run Ubuntu on Ubuntu should be a P0 critical issue for Oracle. What am I doing wrong?










share|improve this question




















  • 1





    How did you install the guest additions?

    – George Udosen
    Dec 13 '17 at 10:58











  • @GeorgeUdosen: that was it. Updated the Q and added an answer. Thanks!

    – Dan Dascalescu
    Dec 13 '17 at 20:58














32












32








32


12






I'm trying to get an Ubuntu VM to run well in the latest VirtualBox (5.2.2), which I installed by running sudo ./VboxLinuxAdditions.run. The problem is I keep getting this error message when the VM starts:




VBoxClient (seamless): failed to start. Stage: Setting guest IRQ filter mas Error: VERR_INTERNAL_ERROR




Ubuntu on Ubuntu in VirtualBox is extremely frustrating



The host is Ubuntu 16.04.3. I've tried two Ubuntu 17.10 distros (Lubuntu and Budgie). Both failed with the same error.



Being unable to run Ubuntu on Ubuntu should be a P0 critical issue for Oracle. What am I doing wrong?










share|improve this question
















I'm trying to get an Ubuntu VM to run well in the latest VirtualBox (5.2.2), which I installed by running sudo ./VboxLinuxAdditions.run. The problem is I keep getting this error message when the VM starts:




VBoxClient (seamless): failed to start. Stage: Setting guest IRQ filter mas Error: VERR_INTERNAL_ERROR




Ubuntu on Ubuntu in VirtualBox is extremely frustrating



The host is Ubuntu 16.04.3. I've tried two Ubuntu 17.10 distros (Lubuntu and Budgie). Both failed with the same error.



Being unable to run Ubuntu on Ubuntu should be a P0 critical issue for Oracle. What am I doing wrong?







virtualbox






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 13 '17 at 19:38







Dan Dascalescu

















asked Dec 13 '17 at 6:41









Dan DascalescuDan Dascalescu

1,14921637




1,14921637








  • 1





    How did you install the guest additions?

    – George Udosen
    Dec 13 '17 at 10:58











  • @GeorgeUdosen: that was it. Updated the Q and added an answer. Thanks!

    – Dan Dascalescu
    Dec 13 '17 at 20:58














  • 1





    How did you install the guest additions?

    – George Udosen
    Dec 13 '17 at 10:58











  • @GeorgeUdosen: that was it. Updated the Q and added an answer. Thanks!

    – Dan Dascalescu
    Dec 13 '17 at 20:58








1




1





How did you install the guest additions?

– George Udosen
Dec 13 '17 at 10:58





How did you install the guest additions?

– George Udosen
Dec 13 '17 at 10:58













@GeorgeUdosen: that was it. Updated the Q and added an answer. Thanks!

– Dan Dascalescu
Dec 13 '17 at 20:58





@GeorgeUdosen: that was it. Updated the Q and added an answer. Thanks!

– Dan Dascalescu
Dec 13 '17 at 20:58










3 Answers
3






active

oldest

votes


















41














Turns out I had to install gcc, make and perl, then reinstall the additions and reboot:



sudo apt-get install gcc make perl
cd /media/$USER/<...>
sudo ./VBoxLinuxAdditions.run
sudo reboot





share|improve this answer





















  • 2





    Worked for me as well! Thanks (Ubuntu 16.04.3 w vboxgas & virtualbox 5.2.6)!

    – Ignorante
    Jan 26 '18 at 22:02






  • 1





    This worked well. The first line fixed the issue; the last three re-install Guest Additions (which can be done in the GUI as well)

    – User that is not a user
    Feb 19 '18 at 19:58






  • 1





    Also worked for me. I noticed that it took much longer for the Guest Additions to install once gcc, make, and perl were installed. Without them, I guess lengthy steps were being skipped. Is there a VirtualBox bug in here? Seems like it should give you an error if vital components are missing.

    – Aren Cambre
    Apr 10 '18 at 14:55






  • 2





    Kernel headers are mandatory too (linux-headers-amd64 or the like). All errors are logged in a sub-log, which makes it difficult to understand why this fails. The run script should dump what tools are missing.

    – Yvan
    May 8 '18 at 2:05













  • Yay thank you! 16.04 x64 on VB 5.2.12 on OSX 10.13.5. I wasted hours on other, longer, slower, very different solutions to get guest-host clipboard sharing to work. Gotta learn to just askubuntu... Gotta say, we're an advanced technological civilization, and we're all pretty technical. Why does it feel like we're 100,000,000 amoebas in a pond?

    – Spike0xff
    Jun 19 '18 at 21:06



















2














In addition to ensuring make, gcc and perl are installed as per Dan's accepted answer it may be necessary to also check for version-specific kernel headers linux-headers-$(uname -r), build-essential and dkms. Catch-all one-liner:



sudo apt install gcc make perl linux-headers-$(uname -r) build-essential dkms 


I ran into this issue while I had the first three package installed. Installing the rest resolved it. It's possible that not all are necessary, but notably only installing the linux-headers package (without version specified) was not enough.






share|improve this answer































    0














    I am on Mac OSX 10.14.3 and working with Virtualbox 5.2.22 and Ubuntu Desktop 16.04.6 virtual machine. In my case, I'm running Ubuntu in 32bit mode because I had trouble getting 16.04 to work in 64bit mode. I recently upgraded to kernel 4.4.0-143 using the typical Ubuntu update and then, when I restarted the VM again, I got this VBoxClient seamless error just like you see here. After trying all kinds of things, such as upgrading Virtualbox, upgrading VBox Extensions, and more -- the resolution was that I rebooted the VM, held the shift key down, and chose kernel 4.4.0-142. Then, I got the error, but was able to run:



    sudo apt-get install --reinstall build-essential virtualbox-guest-utils virtualbox-guest-x11 virtualbox-guest-dkms


    That, of course, would put the wrong virtualbox stuff on my VM, but was actually useful because then I could force the kernel to switch to the proper vbox extensions in my next step. So, with the command above typed, I rebooted my VM, held shift key down, and chose kernel 4.4.0-142. Now, this made the screen too small because it's not running the optimal virtualbox extensions that support proper screen resize with my Mac driver. Not a problem, though, because this was only temporary. So, I then ran this command:



    cd /media/$USER/<...>
    sudo ./VBoxLinuxAdditions.run


    This properly compiled the vbox extensions that were suitable for my computer. I rebooted the VM, held the shift key down, and chose kernel 4.4.0-142. At that point, the VBoxClient seamless error went away, and I had all my functionality I needed including screen resizing, bidirectional clipboard, mounting shared volumes and so on.




    Long story short, the kernel version was at fault, was the best that I
    could determine. There was something up with the 4.4.0-143 kernel that
    was causing Virtualbox to choke. Rolling back to a previous kernel and forcing vbox extensions to reinstall was my fix for now.






    share























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "89"
      };
      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: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      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%2faskubuntu.com%2fquestions%2f985815%2fvboxclient-seamless-failed-to-start-stage-setting-guest-irq-filter-mask-err%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      41














      Turns out I had to install gcc, make and perl, then reinstall the additions and reboot:



      sudo apt-get install gcc make perl
      cd /media/$USER/<...>
      sudo ./VBoxLinuxAdditions.run
      sudo reboot





      share|improve this answer





















      • 2





        Worked for me as well! Thanks (Ubuntu 16.04.3 w vboxgas & virtualbox 5.2.6)!

        – Ignorante
        Jan 26 '18 at 22:02






      • 1





        This worked well. The first line fixed the issue; the last three re-install Guest Additions (which can be done in the GUI as well)

        – User that is not a user
        Feb 19 '18 at 19:58






      • 1





        Also worked for me. I noticed that it took much longer for the Guest Additions to install once gcc, make, and perl were installed. Without them, I guess lengthy steps were being skipped. Is there a VirtualBox bug in here? Seems like it should give you an error if vital components are missing.

        – Aren Cambre
        Apr 10 '18 at 14:55






      • 2





        Kernel headers are mandatory too (linux-headers-amd64 or the like). All errors are logged in a sub-log, which makes it difficult to understand why this fails. The run script should dump what tools are missing.

        – Yvan
        May 8 '18 at 2:05













      • Yay thank you! 16.04 x64 on VB 5.2.12 on OSX 10.13.5. I wasted hours on other, longer, slower, very different solutions to get guest-host clipboard sharing to work. Gotta learn to just askubuntu... Gotta say, we're an advanced technological civilization, and we're all pretty technical. Why does it feel like we're 100,000,000 amoebas in a pond?

        – Spike0xff
        Jun 19 '18 at 21:06
















      41














      Turns out I had to install gcc, make and perl, then reinstall the additions and reboot:



      sudo apt-get install gcc make perl
      cd /media/$USER/<...>
      sudo ./VBoxLinuxAdditions.run
      sudo reboot





      share|improve this answer





















      • 2





        Worked for me as well! Thanks (Ubuntu 16.04.3 w vboxgas & virtualbox 5.2.6)!

        – Ignorante
        Jan 26 '18 at 22:02






      • 1





        This worked well. The first line fixed the issue; the last three re-install Guest Additions (which can be done in the GUI as well)

        – User that is not a user
        Feb 19 '18 at 19:58






      • 1





        Also worked for me. I noticed that it took much longer for the Guest Additions to install once gcc, make, and perl were installed. Without them, I guess lengthy steps were being skipped. Is there a VirtualBox bug in here? Seems like it should give you an error if vital components are missing.

        – Aren Cambre
        Apr 10 '18 at 14:55






      • 2





        Kernel headers are mandatory too (linux-headers-amd64 or the like). All errors are logged in a sub-log, which makes it difficult to understand why this fails. The run script should dump what tools are missing.

        – Yvan
        May 8 '18 at 2:05













      • Yay thank you! 16.04 x64 on VB 5.2.12 on OSX 10.13.5. I wasted hours on other, longer, slower, very different solutions to get guest-host clipboard sharing to work. Gotta learn to just askubuntu... Gotta say, we're an advanced technological civilization, and we're all pretty technical. Why does it feel like we're 100,000,000 amoebas in a pond?

        – Spike0xff
        Jun 19 '18 at 21:06














      41












      41








      41







      Turns out I had to install gcc, make and perl, then reinstall the additions and reboot:



      sudo apt-get install gcc make perl
      cd /media/$USER/<...>
      sudo ./VBoxLinuxAdditions.run
      sudo reboot





      share|improve this answer















      Turns out I had to install gcc, make and perl, then reinstall the additions and reboot:



      sudo apt-get install gcc make perl
      cd /media/$USER/<...>
      sudo ./VBoxLinuxAdditions.run
      sudo reboot






      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Feb 16 '18 at 14:57









      Eric Carvalho

      42.2k17115147




      42.2k17115147










      answered Dec 13 '17 at 20:58









      Dan DascalescuDan Dascalescu

      1,14921637




      1,14921637








      • 2





        Worked for me as well! Thanks (Ubuntu 16.04.3 w vboxgas & virtualbox 5.2.6)!

        – Ignorante
        Jan 26 '18 at 22:02






      • 1





        This worked well. The first line fixed the issue; the last three re-install Guest Additions (which can be done in the GUI as well)

        – User that is not a user
        Feb 19 '18 at 19:58






      • 1





        Also worked for me. I noticed that it took much longer for the Guest Additions to install once gcc, make, and perl were installed. Without them, I guess lengthy steps were being skipped. Is there a VirtualBox bug in here? Seems like it should give you an error if vital components are missing.

        – Aren Cambre
        Apr 10 '18 at 14:55






      • 2





        Kernel headers are mandatory too (linux-headers-amd64 or the like). All errors are logged in a sub-log, which makes it difficult to understand why this fails. The run script should dump what tools are missing.

        – Yvan
        May 8 '18 at 2:05













      • Yay thank you! 16.04 x64 on VB 5.2.12 on OSX 10.13.5. I wasted hours on other, longer, slower, very different solutions to get guest-host clipboard sharing to work. Gotta learn to just askubuntu... Gotta say, we're an advanced technological civilization, and we're all pretty technical. Why does it feel like we're 100,000,000 amoebas in a pond?

        – Spike0xff
        Jun 19 '18 at 21:06














      • 2





        Worked for me as well! Thanks (Ubuntu 16.04.3 w vboxgas & virtualbox 5.2.6)!

        – Ignorante
        Jan 26 '18 at 22:02






      • 1





        This worked well. The first line fixed the issue; the last three re-install Guest Additions (which can be done in the GUI as well)

        – User that is not a user
        Feb 19 '18 at 19:58






      • 1





        Also worked for me. I noticed that it took much longer for the Guest Additions to install once gcc, make, and perl were installed. Without them, I guess lengthy steps were being skipped. Is there a VirtualBox bug in here? Seems like it should give you an error if vital components are missing.

        – Aren Cambre
        Apr 10 '18 at 14:55






      • 2





        Kernel headers are mandatory too (linux-headers-amd64 or the like). All errors are logged in a sub-log, which makes it difficult to understand why this fails. The run script should dump what tools are missing.

        – Yvan
        May 8 '18 at 2:05













      • Yay thank you! 16.04 x64 on VB 5.2.12 on OSX 10.13.5. I wasted hours on other, longer, slower, very different solutions to get guest-host clipboard sharing to work. Gotta learn to just askubuntu... Gotta say, we're an advanced technological civilization, and we're all pretty technical. Why does it feel like we're 100,000,000 amoebas in a pond?

        – Spike0xff
        Jun 19 '18 at 21:06








      2




      2





      Worked for me as well! Thanks (Ubuntu 16.04.3 w vboxgas & virtualbox 5.2.6)!

      – Ignorante
      Jan 26 '18 at 22:02





      Worked for me as well! Thanks (Ubuntu 16.04.3 w vboxgas & virtualbox 5.2.6)!

      – Ignorante
      Jan 26 '18 at 22:02




      1




      1





      This worked well. The first line fixed the issue; the last three re-install Guest Additions (which can be done in the GUI as well)

      – User that is not a user
      Feb 19 '18 at 19:58





      This worked well. The first line fixed the issue; the last three re-install Guest Additions (which can be done in the GUI as well)

      – User that is not a user
      Feb 19 '18 at 19:58




      1




      1





      Also worked for me. I noticed that it took much longer for the Guest Additions to install once gcc, make, and perl were installed. Without them, I guess lengthy steps were being skipped. Is there a VirtualBox bug in here? Seems like it should give you an error if vital components are missing.

      – Aren Cambre
      Apr 10 '18 at 14:55





      Also worked for me. I noticed that it took much longer for the Guest Additions to install once gcc, make, and perl were installed. Without them, I guess lengthy steps were being skipped. Is there a VirtualBox bug in here? Seems like it should give you an error if vital components are missing.

      – Aren Cambre
      Apr 10 '18 at 14:55




      2




      2





      Kernel headers are mandatory too (linux-headers-amd64 or the like). All errors are logged in a sub-log, which makes it difficult to understand why this fails. The run script should dump what tools are missing.

      – Yvan
      May 8 '18 at 2:05







      Kernel headers are mandatory too (linux-headers-amd64 or the like). All errors are logged in a sub-log, which makes it difficult to understand why this fails. The run script should dump what tools are missing.

      – Yvan
      May 8 '18 at 2:05















      Yay thank you! 16.04 x64 on VB 5.2.12 on OSX 10.13.5. I wasted hours on other, longer, slower, very different solutions to get guest-host clipboard sharing to work. Gotta learn to just askubuntu... Gotta say, we're an advanced technological civilization, and we're all pretty technical. Why does it feel like we're 100,000,000 amoebas in a pond?

      – Spike0xff
      Jun 19 '18 at 21:06





      Yay thank you! 16.04 x64 on VB 5.2.12 on OSX 10.13.5. I wasted hours on other, longer, slower, very different solutions to get guest-host clipboard sharing to work. Gotta learn to just askubuntu... Gotta say, we're an advanced technological civilization, and we're all pretty technical. Why does it feel like we're 100,000,000 amoebas in a pond?

      – Spike0xff
      Jun 19 '18 at 21:06













      2














      In addition to ensuring make, gcc and perl are installed as per Dan's accepted answer it may be necessary to also check for version-specific kernel headers linux-headers-$(uname -r), build-essential and dkms. Catch-all one-liner:



      sudo apt install gcc make perl linux-headers-$(uname -r) build-essential dkms 


      I ran into this issue while I had the first three package installed. Installing the rest resolved it. It's possible that not all are necessary, but notably only installing the linux-headers package (without version specified) was not enough.






      share|improve this answer




























        2














        In addition to ensuring make, gcc and perl are installed as per Dan's accepted answer it may be necessary to also check for version-specific kernel headers linux-headers-$(uname -r), build-essential and dkms. Catch-all one-liner:



        sudo apt install gcc make perl linux-headers-$(uname -r) build-essential dkms 


        I ran into this issue while I had the first three package installed. Installing the rest resolved it. It's possible that not all are necessary, but notably only installing the linux-headers package (without version specified) was not enough.






        share|improve this answer


























          2












          2








          2







          In addition to ensuring make, gcc and perl are installed as per Dan's accepted answer it may be necessary to also check for version-specific kernel headers linux-headers-$(uname -r), build-essential and dkms. Catch-all one-liner:



          sudo apt install gcc make perl linux-headers-$(uname -r) build-essential dkms 


          I ran into this issue while I had the first three package installed. Installing the rest resolved it. It's possible that not all are necessary, but notably only installing the linux-headers package (without version specified) was not enough.






          share|improve this answer













          In addition to ensuring make, gcc and perl are installed as per Dan's accepted answer it may be necessary to also check for version-specific kernel headers linux-headers-$(uname -r), build-essential and dkms. Catch-all one-liner:



          sudo apt install gcc make perl linux-headers-$(uname -r) build-essential dkms 


          I ran into this issue while I had the first three package installed. Installing the rest resolved it. It's possible that not all are necessary, but notably only installing the linux-headers package (without version specified) was not enough.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Aug 13 '18 at 8:26









          anlaganlag

          413




          413























              0














              I am on Mac OSX 10.14.3 and working with Virtualbox 5.2.22 and Ubuntu Desktop 16.04.6 virtual machine. In my case, I'm running Ubuntu in 32bit mode because I had trouble getting 16.04 to work in 64bit mode. I recently upgraded to kernel 4.4.0-143 using the typical Ubuntu update and then, when I restarted the VM again, I got this VBoxClient seamless error just like you see here. After trying all kinds of things, such as upgrading Virtualbox, upgrading VBox Extensions, and more -- the resolution was that I rebooted the VM, held the shift key down, and chose kernel 4.4.0-142. Then, I got the error, but was able to run:



              sudo apt-get install --reinstall build-essential virtualbox-guest-utils virtualbox-guest-x11 virtualbox-guest-dkms


              That, of course, would put the wrong virtualbox stuff on my VM, but was actually useful because then I could force the kernel to switch to the proper vbox extensions in my next step. So, with the command above typed, I rebooted my VM, held shift key down, and chose kernel 4.4.0-142. Now, this made the screen too small because it's not running the optimal virtualbox extensions that support proper screen resize with my Mac driver. Not a problem, though, because this was only temporary. So, I then ran this command:



              cd /media/$USER/<...>
              sudo ./VBoxLinuxAdditions.run


              This properly compiled the vbox extensions that were suitable for my computer. I rebooted the VM, held the shift key down, and chose kernel 4.4.0-142. At that point, the VBoxClient seamless error went away, and I had all my functionality I needed including screen resizing, bidirectional clipboard, mounting shared volumes and so on.




              Long story short, the kernel version was at fault, was the best that I
              could determine. There was something up with the 4.4.0-143 kernel that
              was causing Virtualbox to choke. Rolling back to a previous kernel and forcing vbox extensions to reinstall was my fix for now.






              share




























                0














                I am on Mac OSX 10.14.3 and working with Virtualbox 5.2.22 and Ubuntu Desktop 16.04.6 virtual machine. In my case, I'm running Ubuntu in 32bit mode because I had trouble getting 16.04 to work in 64bit mode. I recently upgraded to kernel 4.4.0-143 using the typical Ubuntu update and then, when I restarted the VM again, I got this VBoxClient seamless error just like you see here. After trying all kinds of things, such as upgrading Virtualbox, upgrading VBox Extensions, and more -- the resolution was that I rebooted the VM, held the shift key down, and chose kernel 4.4.0-142. Then, I got the error, but was able to run:



                sudo apt-get install --reinstall build-essential virtualbox-guest-utils virtualbox-guest-x11 virtualbox-guest-dkms


                That, of course, would put the wrong virtualbox stuff on my VM, but was actually useful because then I could force the kernel to switch to the proper vbox extensions in my next step. So, with the command above typed, I rebooted my VM, held shift key down, and chose kernel 4.4.0-142. Now, this made the screen too small because it's not running the optimal virtualbox extensions that support proper screen resize with my Mac driver. Not a problem, though, because this was only temporary. So, I then ran this command:



                cd /media/$USER/<...>
                sudo ./VBoxLinuxAdditions.run


                This properly compiled the vbox extensions that were suitable for my computer. I rebooted the VM, held the shift key down, and chose kernel 4.4.0-142. At that point, the VBoxClient seamless error went away, and I had all my functionality I needed including screen resizing, bidirectional clipboard, mounting shared volumes and so on.




                Long story short, the kernel version was at fault, was the best that I
                could determine. There was something up with the 4.4.0-143 kernel that
                was causing Virtualbox to choke. Rolling back to a previous kernel and forcing vbox extensions to reinstall was my fix for now.






                share


























                  0












                  0








                  0







                  I am on Mac OSX 10.14.3 and working with Virtualbox 5.2.22 and Ubuntu Desktop 16.04.6 virtual machine. In my case, I'm running Ubuntu in 32bit mode because I had trouble getting 16.04 to work in 64bit mode. I recently upgraded to kernel 4.4.0-143 using the typical Ubuntu update and then, when I restarted the VM again, I got this VBoxClient seamless error just like you see here. After trying all kinds of things, such as upgrading Virtualbox, upgrading VBox Extensions, and more -- the resolution was that I rebooted the VM, held the shift key down, and chose kernel 4.4.0-142. Then, I got the error, but was able to run:



                  sudo apt-get install --reinstall build-essential virtualbox-guest-utils virtualbox-guest-x11 virtualbox-guest-dkms


                  That, of course, would put the wrong virtualbox stuff on my VM, but was actually useful because then I could force the kernel to switch to the proper vbox extensions in my next step. So, with the command above typed, I rebooted my VM, held shift key down, and chose kernel 4.4.0-142. Now, this made the screen too small because it's not running the optimal virtualbox extensions that support proper screen resize with my Mac driver. Not a problem, though, because this was only temporary. So, I then ran this command:



                  cd /media/$USER/<...>
                  sudo ./VBoxLinuxAdditions.run


                  This properly compiled the vbox extensions that were suitable for my computer. I rebooted the VM, held the shift key down, and chose kernel 4.4.0-142. At that point, the VBoxClient seamless error went away, and I had all my functionality I needed including screen resizing, bidirectional clipboard, mounting shared volumes and so on.




                  Long story short, the kernel version was at fault, was the best that I
                  could determine. There was something up with the 4.4.0-143 kernel that
                  was causing Virtualbox to choke. Rolling back to a previous kernel and forcing vbox extensions to reinstall was my fix for now.






                  share













                  I am on Mac OSX 10.14.3 and working with Virtualbox 5.2.22 and Ubuntu Desktop 16.04.6 virtual machine. In my case, I'm running Ubuntu in 32bit mode because I had trouble getting 16.04 to work in 64bit mode. I recently upgraded to kernel 4.4.0-143 using the typical Ubuntu update and then, when I restarted the VM again, I got this VBoxClient seamless error just like you see here. After trying all kinds of things, such as upgrading Virtualbox, upgrading VBox Extensions, and more -- the resolution was that I rebooted the VM, held the shift key down, and chose kernel 4.4.0-142. Then, I got the error, but was able to run:



                  sudo apt-get install --reinstall build-essential virtualbox-guest-utils virtualbox-guest-x11 virtualbox-guest-dkms


                  That, of course, would put the wrong virtualbox stuff on my VM, but was actually useful because then I could force the kernel to switch to the proper vbox extensions in my next step. So, with the command above typed, I rebooted my VM, held shift key down, and chose kernel 4.4.0-142. Now, this made the screen too small because it's not running the optimal virtualbox extensions that support proper screen resize with my Mac driver. Not a problem, though, because this was only temporary. So, I then ran this command:



                  cd /media/$USER/<...>
                  sudo ./VBoxLinuxAdditions.run


                  This properly compiled the vbox extensions that were suitable for my computer. I rebooted the VM, held the shift key down, and chose kernel 4.4.0-142. At that point, the VBoxClient seamless error went away, and I had all my functionality I needed including screen resizing, bidirectional clipboard, mounting shared volumes and so on.




                  Long story short, the kernel version was at fault, was the best that I
                  could determine. There was something up with the 4.4.0-143 kernel that
                  was causing Virtualbox to choke. Rolling back to a previous kernel and forcing vbox extensions to reinstall was my fix for now.







                  share











                  share


                  share










                  answered 2 mins ago









                  VolomikeVolomike

                  1,30641431




                  1,30641431






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Ask Ubuntu!


                      • 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%2faskubuntu.com%2fquestions%2f985815%2fvboxclient-seamless-failed-to-start-stage-setting-guest-irq-filter-mask-err%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

                      Why do type traits not work with types in namespace scope?What are POD types in C++?Why can templates only be...

                      Will tsunami waves travel forever if there was no land?Why do tsunami waves begin with the water flowing away...

                      Simple Scan not detecting my scanner (Brother DCP-7055W)Brother MFC-L2700DW printer can print, can't...