one more quesiton, is it possible to change the MTU for multiple vmkernels at the same time? esxcfg-vmknic -m 9000 -s s-vsm-02 -v 265 <this works for one at a time but I have hundreds of dvpo...
See more...
one more quesiton, is it possible to change the MTU for multiple vmkernels at the same time? esxcfg-vmknic -m 9000 -s s-vsm-02 -v 265 <this works for one at a time but I have hundreds of dvports that I need updated.
Is it possible to change the MTU once a host is attached to a cisco nexus and using distributed switching? How can I change this to MTU 9000 for vmnic01 and vmnic1? DVS Name Num Ports ...
See more...
Is it possible to change the MTU once a host is attached to a cisco nexus and using distributed switching? How can I change this to MTU 9000 for vmnic01 and vmnic1? DVS Name Num Ports Used Ports Configured Ports MTU Uplinks s-grnvsm-02 256 46 256 1500 vmnic1,vmnic0 DVPort ID In Use Client 5440 1 vmnic0 5441 1 vmnic1 5442 0 I have sucessfully changed the vmkernels but would also like to change the vswitch MTU size as well. BTW..I am using ESXi 4.1 U1.
Does anyone know if NetApp has a best practice guide for setting up the SWAP (virtual and guest swap) datastore in regards to thin provisioning? I know vmware has a best practice stating this: ...
See more...
Does anyone know if NetApp has a best practice guide for setting up the SWAP (virtual and guest swap) datastore in regards to thin provisioning? I know vmware has a best practice stating this: Taken from page 28 of the vSphere5 Best Practice Guide: Regardless of the storage type or location used for the regular swap file, for the best performance, and to avoid the possibility of running out of space, swap files should not be placed on thin-provisioned storage.
Have you had to move it move than 9 times? Figure 2 Core network scenario Note A KMS host can be installed on a virtual machine, but select a virtual machine that is unlikely to be m...
See more...
Have you had to move it move than 9 times? Figure 2 Core network scenario Note A KMS host can be installed on a virtual machine, but select a virtual machine that is unlikely to be moved to a different host computer. If the virtual KMS host is moved to a different host computer, the operating system detects the change in the underlying hardware, and the KMS host must reactivate with Microsoft. KMS hosts can activate with Microsoft up to nine times. http://technet.microsoft.com/en-us/library/dd878528.aspx
crazy a$$ thing sat at the failure screen for over 3 hours so I got tired and did a CTRL-C and that killed the dialog box and now the installation is moving forward. Not sure what it did or didn'...
See more...
crazy a$$ thing sat at the failure screen for over 3 hours so I got tired and did a CTRL-C and that killed the dialog box and now the installation is moving forward. Not sure what it did or didn't do but at least the progress bar is moving now. BTW, the DBA stated SQL was idle during that whole process. Looks like everything is good. It finally finished.
I have a few backups but I do not think I should have keep the option to preserve events and tasks. O well gues I will wait and see what happens. I am still waiting on the DBA to come back to m...
See more...
I have a few backups but I do not think I should have keep the option to preserve events and tasks. O well gues I will wait and see what happens. I am still waiting on the DBA to come back to me.
I am going from 2.5 to 2.5 U4 and it has been running over an hour and I am starting to get concerned. So even with all those failure messages yours finally did finish?
troberts can you debunk what RParker is stating. troberts do you have any supporting documentation to back up your claim that: VMFS 3.31 in 3.5 introduced a distributed locking optimizati...
See more...
troberts can you debunk what RParker is stating. troberts do you have any supporting documentation to back up your claim that: VMFS 3.31 in 3.5 introduced a distributed locking optimization - optimistic locking. Basically, the actual acquisition of on-disk locks (involving SCSI reservations) is postponed as late as possible in the life cycle of VMFS metadata transactions. Doing so allows the number and duration of SCSI reservations to be reduced, thereby reducing their impact on VM I/O and VMFS metadata I/O originating from other hosts that share the volume. You may see the message - Optimistic Lock Acquired By Another Host - it means that a lock which was held optimistically (not yet acquired on-disk) during a transaction was found to have been acquired on-disk by a different host. In this case, we simply abort and retry the transaction.
Do you have an article you can reference? We have many issues with SCSI reservations using the NetApp Filers and Cisco switches and do not have a resolution to why.
I had the same problem. It must have something to do with the customization file and the R2 template. I was able to deploy a virtual machine if I did not use my old customization file.
To get mine back I did this: First step is to restart the service management on the host where your templates are stored. - \[root@hou-vm01 root]# service mgmt-vmware restart Remove all t...
See more...
To get mine back I did this: First step is to restart the service management on the host where your templates are stored. - \[root@hou-vm01 root]# service mgmt-vmware restart Remove all the orphaned templates from inventory Restart your client Disconnect/reconnect to your VM Host if necessary Browse the datastore where your templates are kept Right click on the .vmtx file and click Add to Inventory You can use the same name as it was before You are done!