vMX
vMX

vMX cannot boot up, staying at db>

[ Edited ]
‎03-21-2017 08:01 AM

When I executed any command starting with ./vmx.sh, the system reported an error: unexpected operator

And the vMX will stuck at db>

 

root@vMX:/mnt/vmx-16.2R1.6# ./vmx.sh --console vcp vmx1
./vmx.sh: 460: [: ubuntu: unexpected operator
--
Login Console Port For vcp-vmx1 - 8601
Press Ctrl-] to exit anytime
--
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
data=0x8b818+0x15ebd8 syms=[0x8+0x939c0+0x8+0xaaaa3]
/packages/sets/pending/boot/os-kernel/contents.izo size=0x776600
/packages/sets/pending/boot/os-kernel/miibus.ko size 0x41ca0 at 0x1275000
loading required module 'netstack'
/packages/sets/pending/boot/netstack/netstack.ko size 0x1044e30 at 0x12b7000
loading required module 'crypto'
/packages/sets/pending/boot/os-crypto/crypto.ko size 0x2e990 at 0x22fc000
/packages/sets/pending/boot/os-kernel/if_em.ko size 0x80ca0 at 0x232b000
/packages/sets/pending/boot/os-kernel/if_fxp.ko size 0x13e28 at 0x23ac000
/packages/sets/pending/boot/os-kernel/if_igb.ko size 0x6baa8 at 0x23c0000
/packages/sets/pending/boot/os-kernel/if_ixlv.ko size 0x30188 at 0x242c000
can't find 'verifiedmnt'
/packages/sets/pending/boot/netstack/mtx_re.ko size 0xf1de8 at 0x245d000
/packages/sets/pending/boot/netstack/pvi_db.ko size 0x6e10 at 0x254f000
/packages/sets/pending/boot/os-vmguest/virtio.ko size 0x5a98 at 0x2556000
/packages/sets/pending/boot/os-vmguest/virtio_blk.ko size 0x7530 at 0x255c000
/packages/sets/pending/boot/os-vmguest/virtio_pci.ko size 0x71f0 at 0x2564000
/packages/sets/pending/boot/os-vmguest/virtio_random.ko size 0x2b48 at 0x256c000
/packages/sets/pending/boot/os-vmguest/virtio_scsi.ko size 0xc378 at 0x256f000
/packages/sets/pending/boot/os-vmguest/if_vtnet.ko size 0x11a00 at 0x257c000
/packages/sets/pending/boot/junos-modules/fips_core.ko size 0x6338 at 0x258e000
/packages/sets/pending/boot/junos-modules/hmac_drbg.ko size 0x8b10 at 0x2595000
/packages/sets/pending/boot/junos-modules/mac_sdk.ko size 0x11de8 at 0x259e000
/packages/sets/pending/boot/junos-modules/sdk_core.ko size 0x24740 at 0x25b0000
/packages/sets/pending/boot/junos-modules/junosprocfs.ko size 0x56c0 at 0x25d5000
/packages/sets/pending/boot/junos-modules/mac_fips.ko size 0x5680 at 0x25db000
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/packages/sets/pending/boot/os-kernel/kernel]...
GDB: debug ports: uart
GDB: current port: uart
KDB: debugger backends: ddb gdb ndb
KDB: current backend: ddb
panic: CPU0 does not support X87 or SSE: 0
cpuid = 0
KDB: enter: panic
[ thread pid 0 tid 0 ]
Stopped at kdb_enter+0x3b: movq $0,0x50b4e2(%rip)
db>

 

The identical configuration works on my Macbook and a Intel PC, but hits KDB panic issue on a newly purchased AMD PC when booting vMX VCP.

Attachments

8 REPLIES 8
vMX

Re: vMX cannot boot up, staying at db>

‎03-21-2017 08:13 AM

Checked KVM. It's fine.

 

root@vMX:~# cat /etc/modprobe.d/qemu-system-x86.conf
options kvm_amd nested=1 enable_apicv=0


root@vMX:~# cat /etc/default/qemu-kvm
# To disable qemu-kvm's page merging feature, set KSM_ENABLED=0 and
# sudo restart qemu-kvm
KSM_ENABLED=0
SLEEP_MILLISECS=200
# To load the vhost_net module, which in some cases can speed up
# network performance, set VHOST_NET_ENABLED to 1.
VHOST_NET_ENABLED=0

# Set this to 1 if you want hugepages to be available to kvm under
# /run/hugepages/kvm
KVM_HUGEPAGES=0


root@vMX:~# egrep -c '(vmx|svm)' /proc/cpuinfo
8


root@vMX:~# kvm-ok
INFO: /dev/kvm exists
KVM acceleration can be used

vMX

Re: vMX cannot boot up, staying at db>

‎03-24-2017 05:47 PM
Hello,

Though the article is for EX, you can still start with this:

https://kb.juniper.net/InfoCenter/index?page=content&id=KB20635&actp=METADATA

