This article explains why the Junos Disk name shows a normal package name rather than a VMHOST package name after upgrading a VMHOST routing engine using a VMHOST package.

Upon upgrading a VMHOST routing engine using a designated VMHOST package, users may notice a discrepancy in the >show vmhost version output.

Despite successfully upgrading the routing engine with a VMHOST package like junos-vmhost-install-mx-x86-64-20.4R3-S3.4.tgz, Junos Disk section shows a conventional Junos package name, such as junos-install-mx-x86-64-20.4R3-S3.4. This apparent mismatch between the expected VMHOST package name and the displayed Junos Disk package name can raise questions about the correctness of the upgrade process.

 

> show vmhost version 
Current root details,           Device sda, Label: jrootb_P, Partition: sda4
Current boot disk: Primary
Current root set: b
UEFI    Version: CBEP_P_SUM1_00.15.01

Primary Disk, Upgrade Time: Fri Dec  1 17:09:54 IST 2023

Version: set p
VMHost Version: 3.1917
VMHost Root: vmhost-x86_64-18.4R3-S7-20210107_0140_builder
VMHost Core: vmhost-core-x86-64-18.4R3-S9.2
kernel: 3.10.100-ovp-rt110-WR6.0.0.38_preempt-rt
Junos Disk: junos-install-mx-x86-64-18.4R3-S9.2

Version: set b
VMHost Version: 5.2329
VMHost Root: vmhost-x86_64-20.4R3-S2-20220205_0803_builder
VMHost Core: vmhost-core-x86-64-20.4R3-S3.4
kernel: 4.8.28-rt10-WR9.0.0.24_ovp
Junos Disk: junos-install-mx-x86-64-20.4R3-S3.4

This behavior observed in the >show vmhost version output under Junos DIsk field is expected and aligns with Junos conventions. The discrepancy in package naming is not indicative of an error or misconfiguration but rather a deliberate design choice.