VMware Cloud Community
edox77
Contributor
Contributor
‎02-13-2012 04:51 AM

SLES 11 64 bit - freeze after hot add new disk

Hello,

on a SLES11 64bit virtual machine i've hot added a new scsi disk then vm completely freeze whithout giving me any possible interaction through console directly ... so power off then power on the new disk is correctly mounted ... What happens? Someone can help me?

Follow vmware.log relatively scsi added device

Feb 10 12:18:32.479: vmx| Vix: [109432 vmxCommands.c:2028]: VMAutomation_HotAddDevice

Feb 10 12:18:32.480: vmx| VMAutomation: Hot add device. asyncCommand=1F178580, type=50, backing=103

Feb 10 12:18:32.480: vmx| HotAdd: Adding scsi-hardDisk with mode 'persistent' to scsi0:2

Feb 10 12:18:32.481: vmx| DISK: OPEN scsi0:2 '/vmfs/volumes/4c909156-07955d49-dcff-1cc1de1c62a2/saetta/saetta_3.vmdk' persistent R[]

Feb 10 12:18:32.487: vmx| DISKLIB-VMFS  : "/vmfs/volumes/4c909156-07955d49-dcff-1cc1de1c62a2/saetta/saetta_3-flat.vmdk" : open successful (10) size = 4294967296, hd = 2028863608. Type 3

Feb 10 12:18:32.488: vmx| DISKLIB-DSCPTR: Opened [0]: "saetta_3-flat.vmdk" (0xa)

Feb 10 12:18:32.488: vmx| DISKLIB-LINK  : Opened '/vmfs/volumes/4c909156-07955d49-dcff-1cc1de1c62a2/saetta/saetta_3.vmdk' (0xa): vmfs, 8388608 sectors / 4 GB.

Feb 10 12:18:32.489: vmx| DISKLIB-LIB   : Opened "/vmfs/volumes/4c909156-07955d49-dcff-1cc1de1c62a2/saetta/saetta_3.vmdk" (flags 0xa, type vmfs).

Feb 10 12:18:32.489: vmx| DISKLIB-LIB   : Content-ID check is now enabled.

Feb 10 12:18:32.490: vmx| DISK: Disk '/vmfs/volumes/4c909156-07955d49-dcff-1cc1de1c62a2/saetta/saetta_3.vmdk' has UUID '60 00 c2 97 a2 20 a0 4e-99 75 42 f4 5c 1c 71 81'

Feb 10 12:18:32.490: vmx| DISK: OPEN '/vmfs/volumes/4c909156-07955d49-dcff-1cc1de1c62a2/saetta/saetta_3.vmdk' Geo (522/255/63) BIOS Geo (0/0/0)

Feb 10 12:18:32.492: vmx| Creating virtual dev for scsi0:2

Feb 10 12:18:32.493: vmx| DumpDiskInfo: scsi0:2 createType=11, capacity = 8388608, numLinks = 1, allocationType = 1

Feb 10 12:18:32.495: vmx| SCSIDiskESXPopulateVDevDesc: Using FS backend

Feb 10 12:18:32.496: vmx| VmdbCtxCheckOneof: One-of: /vm/#_VMX/vmx/cfgState/val/dev/#_scsiDev0:2/class/scsiDev/subclass/ disk []

Feb 10 12:18:32.496: vmx| scsi0:2: Cannot retrieve shares: A one-of constraint has been violated (-19)

Feb 10 12:18:32.497: vmx| VmdbCtxCheckOneof: One-of: /vm/#_VMX/vmx/cfgState/val/dev/#_scsiDev0:2/class/scsiDev/subclass/ disk []

Feb 10 12:18:32.497: vmx| scsi0:2: Cannot retrieve sched/limit/: A one-of constraint has been violated (-19)

Feb 10 12:18:32.498: vmx| VmdbCtxCheckOneof: One-of: /vm/#_VMX/vmx/cfgState/val/dev/#_scsiDev0:2/class/scsiDev/subclass/ disk []

Feb 10 12:18:32.499: vmx| scsi0:2: Cannot retrieve sched/bandwidthCap/: A one-of constraint has been violated (-19)

Feb 10 12:18:32.508: vmx| VMXVmdb_LoadRawConfig: Loading raw config

