Junos OS

 View Only
last person joined: 2 days ago 

Ask questions and share experiences about Junos OS.
Expand all | Collapse all

vJunosEvolved 24.2R1-S2.4 does not boot in EVENG

  • 1.  vJunosEvolved 24.2R1-S2.4 does not boot in EVENG

    Posted 15 days ago

    Hello

     anyone had any luck with the latest vEVO 24.2R1-S2.4 image ?

    I tried in my eveng  community (bare metal) and im unable to boot it:

    ====================

    Failed to open /dev/null for OFD lock probing: No such file or directory
    SeaBIOS (version rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org)
    Machine UUID fe6bbdfa-94e3-4f16-88fb-8633fc2c1db0
    iPXE (http://ipxe.org) 00:03.0 CA00 PCI2.10 PnP PMM+BFF8EE50+BFEEEE50 CA00
    iPXE (http://ipxe.org) 00:04.0 CB00 PCI2.10 PnP PMM BFF8EE50 BFEEEE50 CB00
    iPXE (http://ipxe.org) 00:05.0 CC00 PCI2.10 PnP PMM BFF8EE50 BFEEEE50 CC00
    iPXE (http://ipxe.org) 00:06.0 CD00 PCI2.10 PnP PMM BFF8EE50 BFEEEE50 CD00
    iPXE (http://ipxe.org) 00:07.0 CE00 PCI2.10 PnP PMM BFF8EE50 BFEEEE50 CE00
    iPXE (http://ipxe.org) 00:08.0 CF00 PCI2.10 PnP PMM BFF8EE50 BFEEEE50 CF00
    iPXE (http://ipxe.org) 00:09.0 D000 PCI2.10 PnP PMM BFF8EE50 BFEEEE50 D000
    iPXE (http://ipxe.org) 00:0A.0 D100 PCI2.10 PnP PMM BFF8EE50 BFEEEE50 D100
    iPXE (http://ipxe.org) 00:0B.0 D200 PCI2.10 PnP PMM BFF8EE50 BFEEEE50 D200
    iPXE (http://ipxe.org) 00:0C.0 D300 PCI2.10 PnP PMM BFF8EE50 BFEEEE50 D300
    iPXE (http://ipxe.org) 00:0D.0 D400 PCI2.10 PnP PMM BFF8EE50 BFEEEE50 D400
    iPXE (http://ipxe.org) 00:0E.0 D500 PCI2.10 PnP PMM BFF8EE50 BFEEEE50 D500                                                                               
    iPXE (http://ipxe.org) 00:0F.0 D600 PCI2.10 PnP PMM BFF8EE50 BFEEEE50 D600
    Booting from Hard Disk...

    ====================

    I 've checked MD5 and is ok. I have also tried with some variations in the vjunosevo.yml (include svm=on)  but again without any luck.

    I have no problems with previous releases (23.x)



  • 2.  RE: vJunosEvolved 24.2R1-S2.4 does not boot in EVENG

    Posted 15 days ago

    I think there is no bootloader/OS or something similar as  im unable to boot even with qemu:

    ===================

    root@eveng-bms:/opt/unetlab/addons/qemu/vjunosevo-24.2R1-S2.4#qemu-img check virtioa.qcow2 
    No errors were found on the image.
    28338/655360 = 4.32% allocated, 16.32% fragmented, 0.00% compressed clusters
    Image end offset: 1859715072

    root@eveng-bms:/opt/unetlab/addons/qemu/vjunosevo-24.2R1-S2.4# qemu-img info virtioa.qcow2
    image: virtioa.qcow2
    file format: qcow2
    virtual size: 40 GiB (42949672960 bytes)
    disk size: 1.73 GiB
    cluster_size: 65536
    Format specific information:
        compat: 1.1
        compression type: zlib
        lazy refcounts: false
        refcount bits: 16
        corrupt: false
        extended l2: false

    root@eveng-bms:/opt/unetlab/addons/qemu/vjunosevo-24.2R1-S2.4# qemu-system-x86_64 -nographic -drive file=virtioa.qcow2,format=qcow2 -boot order=c,menu=on
    SeaBIOS (version 1.15.0-1)
    iPXE (https://ipxe.org) 00:03.0 CA00 PCI2.10 PnP PMM+07F8B4A0+07ECB4A0 CA00
                                                                                   
    Press ESC for boot menu.
     
    Select boot device:
     
    1. ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (40960 MiBytes)
    2. Legacy option rom
    3. Floppy [drive A]
    4. DVD/CD [ata1-0: QEMU DVD-ROM ATAPI-4 DVD/CD]
    5. iPXE (PCI 00:03.0)
     
    Booting from Hard Disk...

    ===================

    While with an older image (23.x)  grub bootloader is there....

    =================

    root@eveng-bms:/opt/unetlab/addons/qemu/vjunosevo-23.2R2.21# qemu-system-x86_64 -nographic -drive file=virtioa.qcow2,format=qcow2 -boot order=c,menu=on
    SeaBIOS (version 1.15.0-1)
     
    iPXE (https://ipxe.org) 00:03.0 CA00 PCI2.10 PnP PMM+07F8B4A0+07ECB4A0 CA00
                                                                                   
     
    Press ESC for boot menu.
     
    Select boot device:
     
    1. ata0-0: QEMU HARDDISK ATA-7 Hard-Disk (40960 MiBytes)
    2. Legacy option rom
    3. Floppy [drive A]
    4. DVD/CD [ata1-0: QEMU DVD-ROM ATAPI-4 DVD/CD]
    5. iPXE (PCI 00:03.0)
     
    Booting from Hard Disk...
    GRUB loading.
    Welcome to GRUB!
     
    Grub Cmdpath is (hd0)
    Grub Prefix is (hd0,msdos1)/grub
    Primary /soft - hd0,msdos2
    Primary /data - hd0,msdos5
    Primary /boot - hd0,msdos1
    hasPrimary is ON
    error: no such device: EvoDataS.
    Could not find snaphot DATA label EvoDataS
    Bootstrapped from primary device
    Booting from PRIMARY
     
                                 GNU GRUB  version 2.04

    ...

    ...

    =================




  • 3.  RE: vJunosEvolved 24.2R1-S2.4 does not boot in EVENG

    Posted 15 days ago

    Hi,

    No issue using PNETLAB.




  • 4.  RE: vJunosEvolved 24.2R1-S2.4 does not boot in EVENG

    Posted 14 days ago

    Hello kronicklez,

     no problems with any 23.x images as i said in the beginning. 

    The problem is with the latest 24.2R1-S2.4 .




  • 5.  RE: vJunosEvolved 24.2R1-S2.4 does not boot in EVENG

    Posted 14 days ago

    Hi,

    Sorry....i miss look....let me download and try new version.

    Thanks




  • 6.  RE: vJunosEvolved 24.2R1-S2.4 does not boot in EVENG

    Posted 14 days ago
    Edited by ios46 14 days ago
    I have used qemu to load a linux live CD iso and mount the qcow2 image that corresponds to 24.4 version. If i do an lsblk in this linux live i can see all the partitions of the qcow2 image.

    The difference is that in 24.4 release  it seems that makes use of UEFI/GPT  with a vfat partion for grub options, while using the same method to load and mount older 23.x qcow2 images (23.2R2 and 23.4R2) shows that MBR method with ext4 is used for booting. 




  • 7.  RE: vJunosEvolved 24.2R1-S2.4 does not boot in EVENG

    Posted 14 days ago

    Hi bro,

    I just test and on my pnetlab nothing appear in the console when use latest vEVO. May be the qemu option need to be change.

    Thanks




  • 8.  RE: vJunosEvolved 24.2R1-S2.4 does not boot in EVENG

    Posted 14 days ago

    Add " -bios /usr/share/qemu/OVMF.fd " after the line -smbios type=3,manufacturer=Bochs in the template's qemu_options: line.




  • 9.  RE: vJunosEvolved 24.2R1-S2.4 does not boot in EVENG

    Posted 14 days ago

    I tried it but still no luck.

    ====================================================================

    qemu_options: -machine type=pc,accel=kvm -serial mon:stdio -nographic -smbios type=0,vendor=Bochs,version=Bochs -smbios type=3,manufacturer=Bochs -bios /usr/share/qemu/OVMF.fd -smbios type=1,manufacturer=Bochs,product=Bochs,serial=chassis_no=0:slot=0:type=1:assembly_id=0x0D20:platform=251:master=0:channelized=no -cpu qemu64

    ====================================================================




  • 10.  RE: vJunosEvolved 24.2R1-S2.4 does not boot in EVENG

    Posted 14 days ago

    try this

    ---
    type: qemu
    description: Juniper vEVO Router 24.x
    name: vEVO
    cpulimit: 4
    icon: Juniper-2D-Router-S.svg
    cpu: 4
    ram: 8192
    shutdown: 1
    eth_name:
    - re0:mgmt-0
    eth_format: et-0/0/{0}
    ethernet: 13
    console: telnet
    pci_mode: multifunction
    qemu_arch: x86_64
    qemu_version: 5.2.0
    qemu_nic: virtio-net-pci
    qemu_options: -machine type=pc,accel=kvm -serial mon:stdio -nographic -smbios type=0,vendor=Bochs,version=Bochs -smbios type=3,manufacturer=Bochs -bios /usr/share/qemu/OVMF.fd -smbios type=1,manufacturer=Bochs,product=Bochs,serial=chassis_no=0:slot=0:type=1:assembly_id=0x0D20:platform=251:master=0:channelized=no -cpu IvyBridge,ibpb=on,md-clear=on,spec-ctrl=on,ssbd=on,vmx=on
    ...




  • 11.  RE: vJunosEvolved 24.2R1-S2.4 does not boot in EVENG

    Posted 14 days ago
    Edited by ios46 14 days ago

    Thank you SongYue, but it does not work for me again, even though i switched option vmx=on to svm=on as my CPU is AMD.

    I tried also with -cpu host , EPYC, qemu64 without luck either. The rest of the options you are appending, following the -cpu option are related with vulnerabilities (spectre eg) and i don't think should have any impact, except for vmx/svm which are extensions for KVM virtualization. In any case, no luck with my AMD Ryzen 9 3900XT machine.




  • 12.  RE: vJunosEvolved 24.2R1-S2.4 does not boot in EVENG

    Posted 14 days ago



  • 13.  RE: vJunosEvolved 24.2R1-S2.4 does not boot in EVENG

    Posted 12 days ago

    Dear all

     i was looking on gitlab in the templates section and was looking for images that make use of EFI, and bumped into the xrv8102. I have alos looked into other qemu options and their meaning and i 've managed to boot via qemu:

    ======================================

    root@eveng-bms:/opt/unetlab/addons/qemu/vjunosevo-24.2R1-S2.4# qemu-system-x86_64 -enable-kvm -m 8G -cpu host \
    >   -drive file=virtioa.qcow2,if=virtio,format=qcow2 \
    >   -drive if=pflash,format=raw,readonly=on,file=/usr/share/OVMF/OVMF_CODE.fd \
    >   -nographic -serial mon:stdio -boot menu=on \
    >   -smbios type=0,vendor=Bochs,version=Bochs\
    >   -smbios type=3,manufacturer=Bochs\
    >   -smbios type=1,manufacturer=Bochs,product=Bochs,serial=chassis_no=0:slot=0:type=1:assembly_id=0x0D20:platform=251:master=0:channelized=no\
    >   -machine pc-q35-5.2,accel=kvm \
    >   -smp 4
    3h
    BdsDxe: loading Boot0007 "EFI Internal Shell" from Fv(7CB8BDC9-F8EB-4F34-AAEA-3EE4AF6516A1)/FvFile(7C04A583-9E3E-4F1C-AD65-E05268D0B4D1)
    BdsDxe: starting Boot0007 "EFI Internal Shell" from Fv(7CB8BDC9-F8EB-4F34-AAEA-3EE4AF6516A1)/FvFile(7C04A583-9E3E-4F1C-AD65-E05268D0B4D1)
    UEFI Interactive Shell v2.2
    EDK II
    UEFI v2.70 (EDK II, 0x00010000)
    Mapping table
          FS0: Alias(s):HD1b:;BLK2:
              PciRoot(0x0)/Pci(0x3,0x0)/HD(1,GPT,BB9880FE-E5E9-2344-9CC4-56E846B2E596,0x800,0x63800)
         BLK1: Alias(s):
              PciRoot(0x0)/Pci(0x3,0x0)
         BLK3: Alias(s):
              PciRoot(0x0)/Pci(0x3,0x0)/HD(2,GPT,7115B16D-ECE9-9349-9141-86A9767CF53B,0x64000,0x2000000)
         BLK4: Alias(s):
              PciRoot(0x0)/Pci(0x3,0x0)/HD(3,GPT,53926DD8-0B0F-9F4C-A62B-7AB3DE477EBA,0x2064000,0x800000)
         BLK5: Alias(s):
              PciRoot(0x0)/Pci(0x3,0x0)/HD(5,GPT,766D062F-BF5E-3C4E-B6C9-91D6F27ACD42,0x2864000,0x600000)
         BLK6: Alias(s):
              PciRoot(0x0)/Pci(0x3,0x0)/HD(6,GPT,51B7AB48-FE1F-E744-8C45-75823442FA68,0x2E64000,0x200000)
         BLK7: Alias(s):
              PciRoot(0x0)/Pci(0x3,0x0)/HD(7,GPT,A88469AA-1B3A-F54F-8129-B6249EDA297B,0x3064000,0x1F9BFDF)
         BLK0: Alias(s):
              PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x2,0xFFFF,0x0)
     
     
     
     
    FS0:\> \EFI\BOOT\BOOTX64.EFI p startup.nsh or any other key to continue.
    Welcome to GRUB!
     
    error: TPM chip is not working.
    Secure Grub2 Diskboot
    error: TPM chip is not working.
    error: TPM chip is not working.
    Grub Cmdpath is (hd0,gpt1)/EFI/BOOT
    Grub Prefix is (memdisk)/boot/grub
    Primary /soft - hd0,gpt2
    Primary /data - hd0,gpt5
    Primary /boot - hd0,gpt1
    hasPrimary is ON
    error: no such device: EvoSoftS.
    Could not find snaphot SOFT label EvoSoft
    Bootstrapped from primary device
    Booting from PRIMARY
     
                   GNU GRUB  version 2.02~juniper/rel_v2-79-gb4dc0a4~
     
     ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
     ³*Primary junos-evo-install-ptx-fixed-x86-64-24.2R1-S2.4-EVOI20241213052440->³ 
     ³ Primary [Recover password]                                                 ³
     ³ Primary [Debug System]                                                     ³
     ³                                                                            ³
     ³                                                                            ³
     ³                                                                            ³
     ³                                                                            ³
     ³                                                                            ³
     ³                                                                            ³
     ³                                                                            ³
     ³                                                                            ³
     ³                                                                            ³ 
     ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
     
          Use the ^ and v keys to select which entry is highlighted.          
          Press enter to boot the selected OS, `e' to edit the commands       
          before booting or `c' for a command-line. ESC to return previous    
          menu.                                                               
                                                                                   
                                                                                   
    Disk boot ...
    IMA(1) URO(1) ISSU(1) BEACONS(1) BT(RELEASE)
    Loading kernel ...ok.
    Loading initrd ...ok.
    Booting ...
    error: no suitable video mode found.
    Booting in blind mode
    Watchdog set to 500 seconds
    [    3.310644] watchdog: watchdog0: watchdog did not stop!
    TPM2.0 device node not found. Exiting !!!
    No secondary disk found. Exiting ...
    Unlock encrypted filesystem automatically if needed ...
    TPM2.0 device node not found. Exiting !!!
    Device /dev/vda :
    PCR extend to prevent revealing encryption key ...
    TPM2.0 device node not found. Exiting !!!
      Extending 0000000000000000000000000000000000000000000000000000000000000000 to PCR sha256:11
    TPM2.0 device node not found. Exiting !!!
    Checking disk labels ...
    Installing/Mounting on disk /dev/vda mapped to device virtio0
    Coming back from an uncontrolled reboot, will recreate /data!
    Processing /dev/vda2 for mount on /soft ...[checking]..[ok 1]..[mounting]..done
    Processing /dev/vda7 for mount on /var ...[checking]..[ok 1]..[mounting]..done
    Processing /dev/vda5 for mount on /data ...[checking]..[strong check]..[saving]..[rebuilding]..[mounting]..[restoring]..done
    Processing /dev/vda6 for mount on /data/config ...[checking]..[ok 1]..[mounting]..done
    Processing /data/var/opt_fs for mount on /data/var/external ...[checking]..[ok 1]..[mounting]..done
    Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
    no label, UUID=151e36d3-8bd2-4132-b9df-ba24e89e62b2
    Processing /dev/vda1 for mount on /boot ...[checking]..[ok 1]..[mounting]..done
    Done with local filesystems setup.
    NOTE: Now 9 keys in keyring: %keyring:.ima
    NOTE: Now keyring is empty %keyring:ima_ext
    Postinstall in progress...App manifest not defined in capdb. Skip customizing app policies for this platform ()
    done
    Installing kexec kernel...done
    Warning - Empty root password found
    warning: No configured root password
     
    Juniper Linux Distribution 4.0.14 re0 ttyS0
     
    re0 login: root
    --- JUNOS 24.2R1-S2.4-EVO Linux (none) 5.15.76-yocto-standard-juniper-02086-gc538fa48cd57 #1 SMP PREEMPT Fri May 31 13:38:59 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
    [vrf:none] root@re0:~# 

    ====================================== 

    Of course it needs manual intervention in the beginning in order to boot (FS0: then \EFI\BOOT\BOOTX64.EFI). 

    I ll try to pass them in an EVENG instance and see how it goes as i don't want to mess with overwriting the existing template or create a new one as i believe will complicate the creation of other (eg older instances with a previous release).