SCSI ID shows white for RDM virtual machine disks

Similar Questions

• The maximum for a virtual machine disk size

  Hello

  Can I create a disk to a virtual machine that is larger then 2 TB?

  On a physical box, you convert dynamic disks and their band... but I think VMware recommend snot of dynamic disks.

  Thanks in advance...

  Hello

  2 TB is the max and also the MAX for several operating systems. If for any reason any if you need then you will need to do a bunch of multiple VMDK.

  For more information about the maximum size please see: http://kb.vmware.com/kb/1003565

• 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é

• RDM mapping for multiple virtual machines

  Hi all,

  I created and associated with a 6 GB LUN me ESXi host 5.

  Now I need map that drive more then a VM under this host, I managed to add the first virtual machine disk (via 'change settings' > 'Add' > 'hard drive' > "raw device mapping"), but when I try to do the same thing to another virtual machine, I do not see the disk I used befor in the list "select target lun.

  So, is it possible to connect this same disk as raw device to VM, then one more?

  -Thanks!

  Depending on your configuration (Cluster-in-a-box, Cluster-across-boxes) you may need to configure the mode of virtual SCSI controller properly. Please take a look at http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-mscs-guide.pdf?lang=en for more details.

  André

• RDM for several virtual machines on the same LUN

  Hi, I have a requirement for multiple virtual machines to have access to the same LUN filestore. I think create ROW for each virtual computer to the LUN. I wanted to ask if this is possible and if someone put in place before?

  Are there issues making this record to file/san locks?

  Thank you

  Once you add the raw device map to a virtual computer, you can not add it to each other as well.

  It would satisfy your requirement to add to a virtual computer, assign it a drive name or folder, then that spread out and have another card SMV a drive to it?  Depending on what you're trying to do, which can satisfy because it will work.

  Rich

• Performance metric power group do not show anything on the virtual machine

  Hello

  I have a small question about the metrics of power Group found on the side of the virtual machine in the charts of perf ahead. It shows only 0 for usage.

  If I'm in the same group of metric on the host, it shows the values.

  do you know why it does not show anything on the virtual machine. is a group of metric that is not usable for virtual machines?

  Thank you very much

  Eric

  You have a support contract in place? Otherwise, I can connect this with them for an official answer... If that helps?

• Maximum number of virtual disk for a virtual machine in vSphere 4.1

  I read the maximum record rate and see that the maximum number of virtual disk is 16 for FT.

  I have the same document I seem not to be able to see the number max of virtual disk that can be taken in charge for a virtual machine.

  The number will be the same as the number of LUNS per host which is 256?  I know the max is for the host, but that be will come the number of Director to the total number of virtual disk that can be supported in the virtual machine?

  In fact, in a logic unit number, we can have more than one data store that can be mapped to a virtual disk.

  I'm confused.

  Thank you and have a nice week,

  Anthony.

  If I am not mistaken, you can attach up to 60 virtual disks to a virtual machine. 15 for each of the 4 virtual SCSI controllers.

  André

• WAIT % - % IDLE, what is the average for a virtual machine?

  I did some research on performance of VM problems and worked with the media to see that there is maybe a bottle neck IO that occur with a virtual VMware machine I have performance problems on. The technician found that the WAITING % - % IDLE on average for this virtual machine is around 200%. The tech said it was abnormally high. I forgot to ask her what was normal but wanted to put a post to see if some people out there know what they are on average. What is an average number of see? I have the system done nothing right now and I see 579% waiting and 372% IDLE. The technology has been able to confirm that no IO queue was occurring in the VMkernel or on the HBA controller.

  Some average % positions would be useful. Thank you.

  gdewulf18480 wrote:

  Supposibly the amount of time in a State of waiting for I/O is the WAIT - IDLE % difference. I was wondering if anyone had the numbers for this feeling. Is there anyone with some of them?

  Q: How will I know the VCPU world waiting for I/O events?

  A: WAIT - % IDLE % can give you an estimate on how much time processor is spent waiting for I/O events. It is an estimate only, because the world wait perhaps for other than the i/o resources. Note that we should do it only for the worlds of the WWW, not the other kind of worlds. Because the VMM worlds represent the best guest behavior. For the disk i/o, another alternative is to read the disk latency stats that we explain in the drive section.

  WAIT % by itself cannot be used, you must develop and examine the individual vCPU % EXPECTATION values and subtract their idle time.  You can't do it on the initial view of a single line by VM CPU in esxtop.  If technology that you mentioned did not explain it, he doesn't know what it takes.

  I have lots of virtual machines that are never less than 300% when I wait - % idle and I have no problems.

  It is an example, I caught NimSoft server:

  DHSNMS1 100 100 5 192.63 193,80 0.24 0.03 291,44 1.04

  %EST USED (s) 192 - in other words, almost two processors are used 100%

  The %Idle is 1.04% WAIT 291.44 - according to the calculation of waiting idle, I have a super serious problems of e/s past  But this isn't the case, and expanding, I can see that.

  5665 vmware-vmx 100 1 0.09 0.11 100.00 0.00 0.00 0.01

  5667 100 vmassistant.566 1 0.62 0.65 99,63 0.00 0.00 0.00

  5703 100 mks:DHSNMS1 1 0.01 0.01-100.00 0.00 0.00 0.00

  5704 vcpu 100 - 0:DHSNMS1 1 32,35 32.88 67,28 0.28 0.11 67,14

  5705 vcpu 100 - 1:DHSNMS1 1 31,58 32.05 68.11 0.00 67.85 0.12

  So the changed values unfortunately because of ESXTOP bike when you develop... which is annoying, but anyway.  In this you see % waiting is 67 and 68 with another respectively being 3 to 100% (which is normal) and the idle being %, 0, 0, 0, 67 and 67.8.  Doing the calculation on the processors shows a wait - slowed virtually 0 - or very little IO wait past with processors.  But if you add up all the expectations of % and % is idling, you have 434ish, and the 134ish and do the calculation is the difference of 300 - which is the 3 who are always 100%.

  So there is no way we can answer your question, we can only help you to understand how the values should be interpreted.

  Waiting for i/o States almost always go on the disc anyway, it is unlikely, therefore, the network or the user entered, looking at the stats of disc ESXTOP is a much better way to determine if there is a problem of e/s.

