IOL+QEMU=crash
Posted: Sat Jul 04, 2020 5:14 pm
Hardware : CPU - core i7-8600 (6 Cores), 32GB RAM, 256GB SSD, 1 LANcard
EVE-NG Running on - Hyper-V Windows 10 version 1909
Nested virtualisation enabled
1. check the path of the image ( for windows win-XXXX) - check
2. have you fixed permission(/opt/unetlab/wrappers/unl_wrapper -a fixpermissions) - check
3. file name format matches against EVE-NG requirement mentioned in the site - check
4. Check the logs /opt/unetlab/data/Logs/ - check
Hi
Different EVE-NG versions (now v2.0.3-110), different IOL images, different QEMU images - same problem.
Only IOL images (5,10,15 .. 40+) - work fine, only QEMU images (5,10,15.. 20+) - work fine.
If I start anyone IOL image with anyone QEMU image - kernel panic..
Any solutions?
Tnks
EVE-NG Running on - Hyper-V Windows 10 version 1909
Nested virtualisation enabled
1. check the path of the image ( for windows win-XXXX) - check
2. have you fixed permission(/opt/unetlab/wrappers/unl_wrapper -a fixpermissions) - check
3. file name format matches against EVE-NG requirement mentioned in the site - check
4. Check the logs /opt/unetlab/data/Logs/ - check
Hi
Different EVE-NG versions (now v2.0.3-110), different IOL images, different QEMU images - same problem.
Only IOL images (5,10,15 .. 40+) - work fine, only QEMU images (5,10,15.. 20+) - work fine.
If I start anyone IOL image with anyone QEMU image - kernel panic..
Any solutions?
Tnks