VirtualBox: Guest suddenly boots only into UEFI Interactive Shell












6















Problem with VirtualBox 5.x running on GNU/Linux Debian 9.x host:



EFI-enabled guest suddenly boots only into UEFI Interactive Shell.



UEFI Interactive Shell



It waits for 5 seconds and then it drops to Shell>.



I don't remember any modifications, which I would have done, neither to the host, nor guest, or VirtualBox itself.










share|improve this question





























    6















    Problem with VirtualBox 5.x running on GNU/Linux Debian 9.x host:



    EFI-enabled guest suddenly boots only into UEFI Interactive Shell.



    UEFI Interactive Shell



    It waits for 5 seconds and then it drops to Shell>.



    I don't remember any modifications, which I would have done, neither to the host, nor guest, or VirtualBox itself.










    share|improve this question



























      6












      6








      6


      3






      Problem with VirtualBox 5.x running on GNU/Linux Debian 9.x host:



      EFI-enabled guest suddenly boots only into UEFI Interactive Shell.



      UEFI Interactive Shell



      It waits for 5 seconds and then it drops to Shell>.



      I don't remember any modifications, which I would have done, neither to the host, nor guest, or VirtualBox itself.










      share|improve this question
















      Problem with VirtualBox 5.x running on GNU/Linux Debian 9.x host:



      EFI-enabled guest suddenly boots only into UEFI Interactive Shell.



      UEFI Interactive Shell



      It waits for 5 seconds and then it drops to Shell>.



      I don't remember any modifications, which I would have done, neither to the host, nor guest, or VirtualBox itself.







      virtualbox virtual-machine uefi






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 18 '17 at 8:24







      Vlastimil

















      asked Nov 30 '16 at 0:57









      VlastimilVlastimil

      8,0291363136




      8,0291363136






















          3 Answers
          3






          active

          oldest

          votes


















          6














          Plausible fix:





          1. In UEFI Interactive Shell, enter the file system:



            fs0:



          2. Following up with creating this file:



            edit startup.nsh



          3. Enter this or similar line to it:



            EFIdebiangrubx64.efi


          4. Press CTRL+S to save the file.


          5. Press ENTER to confirm the file name.


          6. Press CTRL+Q to exit the editor.



          7. Restart the Guest:



            reset





          Important notes:




          1. For some reason you have only a few seconds to edit and save the file. If it takes you longer, then the guest may react with a significant delay. Or it may even freeze.


          2. Replace debian with your system's id, e.g. ubuntu. You may verify this by simply going into the EFI directory and running ls.





          Another way:



          If you don't succeed, and supposing your guest is Linux type, I myself had to do it:




          1. Boot from live USB with any Linux.


          2. Mount the root file system.



          3. Create this file on the mounted file system, adjust the path to wherever you have mounted it:



            /boot/efi/startup.nsh


          4. Enter the above explained line to it.







          share|improve this answer

































            0














            Workaround:



            In the VirtualBox settings for your VM, go to System settings and in the Motherboard section un-check the




            Enable EFI (Special OSes only).




            Save the settings and restart your VM.





            Important notes:




            1. This will make the guest system run on BIOS / MBR legacy boot.


            2. Only use, if the solution above does not work for you.







            share|improve this answer


























            • Yes, thank you! It was necessary to Enable EFI in order to make the GParted Live CD work. However, after resizing the disk partitions in GParted, I encountered this error, and also an error "fs0 is not a correct mapping" if I tried to enter the file system. Disabling this flag solved issue.

              – Jamie
              Oct 25 '18 at 5:35



















            0














            I am having this problem and it does not accept any input that I've tried





            share








            New contributor




            GN Trains is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.




















              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%2f326956%2fvirtualbox-guest-suddenly-boots-only-into-uefi-interactive-shell%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









              6














              Plausible fix:





              1. In UEFI Interactive Shell, enter the file system:



                fs0:



              2. Following up with creating this file:



                edit startup.nsh



              3. Enter this or similar line to it:



                EFIdebiangrubx64.efi


              4. Press CTRL+S to save the file.


              5. Press ENTER to confirm the file name.


              6. Press CTRL+Q to exit the editor.



              7. Restart the Guest:



                reset





              Important notes:




              1. For some reason you have only a few seconds to edit and save the file. If it takes you longer, then the guest may react with a significant delay. Or it may even freeze.


              2. Replace debian with your system's id, e.g. ubuntu. You may verify this by simply going into the EFI directory and running ls.





              Another way:



              If you don't succeed, and supposing your guest is Linux type, I myself had to do it:




              1. Boot from live USB with any Linux.


              2. Mount the root file system.



              3. Create this file on the mounted file system, adjust the path to wherever you have mounted it:



                /boot/efi/startup.nsh


              4. Enter the above explained line to it.







              share|improve this answer






























                6














                Plausible fix:





                1. In UEFI Interactive Shell, enter the file system:



                  fs0:



                2. Following up with creating this file:



                  edit startup.nsh



                3. Enter this or similar line to it:



                  EFIdebiangrubx64.efi


                4. Press CTRL+S to save the file.


                5. Press ENTER to confirm the file name.


                6. Press CTRL+Q to exit the editor.



                7. Restart the Guest:



                  reset





                Important notes:




                1. For some reason you have only a few seconds to edit and save the file. If it takes you longer, then the guest may react with a significant delay. Or it may even freeze.


                2. Replace debian with your system's id, e.g. ubuntu. You may verify this by simply going into the EFI directory and running ls.





                Another way:



                If you don't succeed, and supposing your guest is Linux type, I myself had to do it:




                1. Boot from live USB with any Linux.


                2. Mount the root file system.



                3. Create this file on the mounted file system, adjust the path to wherever you have mounted it:



                  /boot/efi/startup.nsh


                4. Enter the above explained line to it.







                share|improve this answer




























                  6












                  6








                  6







                  Plausible fix:





                  1. In UEFI Interactive Shell, enter the file system:



                    fs0:



                  2. Following up with creating this file:



                    edit startup.nsh



                  3. Enter this or similar line to it:



                    EFIdebiangrubx64.efi


                  4. Press CTRL+S to save the file.


                  5. Press ENTER to confirm the file name.


                  6. Press CTRL+Q to exit the editor.



                  7. Restart the Guest:



                    reset





                  Important notes:




                  1. For some reason you have only a few seconds to edit and save the file. If it takes you longer, then the guest may react with a significant delay. Or it may even freeze.


                  2. Replace debian with your system's id, e.g. ubuntu. You may verify this by simply going into the EFI directory and running ls.





                  Another way:



                  If you don't succeed, and supposing your guest is Linux type, I myself had to do it:




                  1. Boot from live USB with any Linux.


                  2. Mount the root file system.



                  3. Create this file on the mounted file system, adjust the path to wherever you have mounted it:



                    /boot/efi/startup.nsh


                  4. Enter the above explained line to it.







                  share|improve this answer















                  Plausible fix:





                  1. In UEFI Interactive Shell, enter the file system:



                    fs0:



                  2. Following up with creating this file:



                    edit startup.nsh



                  3. Enter this or similar line to it:



                    EFIdebiangrubx64.efi


                  4. Press CTRL+S to save the file.


                  5. Press ENTER to confirm the file name.


                  6. Press CTRL+Q to exit the editor.



                  7. Restart the Guest:



                    reset





                  Important notes:




                  1. For some reason you have only a few seconds to edit and save the file. If it takes you longer, then the guest may react with a significant delay. Or it may even freeze.


                  2. Replace debian with your system's id, e.g. ubuntu. You may verify this by simply going into the EFI directory and running ls.





                  Another way:



                  If you don't succeed, and supposing your guest is Linux type, I myself had to do it:




                  1. Boot from live USB with any Linux.


                  2. Mount the root file system.



                  3. Create this file on the mounted file system, adjust the path to wherever you have mounted it:



                    /boot/efi/startup.nsh


                  4. Enter the above explained line to it.








                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Nov 18 '17 at 8:52

























                  answered Nov 30 '16 at 0:57









                  VlastimilVlastimil

                  8,0291363136




                  8,0291363136

























                      0














                      Workaround:



                      In the VirtualBox settings for your VM, go to System settings and in the Motherboard section un-check the




                      Enable EFI (Special OSes only).




                      Save the settings and restart your VM.





                      Important notes:




                      1. This will make the guest system run on BIOS / MBR legacy boot.


                      2. Only use, if the solution above does not work for you.







                      share|improve this answer


























                      • Yes, thank you! It was necessary to Enable EFI in order to make the GParted Live CD work. However, after resizing the disk partitions in GParted, I encountered this error, and also an error "fs0 is not a correct mapping" if I tried to enter the file system. Disabling this flag solved issue.

                        – Jamie
                        Oct 25 '18 at 5:35
















                      0














                      Workaround:



                      In the VirtualBox settings for your VM, go to System settings and in the Motherboard section un-check the




                      Enable EFI (Special OSes only).




                      Save the settings and restart your VM.





                      Important notes:




                      1. This will make the guest system run on BIOS / MBR legacy boot.


                      2. Only use, if the solution above does not work for you.







                      share|improve this answer


























                      • Yes, thank you! It was necessary to Enable EFI in order to make the GParted Live CD work. However, after resizing the disk partitions in GParted, I encountered this error, and also an error "fs0 is not a correct mapping" if I tried to enter the file system. Disabling this flag solved issue.

                        – Jamie
                        Oct 25 '18 at 5:35














                      0












                      0








                      0







                      Workaround:



                      In the VirtualBox settings for your VM, go to System settings and in the Motherboard section un-check the




                      Enable EFI (Special OSes only).




                      Save the settings and restart your VM.





                      Important notes:




                      1. This will make the guest system run on BIOS / MBR legacy boot.


                      2. Only use, if the solution above does not work for you.







                      share|improve this answer















                      Workaround:



                      In the VirtualBox settings for your VM, go to System settings and in the Motherboard section un-check the




                      Enable EFI (Special OSes only).




                      Save the settings and restart your VM.





                      Important notes:




                      1. This will make the guest system run on BIOS / MBR legacy boot.


                      2. Only use, if the solution above does not work for you.








                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited Nov 18 '17 at 8:29









                      Vlastimil

                      8,0291363136




                      8,0291363136










                      answered Jul 18 '17 at 20:27









                      Sagar_c_kSagar_c_k

                      93




                      93













                      • Yes, thank you! It was necessary to Enable EFI in order to make the GParted Live CD work. However, after resizing the disk partitions in GParted, I encountered this error, and also an error "fs0 is not a correct mapping" if I tried to enter the file system. Disabling this flag solved issue.

                        – Jamie
                        Oct 25 '18 at 5:35



















                      • Yes, thank you! It was necessary to Enable EFI in order to make the GParted Live CD work. However, after resizing the disk partitions in GParted, I encountered this error, and also an error "fs0 is not a correct mapping" if I tried to enter the file system. Disabling this flag solved issue.

                        – Jamie
                        Oct 25 '18 at 5:35

















                      Yes, thank you! It was necessary to Enable EFI in order to make the GParted Live CD work. However, after resizing the disk partitions in GParted, I encountered this error, and also an error "fs0 is not a correct mapping" if I tried to enter the file system. Disabling this flag solved issue.

                      – Jamie
                      Oct 25 '18 at 5:35





                      Yes, thank you! It was necessary to Enable EFI in order to make the GParted Live CD work. However, after resizing the disk partitions in GParted, I encountered this error, and also an error "fs0 is not a correct mapping" if I tried to enter the file system. Disabling this flag solved issue.

                      – Jamie
                      Oct 25 '18 at 5:35











                      0














                      I am having this problem and it does not accept any input that I've tried





                      share








                      New contributor




                      GN Trains is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                      Check out our Code of Conduct.

























                        0














                        I am having this problem and it does not accept any input that I've tried





                        share








                        New contributor




                        GN Trains is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                        Check out our Code of Conduct.























                          0












                          0








                          0







                          I am having this problem and it does not accept any input that I've tried





                          share








                          New contributor




                          GN Trains is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.










                          I am having this problem and it does not accept any input that I've tried






                          share








                          New contributor




                          GN Trains is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.








                          share


                          share






                          New contributor




                          GN Trains is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.









                          answered 7 mins ago









                          GN TrainsGN Trains

                          1




                          1




                          New contributor




                          GN Trains is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.





                          New contributor





                          GN Trains is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.






                          GN Trains is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                          Check out our Code of Conduct.






























                              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%2f326956%2fvirtualbox-guest-suddenly-boots-only-into-uefi-interactive-shell%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

                              Loup dans la culture

                              How to solve the problem of ntp “Unable to contact time server” from KDE?

                              Connection limited (no internet access)