Skip navigation
2018
RajeevVCP4 Hot Shot
vExpert

Virtual machine hung

Posted by RajeevVCP4 Mar 26, 2018

If you want to power off hung virtual machine ,

Try these command

 

1. Take process id and kill

 

ps | grep vmx

kill -9 <pid> 300731

 

 

Method-2:-  take vmid and use this command

 

 

vim-cmd vmsvc/getallvms

 

 

vim-cmd vmsvc/power.off <vmid>

 

 

Method-3 :- By world ID

 

 

esxcli vm process list ( take world id)

 

 

esxcli vm process kill -t=soft -w=wordid

From obfl logs

 

5:2018 Mar 17 13:13:12 MST:3.1(21d):selparser:1688: selparser.c:706: # 2D 02 00 00 01 02 00 00 D7 76 AD 5A 33 00 04 07 00 00 00 00 6F A5 92 11 # 22d | 03/17/2018 13:13:11 | BIOS | Processor #0x00 | Configuration Error |  | Asserted

5:2018 Mar 17 22:25:39 MST:3.1(21d):avct_server:1589: callback_http: new client connected, wsi 0x40e03778

5:2018 Mar 17 22:25:39 MST:3.1(21d):avct_server:13538: Client supports encrypted/unencrypted kbd/mouse.

 

From SEL

 

22d | 03/17/2018 13:13:11 | BIOS | Processor #0x00 | Configuration Error |  | Asserted

 

This is cisco bug (CSCuz55148). Vce kb (000004971)

 

Solution:- Proactive plan replace both CPUs.

RajeevVCP4 Hot Shot
vExpert

MCA error detected via CMCI

Posted by RajeevVCP4 Mar 23, 2018

Condition:- Cisco UCS B200 M3

 

 

cpu13:5344825)MCE: 1020: cpu13: MCA error detected via CMCI (Gbl status=0x0): Restart IP: invalid, Error IP: invalid, MCE in progress: no.

cpu13:5344825)MCE: 190: cpu13: bank7: status=0x8c00004000010091: (VAL=1, OVFLW=0, UC=0, EN=0, PCC=0, S=0, AR=0), Addr:0x1421652080 (valid), Misc:0x42389a00 (valid)

2018-03-16T12:36:38.906Z cpu13:5344825)MCE: 199: cpu13: bank7: MCA recoverable error (CE): "Memory Controller Read Error on Channel 1."

 

CIMC | Processor IERR #0x99 | Predictive Failure asserted | Asserted

5:2018 Mar 16 23:13:53 GMT:3.1(21d):selparser:1724: selparser.c:706: # DA 01 00 00 01 02 00 00 B1 4F AC 5A 20 00 04 24 95 00 00 00 7F 05 FF FF # 1da | 03/16/2018 23:13:53 | CIMC | Platform alert LED_BLADE_STATUS #0x95 | LED color is amber | Asserted

 

 

CPU 1 : MCA_ERR_SRC_LOG : 0xc0000000

CPU 2 : READ MCA_ERR_SRC_LOG Register : FAILED : RetVal = 0 : CC = 0x81

 

 

Solution:- replace faulty system board along with TPM.

Scenario :- If we are using N3K and N9K , mostly used teaming policy ip hash , but when we changed NIC/IP its take origination port id.

 

Try to change it by these command

 

To Set the NIC teaming policy on a Virtual Switch on an ESXi 5.x

  • To list the current NIC teaming policy of a vSwitch, use the command:

    # esxcli network vswitch standard policy failover get -v vSwitch0
  • To set the NIC teaming policy of a vSwitch, use this command:
# esxcli network vswitch standard policy failover set -l policy -v vSwitchXFor example, to set the NIC teaming policy of a vSwitch to IP hash:

 

# esxcli network vswitch standard policy failover set -l iphash -v vSwitch0Note: Available Policy Options:
  • explicit = Use explicit failover order
  • portid = Route based upon port id (This is the Default setting)
  • mac = Source Based Upon MAC Hash
  • iphash = Source based up IP hash (This is only to be used in a etherchannel\Portchannel)

To Set the NIC teaming policy on a Port Group

  1. To list the current NIC teaming policy of a port group, run this command:


    esxcli network vswitch standard portgroup policy failover get -p "Management Network"
  2. To set the NIC teaming policy of a port group, run this command:


    esxcli network vswitch standard portgroup policy failover set -p "Management Network" -l "Policy Options"

policy option is iphash

 

VMware Knowledge Base

In vcenter server 6.0 U3b , from vpxd logs.

 

 

--> Panic: Win32 exception: Access Violation (0xc0000005)

--> Read (0) at address 0000000000000058

--> rip: 00007ffde6a18cc0 rsp: 0000000018ede918 rbp: 00000000113f4a40

 

This issue occurs due to Microsoft SQL databases not supporting shared connections.

 

Solution:- Upgrade vcenter server/PSC by 6.0 U3c/d

 

For more information refer

 

VMware Knowledge Base