Feb 10 12:18:32.517: vmx| Vix: [109432 vmxCommands.c:1819]: VMAutomation: Hot plug completed. err=0, vmdbErr=0, asyncCommand=1F178580, OpCode=138

Feb 10 12:18:32.518: vcpu-0| LSI:Rescan requested for scsi0...

Feb 10 12:18:32.641: vmx| Vix: [109432 vmxCommands.c:2248]: VMAutomation_HotPlugCommitBatch: commiting the HotPlug Batch.

Feb 10 12:18:32.641: vmx| Vix: [109432 vmxCommands.c:1819]: VMAutomation: Hot plug completed. err=0, vmdbErr=0, asyncCommand=1F2A1860, OpCode=159

Feb 10 12:18:49.629: vmx| TOOLS received request in VMX to set option 'synctime' -> '0'

Feb 10 12:18:49.631: vmx| VMXVmdb_LoadRawConfig: Loading raw config

Feb 10 12:19:32.522: vmx| GuestRpcSendTimedOut: message to toolbox-dnd timed out.

Feb 10 12:25:06.076: mks| VNCENCODE 6 encoding mode change: (800x600x24depth,32bpp,3200bytes/line)

Feb 10 12:26:19.722: mks| SOCKET 6 (146) recv error 104: Connection reset by peer

Feb 10 12:26:19.723: mks| SOCKET 6 (146) destroying VNC backend on socket error: 1

Feb 10 12:27:02.902: vmx| VMXVmdbCbVmVmxMigrate: Got SET callback for /vm/#_VMX/vmx/migrateState/cmd/##1_527e69/op/=to

Feb 10 12:27:02.903: vmx| VMXVmdbVmVmxMigrateGetParam: type: 1

0 Kudos
3 Replies
Shakaal
Hot Shot
Hot Shot
‎02-13-2012 06:38 AM

Hi,

didnt get much from these logs would reqeust you to upload vmkernel logs.

Regards

0 Kudos
edox77
Contributor
Contributor
‎02-14-2012 12:50 AM

Hi Shakaal,

follow vmkernel log grep with 'hostname'

