Arch linux not booting in QEMU












0















I am using QEMU to install arch linux on a 5G raw img disk and everytime and install it and reboot it boots back into arch but when i close qemu and try boot back into arch i am not prompted with the grub boot but it says WARN: No MBR magic, treating disk as raw. Booting... So i am assuming its only using the RAM and not actually writing anything to the drive. I also thought it was the disk type i was using as i was using qcow2 at first but got the same error so i switched to raw and im still getting the same error. It will say booing and do nothing else forever



This is my command to start QEMU:



.qemu-system-x86_64 -drive file=archlinux.img,index=0,media=disk,format=raw -cdrom archlinux.iso -m 3G -snapshot -cpu core2duo -smp 2


I am installing arch following this tutorial:



https://www.howtoforge.com/tutorial/install-arch-linux-on-virtualbox/


I am not sure if im installing grub properly or not ive just been following the tutorial










share|improve this question























  • I tried booting with another disk which is qcow2 that i jsut created and it has nothing on it and i got same error i think it is because nothing is actually being writen even though arch says that is has been written when i format the disk

    – Dextron
    Jan 6 at 2:50
















0















I am using QEMU to install arch linux on a 5G raw img disk and everytime and install it and reboot it boots back into arch but when i close qemu and try boot back into arch i am not prompted with the grub boot but it says WARN: No MBR magic, treating disk as raw. Booting... So i am assuming its only using the RAM and not actually writing anything to the drive. I also thought it was the disk type i was using as i was using qcow2 at first but got the same error so i switched to raw and im still getting the same error. It will say booing and do nothing else forever



This is my command to start QEMU:



.qemu-system-x86_64 -drive file=archlinux.img,index=0,media=disk,format=raw -cdrom archlinux.iso -m 3G -snapshot -cpu core2duo -smp 2


I am installing arch following this tutorial:



https://www.howtoforge.com/tutorial/install-arch-linux-on-virtualbox/


I am not sure if im installing grub properly or not ive just been following the tutorial










share|improve this question























  • I tried booting with another disk which is qcow2 that i jsut created and it has nothing on it and i got same error i think it is because nothing is actually being writen even though arch says that is has been written when i format the disk

    – Dextron
    Jan 6 at 2:50














0












0








0








I am using QEMU to install arch linux on a 5G raw img disk and everytime and install it and reboot it boots back into arch but when i close qemu and try boot back into arch i am not prompted with the grub boot but it says WARN: No MBR magic, treating disk as raw. Booting... So i am assuming its only using the RAM and not actually writing anything to the drive. I also thought it was the disk type i was using as i was using qcow2 at first but got the same error so i switched to raw and im still getting the same error. It will say booing and do nothing else forever



This is my command to start QEMU:



.qemu-system-x86_64 -drive file=archlinux.img,index=0,media=disk,format=raw -cdrom archlinux.iso -m 3G -snapshot -cpu core2duo -smp 2


I am installing arch following this tutorial:



https://www.howtoforge.com/tutorial/install-arch-linux-on-virtualbox/


I am not sure if im installing grub properly or not ive just been following the tutorial










share|improve this question














I am using QEMU to install arch linux on a 5G raw img disk and everytime and install it and reboot it boots back into arch but when i close qemu and try boot back into arch i am not prompted with the grub boot but it says WARN: No MBR magic, treating disk as raw. Booting... So i am assuming its only using the RAM and not actually writing anything to the drive. I also thought it was the disk type i was using as i was using qcow2 at first but got the same error so i switched to raw and im still getting the same error. It will say booing and do nothing else forever



This is my command to start QEMU:



.qemu-system-x86_64 -drive file=archlinux.img,index=0,media=disk,format=raw -cdrom archlinux.iso -m 3G -snapshot -cpu core2duo -smp 2


I am installing arch following this tutorial:



https://www.howtoforge.com/tutorial/install-arch-linux-on-virtualbox/


I am not sure if im installing grub properly or not ive just been following the tutorial







boot grub arch-linux qemu






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 6 at 2:29









DextronDextron

51




51













  • I tried booting with another disk which is qcow2 that i jsut created and it has nothing on it and i got same error i think it is because nothing is actually being writen even though arch says that is has been written when i format the disk

    – Dextron
    Jan 6 at 2:50



















  • I tried booting with another disk which is qcow2 that i jsut created and it has nothing on it and i got same error i think it is because nothing is actually being writen even though arch says that is has been written when i format the disk

    – Dextron
    Jan 6 at 2:50

















I tried booting with another disk which is qcow2 that i jsut created and it has nothing on it and i got same error i think it is because nothing is actually being writen even though arch says that is has been written when i format the disk

– Dextron
Jan 6 at 2:50





I tried booting with another disk which is qcow2 that i jsut created and it has nothing on it and i got same error i think it is because nothing is actually being writen even though arch says that is has been written when i format the disk

– Dextron
Jan 6 at 2:50










1 Answer
1






active

oldest

votes


















0














You have added the "-snapshot" option to your qemu command line, so this is expected behavior:



According to the manual, the -snapshot option instructs qemu to...




Write to temporary files instead of disk image files. In this case,
the raw disk image you use is not written back. You can however force
the write back by pressing C-a s.







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%2f1391056%2farch-linux-not-booting-in-qemu%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














    You have added the "-snapshot" option to your qemu command line, so this is expected behavior:



    According to the manual, the -snapshot option instructs qemu to...




    Write to temporary files instead of disk image files. In this case,
    the raw disk image you use is not written back. You can however force
    the write back by pressing C-a s.







    share|improve this answer




























      0














      You have added the "-snapshot" option to your qemu command line, so this is expected behavior:



      According to the manual, the -snapshot option instructs qemu to...




      Write to temporary files instead of disk image files. In this case,
      the raw disk image you use is not written back. You can however force
      the write back by pressing C-a s.







      share|improve this answer


























        0












        0








        0







        You have added the "-snapshot" option to your qemu command line, so this is expected behavior:



        According to the manual, the -snapshot option instructs qemu to...




        Write to temporary files instead of disk image files. In this case,
        the raw disk image you use is not written back. You can however force
        the write back by pressing C-a s.







        share|improve this answer













        You have added the "-snapshot" option to your qemu command line, so this is expected behavior:



        According to the manual, the -snapshot option instructs qemu to...




        Write to temporary files instead of disk image files. In this case,
        the raw disk image you use is not written back. You can however force
        the write back by pressing C-a s.








        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 6 at 23:55









        Christoph SommerChristoph Sommer

        2244




        2244






























            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%2f1391056%2farch-linux-not-booting-in-qemu%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

            If I really need a card on my start hand, how many mulligans make sense? [duplicate]

            Alcedinidae

            Can an atomic nucleus contain both particles and antiparticles? [duplicate]