Regards,

Rushi
vMX

Re: vMX cannot boot up, staying at db>

‎04-04-2017 01:08 PM

I'm experiencing the same problem, is this caused by a non compatible (I'm using an old DELL 1950 server) CPU, please help, I'm stuck :

 

Login Console Port For vcp-vmx1 - 8601
Press Ctrl-] to exit anytime
--
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
size 0x11743f0 at 0x12b7000
loading required module 'crypto'
/packages/sets/pending/boot/os-crypto/crypto.ko size 0x2e990 at 0x242c000
/packages/sets/pending/boot/os-kernel/if_em.ko size 0x80ca0 at 0x245b000
/packages/sets/pending/boot/os-kernel/if_fxp.ko size 0x13e28 at 0x24dc000
/packages/sets/pending/boot/os-kernel/if_igb.ko size 0x6bb18 at 0x24f0000
/packages/sets/pending/boot/os-kernel/if_ixlv.ko size 0x30188 at 0x255c000
can't find 'verifiedmnt'
/packages/sets/pending/boot/junos-modules/fips_core.ko size 0x6330 at 0x258d000
/packages/sets/pending/boot/junos-modules/hmac_drbg.ko size 0x8b10 at 0x2594000
/packages/sets/pending/boot/junos-modules/mac_sdk.ko size 0x12560 at 0x259d000
/packages/sets/pending/boot/junos-modules/sdk_core.ko size 0x24bc0 at 0x25b0000
/packages/sets/pending/boot/junos-modules/junosprocfs.ko size 0x56c0 at 0x25d5000
/packages/sets/pending/boot/junos-modules/mac_fips.ko size 0x5680 at 0x25db000
/packages/sets/pending/boot/os-vmguest/virtio.ko size 0x5a98 at 0x25e1000
/packages/sets/pending/boot/os-vmguest/virtio_blk.ko size 0x7530 at 0x25e7000
/packages/sets/pending/boot/os-vmguest/virtio_pci.ko size 0x71f0 at 0x25ef000
/packages/sets/pending/boot/os-vmguest/virtio_random.ko size 0x2b48 at 0x25f7000
/packages/sets/pending/boot/os-vmguest/virtio_scsi.ko size 0xc378 at 0x25fa000
/packages/sets/pending/boot/os-vmguest/if_vtnet.ko size 0x11a00 at 0x2607000
/packages/sets/pending/boot/netstack/pvi_db.ko size 0x6e10 at 0x2619000
/packages/sets/pending/boot/netstack/mtx_re.ko size 0xf9a60 at 0x2620000
can't find 'hdkcb'
/packages/sets/pending/boot/netstack/ptxfabsw.ko size 0x6170 at 0x271a000
can't find 'ixgbe'
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/packages/sets/pending/boot/os-kernel/kernel]...
GDB: debug ports: uart
GDB: current port: uart
KDB: debugger backends: ddb gdb ndb
KDB: current backend: ddb
panic: CPU0 does not support X87 or SSE: 1
cpuid = 0
KDB: enter: panic
[ thread pid 0 tid 0 ]
Stopped at      kdb_enter+0x3b: movq    $0,0x50b5d2(%rip)
db>
db> cont

vMX

Re: vMX cannot boot up, staying at db>

‎04-09-2017 07:46 AM

What's your CPU model? It's likely qemu doesn't recognize CPU flags properly.

 

You may try change <cpu mode> setting in the vCP XML file (scripts/templates/_vRE-ref.xml), from host-model to host-passthrough, then reinstall with vmx.sh.

 

vMX

Re: vMX cannot boot up, staying at db>

‎04-10-2017 02:52 PM

Many Thanks szhong

 

I'm using a standard Intel Xeon proc. editing the .xml file and changing the value corrected the problem, I can now access the vcp console.

 

jp@Junos:~$ cat /proc/cpuinfo | grep model | grep name
model name      : Intel(R) Xeon(R) CPU           E5430  @ 2.66GHz
model name      : Intel(R) Xeon(R) CPU           E5430  @ 2.66GHz
model name      : Intel(R) Xeon(R) CPU           E5430  @ 2.66GHz

vMX

Re: vMX cannot boot up, staying at db>

‎04-11-2017 01:39 PM

Glad to know it works.

 

I guess somehow your current qemu doesn't handle CPU flags properly. It really depends on qemu version and CPU type.

vMX

Re: vMX cannot boot up, staying at db>

a week ago

Hello

how did you do to modify CPU , i have the same issue

 

thanks

vMX

Re: vMX cannot boot up, staying at db>

Tuesday

What the Ubuntu version used here?

 

Which version on vMX is been used? is this SRIOV or VIRTIO?

 

make sure all mimum requirements are met as mentioned below..

https://www.juniper.net/documentation/en_US/vmx/topics/reference/general/vmx-hw-sw-minimums.html

 

-
VR
# Please mark my solution as accepted if it helped, Kudos are appreciated as well.