At any given point of time, these many respective tasks can run at the maximum per object. For example, for a 10 GB vMotion network only 8 concurrent vMotion operations per host will be possible. The 9th one will be queued (though, on the client it says it has started) and the data copy will start only when one of the initial 8 tasks is completed.
Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.
Cheers,
Supreet
Hi
Step to step
I tried version 4.2 and got the same error.
Hello diegodco31,
Thanks for your nice reply with screenshot.
I checked it in this way, the time is alright. But problem is with VMs, they keep changing time.
Thanks in Advance
it seems as if everyone who works with dynamicTypes will read this sooner or later. i have checked unhappyvra´s statement and this looks like the right answer.if i use the findForType method my deployed item does NOT show up in VRA. if i use the DynamicTypesManager.getObject method the deployed item DOES show up in vra. for those who are new to DynamicTypes, you have to bind the result of the DynamicTypesManager.getObject method to an out variable that represents the DynamicTypes Type you use. The following is a scriptable task that sets outitem to the result of the DynamicTypesManager.getObject method. outitem represents the DynamicTypes Type testItem in the namespace test.
testItem2= Server.findForType("DynamicTypes:test.testItem", "testFolder" + "/" + "testItem");
System.log("testItem2 : " + testItem2);
System.log("testItem2.id: " + testItem2.id);
testItem = DynamicTypesManager.getObject("test", "testItem", testItem2.id);
System.log("testItem2.id: " + testItem.id);
item=testItem;
outItem=testItem;
System.log ("testItem2 :" + testItem2);
System.log ("outItem :" + outItem);
System.log ("item :" + item);
finally a few links that helped me:
a good overview: https://www.vcoteam.info/articles/learn-vco/281-enabling-vcloud-
a detailed implementation: https://www.vcoteam.info/articles/learn-vco/323-how-to-create-a-microsoft-dns-dynamic-types-plug-in.html
t.
See if you are synchronizing with the esxi.
Run this command (windows). Check your ntp server is the esxi.
>net time
In the vSphere web client
Actions > Compatibility > Upgrade VM Compatibility....
Have a look at one of my screenshots above. This is unfortunately not an option, because the "Actions" button is grayed out.
How old is this VM that it has the HW version set so low??
I do not remember that. It was installed when ESXi 5.1 was the newest version, so most likely 2013. I have subsequently updated to ESXi 6.0 (through USB installation) without any problems whatsoever. I was also using the native Windows vSphere client app until today. Right now I have updated to 6.7 and problems appeared.
Here is a document talking about the hardware version upgrade: VMware Knowledge Base
Have a look at one of my screenshots above. This is unfortunately not an option, because the "Compatibility" button is grayed out.
Thank you.
Anyway, please follow the upgrade steps again until step 4, but replace the command with the one below, and post the output.
Thanks, here is the output:
Btw. some of those "VIBs Removed" may possibly be my test attempts that I have installed to make it work. I am just mentioning it so that we will not stuck on them while thinking that this is the actual problem (e.g. xAHCI from front.de, locker tools).
What about vmfs not being upgraded issue? Perhaps I should do that manually using SSH command.
[root@ESXi:~] esxcli storage vmfs upgrade -l Datastore
Cannot find VMFS volume with label Datastore
[root@ESXi:~] esxcli storage core path list
sata.vmhba64-sata.0:0-naa.50014ee6567fa232
UID: sata.vmhba64-sata.0:0-naa.50014ee6567fa232
Runtime Name: vmhba64:C0:T0:L0
Device: naa.50014ee6567fa232
Device Display Name: Local ATA Disk (naa.50014ee6567fa232)
Adapter: vmhba64
Channel: 0
Target: 0
LUN: 0
Plugin: NMP
State: active
Transport: sata
Adapter Identifier: sata.vmhba64
Target Identifier: sata.0:0
Adapter Transport Details: Unavailable or path is unclaimed
Target Transport Details: Unavailable or path is unclaimed
Maximum IO Size: 32768
sata.vmhba0-sata.0:0-naa.50014ee260e467d1
UID: sata.vmhba0-sata.0:0-naa.50014ee260e467d1
Runtime Name: vmhba0:C0:T0:L0
Device: naa.50014ee260e467d1
Device Display Name: Local ATA Disk (naa.50014ee260e467d1)
Adapter: vmhba0
Channel: 0
Target: 0
LUN: 0
Plugin: NMP
State: active
Transport: sata
Adapter Identifier: sata.vmhba0
Target Identifier: sata.0:0
Adapter Transport Details: Unavailable or path is unclaimed
Target Transport Details: Unavailable or path is unclaimed
Maximum IO Size: 32768
sata.vmhba1-sata.0:0-naa.5000c5004f06c948
UID: sata.vmhba1-sata.0:0-naa.5000c5004f06c948
Runtime Name: vmhba1:C0:T0:L0
Device: naa.5000c5004f06c948
Device Display Name: Local ATA Disk (naa.5000c5004f06c948)
Adapter: vmhba1
Channel: 0
Target: 0
LUN: 0
Plugin: NMP
State: active
Transport: sata
Adapter Identifier: sata.vmhba1
Target Identifier: sata.0:0
Adapter Transport Details: Unavailable or path is unclaimed
Target Transport Details: Unavailable or path is unclaimed
Maximum IO Size: 32768
Here is the core devices list command output:
Thank you for all of your help!!!!!!!
There's no need to upgrade VMFS. As a side note, an upgrade from VMFS5 to VMFS6 - if you plan to do this at a later time - is no inplace upgrade. You'll have to reformat the datastores.
The vmkernel.log that you've posted contains entries for the 3 disks as being detected as sanpshot LUNs.
Please run
esxcli storage vmfs snapshot list
and if the LUNs show up, you may be able to mount the datastores from the command line by following the steps in https://kb.vmware.com/s/article/1011387
André
here's no need to upgrade VMFS. As a side note, an upgrade from VMFS5 to VMFS6 - if you plan to do this at a later time - is no inplace upgrade. You'll have to reformat the datastores.
You got me at the reformat part, so I will put this out of my head for now.
esxcli storage vmfs snapshot list
Here is the output:
[root@ESXi:/vmfs/volumes] esxcli storage vmfs snapshot list
4fc64015-85243e40-f10f-8c89a57ce0bc
Volume Name: datastore1
VMFS UUID: 4fc64015-85243e40-f10f-8c89a57ce0bc
Can mount: true
Reason for un-mountability:
Can resignature: true
Reason for non-resignaturability:
Unresolved Extent Count: 1
50eeddd9-e71fa408-61be-8c89a57ce0bc
Volume Name: datastore2
VMFS UUID: 50eeddd9-e71fa408-61be-8c89a57ce0bc
Can mount: true
Reason for un-mountability:
Can resignature: true
Reason for non-resignaturability:
Unresolved Extent Count: 1
564e1a27-c0cebf32-54f2-6805ca128dcc
Volume Name: WD Red NAS 6 Tb storage media
VMFS UUID: 564e1a27-c0cebf32-54f2-6805ca128dcc
Can mount: true
Reason for un-mountability:
Can resignature: true
Reason for non-resignaturability:
Unresolved Extent Count: 1
and if the LUNs show up, you may be able to mount the datastores from the command line by following the steps in https://kb.vmware.com/s/article/1011387
I had a look and tried to figure out what command should I put in there. It worked!!!!
I now have 2 of 3 datastores in my vSphere web app, but the last one did not worked. Perhaps I should use a different syntax?
[root@ESXi:/vmfs/volumes] esxcli storage vmfs snapshot mount -l datastore1
[root@ESXi:/vmfs/volumes] esxcli storage vmfs snapshot mount -l datastore2
[root@ESXi:/vmfs/volumes] esxcli storage vmfs snapshot mount -l WD Red NAS 6 Tb storage media
Error: Invalid option Red
Usage: esxcli storage vmfs snapshot mount [cmd options]
Description:
mount Mount a snapshot/replica of a VMFS volume.
Cmd options:
-n|--no-persist Mount the volume non-peristently; the volume will not be automounted after a restart.
-l|--volume-label=<str>
The VMFS volume label of the snapshot to mount.
-u|--volume-uuid=<str>
The VMFS volume uuid of the snapshot to mount.
Edit: I have added "" and even the last one worked!
Thanks for the help.
I would like to increase the system hard drive data space and not one of my virtual hard drives.
How can I assign more data space to the system through vSphere web client or SSH, please?
I have tried to search online, but the only thing I always found is how to increase the virtual hard drive data size which is not what I need.
Perhaps this is burried somewhere between Managed -> Advanced settings configuration options? If so then what option exactly should I change?
Also it might be possible that the space which is not used by virtual hard drives is subsequently being used by ESXi itself and I do not need to do anything? If yes then this is strange, because I sometimes got an error (via SSH) that it is out of space.
Thanks in advance.
I'm not aware of an option to resize the system partitions.
However, this may be caused by large log files (in this case you may want to check the logs to find out, whether there's something wrong).
What you can do, is to create a Scratch location (i.e. a folder) on one of the datastores, and configure it as shown in https://kb.vmware.com/s/article/1033696
André
Hello andvm,
It is almost surely not 1MB-aligned if multiple decimals as this is only going to display a certain number of these in the GUI and in reality probably decimals all the way down.
You can align this by extending the vmdk to the next GB e.g. if it is showing as 1000.123534766345GB then make it 1001GB.
Do note that this may not be the cause of why it won't SvMotion but definitely worth ruling out.
Which vmdk Objects are not 1MB-aligned can be checked via CLI using this script a colleague of mine created:
# ls -lah /vmfs/volumes/vsan*/*/*[!ctk].vmdk | sed 's/ */ /g' | cut -d " " -f 10- | while read line; do size=$(cat "$line" | grep RW | awk '{print $2}'); if [ $(($size % 1048576)) -eq 0 ]; then echo "ALIGNED: $line is $size bytes."; else echo "NOT ALIGNED: $line is $size bytes."; fi; done
Bob
Dear all,
I have ESXi 6.7 and h61ma-e35 (b3) MB. It has 2x ASMedia ASM1061 SATA 6Gb/s and 4x 3Gb/s Intel ports.
I would like to use those 6 Gb/s ports, but ESXi does not detect them. It did not worked on previous versions as well.
I have tried the following:
esxcli software vib install -d http://vibsdepot.v-front.de -n sata-xahci
Even after the restart it does not work and ESXi still does not detect the hard drive that is connected to such ASMedia port while Intel ports work fine.
Any ideas, please?
Thank you.
I want to run Microsoft Flight Simulator 2000 Professionell in Windows 98 SE put when i start Flight Simulator 2000 it says Microsoft Flight Simulator 2000 is an ilegal operation. Can someone help.
i don't think ovftool exists on 4.1
I could use "converter" I guess, may try that.
Rob
