How to start subiquity in qemu on ARM64?How do I install qemu?GTX1080 gpu passthrough QemuUpdating Ubuntu's ARM64 toolchainLibvirt Qemu passwordHow to run armhf executables on an arm64 system?Compile deb packages in arm64Qemu vs. Xen(Qemu): virsh can't find qemuUbuntu 17.10 won't start on QEMUqemu arm64 emulation on host x86, it stuck when booting kernelI can't start my linux in qemu-vm

PTIJ: Which Dr. Seuss books should one obtain?

Do people actually use the word "kaputt" in conversation?

Should I be concerned about student access to a test bank?

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

Are all namekians brothers?

Relations between homogeneous polynomials

What is it called when someone votes for an option that's not their first choice?

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

Capacitor electron flow

Trouble reading roman numeral notation with flats

Can you take a "free object interaction" while incapacitated?

Non-Borel set in arbitrary metric space

How to preserve electronics (computers, ipads, phones) for hundreds of years?

Should a narrator ever describe things based on a character's view instead of facts?

I keep switching characters, how do I stop?

What should be the ideal length of sentences in a blog post for ease of reading?

Why would five hundred and five same as one?

Is there a distance limit for minecart tracks?

Pre-Employment Background Check With Consent For Future Checks

Would this string work as string?

Should I warn a new PhD Student?

Did I make a mistake by ccing email to boss to others?

What (if any) is the reason to buy in small local stores?

1 John in Luther’s Bibel



How to start subiquity in qemu on ARM64?


How do I install qemu?GTX1080 gpu passthrough QemuUpdating Ubuntu's ARM64 toolchainLibvirt Qemu passwordHow to run armhf executables on an arm64 system?Compile deb packages in arm64Qemu vs. Xen(Qemu): virsh can't find qemuUbuntu 17.10 won't start on QEMUqemu arm64 emulation on host x86, it stuck when booting kernelI can't start my linux in qemu-vm













0















I would like to run the Ubuntu installer in qemu. I have used the kernel from the respective Ubuntu CD images and have verified my command line using the AMD64 architecture:



$ qemu-system-x86_64 --version
QEMU emulator version 2.5.0 ..
$ isoinfo -R -x "/install/vmlinuz" -i bionic-server-amd64.iso >linux
$ qemu-system-x86_64 -nodefaults -nographic -kernel linux
-serial stdio -append "console=ttyS0"
-machine pc -cpu qemu64 -m 1G
[ 0.0000000] Linux version 4.15.0-44-generic ..


However, when I try the same thing for ARM64 architecture (not my host arch):



$ qemu-system-aarch64 --version
QEMU emulator version 2.5.0 ..
$ isoinfo -R -x "/install/vmlinuz" -i bionic-server-arm64.iso >linux
$ qemu-system-aarch64 -nodefaults -nographic -kernel linux
-serial stdio -append "console=ttyAMA0"
-machine virt -cpu cortex-a53 -m 1G


I get zero output at 100% cpu usage. How can i determine what went wrong?



Executing with -d unimp -D debug.log reveals:



read access to unsupported AArch64 system register op0:3 op1:0 crn:0 crm:7 op2:2









share|improve this question






















  • Don't you always need to set -M and prepare a pflash and such for arm64, like described here ?

    – Christian Ehrhardt
    Feb 11 at 7:10











  • @ChristianEhrhardt afaik -M is just a deprecated Alias for -machine (which i did use), and -kernel an arch independent shortcut for "put this into ram and jump to it" (which should circumvent all issues from bootloader/EFI)

    – anx
    Feb 11 at 11:53
















0















I would like to run the Ubuntu installer in qemu. I have used the kernel from the respective Ubuntu CD images and have verified my command line using the AMD64 architecture:



$ qemu-system-x86_64 --version
QEMU emulator version 2.5.0 ..
$ isoinfo -R -x "/install/vmlinuz" -i bionic-server-amd64.iso >linux
$ qemu-system-x86_64 -nodefaults -nographic -kernel linux
-serial stdio -append "console=ttyS0"
-machine pc -cpu qemu64 -m 1G
[ 0.0000000] Linux version 4.15.0-44-generic ..


However, when I try the same thing for ARM64 architecture (not my host arch):



$ qemu-system-aarch64 --version
QEMU emulator version 2.5.0 ..
$ isoinfo -R -x "/install/vmlinuz" -i bionic-server-arm64.iso >linux
$ qemu-system-aarch64 -nodefaults -nographic -kernel linux
-serial stdio -append "console=ttyAMA0"
-machine virt -cpu cortex-a53 -m 1G


I get zero output at 100% cpu usage. How can i determine what went wrong?



Executing with -d unimp -D debug.log reveals:



read access to unsupported AArch64 system register op0:3 op1:0 crn:0 crm:7 op2:2









