Mailing List Archive

QEMU not running on new machine
With my older machine locking up once too often at in-opportune times,
I've switched over to a newer machine, which I've tried to set up
identically. QEMU is not laumching. It worked on the older system.
The error message is...

[x8940][waltdnes][~] /home/misc/qemu/arca/boot
Could not access KVM kernel module: No such file or directory
qemu-system-x86_64: failed to initialize kvm: No such file or directory

My user is a member of the kvm group, and I get the same error trying
to launch as root

My system...

* 12-core Intel Skylake with 16 gigs of ram, 64-bit gentoo

* Yes, KVM support is installed in the kernel...
[x8940][waltdnes][~] zgrep KVM_INTEL /proc/config.gz
CONFIG_KVM_INTEL=y

* make.conf contains
QEMU_SOFTMMU_TARGETS="i386 x86_64"
QEMU_USER_TARGETS="i386 x86_64"

* including flags in package.use, I get
[x8940][waltdnes][/etc/portage/package.use] emerge -pv qemu

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild R ] app-emulation/qemu-5.2.0-r3::gentoo USE="aio alsa bzip2 curl doc fdt gtk jpeg opengl oss png sdl slirp ssh usb vhost-net vnc -accessibility -caps (-capstone) -debug -filecaps -glusterfs -gnutls -infiniband -io-uring -iscsi -jack -jemalloc -lzo -multipath -ncurses -nfs -nls -numa -pin-upstream-blobs -plugins -pulseaudio -python -rbd -sasl -sdl-image -seccomp (-selinux) -smartcard -snappy -spice -static -static-user -systemtap -test -udev -usbredir -vde -vhost-user-fs -virgl -virtfs -vte -xattr -xen -xfs -zstd" PYTHON_TARGETS="python3_8 -python3_7 -python3_9" QEMU_SOFTMMU_TARGETS="i386 x86_64 -aarch64 -alpha -arm -avr -cris -hppa -lm32 -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -moxie -nios2 -or1k -ppc -ppc64 -riscv32 -riscv64 -rx -s390x -sh4 -sh4eb -sparc -sparc64 -tricore -unicore32 -xtensa -xtensaeb" QEMU_USER_TARGETS="i386 x86_64 -aarch64 -aarch64_be -alpha -arm -armeb -cris -hppa -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -mipsn32 -mipsn32el -nios2 -or1k -ppc -ppc64 -ppc64abi32 -ppc64le -riscv32 -riscv64 -s390x -sh4 -sh4eb -sparc -sparc32plus -sparc64 -tilegx -xtensa -xtensaeb" 0 KiB

* The startup script is...

[x8940][waltdnes][~] cat /home/misc/qemu/arca/boot
#!/bin/bash
cd /home/misc/qemu/arca
sudo /usr/bin/qemu-system-x86_64 -enable-kvm -runas waltdnes \
-cpu host -monitor vc -display gtk \
-drive file=arcac.img,format=raw \
-netdev user,id=mynetwork \
-device e1000,netdev=mynetwork \
-rtc base=localtime,clock=host \
-m 1024 -name "ArcaOS VM" \
-vga std -parallel none \
${@}

I repeat. it worked on the older machine.

