Running Alpine in Live mode in QEMU: Difference between revisions
mNo edit summary |
mNo edit summary |
||
Line 28: | Line 28: | ||
echo "/dev/vda1 /media/vda1 vfat rw 0 0" >> /etc/fstab | echo "/dev/vda1 /media/vda1 vfat rw 0 0" >> /etc/fstab | ||
mount -a | mount -a | ||
setup-alpine # (select vda1 for saving | setup-alpine # (select vda1 for saving configs) | ||
lbu commit | lbu commit | ||
</pre> | </pre> |
Revision as of 18:41, 16 May 2020
To just give Alpine Linux a try in diskless mode, qemu can be used to boot the .iso file without any need for a virtual HDD image or further configuration.
qemu -m 512 -cdrom alpine-3.2.0-x86_64.iso
Issue
grsec nomodeset
at boot prompt to avoid being forced into graphical mode and loosing access.
Question: Is there a way to pass an apkovl as paramater at this stage?
Response to self: Yes. I do it like this, mounting /dev/vda1 to store the apkovl and the apkcache:
Preparing a KVM with a virtual drive:
mkdir -p /media/usb/images qemu-img create -f raw /media/usb/images/mykvm.config 32M qemu-system-x86_64 -enable-kvm -m 384 \ -name mykvm \ -cdrom /media/usb/images/alpine-3.2.0-x86_64.iso \ -drive file=/media/usb/images/mykvm.config,if=virtio \ -net lan \ -boot d &
And inside the KVM (in alpinelinux):
fdisk /dev/vda #creating a partition mkdosfs /dev/vda1 mkdir -p /media/vda1 echo "/dev/vda1 /media/vda1 vfat rw 0 0" >> /etc/fstab mount -a setup-alpine # (select vda1 for saving configs) lbu commit
The next reboot then loads the generated apkovl and apkcache found on /dev/vda1 -- completely running-from-ram based on the latest official ISO.