share|improve this question






















  • Don't you always need to set -M and prepare a pflash and such for arm64, like described here ?

    – Christian Ehrhardt
    Feb 11 at 7:10











  • @ChristianEhrhardt afaik -M is just a deprecated Alias for -machine (which i did use), and -kernel an arch independent shortcut for "put this into ram and jump to it" (which should circumvent all issues from bootloader/EFI)

    – anx
    Feb 11 at 11:53














0












0








0








I would like to run the Ubuntu installer in qemu. I have used the kernel from the respective Ubuntu CD images and have verified my command line using the AMD64 architecture:



$ qemu-system-x86_64 --version
QEMU emulator version 2.5.0 ..
$ isoinfo -R -x "/install/vmlinuz" -i bionic-server-amd64.iso >linux
$ qemu-system-x86_64 -nodefaults -nographic -kernel linux
-serial stdio -append "console=ttyS0"
-machine pc -cpu qemu64 -m 1G
[ 0.0000000] Linux version 4.15.0-44-generic ..


However, when I try the same thing for ARM64 architecture (not my host arch):



$ qemu-system-aarch64 --version
QEMU emulator version 2.5.0 ..
$ isoinfo -R -x "/install/vmlinuz" -i bionic-server-arm64.iso >linux
$ qemu-system-aarch64 -nodefaults -nographic -kernel linux
-serial stdio -append "console=ttyAMA0"
-machine virt -cpu cortex-a53 -m 1G


I get zero output at 100% cpu usage. How can i determine what went wrong?



Executing with -d unimp -D debug.log reveals:



read access to unsupported AArch64 system register op0:3 op1:0 crn:0 crm:7 op2:2









share|improve this question














I would like to run the Ubuntu installer in qemu. I have used the kernel from the respective Ubuntu CD images and have verified my command line using the AMD64 architecture:



$ qemu-system-x86_64 --version
QEMU emulator version 2.5.0 ..
$ isoinfo -R -x "/install/vmlinuz" -i bionic-server-amd64.iso >linux
$ qemu-system-x86_64 -nodefaults -nographic -kernel linux
-serial stdio -append "console=ttyS0"
-machine pc -cpu qemu64 -m 1G
[ 0.0000000] Linux version 4.15.0-44-generic ..


However, when I try the same thing for ARM64 architecture (not my host arch):



$ qemu-system-aarch64 --version
QEMU emulator version 2.5.0 ..
$ isoinfo -R -x "/install/vmlinuz" -i bionic-server-arm64.iso >linux
$ qemu-system-aarch64 -nodefaults -nographic -kernel linux
-serial stdio -append "console=ttyAMA0"
-machine virt -cpu cortex-a53 -m 1G


I get zero output at 100% cpu usage. How can i determine what went wrong?



Executing with -d unimp -D debug.log reveals:



read access to unsupported AArch64 system register op0:3 op1:0 crn:0 crm:7 op2:2






16.04 virtualization qemu arm64






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Feb 9 at 7:34









anxanx

1,20211332




1,20211332












  • Don't you always need to set -M and prepare a pflash and such for arm64, like described here ?

    – Christian Ehrhardt
    Feb 11 at 7:10











  • @ChristianEhrhardt afaik -M is just a deprecated Alias for -machine (which i did use), and -kernel an arch independent shortcut for "put this into ram and jump to it" (which should circumvent all issues from bootloader/EFI)

    – anx
    Feb 11 at 11:53


















  • Don't you always need to set -M and prepare a pflash and such for arm64, like described here ?

    – Christian Ehrhardt
    Feb 11 at 7:10











  • @ChristianEhrhardt afaik -M is just a deprecated Alias for -machine (which i did use), and -kernel an arch independent shortcut for "put this into ram and jump to it" (which should circumvent all issues from bootloader/EFI)

    – anx
    Feb 11 at 11:53

















Don't you always need to set -M and prepare a pflash and such for arm64, like described here ?

– Christian Ehrhardt
Feb 11 at 7:10





Don't you always need to set -M and prepare a pflash and such for arm64, like described here ?

– Christian Ehrhardt
Feb 11 at 7:10













@ChristianEhrhardt afaik -M is just a deprecated Alias for -machine (which i did use), and -kernel an arch independent shortcut for "put this into ram and jump to it" (which should circumvent all issues from bootloader/EFI)

– anx
Feb 11 at 11:53






@ChristianEhrhardt afaik -M is just a deprecated Alias for -machine (which i did use), and -kernel an arch independent shortcut for "put this into ram and jump to it" (which should circumvent all issues from bootloader/EFI)

– anx
Feb 11 at 11:53











1 Answer
1






active

oldest

votes


















0














Just upgrade your system.



Both AMD64 and ARM64 kernels start exactly as attempted in question using QEMU emulator version 3.1.0



