vMX
Highlighted
vMX

vMX on VMware - vCP Rebooting

‎02-24-2017 02:40 PM

Playing around with some vMX instances on VMware.  Noticing that the vCP VM is consistently rebooting with what appears to be a kernel panic, general protection fault.

 

The vFPC logs "Fail to enable PCI MSIX, or not enough msix entries uio device registered with irq 10" (swaps between 10 and 11.

 

Need to enable telnet <----> serial so i can pull the syslog from the vCP; but curious if anyone else has noticed this.  
Both VMs are configured for the right hw requirements for lite-mode.

Senior Engineer at Synoptek, LLC.
JNCIP-ENT
JNCIS-SEC

Aspiring JNCIE.
My words are my own.
7 REPLIES 7
Highlighted
vMX

Re: vMX on VMware - vCP Rebooting

‎02-24-2017 02:49 PM

I saw similar message before but it's casued by not having enongh vCPU...

Highlighted
vMX

Re: vMX on VMware - vCP Rebooting

‎02-24-2017 03:00 PM

On Which vm?  the vCP or vFPC?  I have 1 socket / 1 core vCPU on the vCP virtual machine, and 3 socket / 1 core per socket vCPU on the vFCP virtual machine which is all supposedly the recommended spec.

Senior Engineer at Synoptek, LLC.
JNCIP-ENT
JNCIS-SEC

Aspiring JNCIE.
My words are my own.
Highlighted
vMX

Re: vMX on VMware - vCP Rebooting

‎02-24-2017 03:16 PM

vFP, could you try with 4 vCPUs?

Highlighted
vMX

Re: vMX on VMware - vCP Rebooting

‎02-24-2017 04:02 PM

Yeah, the issue appears entirely isolated to the vCP VM. 

For whats its worth I managed to catch two issues as they happened.  Both popped this onto the console screen:

 

spin lock 0xfffff8001a0014e0 () held by 0xfffff800043209c0 (tid 0) too long
panic: spin lock held too long


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x1a000000038
fault code              = supervisor write data, page not present
instruction pointer     = 0x20:0xffffffff8159ec85
stack pointer           = 0x28:0xfffffe0094d8b8b0
frame pointer           = 0x28:0xfffffe0094d8b8f0
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 4985 (rdd)
trap number             = 12
panic: page fault
cpuid = 0
Uptime: 4m49s
Dumping 252 out of 2011 MB:..7%..13%..26%..32%..45%..51%..64%..77%..83%..96%
Dump complete
Senior Engineer at Synoptek, LLC.
JNCIP-ENT
JNCIS-SEC

Aspiring JNCIE.
My words are my own.
Highlighted
vMX

Re: vMX on VMware - vCP Rebooting

‎02-24-2017 04:34 PM

Do you mind shring whole boot log and RSI?

vMX

Re: vMX on VMware - vCP Rebooting

‎02-27-2017 11:19 AM

Hi,

Sorry for the delay.

I am trying to get the information for you, difficult to get it all before the VM panics and reboots.  I've managed to get the logs but getting the support info is proving more difficult.  I managed to get a "request support information brief" if that helps.

 

Interestingly enough, I setup two more vMXs on my home lab using VMware Workstation 12 and those have been running near nonstop since Friday night.

Senior Engineer at Synoptek, LLC.
JNCIP-ENT
JNCIS-SEC

Aspiring JNCIE.
My words are my own.

Attachments

Highlighted
vMX

Re: vMX on VMware - vCP Rebooting

‎02-27-2017 05:41 PM

The first thing you may want to try is to remove the dhcp setting under fxp0, fxp0 doesn't support DHCP, you have to manually set its address.

Feedback