LinuxQuestions.org - Qemu NO KVM

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Qemu NO KVM (https://www.linuxquestions.org/questions/slackware-14/qemu-no-kvm-4175668274/)

I'm sorry if this has been asked & answered before. I searched exhaustively for RECENT articles or forum posts that explicitly listed the steps to get Qemu running on my 64 bit Slackware 14.2 system, BUT alas! I cannot find anything CURRENT.

My system DOES NOT use virtualization. There is no option for it in the BIOS. I LOOKED!

It is a 64 bit system:

Code:

# lscpu

Architecture:          x86_64

CPU op-mode(s):        32-bit, 64-bit

Byte Order:            Little Endian

CPU(s):                2

On-line CPU(s) list:  0,1

Thread(s) per core:    1

Core(s) per socket:    2

Socket(s):            1

Vendor ID:            GenuineIntel

CPU family:            6

Model:                23

Model name:            Intel(R) Core(TM)2 CPU        E7400  @ 2.80GHz

Stepping:              10

CPU MHz:              2799.948

BogoMIPS:              5599.89

L1d cache:            32K

L1i cache:            32K

L2 cache:              3072K

Flags:                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni monitor tm2 ssse3 lahf_lm kaiser dtherm

Code:

# cat /proc/cpuinfo

processor        : 0

vendor_id        : GenuineIntel

cpu family        : 6

model                : 23

model name        : Intel(R) Core(TM)2 CPU        E7400  @ 2.80GHz

stepping        : 10

cpu MHz                : 2799.948

cache size        : 3072 KB

physical id        : 0

siblings        : 2

core id                : 0

cpu cores        : 2

apicid                : 0

initial apicid        : 0

fpu                : yes

fpu_exception        : yes

cpuid level        : 13

wp                : yes

flags                : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni monitor tm2 ssse3 lahf_lm kaiser dtherm

bugs                : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit

bogomips        : 5599.89

clflush size        : 64

cache_alignment        : 64

address sizes        : 36 bits physical, 48 bits virtual

power management:



processor        : 1

vendor_id        : GenuineIntel

cpu family        : 6

model                : 23

model name        : Intel(R) Core(TM)2 CPU        E7400  @ 2.80GHz

stepping        : 10

cpu MHz                : 2799.948

cache size        : 3072 KB

physical id        : 0

siblings        : 2

core id                : 1

cpu cores        : 2

apicid                : 1

initial apicid        : 1

fpu                : yes

fpu_exception        : yes

cpuid level        : 13

wp                : yes

flags                : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni monitor tm2 ssse3 lahf_lm kaiser dtherm

bugs                : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit

bogomips        : 5599.89

clflush size        : 64

cache_alignment        : 64

address sizes        : 36 bits physical, 48 bits virtual

power management:

Is it possible to install Qemu WITHOUT KVM? Because I am missing "/dev/kvm".

Also Qemu can't seem to install from the new 4.1.0 Slackbuild. It fails every time.

The main goal here is to run Android-x86 inside Qemu.

Indeed you can install and run Qemu without kvm. We can't help you about the failure to build it with so few information.

What do you need to know? Just ask.

We did to know what command you typed to run the SlackBuild and the exact error messages you got when running it.

I ran this command:

Quote:

# BRIDGE_HELPER_SETUID=yes TARGETS=all ./qemu.SlackBuild

And it ended like so:

Quote:

contrib/vhost-user-gpu/vugbm.c: In function ‘map_bo’:
contrib/vhost-user-gpu/vugbm.c:161:17: warning: implicit declaration of function ‘gbm_bo_map’ [-Wimplicit-function-declaration]
buf->mmap = gbm_bo_map(buf->bo, 0, 0, buf->width, buf->height,
^
contrib/vhost-user-gpu/vugbm.c:161:5: warning: nested extern declaration of ‘gbm_bo_map’ [-Wnested-externs]
buf->mmap = gbm_bo_map(buf->bo, 0, 0, buf->width, buf->height,
^
contrib/vhost-user-gpu/vugbm.c:162:28: error: ‘GBM_BO_TRANSFER_READ_WRITE’ undeclared (first use in this function)
GBM_BO_TRANSFER_READ_WRITE, &stride,
^
contrib/vhost-user-gpu/vugbm.c:162:28: note: each undeclared identifier is reported only once for each function it appears in
contrib/vhost-user-gpu/vugbm.c: In function ‘unmap_bo’:
contrib/vhost-user-gpu/vugbm.c:173:5: warning: implicit declaration of function ‘gbm_bo_unmap’ [-Wimplicit-function-declaration]
gbm_bo_unmap(buf->bo, buf->mmap_data);
^
contrib/vhost-user-gpu/vugbm.c:173:5: warning: nested extern declaration of ‘gbm_bo_unmap’ [-Wnested-externs]
/tmp/SBo/qemu-4.1.0/rules.mak:69: recipe for target 'contrib/vhost-user-gpu/vugbm.o' failed
make: *** [contrib/vhost-user-gpu/vugbm.o] Error 1

If not done, replace this line from the SlackBuild
--enable-kvm \

by:
--disable-kvm \

then try again.

I ma not sure this be the issue, but it's worth trying.

LOL! I didn't see that as an option. I removed it and am running the slackbuild now. In a moment, I will tell you how it ran.

Is this the exact same as before?

Quote:

have you installed virglrenderer, by any chance?
qemu's README says

Code:

NOTE:

To compile with virglrenderer, you will need to upgrade to

mesa-12.0.0 or higher.

so, if you have installed virglrenderer just removepkg it before trying to build qemu.

BTW, if you don't have virtualization extensions available for your cpu, maybe your best option could be virtualbox.

by the way I previously installed, via: "#slapt-src -i ...":
pcsc-lite spice-protocol liburcu acpica meson graphviz python-evdev pyudev python3 libiscsi libcacard spice usbredir virglrenderer device-tree-compiler libnfs snappy glusterfs vde2 libqcow ovmf

Yes it's the same. Do you have SDL2 installed?

Quote:

Originally Posted by chaz_bro1972 (Post 6081999)

you should read the READMEs of the stuff you install from SBo, also if you are using slapt-src...

Also installed libvirt & virt-manager.

Yes, I have these SDL2 packages:

Quote:

ls /var/log/packages/SDL*
/var/log/packages/SDL2-2.0.4-x86_64-1dj /var/log/packages/SDL2_net-2.0.1-x86_64-1salix /var/log/packages/SDL_gfx-2.0.25-x86_64-1dj
/var/log/packages/SDL2_image-2.0.1-x86_64-1dj /var/log/packages/SDL2_ttf-2.0.13-x86_64-1dj /var/log/packages/SDL_perl-1.20.0-x86_64-7dj
/var/log/packages/SDL2_mixer-2.0.1-x86_64-1dj /var/log/packages/SDL_Pango-0.1.2-x86_64-5dj /var/log/packages/SDL_sound-1.0.3-x86_64-1salix

But it's an older version that the one in SBo., that could be the issue.

More generally, mixing packages coming from several repositories not ins sync wrt versions is a good receipt for failure.

So, if you run Slackware, only use packages intended for Slackware.