cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5566
Views
10
Helpful
4
Replies

Cisco ISE - Unsupported Hardware Detected

Hello,

 

I'm having difficulties with bootstrapping Cisco ISE 2.7.0 VM in GNS3.

During the bootstrap I always receive the following error message:

 

*** checking for supported platform

*** ERROR: UNSUPPORTED HARDWARE DETECTED"

*** Cisco UDI (Unique Device Identifier) not found on this appliance.

*** Exiting installation

System halted

 

Below is an error log from GNS3 VM:


Start QEMU with /usr/bin/qemu-system-x86_64 -name ISE-1 -m 20000M -smp cpus=8,so ckets=1 -enable-kvm -machine smm=off -boot order=c -cdrom /opt/gns3/images/QEMU/ ise-2.7.0.356.SPA.x86_64.iso -drive file=/opt/gns3/projects/e36b9cce-2ad3-428e-9 a5d-207871101131/project-files/qemu/2aae9c07-f2af-4fd5-b191-782f62c98c48/hda_dis k.qcow2,if=ide,index=0,media=disk,id=drive0 -uuid 2aae9c07-f2af-4fd5-b191-782f62 c98c48 -vnc 0.0.0.0:0 -monitor tcp:127.0.0.1:36223,server,nowait -net none -devi ce e1000,mac=0c:11:31:8c:48:00,netdev=gns3-0 -netdev socket,id=gns3-0,udp=127.0. 0.1:20001,localaddr=127.0.0.1:20000 -device e1000,mac=0c:11:31:8c:48:01,netdev=g ns3-1 -netdev socket,id=gns3-1,udp=127.0.0.1:20003,localaddr=127.0.0.1:20002

Execution log:
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:E CX.vmx [bit 5]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:E CX.vmx [bit 5]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:E CX.vmx [bit 5]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:E CX.vmx [bit 5]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:E CX.vmx [bit 5]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:E CX.vmx [bit 5]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:E CX.vmx [bit 5]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:E CX.vmx [bit 5]

 

I changed the configuration file of qemu-system-x86.conf located under /etc/modprobe.d as per below and rebooted VM, but no joy...

 

gns3@gns3vm:/etc/modprobe.d$ cat qemu-system-x86.conf
options kvm_amd nested=1
options kvm halt_poll_ns=0
gns3@gns3vm:/etc/modprobe.d$

 

I also checked other threads / discussions but I didn't find any relevant info.

 

This issue started since PC reinstall, it worked fine before.

 

GNS3 / GNS3 VM version: 2.2.17

Components: AMD Ryzen 9

Allocated resources to ISE node: 8 vCPUs, 20 GB RAM

The ISE image is from official Cisco website.

 

I believe that this is related to AMD CPU, but have no clue where the issue lies.

Any help / inputs will be much appreciated.

1 Accepted Solution

Accepted Solutions

Managed to make the ISE VM working by installing it directly under VMware workstation and then linking it under GNS3 as VMware VM.

 

I checked the link you provided but unfortunately I did not manage the conversion between vmdk and qcow2...

I remember that last time I've done something in the GNS3 VM shell, something about KVM acceleration...

 

Anyway, at least I can say that it is working now. Not ideally because I'd like to have a QEMU template directly under GNS3 but at least I can lab again.

 

It appeared to be more GNS3 VM related issue than issue with the ISE VM itself, so I think I'll open a case with GNS3 team instead.

 

Thanks a lot for your help, much appreciated.

View solution in original post

4 Replies 4

Mark Elsen
Hall of Fame
Hall of Fame

 

 - Check if this article can help :

               https://www.gns3.com/community/featured/cisco-ise-unsupported-hardware-d

 M.



-- Let everything happen to you  
       Beauty and terror
      Just keep going    
       No feeling is final
Reiner Maria Rilke (1899)

Managed to make the ISE VM working by installing it directly under VMware workstation and then linking it under GNS3 as VMware VM.

 

I checked the link you provided but unfortunately I did not manage the conversion between vmdk and qcow2...

I remember that last time I've done something in the GNS3 VM shell, something about KVM acceleration...

 

Anyway, at least I can say that it is working now. Not ideally because I'd like to have a QEMU template directly under GNS3 but at least I can lab again.

 

It appeared to be more GNS3 VM related issue than issue with the ISE VM itself, so I think I'll open a case with GNS3 team instead.

 

Thanks a lot for your help, much appreciated.

I already checked this and I did not find anything related to my problem, but thank you for your input.