iSCSI without Jumbo frames for 15 Virtual Machines

Similar Questions

• Setting Options such as Hotplug for all virtual machines

  Hello!

  I have about 5 esxi hosts 5 and about 50 virtual machines

  Unfortunately I forgot to select some options like activate the plug-in memory and cpu hot

  I have 2 questions

  1 can I do this without turning off the machine

  2. How do I make a few options like this (or for example another option as vmtools update during the feeding cycle) for all virtual machines in my environment

  It's too much time to go to all virtual machines and turn them off and turn on these options

  Thank you very much

  These features must be enabled before the virtual machine is running.  So, you will need to turn them off and then use something like powercli to enable the features and turn them back on.

  Here is an example on how to do it with powercli: http://ict-freak.nl/2009/10/05/powercli-enabledisable-the-vm-hot-add-features/

  -KjB

• Can join a Cluster of storage disk out of Maintenance DTS Mode to set up the profiles for a virtual machine storage policies?...

  Can join a Cluster of storage disk out of Maintenance DTS Mode to set up the profiles for a virtual machine storage policies?...

  
  IE can you define the rules of affinity DTS depending on how the rules of storage of profiles are configured for a virtual machine?

  In my mind it seems there is disconnect from the DTS and storage profiles.

  Thank you.

  = NOTE =.

  My lab at home, 2 organizes running ESXi 5.0

  Dv01 has

  Of startup vmfs 7200 RPM 160 G = dv01-BOOT

  Vmfs 1 TB 7200 RPM = VM02-VMFS

  VM02 has

  Of startup vmfs 7200 RPM 160 G = VM02-BOOT

  Vmfs 1 TB 7200 RPM = VM02-VMFS

  Vmfs 5900 RPM 2 TB = VM02-TV01

  I have (3) facility profiles of storage using 'User-defined storage Capablity' as shown below:

  (160 @ 7200 RPM SATA) boot > Boot

  Fast (160 7200 RPM SATA and 1 TB @ 7200 RPM SATA) > fast

  Slow (2 TB @ 5900 RPM SATA) > slow

  Then, I set up a storage Cluster with my local disks on dv01 (only to date)

  LocalVM disc dv01-BOOT and dv01-VMFS disk of the 'cluster of storage.

  I have a computer virtual called DC01 (HardDisk1) want to live on 'Boot' profile storage drive
  His "Non-compliant" poster according to the storage profile, it should run on drive 'boot' on dv01

  To get to this point, I put the StorageCluster in Mode of Maintenace 'DTS' and forced a sVmotion of all virtual machines off dv01-BOOT

  No disks are IO or claim of space.

  But once I take the 'DTS Maintenacne mode' STARTUP dv01 floppy is now get the DTS to return him to satisfy the storage profile (rule) I install... IE do the 'storage profile' VM complient (without doing a few externall API, the PS script or the 3rd party software calls)... ??

  Seems weird it is (or may be) such disconnection of a memory of the profiles and the StorageClusters and the DTS?

  Thank you...

  At this point, I think that storage DRS and storage profiles are two technologies to separate and work independently, but what you suggest is a great idea-

