xybal's Posts

I've found this on the web: /usr/bin/vmware-cmd <cfg> stop <powerop_mode> Here the <powerop_mode> is the tricky option. There are three options: Soft: VMware tools... See more...
I've found this on the web: /usr/bin/vmware-cmd <cfg> stop <powerop_mode> Here the <powerop_mode> is the tricky option. There are three options: Soft: VMware tools need to be installed and running, therefore there are many cases when this will not work! Hard: Performs the operation no matter what Trysoft: Trys a soft and if that fails proceeds to a Hard. This is the best one in my opinion In my case I understand that I have to use the "Trysoft" mode.
thx you very much for your help, Now is it possible to do the same with instead of brutal poweroff, doing a clean shutdown like it's would be possible creating a scheduled task ? ... See more...
thx you very much for your help, Now is it possible to do the same with instead of brutal poweroff, doing a clean shutdown like it's would be possible creating a scheduled task ? Thx
Hi, I've got to poweroff all the Vms from a cluster (approximatively 200 Vms). Is it possible to create a scheduled task selecting all Vms concerned at once time. I've alr... See more...
Hi, I've got to poweroff all the Vms from a cluster (approximatively 200 Vms). Is it possible to create a scheduled task selecting all Vms concerned at once time. I've already did it for several VM but I won't do it for all manually. How can I do it in once time ? Thx
Hi, Since we upgrade our ESX cluster to v3.5u5 we can't add another LUN (no recognition) on it. On an ESX node 3.5u4 I manage to add this same LUN but not on an ESX 3.5u5. ... See more...
Hi, Since we upgrade our ESX cluster to v3.5u5 we can't add another LUN (no recognition) on it. On an ESX node 3.5u4 I manage to add this same LUN but not on an ESX 3.5u5. I've already found this interesting link on the web : http://blog.festag.de/?p=176 Now I understand my Pb but I don't know how to workaround ? Can anyone help me please ? Thx very much logs in vmkwarning : Mar 5 15:47:38 GEV0H001 vmkernel: 30:01:26:10.990 cpu2:1041)WARNING: SCSI: 2342: vmhba4:C0:T0:L4: Path's Disk id (new) - <type 2, len 22, lun 4, devType 0, scsi 3, h(id) 11328340606413863509> Mar 5 15:47:38 GEV0H001 vmkernel: 30:01:26:10.990 cpu2:1041)WARNING: SCSI: 2344: vmhba4:C0:T0:L4: Target's Disk id (old) - <type 2, len 22, lun 4, devType 0, scsi 3, h(id) 2634864624073550305> Mar 5 15:47:40 GEV0H001 vmkernel: 30:01:26:11.067 cpu2:1041)WARNING: SCSI: 2340: The physical media represented by vmhba4:1:4 has changed. The device cannot be re-synchronized with the system. This is a critical error. Check below id details: Mar 5 15:47:40 GEV0H001 vmkernel: 30:01:26:11.067 cpu2:1041)WARNING: SCSI: 2342: vmhba4:C0:T1:L4: Path's Disk id (new) - <type 2, len 22, lun 4, devType 0, scsi 3, h(id) 11328340606413863509> Mar 5 15:47:40 GEV0H001 vmkernel: 30:01:26:11.067 cpu2:1041)WARNING: SCSI: 2344: vmhba4:C0:T1:L4: Target's Disk id (old) - <type 2, len 22, lun 4, devType 0, scsi 3, h(id) 2634864624073550305> Mar 5 15:47:43 GEV0H001 vmkernel: 30:01:26:11.142 cpu0:1041)WARNING: ScsiDevice: 4651: Can't add device 'vml.020030000060060e8005488c000000488c000007054f50454e2d56'. A device with that uid already exists. Mar 5 15:47:43 GEV0H001 vmkernel: 30:01:26:11.142 cpu0:1041)WARNING: SCSI: 5583: Could not register a Logical Device for target vmhba3:0:48: Already exists Mar 5 15:47:43 GEV0H001 vmkernel: 30:01:26:11.142 cpu0:1041)WARNING: SCSI: 2747: Failed to register target vmhba3:0:48 with PSA framework: Already exists
Hi, Since we upgrade our ESX cluster to v3.5u5 we can't add another LUN (no recognition) on it. On an ESX node 3.5u4 I manage to add this same LUN but not on an ESX 3.5u5. ... See more...
Hi, Since we upgrade our ESX cluster to v3.5u5 we can't add another LUN (no recognition) on it. On an ESX node 3.5u4 I manage to add this same LUN but not on an ESX 3.5u5. I've already found this interesting link on the web : http://blog.festag.de/?p=176 Now I understand my Pb but I don't know how to workaround ? Can anyone help me please ? Thx very much logs in vmkwarning : Mar 5 15:47:38 GEV0H001 vmkernel: 30:01:26:10.990 cpu2:1041)WARNING: SCSI: 2342: vmhba4:C0:T0:L4: Path's Disk id (new) - <type 2, len 22, lun 4, devType 0, scsi 3, h(id) 11328340606413863509> Mar 5 15:47:38 GEV0H001 vmkernel: 30:01:26:10.990 cpu2:1041)WARNING: SCSI: 2344: vmhba4:C0:T0:L4: Target's Disk id (old) - <type 2, len 22, lun 4, devType 0, scsi 3, h(id) 2634864624073550305> Mar 5 15:47:40 GEV0H001 vmkernel: 30:01:26:11.067 cpu2:1041)WARNING: SCSI: 2340: The physical media represented by vmhba4:1:4 has changed. The device cannot be re-synchronized with the system. This is a critical error. Check below id details: Mar 5 15:47:40 GEV0H001 vmkernel: 30:01:26:11.067 cpu2:1041)WARNING: SCSI: 2342: vmhba4:C0:T1:L4: Path's Disk id (new) - <type 2, len 22, lun 4, devType 0, scsi 3, h(id) 11328340606413863509> Mar 5 15:47:40 GEV0H001 vmkernel: 30:01:26:11.067 cpu2:1041)WARNING: SCSI: 2344: vmhba4:C0:T1:L4: Target's Disk id (old) - <type 2, len 22, lun 4, devType 0, scsi 3, h(id) 2634864624073550305> Mar 5 15:47:43 GEV0H001 vmkernel: 30:01:26:11.142 cpu0:1041)WARNING: ScsiDevice: 4651: Can't add device 'vml.020030000060060e8005488c000000488c000007054f50454e2d56'. A device with that uid already exists. Mar 5 15:47:43 GEV0H001 vmkernel: 30:01:26:11.142 cpu0:1041)WARNING: SCSI: 5583: Could not register a Logical Device for target vmhba3:0:48: Already exists Mar 5 15:47:43 GEV0H001 vmkernel: 30:01:26:11.142 cpu0:1041)WARNING: SCSI: 2747: Failed to register target vmhba3:0:48 with PSA framework: Already exists
Hi, Thank you for this info. What are you meaning about different way to present the same LUN ? Thx
Hi, Yes I think I've already talked about this pb in another post. I don't really understand what is exactly the Pb, can you explain me in simple words what's wrong with this L... See more...
Hi, Yes I think I've already talked about this pb in another post. I don't really understand what is exactly the Pb, can you explain me in simple words what's wrong with this LUN ? Thx
Hi I've got these messages in my vmkwarning and vmkernel when I try to scan for a new LUN: Mar 3 14:18:03 GQV00501 vmkernel: 21:23:21:44.233 cpu0:1040)WARNING: ScsiDevice: 4651: Ca... See more...
Hi I've got these messages in my vmkwarning and vmkernel when I try to scan for a new LUN: Mar 3 14:18:03 GQV00501 vmkernel: 21:23:21:44.233 cpu0:1040)WARNING: ScsiDevice: 4651: Can't add device 'vml.020024000060060e8005488c000000488c000007054f50454e2d56'. A device with that uid already exists. Mar 3 14:18:03 GQV00501 vmkernel: 21:23:21:44.233 cpu0:1040)WARNING: SCSI: 5583: Could not register a Logical Device for target vmhba1:0:36: Already exists Mar 3 14:18:03 GQV00501 vmkernel: 21:23:21:44.233 cpu0:1040)WARNING: SCSI: 2747: Failed to register target vmhba1:0:36 with PSA framework: Already exists Is someone can help me and give me a solution / workaround ? Thx
Yes I have already rescan all my HBA with rescan button and with this script which do the same : #!/usr/bin/perl -w #Filename: rescan-hbas.pl #No warranty is provided with this script u... See more...
Yes I have already rescan all my HBA with rescan button and with this script which do the same : #!/usr/bin/perl -w #Filename: rescan-hbas.pl #No warranty is provided with this script use strict; my @hbas = `/usr/sbin/esxcfg-info \| grep vmkernel -i \| grep hba \| awk -F\. \{\'print \$29\'\}`; print "The following HBAs were detected on this system:\n"; print "\t@hbas"; foreach my $hba (@hbas) { system("/usr/sbin/esxcfg-rescan $hba"); } print "Checking to see if SW iSCSI is in use...."; my $iscsi = `/usr/sbin/esxcfg-swiscsi -q`; chomp ($iscsi); print "$iscsi\n"; if ($iscsi eq "Software iSCSI is enabled") { system("/usr/sbin/esxcfg-swiscsi -s") } Now I've found something interresting in vmkernel logs : Mar 3 14:18:03 GQV00501 vmkernel: 21:23:21:44.233 cpu0:1040)WARNING: ScsiDevice: 4651: Can't add device 'vml.020024000060060e8005488c000000488c000007054f50454e2d56'. A device with that uid already exists. Mar 3 14:18:03 GQV00501 vmkernel: 21:23:21:44.233 cpu0:1040)WARNING: SCSI: 5583: Could not register a Logical Device for target vmhba1:0:36: Already exists Mar 3 14:18:03 GQV00501 vmkernel: 21:23:21:44.233 cpu0:1040)WARNING: SCSI: 2747: Failed to register target vmhba1:0:36 with PSA framework: Already exists What can I do to avoid this ? Thx
I've alreasy got thisPb in the past and the only solution I found was to reboot each node. Now I can do it s what can replace this action ? Thx
Sorry, but I have not reach the 256 limitation. I just wuld like to create an 36th datastore, the LUn is well presented to my ESX nodes but I can't add it because I can see the... See more...
Sorry, but I have not reach the 256 limitation. I just wuld like to create an 36th datastore, the LUn is well presented to my ESX nodes but I can't add it because I can see the LUN number ? What can I do more to see this LUN ? Thx
Ok thx but what can I do more to create another datastore in these conditions ? Thx
Hi, Is there a limitation of the nimber of datastores attached to an ESX node ? If yes what is this limitation ? In fact I've already attached 35 datastores to each... See more...
Hi, Is there a limitation of the nimber of datastores attached to an ESX node ? If yes what is this limitation ? In fact I've already attached 35 datastores to each node which compose my cluster. Now I don't managed to add another datastore that's the meaning of my question. Thx very much for your help.
<level-80000001> edx - 0--- ---0 - - - - - usefull links: NX/XD: NX for AMD and XD for Intel eXecution Disable RDTSCP: This instruction can be e... See more...
<level-80000001> edx - 0--- ---0 - - - - - usefull links: NX/XD: NX for AMD and XD for Intel eXecution Disable RDTSCP: This instruction can be executed only by privileged code and is specific to AMD CPUs
In fact I've read that I had to active in BIOS : - protection against XD flag - activate Intel virtualisation technology If I don't activate these options in bios I can us... See more...
In fact I've read that I had to active in BIOS : - protection against XD flag - activate Intel virtualisation technology If I don't activate these options in bios I can use CPU mask like this for the EDX register : <level-80000001> edx - 0--- ---0 - - - - -
yes I know that but when you have existing Xeon E5405 and you want to add E5504 is there a solution to use EVC ?
Hi, We've got several "old" intel Xeon E5405 @2ghz in our main cluster. Since an add of a ESX node a bit more recent ( E5405 @2ghz stepping +1) I've already modify the CPU mask... See more...
Hi, We've got several "old" intel Xeon E5405 @2ghz in our main cluster. Since an add of a ESX node a bit more recent ( E5405 @2ghz stepping +1) I've already modify the CPU mask on our vCenter. My Pb is that now I had to add a recent HP 380G6 (intel xeon E5504 @2ghz) in this cluster. When I try to enable EVC it tells me that there's an hardware incompatibility (in fact all nodes with the intel Xeon E5405). HOW can I workaround for: - Enabling EVC ? if it's possible ? OR - Creating a CPU mask corresponding to my farm ?How to do it ? and is someone able to calculte it See below "/proc/vmware/cpuinfo" of all my 3 kinds of CPU: pcpu 00 01 02 03 04 05 06 07 family 06 06 06 06 06 06 06 06 model ** 26 ** 26 26 26 26 26 26 26 type 00 00 00 00 00 00 00 00stepping ** 05 ** 05 05 05 05 05 05 05 tscKhz 2000070 2000070 2000070 2000070 2000070 2000070 2000070 2000070processorKhz 2000070 2000070 2000070 2000070 2000070 2000070 2000070 2000070 busKhz 133338 133338 133338 133338 133338 133338 133338 133338 name GenuineIntel GenuineIntel GenuineIntel GenuineIntel GenuineIntel GenuineIntel GenuineIntel GenuineIntel ebx 0x00100800 0x02100800 0x04100800 0x06100800 0x10100800 0x12100800 0x14100800 0x16100800ecxFeat 0x009ce3bd 0x009ce3bd 0x009ce3bd 0x009ce3bd 0x009ce3bd 0x009ce3bd 0x009ce3bd 0x009ce3bdedxFeat 0xbfebfbff 0xbfebfbff 0xbfebfbff 0xbfebfbff 0xbfebfbff 0xbfebfbff 0xbfebfbff 0xbfebfbffinitApic 0x00000000 0x00000002 0x00000004 0x00000006 0x00000010 0x00000012 0x00000014 0x00000016 apicID 0x00000000 0x00000002 0x00000004 0x00000006 0x00000010 0x00000012 0x00000014 0x00000016 pcpu 00 01 02 03 04 05 06 07 family 06 06 06 06 06 06 06 06 model 23 23 23 23 23 23 23 23 type 00 00 00 00 00 00 00 00stepping ** 06 ** 06 06 06 06 06 06 06 tscKhz 1999999 1999999 1999999 1999999 1999999 1999999 1999999 1999999processorKhz 1999999 1999999 1999999 1999999 1999999 1999999 1999999 1999999 busKhz 333333 333333 333333 333333 333333 333333 333333 333333 name GenuineIntel GenuineIntel GenuineIntel GenuineIntel GenuineIntel GenuineIntel GenuineIntel GenuineIntel ebx 0x00040800 0x01040800 0x02040800 0x03040800 0x04040800 0x05040800 0x06040800 0x07040800ecxFeat 0x000ce33d 0x000ce33d 0x000ce33d 0x000ce33d 0x000ce33d 0x000ce33d 0x000ce33d 0x000ce33dedxFeat 0xbfebfbff 0xbfebfbff 0xbfebfbff 0xbfebfbff 0xbfebfbff 0xbfebfbff 0xbfebfbff 0xbfebfbffinitApic 0x00000000 0x00000001 0x00000002 0x00000003 0x00000004 0x00000005 0x00000006 0x00000007 apicID 0x00000000 0x00000001 0x00000002 0x00000003 0x00000004 0x00000005 0x00000006 0x00000007 pcpu 00 01 02 03 04 05 06 07 family 06 06 06 06 06 06 06 06 model 23 23 23 23 23 23 23 23 type 00 00 00 00 00 00 00 00stepping **10 ** 10 10 10 10 10 10 10 tscKhz 1999999 1999999 1999999 1999999 1999999 1999999 1999999 1999999processorKhz 1999999 1999999 1999999 1999999 1999999 1999999 1999999 1999999 busKhz 333333 333333 333333 333333 333333 333333 333333 333333 name GenuineIntel GenuineIntel GenuineIntel GenuineIntel GenuineIntel GenuineIntel GenuineIntel GenuineIntel ebx 0x00040800 0x01040800 0x02040800 0x03040800 0x04040800 0x05040800 0x06040800 0x07040800ecxFeat 0x040ce33d 0x040ce33d 0x040ce33d 0x040ce33d 0x040ce33d 0x040ce33d 0x040ce33d 0x040ce33dedxFeat 0xbfebfbff 0xbfebfbff 0xbfebfbff 0xbfebfbff 0xbfebfbff 0xbfebfbff 0xbfebfbff 0xbfebfbffinitApic 0x00000000 0x00000001 0x00000002 0x00000003 0x00000004 0x00000005 0x00000006 0x00000007 apicID 0x00000000 0x00000001 0x00000002 0x00000003 0x00000004 0x00000005 0x00000006 0x00000007 Thx very much
Already done but still doesn't work. Any another idea ? please
Hi, My vCenter (2.5u5) is a VM. My ESX nodes are V3.5u5. I've powered off my vCenter cleanly powering off my VM. After that I've accessed onother node and regertered vcent... See more...
Hi, My vCenter (2.5u5) is a VM. My ESX nodes are V3.5u5. I've powered off my vCenter cleanly powering off my VM. After that I've accessed onother node and regertered vcenter on this new node. But when I try to bot my VM it complains "Could not power on VM: no swap file". I've tried to "lsof" on all nodes and noticed that all nodes were trying launch a process to join my vCenter. Now I'm putting all my ESX nodes in "evaluation mode" to avoid ESX nodes to launch the process calling vCenter. I've still got my error message. What Can I try to do more ? Here are my vmkernel logs: Feb 8 16:24:30 YYYYYYYYY vmkernel: gen 38234, mode 1, owner 4b699545-6321cd8a-fb91-001e0b72b842 mtime 432053] Feb 8 16:25:33 YYYYYYYYY vmkernel: 4:02:11:27.446 cpu3:1041)World: vm 1225: 901: Starting world vmware-vmx with flags 4 Feb 8 16:25:33 YYYYYYYYY vmkernel: 4:02:11:28.287 cpu0:1225)World: vm 1226: 901: Starting world vmm0:XXXXXXX with flags 8 Feb 8 16:25:33 YYYYYYYYY vmkernel: 4:02:11:28.287 cpu0:1225)Sched: vm 1226: 5333: adding 'vmm0:XXXXXX': group 'host/user': cpu: shares=607 min=0 minLimit=-1 max=-1 Feb 8 16:25:33 YYYYYYYYY vmkernel: 4:02:11:28.287 cpu0:1225)Sched: vm 1226: 5352: renamed group 61 to vm.1225 Feb 8 16:25:33 YYYYYYYYY vmkernel: 4:02:11:28.287 cpu0:1225)Sched: vm 1226: 5366: moved group 61 to be under group 4 Feb 8 16:25:33 YYYYYYYYY vmkernel: 4:02:11:28.306 cpu3:1225)FS3: 2048: Checking if lock holders are live for lock [type 10c00001 offset 40040448 v 11, hb offset 3694080 Feb 8 16:25:33 YYYYYYYYY vmkernel: gen 36957, mode 1, owner 4b699545-6321cd8a-fb91-001e0b72b842 mtime 423363] Feb 8 16:25:37 YYYYYYYYY vmkernel: 4:02:11:32.320 cpu0:1225)WARNING: Swap: vm 1226: 2268: Failed to open swap file '/volumes/4948c57c-a4002086-582b-001e0b72b842/XXXXXXX/XXXXXXXX-f1c06d67.vswp': Lock was not free Feb 8 16:25:37 YYYYYYYYY vmkernel: 4:02:11:32.320 cpu0:1225)WARNING: Swap: vm 1226: 3586: Failed to initialize swap file '/volumes/4948c57c-a4002086-582b-001e0b72b842/XXXXXXX/XXXXXXX-f1c06d67.vswp': Lock was not free Feb 8 16:25:37 YYYYYYYYY vmkernel: 4:02:11:32.320 cpu0:1225)WARNING: World: vm 1226: 911: init fn swap failed with: No swap file! Feb 8 16:25:37 YYYYYYYYY vmkernel: 4:02:11:32.320 cpu0:1225)WARNING: World: vm 1226: 1776: WorldInit failed: trying to cleanup. vmkwarning logs : Feb 8 16:25:37 YYYYYYYYY vmkernel: 4:02:11:32.320 cpu0:1225)WARNING: Swap: vm 1226: 2268: Failed to open swap file '/volumes/4948c57c-a4002086-582b-001e0b72b842/XXXXXX/XXXXXX-f1c06d67.vswp': Lock was not free Feb 8 16:25:37 YYYYYYYYY vmkernel: 4:02:11:32.320 cpu0:1225)WARNING: Swap: vm 1226: 3586: Failed to initialize swap file '/volumes/4948c57c-a4002086-582b-001e0b72b842/XXXXXXX/XXXXXXX-f1c06d67.vswp': Lock was not free Feb 8 16:25:37 YYYYYYYYY vmkernel: 4:02:11:32.320 cpu0:1225)WARNING: World: vm 1226: 911: init fn swap failed with: No swap file! Feb 8 16:25:37 YYYYYYYYY vmkernel: 4:02:11:32.320 cpu0:1225)WARNING: World: vm 1226: 1776: WorldInit failed: trying to cleanup. Thx for your help
hi, When I boot my vCenter it takes about more than 20 minutes to start and after that I've got the message shown below. I precise that I've got no network on this VM when it's... See more...
hi, When I boot my vCenter it takes about more than 20 minutes to start and after that I've got the message shown below. I precise that I've got no network on this VM when it's in this state. Is there any workaround to save my vCenter ? Thx very much