--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
Re: QEMU not running on new machine [ In reply to ]
On Wed, 2021-05-26 at 12:50 -0400, Walter Dnes wrote:
>   With my older machine locking up once too often at in-opportune
> times,
> I've switched over to a newer machine, which I've tried to set up
> identically.  QEMU is not laumching.  It worked on the older system.
> The error message is...
>
> [x8940][waltdnes][~] /home/misc/qemu/arca/boot
> Could not access KVM kernel module: No such file or directory
> qemu-system-x86_64: failed to initialize kvm: No such file or directory
>
>   My user is a member of the kvm group, and I get the same error trying
> to launch as root
>
> My system...
>
> * 12-core Intel Skylake with 16 gigs of ram, 64-bit gentoo
>
> * Yes, KVM support is installed in the kernel...
> [x8940][waltdnes][~] zgrep KVM_INTEL /proc/config.gz
> CONFIG_KVM_INTEL=y
>
> * make.conf contains
> QEMU_SOFTMMU_TARGETS="i386 x86_64"
> QEMU_USER_TARGETS="i386 x86_64"
>
> * including flags in package.use, I get
> [x8940][waltdnes][/etc/portage/package.use] emerge -pv qemu
>
> These are the packages that would be merged, in order:
>
> Calculating dependencies... done!
> [ebuild   R    ] app-emulation/qemu-5.2.0-r3::gentoo  USE="aio alsa
> bzip2 curl doc fdt gtk jpeg opengl oss png sdl slirp ssh usb vhost-net
> vnc -accessibility -caps (-capstone) -debug -filecaps -glusterfs -
> gnutls -infiniband -io-uring -iscsi -jack -jemalloc -lzo -multipath -
> ncurses -nfs -nls -numa -pin-upstream-blobs -plugins -pulseaudio -
> python -rbd -sasl -sdl-image -seccomp (-selinux) -smartcard -snappy -
> spice -static -static-user -systemtap -test -udev -usbredir -vde -
> vhost-user-fs -virgl -virtfs -vte -xattr -xen -xfs -zstd"
> PYTHON_TARGETS="python3_8 -python3_7 -python3_9"
> QEMU_SOFTMMU_TARGETS="i386 x86_64 -aarch64 -alpha -arm -avr -cris -hppa
> -lm32 -m68k -microblaze -microblazeel -mips -mips64 -mips64el -mipsel -
> moxie -nios2 -or1k -ppc -ppc64 -riscv32 -riscv64 -rx -s390x -sh4 -sh4eb
> -sparc -sparc64 -tricore -unicore32 -xtensa -xtensaeb"
> QEMU_USER_TARGETS="i386 x86_64 -aarch64 -aarch64_be -alpha -arm -armeb
> -cris -hppa -m68k -microblaze -microblazeel -mips -mips64 -mips64el -
> mipsel -mipsn32 -mipsn32el -nios2 -or1k -ppc -ppc64 -ppc64abi32 -
> ppc64le -riscv32 -riscv64 -s390x -sh4 -sh4eb -sparc -sparc32plus -
> sparc64 -tilegx -xtensa -xtensaeb" 0 KiB
>
> * The startup script is...
>
> [x8940][waltdnes][~] cat /home/misc/qemu/arca/boot
> #!/bin/bash
> cd /home/misc/qemu/arca
> sudo /usr/bin/qemu-system-x86_64 -enable-kvm -runas waltdnes \
>    -cpu host -monitor vc -display gtk \
>    -drive file=arcac.img,format=raw \
>    -netdev user,id=mynetwork \
>    -device e1000,netdev=mynetwork \
>    -rtc base=localtime,clock=host \
>    -m 1024 -name "ArcaOS VM" \
>    -vga std -parallel none \
>    ${@}
>
>   I repeat. it worked on the older machine.
>

Hi,

What comes to my mind is actually describe in here[1]. Possibly
virtualization is disabled in BIOS/Firmware.


[1] https://wiki.gentoo.org/wiki/QEMU#BIOS_and_UEFI_firmware
Re: QEMU not running on new machine [ In reply to ]
On Wed, May 26, 2021 at 07:43:59PM +0200, Branko Grubi?? wrote
>
> Hi,
>
> What comes to my mind is actually describe in here[1]. Possibly
> virtualization is disabled in BIOS/Firmware.
>
>
> [1] https://wiki.gentoo.org/wiki/QEMU#BIOS_and_UEFI_firmware

Thank you very much; that was it. QEMU is now up and running. I had
to dig through to almost the end of the BIOS setup to find and click on
"Enable Intel virtualization technology".

--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications