Hi Andrew,
I use the below .sh start script for Debian on armhf, network works
fine last time I tried it.
Thanks, it seems to use same -device virtio-net-device so may be fedora need some additional actions inside vm...
Turned out virt-2.11 was *really* important for Fedora, with this option I have network device inside vm, and after some battle with systemd (something inside network service depend on dbus .. bad surprize for someone who disabled dbus earlier! Started it back by systemctl enable dbus-daemon. Also, for some reason resolv.conf was set wrong, so I just moved systemd's created resolv.conf symlink from /etc and run dhclient directly ...) dnf seems to work its way towards installing midnight commander! I not dare to say when it might finis it, so I can try to install gcc and friends ...
But progress!
You can modify inside the virtual disk if
you mount it as a nbd loop device, I seem to remember if I did it your
way it was read-only, but that was year ago. I used it to change the
root password to no password at all when I forgot it....
MatN
====
#!/bin/bash
# note: after succesfull install and working network access (apt),
comment out the cdrom from # /etc/apt/sources.list
ISO=/mnt/DataCommon/ISOs/Debian_11/debian-11.1.0-armhf-netinst.iso
# Because qemu must be started with a direct kernel parameter, use a
variable to specify # the version. After a kernel update, extract the
proper vmlinuz and initrd files from the client, # and place them in
the directory where this script is started from, then update the
VERSION # accordingly. VERSION=5.10.0-18
qemu-system-arm -machine virt -cpu cortex-a15 -smp cpus=8,maxcpus=8
--append "root=/dev/vda1 console=ttyAMA0 earlyprintk=ttyAMA0" \
-kernel ./vmlinuz-$VERSION-armmp-lpae -initrd
./initrd.img-$VERSION-armmp-lpae -m 4096 \ -netdev
user,id=n0,hostfwd=tcp::10022-:22,smb=/home/mat/qemu_shared_folder
-device virtio-net-device,netdev=n0 \ -drive
file=debian11-arm.qcow2,if=none,format=qcow2,id=hd0 -device
virtio-blk-device,drive=hd0 \ -serial stdio
=============