NX-OSv9k cannot be loaded in eve-ng

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

Locked
snurfit
Posts: 13
Joined: Fri Jun 02, 2017 10:43 am

Re: NX-OSv9k cannot be loaded in eve-ng

Post by snurfit » Tue Jun 06, 2017 12:10 pm

Yep, thats the one!

Still no dice on my end though :(
Top
snurfit
Posts: 13
Joined: Fri Jun 02, 2017 10:43 am

Re: NX-OSv9k cannot be loaded in eve-ng

Post by snurfit » Thu Jun 08, 2017 9:56 am

No-one else facing this issue at all?
Top
Uldis (UD)
Posts: 5190
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:
Contact Uldis (UD)

Re: NX-OSv9k cannot be loaded in eve-ng

Post by Uldis (UD) » Thu Jun 08, 2017 7:32 pm

NX9K works gret if you have sufficient CPU and RAM.
Min requirements for single NX9K is x2CPU and 8G RAM.

Laptop version i7 can run one NX9K only..because of only 4 treads on CPU is available.
Top
snurfit
Posts: 13
Joined: Fri Jun 02, 2017 10:43 am

Re: NX-OSv9k cannot be loaded in eve-ng

Post by snurfit » Sun Jun 11, 2017 7:56 am

This is on a server though. EVE-NG is running on top of ESXi, with 24Gig of memory for the EVE-NG VM.

I have tried multiple combinations of memory for the NX-OSv9K node, including everything from 2 CPU's and 8Gig of memory to 4 CPU's and 16G of memory. It still stalls with the following: (endless loop):

Code: Select all

3h
3h
3h
3h
3h
3h
3h
Boot Failed. EFI Floppy
Boot Failed. EFI Floppy 1
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,1)/EndEntire
Total memory is 0xa0000 
Total memory is 0xbee3c000 
Sysconf checksum failed. Using default values
WARNING:  No BIOS Info found 
Sysconf checksum failed. Using default values
serial --speed=115200 --word=8 --stop=1 --parity=no
 
success 
Sysconf checksum failed. Using default values
Strlen bootflash: is 10 
Device bootflash: is Drive 0x80 Partition 3 
Strlen bootflash: is 10 
Device bootflash: is Drive 0x81 Partition 3 
ATE0Q1&D2&C1S0=1
Trying to read config file /boot/grub/menu.lst.local from (hd0,4) 
 Filesystem type is ext2fs, partition type 0x83
Number of devices detected by BIOS is 2
Failed. Trying to read config file from (hd0,5) 
 Filesystem type is ext2fs, partition type 0x83
Number of devices detected by BIOS is 2
3h
3h
I have also tried on a different ESXi host, but with the same result. Running the newest version of EVE-NG (updated with APT).

Thanks!
Top
Jay-T
Posts: 1
Joined: Sun Jun 11, 2017 8:34 am

Re: NX-OSv9k cannot be loaded in eve-ng

Post by Jay-T » Sun Jun 11, 2017 9:18 am

Hi fellows. Have the same issue with N9K. I'm also able to launch nxosv9k 7.0.3.I6.1 in ESXi. Worked around with option efi.serialconsole.enabled = "TRUE" in .vmx file of VM to see normal boot process and noticed that after "Number of devices detected by BIOS is 1" it is trying to boot image. I suppose that in EVE it stucks in "loader >" and cannot to boot image properly.
This is ESXI VM loading log:

Code: Select all

Attempting to start up from:
 > EFI VMware Virtual IDE Hard Drive (IDE 0:0)...

/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,1,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(1,7)/ATAPI(0,1,0)/EndEntire
Total memory is 0x0 
Total memory is 0xbfb26000 
Sysconf checksum failed. Using default values
WARNING:  No BIOS Info found 
Sysconf checksum failed. Using default values
serial --speed=115200 --word=8 --stop=1 --parity=no
 
success 
Sysconf checksum failed. Using default values
Strlen bootflash: is 10 
Device bootflash: is Drive 0x80 Partition 3 
ATE0Q1&D2&C1S0=1
Trying to read config file /boot/grub/menu.lst.local from (hd0,4) 
 Filesystem type is ext2fs, partition type 0x83
Number of devices detected by BIOS is 1

Autobooting bootflash:/nxos.7.0.3.I6.1.bin ...
Booting bootflash:/nxos.7.0.3.I6.1.bin 
Trying diskboot 
dev_str: bootflash: partition_str: 3 filename_str /nxos.7.0.3.I6.1.bin 
command = root (hd0,3)
 Filesystem type is ext2fs, partition type 0x83
Formed cmdline  console=ttyS0,115200n8nn  card_index=21099 dummy_sprom ksimg=nxos.7.0.3.I6.1.bin  loader_ver="5.00.9"  quiet debug  
Formed cmdline  console=ttyS0,115200n8nn  card_index=21099 dummy_sprom ksimg=nxos.7.0.3.I6.1.bin  loader_ver="5.00.9"  quiet debug  ksimg=bootflash  card_index=21099 dummy_sprom  
Booting kickstart image: bootflash::3:/nxos.7.0.3.I6.1.bin....
Number of devices detected by BIOS is 1
NBI header
magic: 1b031336, len: 54, location: 94400000 (bx=0, ds=9440), exec addr: 92800000 16 16 

segment header
length: 4, vendor: 11 flags: 0, loadaddr: 94000, image len: 200, memory length: 400
Reading data for kernel param. Len 512
Cmd line:  console=ttyS0,115200n8nn  card_index=21099 dummy_sprom ksimg=nxos.7.0.3.I6.1.bin  loader_ver="5.00.9"  quiet debug  ksimg=bootflash  card_index=21099 dummy_sprom rw root=/dev/ram0 rdbase=0x8000000 ip=off ramdisk_size=131072 panic=5 quiet coredump_filter=0xb mtdparts=physmap-flash.0:256k(RR_LOG),512k(mtdoops),16M(plog),16M(trace) intel_idle.max_cstate=2 pcie_ports=native nopat slub_debug=- cpuidle.off=1 

segment header
length: 4, vendor: 14 flags: 0, loadaddr: 100000, image len: 52dc00, memory length: 800000
Loading kernel length 5430272 
file_size 5430272 real_size 4502 prot_kernel_size 5414400 setupsects 30 
x86_64/loader/linux.c:102: real_size = 2000, prot_size = 52a000, mmap_size = 540
x86_64/loader/linux.c:133: physical_start = 1000, physical_end = a0000
x86_64/loader/linux.c:146: trying to allocate 2 pages at 9e000
Trying to allocate 1322 pages for VMLINUZ
Allocated prot_mode_mem 0xbcd48000 real_mode_mem 0x0009e000
[Linux-EFI, setup=0x1196, size=0x529e00]

segment header
length: 14, vendor: 15 flags: 0, loadaddr: a2e000, image len: 2cf8e000, memory length: 10000000
Loading intird 754507776 
x86_64/loader/linux.c:573: initrd_pages: 184206
x86_64/loader/linux.c:584: addr_min: 0x0 addr_max: 0x7ffff000 mmap_size: 1344
x86_64/loader/linux.c:603: desc = {type=7,ps=0x1000,vs=0x0,sz=157,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x100000,vs=0x0,sz=522749,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x80000000,vs=0x0,sz=249160,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0xbd2ee000,vs=0x0,sz=71,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0xbd352000,vs=0x0,sz=9,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x100000000,vs=0x0,sz=1310720,attr=15}
Top
ee_cskaa
Posts: 13
Joined: Fri May 26, 2017 10:42 am

Re: NX-OSv9k cannot be loaded in eve-ng

Post by ee_cskaa » Mon Jun 12, 2017 1:36 am

Seems many guys have same problem, but no solution yet. I just keeping the two nx9k running after first success boot. If I reboot the n9k again, it still keep endless loop.
Top
Uldis (UD)
Posts: 5190
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:
Contact Uldis (UD)

Re: NX-OSv9k cannot be loaded in eve-ng

Post by Uldis (UD) » Mon Jun 12, 2017 6:49 am

ee_cskaa wrote: ↑
Mon Jun 12, 2017 1:36 am
 Seems many guys have same problem, but no solution yet. I just keeping the two nx9k running after first success boot. If I reboot the n9k again, it still keep endless loop.
But did you set boot nexus from its NXOS after first time boot success?
read How To
Top
ee_cskaa
Posts: 13
Joined: Fri May 26, 2017 10:42 am

Re: NX-OSv9k cannot be loaded in eve-ng

Post by ee_cskaa » Mon Jun 12, 2017 2:18 pm

Uldis (UD) wrote: ↑
Mon Jun 12, 2017 6:49 am
ee_cskaa wrote: ↑
Mon Jun 12, 2017 1:36 am
 Seems many guys have same problem, but no solution yet. I just keeping the two nx9k running after first success boot. If I reboot the n9k again, it still keep endless loop.
But did you set boot nexus from its NXOS after first time boot success?
read How To
Yes, I put the command below on the start up config of N9K, and then reboot. It still keep loop after loading the image...

boot nxos bootflash:/nxos.7.0.3.I6.1.bin

Boot Failed. EFI Floppy
Boot Failed. EFI Floppy 1
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,1)/EndEntire
Total memory is 0xa0000
Total memory is 0xbee3c000
Sysconf checksum failed. Using default values
WARNING: No BIOS Info found
Sysconf checksum failed. Using default values
serial --speed=115200 --word=8 --stop=1 --parity=no

success
Sysconf checksum failed. Using default values
Strlen bootflash: is 10
Device bootflash: is Drive 0x80 Partition 3
Strlen bootflash: is 10
Device bootflash: is Drive 0x81 Partition 3
ATE0Q1&D2&C1S0=1
Trying to read config file /boot/grub/menu.lst.local from (hd0,4)
Filesystem type is ext2fs, partition type 0x83
Number of devices detected by BIOS is 2

Autobooting bootflash:/nxos.7.0.3.I6.1.bin ...
Booting bootflash:/nxos.7.0.3.I6.1.bin
Trying diskboot
dev_str: bootflash: partition_str: 3 filename_str /nxos.7.0.3.I6.1.bin
command = root (hd0,3)
Filesystem type is ext2fs, partition type 0x83
Formed cmdline console=ttyS0,115200n8nn card_index=21099 dummy_sprom ksimg=nxos.7.0.3.I6.1.bin loader_ver="5.00.9" quiet debug
Formed cmdline console=ttyS0,115200n8nn card_index=21099 dummy_sprom ksimg=nxos.7.0.3.I6.1.bin loader_ver="5.00.9" quiet debug ksimg=bootflash card_index=21099 dummy_sprom
Booting kickstart image: bootflash::3:/nxos.7.0.3.I6.1.bin....
Number of devices detected by BIOS is 2
NBI header
magic: 1b031336, len: 54, location: 94400000 (bx=0, ds=9440), exec addr: 92800000 16 16

segment header
length: 4, vendor: 11 flags: 0, loadaddr: 94000, image len: 200, memory length: 400
Reading data for kernel param. Len 512
Cmd line: console=ttyS0,115200n8nn card_index=21099 dummy_sprom ksimg=nxos.7.0.3.I6.1.bin loader_ver="5.00.9" quiet debug ksimg=bootflash card_index=21099 dummy_sprom rw root=/dev/ram0 rdbase=0x8000000 ip=off ramdisk_size=131072 panic=5 quiet coredump_filter=0xb mtdparts=physmap-flash.0:256k(RR_LOG),512k(mtdoops),16M(plog),16M(trace) intel_idle.max_cstate=2 pcie_ports=native nopat slub_debug=- cpuidle.off=1

segment header
length: 4, vendor: 14 flags: 0, loadaddr: 100000, image len: 52dc00, memory length: 800000
Loading kernel length 5430272
file_size 5430272 real_size 4502 prot_kernel_size 5414400 setupsects 30
x86_64/loader/linux.c:102: real_size = 2000, prot_size = 52a000, mmap_size = 510
x86_64/loader/linux.c:133: physical_start = 0, physical_end = a0000
x86_64/loader/linux.c:146: trying to allocate 2 pages at 9e000
Trying to allocate 1322 pages for VMLINUZ
Allocated prot_mode_mem 0xbcda4000 real_mode_mem 0x0009e000
[Linux-EFI, setup=0x1196, size=0x529e00]

segment header
length: 14, vendor: 15 flags: 0, loadaddr: a2e000, image len: 2cf8e000, memory length: 10000000
Loading intird 754507776
x86_64/loader/linux.c:573: initrd_pages: 184206
x86_64/loader/linux.c:584: addr_min: 0x0 addr_max: 0x7ffff000 mmap_size: 1440
x86_64/loader/linux.c:603: desc = {type=7,ps=0x0,vs=0x0,sz=158,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x100000,vs=0x0,sz=1824,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x1000000,vs=0x0,sz=518909,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x80000000,vs=0x0,sz=245760,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0xbc020000,vs=0x0,sz=3460,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0xbd34a000,vs=0x0,sz=117,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0xbd3c2000,vs=0x0,sz=1,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x100000000,vs=0x0,sz=1835008,attr=15}

Loading [719M/719M]
3h
3h
3h
3h
3h
3h
3h
Boot Failed. EFI Floppy
Boot Failed. EFI Floppy 1
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,1)/EndEntire
Total memory is 0xa0000
Total memory is 0xbee3c000
Sysconf checksum failed. Using default values
WARNING: No BIOS Info found
Sysconf checksum failed. Using default values
serial --speed=115200 --word=8 --stop=1 --parity=no

success
Sysconf checksum failed. Using default values
Strlen bootflash: is 10
Device bootflash: is Drive 0x80 Partition 3
Strlen bootflash: is 10
Device bootflash: is Drive 0x81 Partition 3
ATE0Q1&D2&C1S0=1
Trying to read config file /boot/grub/menu.lst.local from (hd0,4)
Filesystem type is ext2fs, partition type 0x83
Number of devices detected by BIOS is 2

Autobooting bootflash:/nxos.7.0.3.I6.1.bin ...
Booting bootflash:/nxos.7.0.3.I6.1.bin
Trying diskboot
dev_str: bootflash: partition_str: 3 filename_str /nxos.7.0.3.I6.1.bin
command = root (hd0,3)
Filesystem type is ext2fs, partition type 0x83
Formed cmdline console=ttyS0,115200n8nn card_index=21099 dummy_sprom ksimg=nxos.7.0.3.I6.1.bin loader_ver="5.00.9" quiet debug
Formed cmdline console=ttyS0,115200n8nn card_index=21099 dummy_sprom ksimg=nxos.7.0.3.I6.1.bin loader_ver="5.00.9" quiet debug ksimg=bootflash card_index=21099 dummy_sprom
Booting kickstart image: bootflash::3:/nxos.7.0.3.I6.1.bin....
Number of devices detected by BIOS is 2
NBI header
magic: 1b031336, len: 54, location: 94400000 (bx=0, ds=9440), exec addr: 92800000 16 16

segment header
length: 4, vendor: 11 flags: 0, loadaddr: 94000, image len: 200, memory length: 400
Reading data for kernel param. Len 512
Cmd line: console=ttyS0,115200n8nn card_index=21099 dummy_sprom ksimg=nxos.7.0.3.I6.1.bin loader_ver="5.00.9" quiet debug ksimg=bootflash card_index=21099 dummy_sprom rw root=/dev/ram0 rdbase=0x8000000 ip=off ramdisk_size=131072 panic=5 quiet coredump_filter=0xb mtdparts=physmap-flash.0:256k(RR_LOG),512k(mtdoops),16M(plog),16M(trace) intel_idle.max_cstate=2 pcie_ports=native nopat slub_debug=- cpuidle.off=1

segment header
length: 4, vendor: 14 flags: 0, loadaddr: 100000, image len: 52dc00, memory length: 800000
Loading kernel length 5430272
file_size 5430272 real_size 4502 prot_kernel_size 5414400 setupsects 30
x86_64/loader/linux.c:102: real_size = 2000, prot_size = 52a000, mmap_size = 510
x86_64/loader/linux.c:133: physical_start = 0, physical_end = a0000
x86_64/loader/linux.c:146: trying to allocate 2 pages at 9e000
Trying to allocate 1322 pages for VMLINUZ
Allocated prot_mode_mem 0xbcd95000 real_mode_mem 0x0009e000
[Linux-EFI, setup=0x1196, size=0x529e00]

segment header
length: 14, vendor: 15 flags: 0, loadaddr: a2e000, image len: 2cf8e000, memory length: 10000000
Loading intird 754507776
x86_64/loader/linux.c:573: initrd_pages: 184206
x86_64/loader/linux.c:584: addr_min: 0x0 addr_max: 0x7ffff000 mmap_size: 1440
x86_64/loader/linux.c:603: desc = {type=7,ps=0x0,vs=0x0,sz=158,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x100000,vs=0x0,sz=1824,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x1000000,vs=0x0,sz=518909,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x80000000,vs=0x0,sz=245760,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0xbc020000,vs=0x0,sz=3445,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0xbd33b000,vs=0x0,sz=117,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0xbd3b3000,vs=0x0,sz=1,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x100000000,vs=0x0,sz=1835008,attr=15}

Loading [416M/719M]
Top
Uldis (UD)
Posts: 5190
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:
Contact Uldis (UD)

Re: NX-OSv9k cannot be loaded in eve-ng

Post by Uldis (UD) » Mon Jun 12, 2017 3:23 pm

if you have only:
EVE-NG in ESXi ver 6.5 (2 vcpu and 64G RAM)

then Nexus will not work on such config.
Need more vCPU for VM to give.

This looping happens if your CPU simply has no power to boot NXOS...
Thats it
Top
ee_cskaa
Posts: 13
Joined: Fri May 26, 2017 10:42 am

Re: NX-OSv9k cannot be loaded in eve-ng

Post by ee_cskaa » Tue Jun 13, 2017 10:36 am

Uldis (UD) wrote: ↑
Mon Jun 12, 2017 3:23 pm
 if you have only:
EVE-NG in ESXi ver 6.5 (2 vcpu and 64G RAM)

then Nexus will not work on such config.
Need more vCPU for VM to give.

This looping happens if your CPU simply has no power to boot NXOS...
Thats it
I assigned 8 vcpu (4*2) and 64G RAM to EVE-NG. Not enough?
Top
Locked

Return to “EVE-NG Help-Desk”