8/27/2023 0 Comments Qemu system command not found![]() # CONFIG_KVM_DEBUG_FS is not ~]$ lsmod | grep kvm Virtualization: ~]$ zgrep CONFIG_KVM /proc/config.gz ![]() Here is the output of a few commands to confirm my hardware and kernel support of kvm: ~]$ LC_ALL=C lscpu | grep Virtualization I have removed and installed the package a few times since then and the problem still persists. I can confirm I have all the dependencies (besides optional) listed here. Despite this since then I have shredded those partitions, encrypted them again and this time have put ext4 as a filesystem and now I am still facing the exact same case of qemu not executing which makes me think this had nothing to do with filesystems in the first place. So before qemu stopped working as the archwiki suggests I disabled CoW on the directories containing my VMs using the following tip in the green paragraph). However the user I am logged in as is the owner of both their mount points and has r / w/ x permissions. I should note that both the windows VM and the arch VM are on encrypted partitions (luks2) containing a btrfs filesystem and are mounted (manually only when needed) on /mnt/. ![]() running qemu-system-x86_64 on it's own does the same. And to boot it up I used qemu-system-x86_64 -enable-kvm -cpu host -cdrom ~/Downloads/archlinux-2019.04.01-x86_64.iso -boot order=d -drive file=/mnt/VMS/webserver_test_arch/webserver_test_arch.img,format=raw -m 4G, however this is when qemu-system-x86_64 did not return any output and instantly dropped me back to $. As per the archwiki I used $ qemu-img create -f raw image_file 20G to create the image. Yesterday I created a new image which was to be used for a local arch web server. Two days ago I installed the qemu package from extra and followed this article on how to set up Windows10, and it all worked properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |