David Cordeiro Posted November 14, 2020 Share Posted November 14, 2020 (edited) Hi, Im an unexperienced linux user but i've managed to get Eve-NG installed has a VM. The issue is that Eve-ng is not recognizing AMD virtualization and it seems this is causing some issues loading some cisco images (VIOS) and even Windows images within Eve to run. I've confirmed that its active on BIOS. Is there something missing? domain type='kvm' id='24'> <name>EVE-NG</name> <uuid>11e9d867-9251-ade2-3747-213300138c4e</uuid> <metadata> <vmtemplate xmlns="unraid" name="Slackware" icon="slackware.png" os="slackware"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='4' threads='1'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> root@eve-ng:~# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 158 Model name: Intel(R) Core(TM) i5-7600K CPU @ 3.80GHz Stepping: 9 CPU MHz: 3791.877 BogoMIPS: 7583.75 L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 6144K NUMA node0 CPU(s): 0-3 Edited November 16, 2020 by David Cordeiro New issue Quote Link to comment
David Cordeiro Posted November 16, 2020 Author Share Posted November 16, 2020 On Unraid itself it is active. So im guessing this has to do something with the VM itself. I've followed countless posts, exhausted every possibility i could find, my last chance is someone with more knowledge to help me on this. Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 158 Model name: Intel(R) Core(TM) i5-7600K CPU @ 3.80GHz Stepping: 9 CPU MHz: 4128.502 CPU max MHz: 4200.0000 CPU min MHz: 800.0000 BogoMIPS: 7584.00 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache: 1 MiB L3 cache: 6 MiB NUMA node0 CPU(s): 0-3 Quote Link to comment
David Cordeiro Posted November 16, 2020 Author Share Posted November 16, 2020 FIXED 3 Days later.... Modify the syslinux.cfg file to add this kernel argument. 1. Log in as root to your host OS (unraid) and edit syslinux.cfg. $ vi /boot/syslinux/syslinux.cfg 2. Modification is below in bold. label unRAID OS menu default kernel /bzimage append initrd=/bzroot kvm-intel.nested=1,/bzroot-gui Quote Link to comment
bphillips330 Posted September 12, 2022 Share Posted September 12, 2022 I just came across this old thread. I was having issues with EVE-NG just crashing my server after a while. Started reading on Nested kvm's which I didn't even know about. Hopefully this fixes my issue. If you are still around, any other tips and tricks with EVE? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.