Qemu cannot recognize file changes immediately












1















I'm completing Brokenthorn OS tutorial where I create a virtual floppy in Ubuntu using MSDOSFS command and then I make changes to this virtual floppy, like changing its MBR using DD command and copying and removing files, the problem is when I make some changes and then run it on Qemu, it doesn't detect changes and shows result as if I hadn't made any change to the floppy drive, but after running and exit qemu some times, it then starts showing me correct result. Why doesn't qemu detect changes immediately?










share|improve this question

























  • Hi, thanks for your response. Do you mean I should mount virtual floppy copy files to it and then unmount it and then use it on qemu?

    – Amir Khan
    Nov 25 '18 at 6:40











  • I create virtual floppy images using msdosfs command, then mount a folder on it using, "mount imagename.img foldername" command then I copy files to folder using simple cp.

    – Amir Khan
    Nov 25 '18 at 6:46








  • 1





    Thank you so much, your solution worked. Now its working very well. THANKS.

    – Amir Khan
    Nov 25 '18 at 6:59
















1















I'm completing Brokenthorn OS tutorial where I create a virtual floppy in Ubuntu using MSDOSFS command and then I make changes to this virtual floppy, like changing its MBR using DD command and copying and removing files, the problem is when I make some changes and then run it on Qemu, it doesn't detect changes and shows result as if I hadn't made any change to the floppy drive, but after running and exit qemu some times, it then starts showing me correct result. Why doesn't qemu detect changes immediately?










share|improve this question

























  • Hi, thanks for your response. Do you mean I should mount virtual floppy copy files to it and then unmount it and then use it on qemu?

    – Amir Khan
    Nov 25 '18 at 6:40











  • I create virtual floppy images using msdosfs command, then mount a folder on it using, "mount imagename.img foldername" command then I copy files to folder using simple cp.

    – Amir Khan
    Nov 25 '18 at 6:46








  • 1





    Thank you so much, your solution worked. Now its working very well. THANKS.

    – Amir Khan
    Nov 25 '18 at 6:59














1












1








1


1






I'm completing Brokenthorn OS tutorial where I create a virtual floppy in Ubuntu using MSDOSFS command and then I make changes to this virtual floppy, like changing its MBR using DD command and copying and removing files, the problem is when I make some changes and then run it on Qemu, it doesn't detect changes and shows result as if I hadn't made any change to the floppy drive, but after running and exit qemu some times, it then starts showing me correct result. Why doesn't qemu detect changes immediately?










share|improve this question
















I'm completing Brokenthorn OS tutorial where I create a virtual floppy in Ubuntu using MSDOSFS command and then I make changes to this virtual floppy, like changing its MBR using DD command and copying and removing files, the problem is when I make some changes and then run it on Qemu, it doesn't detect changes and shows result as if I hadn't made any change to the floppy drive, but after running and exit qemu some times, it then starts showing me correct result. Why doesn't qemu detect changes immediately?







qemu mount bootloader osdev






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 26 '18 at 1:41









Michael Petch

26.4k556105




26.4k556105










asked Nov 25 '18 at 6:23









Amir KhanAmir Khan

104




104













  • Hi, thanks for your response. Do you mean I should mount virtual floppy copy files to it and then unmount it and then use it on qemu?

    – Amir Khan
    Nov 25 '18 at 6:40











  • I create virtual floppy images using msdosfs command, then mount a folder on it using, "mount imagename.img foldername" command then I copy files to folder using simple cp.

    – Amir Khan
    Nov 25 '18 at 6:46








  • 1





    Thank you so much, your solution worked. Now its working very well. THANKS.

    – Amir Khan
    Nov 25 '18 at 6:59



















  • Hi, thanks for your response. Do you mean I should mount virtual floppy copy files to it and then unmount it and then use it on qemu?

    – Amir Khan
    Nov 25 '18 at 6:40











  • I create virtual floppy images using msdosfs command, then mount a folder on it using, "mount imagename.img foldername" command then I copy files to folder using simple cp.

    – Amir Khan
    Nov 25 '18 at 6:46








  • 1





    Thank you so much, your solution worked. Now its working very well. THANKS.

    – Amir Khan
    Nov 25 '18 at 6:59

















Hi, thanks for your response. Do you mean I should mount virtual floppy copy files to it and then unmount it and then use it on qemu?

– Amir Khan
Nov 25 '18 at 6:40





Hi, thanks for your response. Do you mean I should mount virtual floppy copy files to it and then unmount it and then use it on qemu?

– Amir Khan
Nov 25 '18 at 6:40













I create virtual floppy images using msdosfs command, then mount a folder on it using, "mount imagename.img foldername" command then I copy files to folder using simple cp.

– Amir Khan
Nov 25 '18 at 6:46







I create virtual floppy images using msdosfs command, then mount a folder on it using, "mount imagename.img foldername" command then I copy files to folder using simple cp.

– Amir Khan
Nov 25 '18 at 6:46






1




1





Thank you so much, your solution worked. Now its working very well. THANKS.

– Amir Khan
Nov 25 '18 at 6:59





Thank you so much, your solution worked. Now its working very well. THANKS.

– Amir Khan
Nov 25 '18 at 6:59












1 Answer
1






active

oldest

votes


















0














When you are finished updating / deleting / copying files you should use the umount command to unmount the directory when finished. That will ensure all the file updates are complete. At that point try running it in QEMU. My guess is that you are keeping the file system mounted while running QEMU. That can cause the type of problems you seem to be observing.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    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%2fstackoverflow.com%2fquestions%2f53465168%2fqemu-cannot-recognize-file-changes-immediately%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














    When you are finished updating / deleting / copying files you should use the umount command to unmount the directory when finished. That will ensure all the file updates are complete. At that point try running it in QEMU. My guess is that you are keeping the file system mounted while running QEMU. That can cause the type of problems you seem to be observing.






    share|improve this answer




























      0














      When you are finished updating / deleting / copying files you should use the umount command to unmount the directory when finished. That will ensure all the file updates are complete. At that point try running it in QEMU. My guess is that you are keeping the file system mounted while running QEMU. That can cause the type of problems you seem to be observing.






      share|improve this answer


























        0












        0








        0







        When you are finished updating / deleting / copying files you should use the umount command to unmount the directory when finished. That will ensure all the file updates are complete. At that point try running it in QEMU. My guess is that you are keeping the file system mounted while running QEMU. That can cause the type of problems you seem to be observing.






        share|improve this answer













        When you are finished updating / deleting / copying files you should use the umount command to unmount the directory when finished. That will ensure all the file updates are complete. At that point try running it in QEMU. My guess is that you are keeping the file system mounted while running QEMU. That can cause the type of problems you seem to be observing.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 25 '18 at 7:01









        Michael PetchMichael Petch

        26.4k556105




        26.4k556105
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • 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%2fstackoverflow.com%2fquestions%2f53465168%2fqemu-cannot-recognize-file-changes-immediately%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

            Create new schema in PostgreSQL using DBeaver

            Deepest pit of an array with Javascript: test on Codility

            Costa Masnaga