• ESXi 5 - Longmode is disabled for this virtual machine.

  Hello

  I installed ESXi 5.0.0 469512 on a Dell Optiplex 755 with Intel Core 2 Duo E8400 processor @ 3 .00GHz with 4 GB of RAM. In the BIOS (version A21), I have the following options enabled:

  Performance-

  Virtualization: on

  VT for direct i/o: on

  Execution of trust: on

  Security-

  TPM security: on

  Activation of the TPM secure: assets

  Execute Disable: on

  I am unable to run any 64-bit OSs. For example, when I try to start vMA VM 5.0, I get the following Message from the Virtual Machine:

  "This virtual machine is configured for 64-bit operating systems. However, the 64-bit mode is not possible.

  Longmode is disabled for this virtual machine.
  For more information, see http://VMware.com/info?id=152 .
  Continue without 64 bit support? »

  I ran the "processor check for 64-bit compatibility ' and if confirmed I can run 64-bit guest OS.

  I tried to add vhv.allow = "TRUE" to/etc/vmware/config, but it made no difference.

  In the vmware.log file is that it makes meantion 'virtualization software is incompatible with the long mode on this platform. Disabling longmode. "I have attached the full logfile for details.

  Any help will be greatly appreciated.

  Thank you Paul.

  According to the log file

  Frequent: MSR 0x3a = 0x3--> currently '0011', should be 'x 1 x 1 "'.

  VT - x is not enabled (bit 0 + 2 required)

  There were other debates, where that allows "Trusted execution" cause problems. I "suggest that you configure the settings of the BIOS as follows:"

  Performance-

  Virtualization: on (assuming it's VT - x)

  VT for direct i/o: Off (unless you need it)

  Execution of trust: Off

  Security-

  The TPM secure security: Off

  Activation of the TPM secure: inactive

  Execute Disable: on

  After you change the settings, you will need to power cycle the system.

  André

• List of the files in the data store for the virtual machine

  Hello

  How to list the files of data store for the virtual machine? I can't find reference to the command.

  Thank you

  If you have installed vCLI and vSphere SDK for Perl, you have extra utilities on top of what is there with the vCLI, take a look at this list: http://www.vmware.com/support/developer/viperltoolkit/viperl40/doc/vsperl_util_index.html

  A script that can help with the list of files to store data for a given virtual machine is dsbrowse.pl

  Here is an example:

  [vi-admin@scofield ~]$ /usr/lib/vmware-vcli/apps/host/dsbrowse.pl --server himalaya.primp-industries.com --username root --name dlgCore-iSCSI.test
  
  Information about datastore : 'dlgCore-iSCSI.test'
  ---------------------------
  Summary
   Name             : dlgCore-iSCSI.test
   Location         : /vmfs/volumes/4a26f505-02dfd8a4-6867-003048d9586a
   File system      : VMFS
   Maximum Capacity : 15.75 GB
   Available space  : 11.654296875 GB
  
  Hosts associated with this datastore.
   himalaya.primp-industries.com
  
  Virtual machines on this datastore.
   None
  
  Templates on this datastore.
   None
  
  Datastore Folder Structure.
   Folder Path: '[http://dlgCore-iSCSI.test|http://dlgCore-iSCSI.test]'
   Files present
    testagain
    testlab-1
    testlab-2
    testlab-3
    testlab-4
    testlab-5
    testlab-6
    testlab-7
    testlab-8
    testlab-9
    testlab-10
    testlab-11
    testlab-12
    testlab-13
    testlab-14
    testlab-15
  
   Folder Path: '[http://dlgCore-iSCSI.test|http://dlgCore-iSCSI.test] testagain'
   Files present
    testagain.vmdk
    vmware.log
    testagain.nvram
    vmware-70.log
    vmware-65.log
    vmware-66.log
    vmware-68.log
    vmware-67.log
    vmware-69.log
    testagain-flat.vmdk
    testagain.vmx
    testagain.vmxf
    testagain.vmsd
  

  =========================================================================

  William Lam

  VMware vExpert 2009

  Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

  repository scripts vGhetto

  VMware Code Central - Scripts/code samples for developers and administrators

  150 VMware developer

  Twitter: @lamw

  If you find this information useful, please give points to "correct" or "useful".

• SRM 5.5 - vSphere replication - error: impossible to reverse the replication for the Virtual Machine. A snapshot operation cannot be performed

  Hi all, we have just run a test DR failover of a couple of virtual machines in our protected our failover site and all site swung perfectly, two virtual machines came online and all applications work well. However when we cam to r-eprotect machines virtual, we get some errors.

  One of the virtual machines seems to have lived the reprotect end process, it is still running, but has not moved to 89% for some time. The virtual machine has a couple of grand (a little less than 2 TB) VMDK. slow progress is just a consequence of the large VMDK?

  More worrisome is the virtual machine which don't reprotect at all. It generates an error whenever I click on the "Restore" button (error: impossible to reverse the replication for the Virtual Machine.) A snapshot operation can not be performed).

  
  Does anyone have any ideas as to the cause?

  Thanks in advance for any help.

  Andy

  Finally got to the bottom of this. The issue was that reprotect SRM work was trying to dispel any snapshots that were taken on the computer object virtual destination in VMWare, but could not clean snapshots.

  The reason why snapshots would not consolidate was because it was snapshots of temporary VEEAM who in fact any snapshot file listed in the VSAN data store. So when we looked through the browser data store, no snapshot file existed in the virtual computers folder. Trying a manual removal also failed.

  To fix this, we created a snapshot of the virtual machine in the original data center (note is the engine to the bottom of the virtual machine), this effect was to get rid of the 'fade' snapshot that was visible in the Snapshot Manager that VEEAM backup had left behind. Once this had disappeared, the reprotect back to DCA worked perfectly.

• A suspended snapshot could not be created for the virtual machine (DC) ha-data center (DC) \vm\VMware vCenter Server Appliance.

  Hello gentlemen,

  I can not only save this virtual machine with Backup Exec 2014 for a long time.

  They are there was no snapshot in snapshot Manager.

  Could you help me?

  A suspended snapshot could not be created for the virtual machine (DC) ha-data center (DC) \vm\VMware vCenter Server Appliance.

  V-79-57344-38260 - failed to create a snapshot of the virtual machine. The virtual machine is no longer exist, or may be too busy to pause to take the snap.

  A suspended snapshot could not be created for the virtual machine (DC) ha-data center (DC) \vm\FRPA111PRIM01.

  V-79-57344-38299-\vm\FRPA111PRIM01 ha-data center (DC) VMVCB::\\192.168.204.42\VCGuestVm\ (DC). To try to take a snapshot of a virtual machine failed because it could not be suspended in a file system.

  Hello

  I found the solution.

  I disabled the JOB BE general relativity.

  and the host where the virtual machine belong was not the right time. No Ntp server has been configured.

  I did and now there works.

  I think that the problem can come from this.

• Definition of levels of booking for a virtual machine

  The vcloud usage meter says:

  NET points = (vGB hours X points per 1 GB reserved RAM) / hours per month

  
  

  A month calendar of 30 days, a service provider uses the vCloud package provider services - first Edition to configure its virtual machine with 16 vGB for 15 days and 48 vGB 15 days remaining. The level of booking for the virtual machine is set to 75 percent for the whole month.

  15 days x 24 hours x 16 vGB x 0.75 = 4 320 hours of vGB

  15 days x 24 hours x 24 vGB (vGB 48 x 0.75 but capped at 24 GB) = 8 640 hours of vGB

  Total number of hours of vGB = 12 960 hours of vGB

  Total points = 12 960 vGB hours ÷ 720 hours / month x 7 points (for Prime Minister) = 126 points

  Where "the level of booking' for a virtual machine?  Is - this talk on VM bookings each parameter in vCenter Server, or do something to the extent of consumption vCloud himself?

  Hello. The reservation level is set for each virtual machine, using a vSphere Client or API.

• VCenter shows a network for a virtual machine that is not associated with any host

  I have a win2k3 VM who at one point had a network assigned to him called "MONITORING".  This network is configured is no longer in the ESXi (5.5) environment.  The virtual machine is connected to a network called "PRD-SURVEILLANCE" which is correct.  It's not really cause a problem, but I can't find a way to get rid of the object of MONITORING network.

  In VCenter MONITORING networks has a VM of 1 meter, the number of hosts of 0.  I also see it in the VM - dialog box, change the settings, but there is no option to remove it.  Profile Image to the virtual machine is version 10 so I can't use the old Client of VI to try to remove it.  I have checked each host and do not see this listed network object.

  I tried to restart the VM, it migration between hosts, changing its network of SURVEILLANCE of PRD to another network and vice versa and close - remove NIC and add a new card network.  MONITORING legacy network still appears in the config.

  For the virtual machine's .vmx file shows that the correct network: ethernet0.networkName = 'RDP-ANALYSIS '.

  Any suggestions on how I can remove the artifact of MONITORING network?

  The virtual machine has a preview that was created at the time where the MONITORING network was still affected?

  André

• How to find the age of a child and snapshot number snapshot for a virtual machine.

  Hi all

  How to find the age of a snapshot for a virtual machine child count and snapshot.

  This code snippet should help... Assuming that you have the following entries:

  VM (VC:VirtualMachine)

  snapshot (VC:VirtualMachineSnapshot)

  System.log("====== Snapshot details for VM: "+snapshot.config.name+" ======");
  var snapshotTrees = vm.snapshot.rootSnapshotList;
  System.log("Snapshot Tree Count: "+snapshotTrees.length);
  for each (snapshotTree in snapshotTrees){
      showSnapshotInfo(snapshotTree, snapshot);
  }
  
  function showSnapshotInfo(snapshotTree, selectedSnapshot){
      if(selectedSnapshot == snapshotTree.snapshot){
          System.log("====================");
          System.log("Name: "+snapshotTree.name);
          System.log("Id: "+snapshotTree.id);
          System.log("Description: "+snapshotTree.description);
          System.log("createTime: "+snapshotTree.createTime);
          System.log("quiesced: "+snapshotTree.quiesced);
          System.log("replaySupported: "+snapshotTree.replaySupported);
          System.log("backupManifest: "+snapshotTree.backupManifest);
          System.log("snapshot id: "+snapshotTree.snapshot.id);
          System.log("state: "+snapshotTree.state.value);
          var childSnapshotList = snapshotTree.childSnapshotList;
          if(childSnapshotList != null){
              System.log("childSnapshotList length: "+snapshotTree.childSnapshotList.length);
          }
          System.log("");
      }
      if(snapshotTree.childSnapshotList != null){
          System.log("Children found: "+snapshotTree.childSnapshotList.length);
          for each (childSnapshotTree in snapshotTree.childSnapshotList){
              showSnapshotInfo(childSnapshotTree, selectedSnapshot);
          }
      }
  }
  

  During the passage of one of my virtual machines, here is an example of output I get:

  [2014-06-12 15:19:21.493] [I] Snapshot Tree Count: 1
  [2014-06-12 15:19:21.493] [I] ====================
  [2014-06-12 15:19:21.494] [I] Name: before upgrade to 5.0.1
  [2014-06-12 15:19:21.494] [I] Id: 31
  [2014-06-12 15:19:21.494] [I] Description:
  [2014-06-12 15:19:21.495] [I] createTime: Mon Mar 19 2012 13:48:57 GMT-0400 (EDT)
  [2014-06-12 15:19:21.495] [I] quiesced: false
  [2014-06-12 15:19:21.495] [I] replaySupported: null
  [2014-06-12 15:19:21.495] [I] backupManifest: null
  [2014-06-12 15:19:21.496] [I] snapshot id: snapshot-83
  [2014-06-12 15:19:21.496] [I] state: poweredOff
  [2014-06-12 15:19:21.496] [I] childSnapshotList length: 1
  [2014-06-12 15:19:21.496] [I]
  [2014-06-12 15:19:21.497] [I] ====================
  [2014-06-12 15:19:21.497] [I] Name: Before 5.1 upgrade
  [2014-06-12 15:19:21.497] [I] Id: 36
  [2014-06-12 15:19:21.497] [I] Description:
  [2014-06-12 15:19:21.498] [I] createTime: Fri Sep 21 2012 21:59:58 GMT-0400 (EDT)
  [2014-06-12 15:19:21.498] [I] quiesced: false
  [2014-06-12 15:19:21.498] [I] replaySupported: null
  [2014-06-12 15:19:21.498] [I] backupManifest: null
  [2014-06-12 15:19:21.499] [I] snapshot id: snapshot-84
  [2014-06-12 15:19:21.499] [I] state: poweredOff
  [2014-06-12 15:19:21.499] [I] childSnapshotList length: 1
  [2014-06-12 15:19:21.499] [I]
  [2014-06-12 15:19:21.500] [I] ====================
  [2014-06-12 15:19:21.500] [I] Name: Before Named Instance
  [2014-06-12 15:19:21.500] [I] Id: 37
  [2014-06-12 15:19:21.501] [I] Description:
  [2014-06-12 15:19:21.501] [I] createTime: Mon Nov 11 2013 13:40:46 GMT-0500 (EST)
  [2014-06-12 15:19:21.501] [I] quiesced: false
  [2014-06-12 15:19:21.501] [I] replaySupported: null
  [2014-06-12 15:19:21.502] [I] backupManifest: null
  [2014-06-12 15:19:21.502] [I] snapshot id: snapshot-236
  [2014-06-12 15:19:21.502] [I] state: poweredOff
  [2014-06-12 15:19:21.502] [I]
  

• change default location for new virtual machines programmatically

  I know that you can change the default location for new virtual machines through the preferences GUI, but I want to be able to change it for all those who use VMWare Workstation in my company, so that it is more advanced to the personal folder of the user.

  Where exactly is stored?  I don't see in the registry.

  Thank you!

  WS does not use the registry to store settings.

  Set the path in UNK for each user:
  prefvmx.defaultVMPath = "F:\. »

• Change tracking (CTK) block is supported for this virtual machine, but was refused. This will increase the CPU proxy and consumption of IOP.

  I have problems with a client of VMware image-level in an EMC Avamar backup.  So far, we have not been able to find information about this message in the backup log file.  It is originally the backup to take a very long period of time (on average 10-11 hours).

  2014-02-28 14:20:57 avvcbimage < 14681 > Info: change tracking (CTK) block is supported for this virtual machine, but was refused. This will increase the CPU proxy and consumption of IOP.

  We cannot determine why CBT is "denied".  Has anyone here run across this issue before or seen any other type of backup VMware image have denied CBT?

  Everything I checked watch that CBT is successfully activated since the file vmx for the customer to the Avamar config.

  ESXi host is Enterprise Plus 4.1.0 260247

  After spending some time on this issue, the ultimate resolution withdrew the Avamar vm and then add it again.  After that, CBT began to work properly.  It seems that there is a parameter that has been 'stuck' pertaining to this virtual machine that wasn't behaving properly.

• Disable the clichés for individual virtual machines?

  Hi all

  Is it possible to disable support for snapshot for individual virtual machines, perhaps via a parameter for it?  Or is the closest answer you to put all its virtual disks in independent mode?  Try to see how to better meet the requirements that certain suppliers impose that the VM/device does not catch instant and thought that the best solution is to disable the feature for the specific VM (s) only.  Thank you!

  You can watch the snapshot.maxSnapshots configuration setting. See KB 1031280 for more information.

• 'Disable the alarm action' for a virtual machine

  Hello

  I want to disable all actions for a virtual machine alarm, while I have to disable FT to clone a virtual machine. My script are ready for cloning but I have a solution to disable the actions of alarm for a virtual machine via PowerCLI to can´t. Someone knows a solution for PowerCLI 5.1R1?

  Thank you

  Michael

  -Entity parameter requires an inventory of PowerCLI as value object and does not have the names. You can try it like this:

  Get-AlarmActionState-entity (Get-VM-name VMTEST1) - Recurse: $false

• List of data store, SpaceProvisioned, Spaceused for multiple virtual machines

  Hello

  I want to list the data store, the SpaceProvisioned, the Spaceused for several virtual machines.

  I wrote the following lines, but this didn t work:

  $vms = get - VM v998spwmv10175n
  {foreach ($vm to $vms)
  $vmname = $vm. Name
  $vmdiskprovisioned = $vm. ProvisionedSpaceGB
  $vmdiskused = $vm. UsedSpaceGB
  $vmdiskpath = get-disk hard - VM $vm | Select file name
  Select @{N = "VMname"; E = {$vmname}},
  @{N = "VMDiskPath"; E = {$vmdiskpath}},
  @{N = "VMDiskProvisioned"; E = {$vmdiskprovisioned}},
  @{N = "VMDiskUsed"; E = {$vmdiskused}} | Format-Table

  }

  What wrong with it? I'm away right?

  THX in advance

  Chakoe

  The following script lists each vDisk in a separate line. The VMDiskProvisioned and VMDiskUsed properties are always those of the virtual machine.

  $vms = Get-VM v998spwmv10175n
  & {foreach ( $vm in $vms ) {
    $vmname = $vm.Name
    $vmdiskprovisioned = $vm.ProvisionedSpaceGB
    $vmdiskused = $vm.UsedSpaceGB
    foreach ($HardDisk in (Get-Harddisk -VM $vm)) {
      $HardDisk | Select-Object -Property @{N="VMname"; E={$vmname }},
            @{N="VMDiskPath"; E={$HardDisk.FileName}},
            @{N="VMDiskProvisioned"; E={$vmdiskprovisioned }},
            @{N="VMDiskUsed"; E={$vmdiskused  }}
    }
  }}