Hello everyone! Actually I'm encountering a huge problem that I'll explain in steps, in order to be clear and discursive. First of all, I've deployed eve-ng Community Edition 2.0.3-92 on a KVM with those specs:
Server DELL PowerEdge R420 CPU: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz (24 Core total) RAM: 24GB RAM HDD: 4x 2TB All was working fine, KVM virtualization was working well and i was able to deploy qemu images like PaloAlto (PANOS-8.0.5) with qemu-options accell=kvm without any problem. After an internal company upgrade, i've decided to migrate this tool on Ovirt 4.2, in a node with following specs: SuperMicro Server CPU: Intel (R) Xeon (R) Platinum 8160T @ 2.10GHz (96 Core Total) RAM: 256 GB (16x16) DDR4 2666Mhz Samsung M393A2K40BB2-CTD HDD: x 2 Seagate ST500LM021-1KJ152 SATA 3.0 500GB SSD: x 2 SSD Samsung SSD 850 PRO 1TB NVMe: x 4 KXG50ZNV512G TOSHIBA 512GB (RAID0) Before migration eve-ng had 12 cores, 12 GB RAM and 90 GB HDD. After migration he has now 16 Core, 32GB RAM and RAID0 100GB. On Ovirt Pass-Through Host CPU is activated on VM, CPU nesting is activated too and after new release (2.0.5-95) those are eve-info command logs: eve-ng-info-ovirt: https://paste.fedoraproject.org/paste/Mom-~CXmnlU3cWCUdxPXFg Those are the previous eve-info command logs (on KVM): eve-ng-info-kvm: https://paste.fedoraproject.org/paste/AhqiapiyG5lJcHQBlrbJgw Also, here you can find output of cpuinfo of both node (KVM and Ovirt): cpuinfo-kvm: https://paste.fedoraproject.org/paste/6TQDHxCmiEMosF1qtcdSDQ cpuinfo-ovirt: https://paste.fedoraproject.org/paste/LmieowOvc7WwkEWW9JMduQ On both nodes, output of cat /sys/module/kvm_intel/parameters/nested is Y at least, this is the output of virsh dumpxml of both nodes: eve-ng-ovirt.xml: https://paste.fedoraproject.org/paste/s5SbdWhBHTWJs9O2Be~y8w eve-ng-kvm.xml: https://paste.fedoraproject.org/paste/Yz1E9taAkNT-JyTj8cBR-g However, after migration, i'm not able to deploy qemu images with accell=kvm enabled anymore. With same example PANOS-8.0.5 i'm able to run this qemu image only with this setting removed. Thinking on a migration problem, i've deployed a new eve-ng VM with same specs but problem is still present. Have you any idea on what might be the problem? Thanks for your support. _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/36M3ONT5CRBVD3EIKWTMSKENHIWXJ4ZN/