[root@pwfesx4 ~]# cat /var/log/vmkernel.2 |grep saetta
Feb 24 23:47:04 pwfesx4 vmkernel: 66:22:11:35.671 cpu9:5686)World: vm 5687: 1534: Starting world vmm0:saetta with flags 4008
Feb 24 23:47:04 pwfesx4 vmkernel: 66:22:11:35.671 cpu9:5686)Sched: vm 5687: 6047: Adding world 'vmm0:saetta', group 'host/user', cpu: shares=-3 min=0 minLimit=-1 max=-1, mem: shares=-3 min=0 minLimit=-1 max=1015808
Feb 24 23:47:04 pwfesx4 vmkernel: 66:22:11:35.690 cpu10:5686)World: vm 5689: 1534: Starting world vmm1:saetta with flags 4008
Feb 24 23:47:04 pwfesx4 vmkernel: 66:22:11:35.690 cpu10:5686)World: vm 5690: 1534: Starting world vmm2:saetta with flags 4008
Feb 24 23:47:04 pwfesx4 vmkernel: 66:22:11:35.690 cpu10:5686)World: vm 5691: 1534: Starting world vmm3:saetta with flags 4008
Feb 24 23:47:04 pwfesx4 vmkernel: 66:22:11:35.690 cpu10:5686)World: vm 5692: 1534: Starting world vmm4:saetta with flags 4008
Feb 24 23:47:04 pwfesx4 vmkernel: 66:22:11:35.690 cpu10:5686)World: vm 5693: 1534: Starting world vmm5:saetta with flags 4008
Feb 24 23:47:04 pwfesx4 vmkernel: 66:22:11:35.690 cpu10:5686)World: vm 5694: 1534: Starting world vmm6:saetta with flags 4008
Feb 24 23:47:04 pwfesx4 vmkernel: 66:22:11:35.690 cpu10:5686)World: vm 5695: 1534: Starting world vmm7:saetta with flags 4008
Feb 24 23:47:43 pwfesx4 vmkernel: 66:22:12:15.164 cpu21:5687)Net: 1421: connected saetta eth0 to VL-DCS-PIRWEB-BE, portID 0x300001e
Feb 24 23:47:43 pwfesx4 vmkernel: 66:22:12:15.169 cpu20:5687)Net: 1421: connected saetta eth0 to VL-DCS-PIRWEB-PUB-SLB, portID 0x400001d
Feb 24 23:47:44 pwfesx4 vmkernel: 66:22:12:15.459 cpu18:5687)Net: 1421: connected saetta eth0 to VL-DCS-PIRWEB-MGT-SLB, portID 0x1000017
Feb 24 23:47:44 pwfesx4 vmkernel: 66:22:12:15.660 cpu20:5687)Net: 1421: connected saetta eth0 to VL-DCS-PIRWEB-BCK, portID 0x5000023
Feb 24 23:48:46 pwfesx4 vmkernel: 66:22:13:18.065 cpu18:5686)World: vm 5711: 1534: Starting world vmm0:saetta with flags 4008
Feb 24 23:48:46 pwfesx4 vmkernel: 66:22:13:18.065 cpu18:5686)Sched: vm 5711: 6047: Adding world 'vmm0:saetta', group 'host/user', cpu: shares=-3 min=0 minLimit=-1 max=-1, mem: shares=-3 min=0 minLimit=-1 max=1015808
Feb 24 23:48:47 pwfesx4 vmkernel: 66:22:13:19.453 cpu20:5686)World: vm 5713: 1534: Starting world vmm1:saetta with flags 4008
Feb 24 23:48:47 pwfesx4 vmkernel: 66:22:13:19.453 cpu20:5686)World: vm 5714: 1534: Starting world vmm2:saetta with flags 4008
Feb 24 23:48:47 pwfesx4 vmkernel: 66:22:13:19.453 cpu20:5686)World: vm 5715: 1534: Starting world vmm3:saetta with flags 4008
Feb 24 23:48:47 pwfesx4 vmkernel: 66:22:13:19.453 cpu20:5686)World: vm 5716: 1534: Starting world vmm4:saetta with flags 4008
Feb 24 23:48:47 pwfesx4 vmkernel: 66:22:13:19.453 cpu20:5686)World: vm 5717: 1534: Starting world vmm5:saetta with flags 4008
Feb 24 23:48:47 pwfesx4 vmkernel: 66:22:13:19.454 cpu20:5686)World: vm 5718: 1534: Starting world vmm6:saetta with flags 4008
Feb 24 23:48:47 pwfesx4 vmkernel: 66:22:13:19.454 cpu20:5686)World: vm 5719: 1534: Starting world vmm7:saetta with flags 4008
Feb 24 23:48:51 pwfesx4 vmkernel: 66:22:13:22.764 cpu19:5711)Net: 1421: connected saetta eth0 to VL-DCS-PIRWEB-BE, portID 0x300001f
Feb 24 23:48:51 pwfesx4 vmkernel: 66:22:13:23.017 cpu23:5711)Net: 1421: connected saetta eth0 to VL-DCS-PIRWEB-PUB-SLB, portID 0x400001e
Feb 24 23:48:51 pwfesx4 vmkernel: 66:22:13:23.018 cpu20:5711)Net: 1421: connected saetta eth0 to VL-DCS-PIRWEB-MGT-SLB, portID 0x1000018
Feb 24 23:48:51 pwfesx4 vmkernel: 66:22:13:23.019 cpu20:5711)Net: 1421: connected saetta eth0 to VL-DCS-PIRWEB-BCK, portID 0x5000024

Nothing seems strange, this log report a virtual machine startup (after freeze when I reset virtual machine) ... th only thing what's wrong is the host time wich differs from vm time, but this cannot generate freeze ...

0 Kudos
raj196
Enthusiast
Enthusiast
‎02-14-2012 01:49 AM

Hi edox77.  lets start resolving this problem from basic step . 1-If it physical harddisk please remove it and check eventviewer  any error related to storae or storage controler .  Then again plug this harddisk and try to boot if it dididnt boot then try to connect  with another controler .still having prbole then without further stpes replace another disk.  2-if its vxd storage  If you've downloaded a .VXD file and need to know what program to use it    3-Is there any error in hostd.log log file (/var/log/vmware/hostd.log) then please uplod same .

If at first you don't succeed; call it version 1.0"
0 Kudos