Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building image - how long should the build take? #6

Open
pfk-beta opened this issue Jan 24, 2024 · 0 comments
Open

Building image - how long should the build take? #6

pfk-beta opened this issue Jan 24, 2024 · 0 comments

Comments

@pfk-beta
Copy link

pfk-beta commented Jan 24, 2024

Hello,
I followed the instruction, with some minor modifications (install test-arch, add apt opts to allow unauthenticated repo and packages). After running shell script I have get qemu command:

sudo qemu-system-arm   \
-net nic,model=virtio \
-net user \
-object rng-random,filename=/dev/urandom,id=rng0 -device virtio-rng-pci,rng=rng0,id=rng-device0 \
-drive if=virtio,file=/var/tmp/debian-bullseye-armhf.img,index=0,format=raw,discard=unmap,detect-zeroes=unmap \
-drive if=pflash,format=raw,unit=0,file=/usr/share/AAVMF/AAVMF32_CODE.fd,readonly=on  \
-drive if=pflash,format=raw,unit=1,file=/var/tmp/debian-bullseye-armhf-efivars.fd \
-m 1024 \
-cpu max \
-machine virt

But when I run this command, I've get QEMU guest window, with QEMU Monitor shell. And nothing is happend. Is something working under the hood? How much should it take to build the image? HTOP is monitoring: 0.6% of CPU.

@pfk-beta pfk-beta changed the title QEMU Monitor waiting for response Building image - how long should the build take? Jan 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant