Junosphere
This forum is intended for all discussions and questions relating to Junosphere. It is a branch-off from the former "Junos and Junosphere" forum, which is now titled "Junos".
Highlighted
Junosphere

Device in boot loop

‎11-11-2015 11:20 AM

Hi All  i have a weird one , i have a device of a exported topology and one of the devices is in a strange loop , i have tried to delete the topology and import it again from the a known good file , but it has the same results .... 

 

what now ? 

 

 

Consoles: serial port
BIOS drive A: is disk0
BIOS drive C: is disk1
BIOS 637kB/1571828kB available memory

FreeBSD/i386 bootstrap loader, Revision 1.1
(builder@junos-core01.juniper.net, Mon Aug  8 04:58:35 UTC 2011)
Loading /boot/defaults/loader.conf
/kernel text=0x79701c     smbios_init: Bad SMBIOS data checksum
Consoles: serial port
BIOS drive A: is disk0
BIOS drive C: is disk1
BIOS 637kB/1571828kB available memory

FreeBSD/i386 bootstrap loader, Revision 1.1
(builder@junos-core01.juniper.net, Mon Aug  8 04:58:35 UTC 2011)
Loading /boot/defaults/loader.conf
/kernel text=0x79701c     smbios_init: Bad SMBIOS data checksum
Consoles: serial port
BIOS drive A: is disk0
BIOS drive C: is disk1
BIOS 637kB/1571828kB available memory

FreeBSD/i386 bootstrap loader, Revision 1.1
(builder@junos-core01.juniper.net, Mon Aug  8 04:58:35 UTC 2011)
Loading /boot/defaults/loader.conf
/kernel text=0x79701c     smbios_init: Bad SMBIOS data checksum
Consoles: serial port
BIOS drive A: is disk0
BIOS drive C: is disk1
BIOS 637kB/1571828kB available memory

FreeBSD/i386 bootstrap loader, Revision 1.1
(builder@junos-core01.juniper.net, Mon Aug  8 04:58:35 UTC 2011)
Loading /boot/defaults/loader.conf
/kernel text=0x79701c     smbios_init: Bad SMBIOS data checksum
Please Mark My Solution Accepted if it Helped, Kudos are Appreciated Too
1 REPLY
Junosphere
Solution
Accepted by topic author IK
‎11-18-2015 11:59 AM

Re: Device in boot loop

‎11-18-2015 11:59 AM

the root cause to this is, the older images prior to version 14.1 were not built to run in the high order memory on a server. When a random device gets spun/put on the host high order memory, during the boot strap process, it referenced bad memory pages. As such, the guest OS, did not understand what it is because the BIOS information was incorrect. Furthermore, when it tried to load config file, it pulls data from 'bad' memory pages. That is the reason why some of the VMs failed.

 

Version 14.1 apparently addressed this issue. Functionally, 14.1 is the same as the older versions. 14.1 has more bug fixes. The only reason why it is considered as experimental is because this is the last VJX version that will support only for critical defects. Older versions of VJX were no longer supported

Please Mark My Solution Accepted if it Helped, Kudos are Appreciated Too