• VI Client shows 95% starting a virtual machine but the virtual machine is already up

  VI Client shows 95% starting a virtual machine but the virtual machine is already running and so for a few days. E customer VI is not refreshing or the management console should be cycled/restarted?

  ESXi, correct?

  See this link

  http://www.VM-help.com/ESX/esx3i/ESXi_restart_agents.php

• Fret is disabled for this virtual machine

  Host environment: Windows XP Professional x 64 SP2

  Environment comments: Windows Server 2003 R2 SP2

  Of disk space free hosting environment: 31.1 GB

  Comments environment size the disc: 13 GB (total 20, 7 for free)

  Comments environment size the disc on host drive: 20 GB

  VMWare version: Workstation 6.5.0 build 118166.

  The question:

  I am currently unable to carry out the reduction operation.

  I did a search on google and find a few scenarios:

  • http://communities.VMware.com/thread/113057

  • http://communities.VMware.com/thread/151594

  However, I was not able to solve the problem.

  The full message is as follows:

  Fret is disabled for this virtual machine.  Shrinkage is disabled for linked clones, parents of clones related, préalloués disks, snapshots, and other factors.

  This virtual machine has definitely shrunk in front.  I tried to reinstall VMWare Tools and it does not correct.  I checked that there are no snapshots in the Snapshot Manager.  I also tried as suggested by one of the sons: adding a snapshot and then remove it.  I'm unable to the fret.  Of course, this isn't a linked clone or a parent of a linked clone (do not know how to use them).  How can I tell if it is a pre-allocated disk (I don't think it's, but who knows)?

  On the file system, the looks of the directory as follows:

  • ------& lt; GUID & gt;. vmem.lck

  • \Windows server 2003 Standard Edition.vmdk.lck

  • \Windows server 2003 Standard Edition.vmx.lck

  • & lt; GUID & gt;. vmem

  • VMware - 0.log

  • VMware - 1.log

  • VMware - 2.log

  • VMware.log

  • Windows Server 2003 Standard Edition.nvram

  • Windows Server 2003 Standard Edition.vmdk

  • Windows Server 2003 Standard Edition.vmsd

  • Windows Server 2003 Standard Edition.vmx

  • Windows Server 2003 Standard Edition.vmxf

  • Windows Server 2003 Standard Edition - flat hard

  Any help would be appreciated.

  The list of files that you show your virtual disk is pre-allocated (*-flat.vmdk).  As the message says, you will not be able to reduce a drive pré-alloués.

• 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.

• VMX and newspapers for the Virtual Machine

  Hi guys

  I had a virtual machine that is running but view vcenter is inaccessible

  

  take a look at the data store that I see the Virtual Machine lack .vmx file and saves the files, so I already schedule maintenance for my client windows, but I just want to be sure about:

  -Stop VM

  -Remove the inventory

  -create a new virtual machine and add the existing virtual drive

  -Power on VM, everything should be good

  

  Basically follow this KB

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 1002294

  Or should I be worried about the consistency of VMDK?

  Thank you very much

  > Or should I be worried about the consistency of VMDK?

  Less consistency, but more info on missing hard of header/descriptor files! It seems that someone tried to delete files of the virtual machine from the store data, but because of the locks on files that only some files have been deleted. According to the used backup application, you may be able to recover the missing files in the backup. If not, you can for example follow VMware KB: Re-create a missing virtual machine disk descriptor file, or create a new virtual machine in a laboratory environment (with the same disc size, configuration and the name) and allows to download the .vmx and hard descriptor WinSCP example files. If you have enough disk space in the lab, creating thin configured virtual disks and then change the file descriptor (remove ddb.thinProvisioned = '1')

  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]