VirtualBox VMs crash rapidly Announcing the arrival of Valued Associate #679: Cesar Manara ...

Why are there no cargo aircraft with "flying wing" design?

Doubts about chords

What happens to sewage if there is no river near by?

Is the address of a local variable a constexpr?

How widely used is the term Treppenwitz? Is it something that most Germans know?

How to deal with a team lead who never gives me credit?

Proof involving the spectral radius and Jordan Canonical form

How to find all the available tools in macOS terminal?

How does a Death Domain cleric's Touch of Death feature work with Touch-range spells delivered by familiars?

G-Code for resetting to 100% speed

What causes the vertical darker bands in my photo?

How can players work together to take actions that are otherwise impossible?

Why is "Consequences inflicted." not a sentence?

Java 8 stream max() function argument type Comparator vs Comparable

What are the motives behind Cersei's orders given to Bronn?

3 doors, three guards, one stone

Sorting numerically

The logistics of corpse disposal

How can I make names more distinctive without making them longer?

Right-skewed distribution with mean equals to mode?

How discoverable are IPv6 addresses and AAAA names by potential attackers?

Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?

Did Xerox really develop the first LAN?

Are my PIs rude or am I just being too sensitive?



VirtualBox VMs crash rapidly



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Virtualbox: inaccessable VMs?Syncing or version controlling virtualbox VMsExporting VMs with VirtualBoxVirtualBox multiple VMs bridged to one NICvirtualbox mouse integration across VMs and hostSpread VirtualBox VMs over coresSetting up DHCP for Virtualbox VMsNetworking trouble in VirtualBox Guest VMsCopy and paste to VirtualBox VMs





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I've used VirtualBox on a number of machines (including some really old creaky ones) over the years with great success. However, I have a new computer where it doesn't work! 64-bit AMD machine with Windows 10 x64 (up to date on patches). VirtualBox works fine in the control panels, but whenever I open a VM, that VM hard freezes almost exactly 5 seconds after startup. I've tried disc images that work fine on other machines. Most recently FreeDOS 1.2 and openSuSE LEAP. What kind of settings should I look for that might need adjustment on the computer?










share|improve this question





























    0















    I've used VirtualBox on a number of machines (including some really old creaky ones) over the years with great success. However, I have a new computer where it doesn't work! 64-bit AMD machine with Windows 10 x64 (up to date on patches). VirtualBox works fine in the control panels, but whenever I open a VM, that VM hard freezes almost exactly 5 seconds after startup. I've tried disc images that work fine on other machines. Most recently FreeDOS 1.2 and openSuSE LEAP. What kind of settings should I look for that might need adjustment on the computer?










    share|improve this question

























      0












      0








      0








      I've used VirtualBox on a number of machines (including some really old creaky ones) over the years with great success. However, I have a new computer where it doesn't work! 64-bit AMD machine with Windows 10 x64 (up to date on patches). VirtualBox works fine in the control panels, but whenever I open a VM, that VM hard freezes almost exactly 5 seconds after startup. I've tried disc images that work fine on other machines. Most recently FreeDOS 1.2 and openSuSE LEAP. What kind of settings should I look for that might need adjustment on the computer?










      share|improve this question














      I've used VirtualBox on a number of machines (including some really old creaky ones) over the years with great success. However, I have a new computer where it doesn't work! 64-bit AMD machine with Windows 10 x64 (up to date on patches). VirtualBox works fine in the control panels, but whenever I open a VM, that VM hard freezes almost exactly 5 seconds after startup. I've tried disc images that work fine on other machines. Most recently FreeDOS 1.2 and openSuSE LEAP. What kind of settings should I look for that might need adjustment on the computer?







      virtualbox virtual-machine






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked yesterday









      Brian KnoblauchBrian Knoblauch

      3,62693150




      3,62693150






















          1 Answer
          1






          active

          oldest

          votes


















          0














          Aha, figured it out already. Somehow Hyper-V got enabled on that machine and rather than alerting in some fashion, VirtualBox VMs instead crash seconds after startup. Disabled Hyper-V in Program Features and I'm all good again!






          share|improve this answer
























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            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%2fsuperuser.com%2fquestions%2f1425465%2fvirtualbox-vms-crash-rapidly%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Aha, figured it out already. Somehow Hyper-V got enabled on that machine and rather than alerting in some fashion, VirtualBox VMs instead crash seconds after startup. Disabled Hyper-V in Program Features and I'm all good again!






            share|improve this answer




























              0














              Aha, figured it out already. Somehow Hyper-V got enabled on that machine and rather than alerting in some fashion, VirtualBox VMs instead crash seconds after startup. Disabled Hyper-V in Program Features and I'm all good again!






              share|improve this answer


























                0












                0








                0







                Aha, figured it out already. Somehow Hyper-V got enabled on that machine and rather than alerting in some fashion, VirtualBox VMs instead crash seconds after startup. Disabled Hyper-V in Program Features and I'm all good again!






                share|improve this answer













                Aha, figured it out already. Somehow Hyper-V got enabled on that machine and rather than alerting in some fashion, VirtualBox VMs instead crash seconds after startup. Disabled Hyper-V in Program Features and I'm all good again!







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered yesterday









                Brian KnoblauchBrian Knoblauch

                3,62693150




                3,62693150






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • 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%2fsuperuser.com%2fquestions%2f1425465%2fvirtualbox-vms-crash-rapidly%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

                    VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...

                    Tribunal Administrativo e Fiscal de Mirandela Referências Menu de...

                    Couldn't open a raw socket. Error: Permission denied (13) (nmap)Is it possible to run networking commands...