Note that the command line is not exactly the same though, console=ttyS0 translates to console=ttyAMA0 on ARM. To really start subiquity, add -initrd initrd -cdrom bionic-server-arm64.iso



  • extract using isoinfo -R -x "/install/initrd.gz" -i bionic-server-arm64.iso >initrd (verify results - isoinfo will not fail verbosely)

  • loading from ISO will be slow, adding virtio & more cores may result in significant speedup

  • when adding a preseed file, note the cdrom mount location, e.g. file=/cdrom/preseed/example.seed




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%2f1116867%2fhow-to-start-subiquity-in-qemu-on-arm64%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














    Just upgrade your system.



    Both AMD64 and ARM64 kernels start exactly as attempted in question using QEMU emulator version 3.1.0



    Note that the command line is not exactly the same though, console=ttyS0 translates to console=ttyAMA0 on ARM. To really start subiquity, add -initrd initrd -cdrom bionic-server-arm64.iso



    • extract using isoinfo -R -x "/install/initrd.gz" -i bionic-server-arm64.iso >initrd (verify results - isoinfo will not fail verbosely)

    • loading from ISO will be slow, adding virtio & more cores may result in significant speedup

    • when adding a preseed file, note the cdrom mount location, e.g. file=/cdrom/preseed/example.seed




    share



























      0














      Just upgrade your system.



      Both AMD64 and ARM64 kernels start exactly as attempted in question using QEMU emulator version 3.1.0



      Note that the command line is not exactly the same though, console=ttyS0 translates to console=ttyAMA0 on ARM. To really start subiquity, add -initrd initrd -cdrom bionic-server-arm64.iso



      • extract using isoinfo -R -x "/install/initrd.gz" -i bionic-server-arm64.iso >initrd (verify results - isoinfo will not fail verbosely)

      • loading from ISO will be slow, adding virtio & more cores may result in significant speedup

      • when adding a preseed file, note the cdrom mount location, e.g. file=/cdrom/preseed/example.seed




      share

























        0












        0








        0







        Just upgrade your system.



        Both AMD64 and ARM64 kernels start exactly as attempted in question using QEMU emulator version 3.1.0



        Note that the command line is not exactly the same though, console=ttyS0 translates to console=ttyAMA0 on ARM. To really start subiquity, add -initrd initrd -cdrom bionic-server-arm64.iso



        • extract using isoinfo -R -x "/install/initrd.gz" -i bionic-server-arm64.iso >initrd (verify results - isoinfo will not fail verbosely)

        • loading from ISO will be slow, adding virtio & more cores may result in significant speedup

        • when adding a preseed file, note the cdrom mount location, e.g. file=/cdrom/preseed/example.seed




        share













        Just upgrade your system.



        Both AMD64 and ARM64 kernels start exactly as attempted in question using QEMU emulator version 3.1.0



        Note that the command line is not exactly the same though, console=ttyS0 translates to console=ttyAMA0 on ARM. To really start subiquity, add -initrd initrd -cdrom bionic-server-arm64.iso



        • extract using isoinfo -R -x "/install/initrd.gz" -i bionic-server-arm64.iso >initrd (verify results - isoinfo will not fail verbosely)

        • loading from ISO will be slow, adding virtio & more cores may result in significant speedup

        • when adding a preseed file, note the cdrom mount location, e.g. file=/cdrom/preseed/example.seed





        share











        share


        share










        answered 4 mins ago









        anxanx

        1,20211332




        1,20211332



























            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%2f1116867%2fhow-to-start-subiquity-in-qemu-on-arm64%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

            Möglingen Índice Localización Historia Demografía Referencias Enlaces externos Menú de navegación48°53′18″N 9°07′45″E / 48.888333333333, 9.129166666666748°53′18″N 9°07′45″E / 48.888333333333, 9.1291666666667Sitio web oficial Mapa de Möglingen«Gemeinden in Deutschland nach Fläche, Bevölkerung und Postleitzahl am 30.09.2016»Möglingen

            Virtualbox - Configuration error: Querying “UUID” failed (VERR_CFGM_VALUE_NOT_FOUND)“VERR_SUPLIB_WORLD_WRITABLE” error when trying to installing OS in virtualboxVirtual Box Kernel errorFailed to open a seesion for the virtual machineFailed to open a session for the virtual machineUbuntu 14.04 LTS Virtualbox errorcan't use VM VirtualBoxusing virtualboxI can't run Linux-64 Bit on VirtualBoxUnable to insert the virtual optical disk (VBoxguestaddition) in virtual machine for ubuntu server in win 10VirtuaBox in Ubuntu 18.04 Issues with Win10.ISO Installation

            Antonio De Lisio Carrera Referencias Menú de navegación«Caracas: evolución relacional multipleja»«Cuando los gobiernos subestiman a las localidades: L a Iniciativa para la Integración de la Infraestructura Regional Suramericana (IIRSA) en la frontera Colombo-Venezolana»«Maestría en Planificación Integral del Ambiente»«La Metrópoli Caraqueña: Expansión Simplificadora o Articulación Diversificante»«La Metrópoli Caraqueña: Expansión Simplificadora o Articulación Diversificante»«Conózcanos»«Caracas: evolución relacional multipleja»«La Metrópoli Caraqueña: Expansión Simplificadora o Articulación Diversificante»