Anyone who can explain me this multicast filtering mode in vmware vsphere 6?

I'm trying to access a VM on a ESXi machine i've just created. I've set the VM with the specs I desire and have tried to access the console only to get this error:

I've checked multiple sites and at first it was showing an SSL error in the log which i've now resolved by turning that on in the ESXi configuration. My log file is below:

2015-09-07T15:56:47.812+01:00| vmrc| I120: vmdbLayout::Cnx::ConnectMksClient: Connecting via remote MKS

2015-09-07T15:56:47.812+01:00| vmrc| I120: VMClient_ConnectMksClientEx

2015-09-07T15:56:47.812+01:00| vmrc| I120: VMClient_ConnectMksClientEx - trying remote socket connection to 144.76.96.16:902 /vmfs/volumes/55e971d2-81456e92-fdab-6805ca01ab11/vCenter/vCenter.vmx

2015-09-07T15:56:47.812+01:00| vmrc| I120: VMClientConnectSocketEx

2015-09-07T15:57:08.853+01:00| vmrc| I120: CnxOpenTCPSocket: Cannot connect to server 144.76.96.16:902: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

2015-09-07T15:57:08.853+01:00| vmrc| I120: CnxAuthdConnect: Returning false because CnxAuthdConnectTCP failed

2015-09-07T15:57:08.853+01:00| vmrc| I120: CnxConnectAuthd: Returning false because CnxAuthdConnect failed

2015-09-07T15:57:08.853+01:00| vmrc| I120: Cnx_Connect: Returning false because CnxConnectAuthd failed

2015-09-07T15:57:08.853+01:00| vmrc| I120: Cnx_Connect: Error message: Failed to connect to server 144.76.96.16:902

2015-09-07T15:57:08.853+01:00| vmrc| I120: VMClient_ConnectMksClientEx - Remote socket connection failed.

2015-09-07T15:57:08.853+01:00| vmrc| I120: VMClient_ConnectMksClientEx - trying local socket connection to /vmfs/volumes/55e971d2-81456e92-fdab-6805ca01ab11/vCenter/vCenter.vmx

2015-09-07T15:57:08.853+01:00| vmrc| I120: VMClientConnectSocketEx

2015-09-07T15:57:08.853+01:00| vmrc| I120: CnxAuthdConnectPipe: Returning false because we ran out of retries when CreateFileW

2015-09-07T15:57:08.853+01:00| vmrc| I120: CnxAuthdConnect: Returning false because CnxAuthdConnectPipe failed

2015-09-07T15:57:08.853+01:00| vmrc| I120: CnxConnectAuthd: Returning false because CnxAuthdConnect failed

2015-09-07T15:57:08.853+01:00| vmrc| I120: Cnx_Connect: Returning false because CnxConnectAuthd failed

2015-09-07T15:57:08.853+01:00| vmrc| I120: Cnx_Connect: Error message: Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period

2015-09-07T15:57:08.853+01:00| vmrc| I120: VMClient_ConnectMksClientEx - Local socket connection failed.

2015-09-07T15:57:08.853+01:00| vmrc| I120: cui::MKS::OnSetAttachedError

2015-09-07T15:57:08.853+01:00| vmrc| I120: cui::vmrc::DlgMgrImpl: "Unable to connect to the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period"

2015-09-07T15:57:08.868+01:00| vmrc| I120: cui::MKS::OnSetAttachedCompleted

2015-09-07T16:02:20.190+01:00| vmrc| I120: cui::vmrc::VMCnx::Disconnect: Disconnect from MOID "1" on "144.76.96.16:443" while "connected"

2015-09-07T16:02:20.190+01:00| vmrc| I120: cui::vmrc::VMCnx::DoDisconnect: Disconnecting from MOID "1" on "144.76.96.16:443"

2015-09-07T16:02:20.190+01:00| vmrc| I120: VMMgr::CloseVM: closing VM at /vm/#_3C84C10_1/

2015-09-07T16:02:20.190+01:00| vmrc| I120: VMMgr::OnVMDestroyed: cleaning up after destroyed VM at /vm/#_3C84C10_1/

2015-09-07T16:02:20.190+01:00| vmrc| I120: cui::MKS::SetAttached

2015-09-07T16:02:20.190+01:00| vmrc| I120: cui::MKS::OnSetAttachedCompleted

2015-09-07T16:02:20.237+01:00| vmrc| I120: cui::vmrc::VMCnxMgr::EmitConnectionStateSignal: Emitting "disconnected" signal (requested) for MOID "1" on "144.76.96.16:443" - reason 'Disconnection successful.'

2015-09-07T16:02:20.237+01:00| vmrc| I120: cui::vmrc::VMRC::OnActiveVMCnxChanged: Active VMCnx: (none)

2015-09-07T16:02:20.253+01:00| vmrc| I120: vmClientCore::InvokeMgr::Shutdown

2015-09-07T16:02:20.268+01:00| vmrc| I120: Clean exit

Hello Folks,

i'm so much interested to start studying for this certificate but i have no vmware experience , just network experience.

can this certificate be achieved without vmware experience? how long it should take on average to study it ?

Thanks

VMware ESXi 5.5 Enterprise

VMhost Server: Dell PowerEdge R730 Intel Xeon CPU E5-2687W @ 3.10GHz with 767.91 GB memory.

vSwitch1 (Local with no vmnic assigned)

Virtual Machines:  2 MS Windows 2008 R2 with 10 GB LAN nic

    (Both on the same VMhost)

We are planning to implement more of 10 GB networking.

Using the iperf3 network speed test between the two virtual machines (MS Windows 2008 R2), I get up to around 5 GB.

Running the same iperf3 between two virtual machines (Linux OS), I get up to around 8 - 9 GB.

1.  Are any of you able to get around 8 GB speed between 2 MS Window 2008 R2 virtual machines?

2.  Or what is fastest network speed do you get in a MS Windows 2008 R2 virtual machines?

3.  What is the solution or tuning settings?

I even run "iperf3 -s" and "iperf3 -c 127.0.0.1" in one MS Windows 2008 R2 virtual machine, and I still get around 5 GB.

Thank you in advance,

Dean

Hi All,

I am using VMWarePlayer, freebie version, 6.0.7 build-2844087.

I am running windows7 ultimate as the host operating system.

I am an MSDN so I have the MSDN versions of all these things.

I have been using vmware for ages and, quite suddenly, I am getting errors.

I suspect it is the underlying hard drive so let me tell you the symptoms.

It might not be the hard drive...it could be a vmware player problem too.

The log below tells you what is coming out of the log.

However I notice that on the two VMs that I use the most that the virtual disks have grown to 219GB for my win7 and 236GB for my Windows Server 2012 VM. This is very excessive growth since the last backup versions were win7 186gb and 2012 windows server 161GB.

It is not reasonable to add 40GB and 60GB in a few weeks. The last backups were on 2015-08-15.

I have twice run the win7 checkdisk with repair. The underlying disk is 3TB so it takes about 8 hours to do that.

The checkdisk repair does find a bad sector in the win7 machine each time but I think the problem must be different.

Why? Because I have never had a problem on the windows server 2012 disk. And I have not used it for a couple of weeks. I started it today just to empty out the drop box associated with it and it immediately got the same problem.

I downloaded vmware-vdiskmanager in the SDK and ran these two commands as follows.

E:\temp\vmware sdk\bin>vmware-vdiskmanager -R "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk"

VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.

The virtual disk, 'E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk', was corrupted and has been successfully repaired.

E:\temp\vmware sdk\bin>vmware-vdiskmanager -R "E:\01-VirtualMachines\IBIDEV02\IBIDEV02.vmdk"

VixDiskLib: Invalid configuration file parameter. Failed to read configuration file.

The virtual disk, 'E:\01-VirtualMachines\IBIDEV02\IBIDEV02.vmdk', was corruptedand has been successfully repaired.

Even so I started the Win7 VMWare again and it issued the same error very soon after starting.

This is making my VMs unusable and I an concerned to start any more VMs for fear this is a VMware problem that is actually somehow damaging the virtual disks.

Has anyone seen this before? I am thinking of unistalling and re-installing VMWARE just to see if that makes the machine stable again.

Any and all tips would be very much appreciated.

Best Regards

Peter

2015-09-07T15:39:42.812+02:00| vmx| I120: Msg_Question:

2015-09-07T15:39:42.812+02:00| vmx| I120: [msg.vmxaiomgr.retrycontabort.rudeunplug] The operation on file "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" failed.

2015-09-07T15:39:42.812+02:00| vmx| I120+ If the file resides on a remote file system, make sure that the network connection and the server where this disk resides are functioning properly. If the file resides on removable media, reattach the media.

2015-09-07T15:39:42.812+02:00| vmx| I120+ Select Retry to attempt the operation again.

2015-09-07T15:39:42.812+02:00| vmx| I120+ Select Cancel to end this session.

2015-09-07T15:39:42.812+02:00| vmx| I120+ Select Continue to forward the error to the guest operating system.

2015-09-07T15:39:42.812+02:00| vmx| I120: ----------------------------------------

2015-09-07T15:39:50.021+02:00| vmx| I120: MsgQuestion: msg.vmxaiomgr.retrycontabort.rudeunplug reply=2

2015-09-07T15:39:50.021+02:00| vmx| I120: DISKLIB-LIB   : RWv failed ioId: #46125 (1507337) (9) .

2015-09-07T15:39:50.021+02:00| vmx| I120: DISK: Disk i/o on scsi0:0 failed: Data error (cyclic redundancy check) (1507337)

2015-09-07T15:39:50.021+02:00| vmx| I120: ###### dumping content of iov ######

2015-09-07T15:39:50.021+02:00| vmx| I120: READ

2015-09-07T15:39:50.021+02:00| vmx| I120: startSector = 90502920

2015-09-07T15:39:50.021+02:00| vmx| I120: numSectors = 56

2015-09-07T15:39:50.021+02:00| vmx| I120: numBytes = 28672

2015-09-07T15:39:50.021+02:00| vmx| I120: numEntries = 7

2015-09-07T15:39:50.021+02:00| vmx| I120:   entries[0] = 1C387F000 / 4096

2015-09-07T15:39:50.021+02:00| vmx| I120:   entries[1] = 1B9400000 / 4096

2015-09-07T15:39:50.021+02:00| vmx| I120:   entries[2] = 1B9581000 / 4096

2015-09-07T15:39:50.021+02:00| vmx| I120:   entries[3] = 188102000 / 4096

2015-09-07T15:39:50.021+02:00| vmx| I120:   entries[4] = 188683000 / 4096

2015-09-07T15:39:50.021+02:00| vmx| I120:   entries[5] = 187484000 / 4096

2015-09-07T15:39:50.021+02:00| vmx| I120:   entries[6] = 188505000 / 4096

2015-09-07T15:39:50.021+02:00| vmx| I120: scsi0:0: Command READ(10) took 44.796 seconds (ok)

2015-09-07T15:39:50.021+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 7.560 seconds (ok)

2015-09-07T15:39:50.021+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 7.560 seconds (ok)

2015-09-07T15:39:50.021+02:00| vmx| I120: scsi0:0: Command READ(10) took 10.326 seconds (ok)

2015-09-07T15:39:50.021+02:00| vmx| I120: scsi0:0: Command READ(10) took 10.337 seconds (ok)

2015-09-07T15:39:50.021+02:00| vmx| I120: scsi0:0: Command READ(10) took 13.530 seconds (ok)

2015-09-07T15:39:50.021+02:00| vmx| I120: scsi0:0: Command READ(10) took 13.528 seconds (ok)

2015-09-07T15:39:50.021+02:00| vmx| I120: scsi0:0: Command READ(10) took 10.420 seconds (ok)

2015-09-07T15:39:53.034+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 2.598 seconds (ok)

2015-09-07T15:39:53.034+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 2.568 seconds (ok)

2015-09-07T15:39:53.050+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.935 seconds (ok)

2015-09-07T15:39:53.059+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.935 seconds (ok)

2015-09-07T15:39:53.087+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.953 seconds (ok)

2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR: Retry on read "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : Data error (cyclic redundancy check).

2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR: system : err=170002 errCode=23 freeSpace=1338803728384

2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR: "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : read s=155051954176 n=28672 ne=7, fai=0

2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR:             v[0]=12BF7000:4096

2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR:             v[1]=12C15000:4096

2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR:             v[2]=12C19000:4096

2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR:             v[3]=12C21000:4096

2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR:             v[4]=1557A000:4096

2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR:             v[5]=155B6000:4096

2015-09-07T15:39:56.120+02:00| vmx| I120: VMXAIOMGR:             v[6]=F179000:4096

2015-09-07T15:39:56.120+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.004 seconds (ok)

2015-09-07T15:39:56.120+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 1.663 seconds (ok)

2015-09-07T15:39:56.120+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 1.663 seconds (ok)

2015-09-07T15:39:56.120+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.998 seconds (ok)

2015-09-07T15:39:56.121+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.033 seconds (ok)

2015-09-07T15:39:56.121+02:00| vmx| I120: scsi0:0: Command READ(10) took 6.090 seconds (ok)

2015-09-07T15:39:56.121+02:00| vmx| I120: scsi0:0: Command READ(10) took 6.093 seconds (ok)

2015-09-07T15:39:59.332+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 1.875 seconds (ok)

2015-09-07T15:39:59.342+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.128 seconds (ok)

2015-09-07T15:39:59.355+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.175 seconds (ok)

2015-09-07T15:39:59.356+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.175 seconds (ok)

2015-09-07T15:39:59.376+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.125 seconds (ok)

2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR: Retry on read "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : Data error (cyclic redundancy check).

2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR: system : err=170002 errCode=23 freeSpace=1338803728384

2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR: "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : read s=155051954176 n=28672 ne=7, fai=0

2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR:             v[0]=12BF7000:4096

2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR:             v[1]=12C15000:4096

2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR:             v[2]=12C19000:4096

2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR:             v[3]=12C21000:4096

2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR:             v[4]=1557A000:4096

2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR:             v[5]=155B6000:4096

2015-09-07T15:40:02.497+02:00| vmx| I120: VMXAIOMGR:             v[6]=F179000:4096

2015-09-07T15:40:02.497+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 2.048 seconds (ok)

2015-09-07T15:40:02.497+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 1.434 seconds (ok)

2015-09-07T15:40:02.497+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.140 seconds (ok)

2015-09-07T15:40:02.498+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.124 seconds (ok)

2015-09-07T15:40:02.498+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.106 seconds (ok)

2015-09-07T15:40:02.498+02:00| vmx| I120: scsi0:0: Command READ(10) took 6.245 seconds (ok)

2015-09-07T15:40:02.498+02:00| vmx| I120: scsi0:0: Command READ(10) took 6.255 seconds (ok)

2015-09-07T15:40:05.399+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.900 seconds (ok)

2015-09-07T15:40:05.401+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.902 seconds (ok)

2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR: Retry on read "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : Data error (cyclic redundancy check).

2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR: system : err=170002 errCode=23 freeSpace=1338803728384

2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR: "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : read s=155051954176 n=28672 ne=7, fai=0

2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR:             v[0]=12BF7000:4096

2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR:             v[1]=12C15000:4096

2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR:             v[2]=12C19000:4096

2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR:             v[3]=12C21000:4096

2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR:             v[4]=1557A000:4096

2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR:             v[5]=155B6000:4096

2015-09-07T15:40:08.499+02:00| vmx| I120: VMXAIOMGR:             v[6]=F179000:4096

2015-09-07T15:40:08.499+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 2.045 seconds (ok)

2015-09-07T15:40:08.499+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.099 seconds (ok)

2015-09-07T15:40:08.499+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.098 seconds (ok)

2015-09-07T15:40:08.499+02:00| vmx| I120: scsi0:0: Command READ(10) took 5.990 seconds (ok)

2015-09-07T15:40:08.500+02:00| vmx| I120: scsi0:0: Command READ(10) took 5.997 seconds (ok)

2015-09-07T15:40:08.500+02:00| vmx| I120: scsi0:0: Command READ(10) took 6.000 seconds (ok)

2015-09-07T15:40:11.442+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.938 seconds (ok)

2015-09-07T15:40:11.458+02:00| vmx| I120: scsi0:0: Command READ(10) took 1.998 seconds (ok)

2015-09-07T15:40:11.461+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.939 seconds (ok)

2015-09-07T15:40:11.472+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.971 seconds (ok)

2015-09-07T15:40:11.483+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.981 seconds (ok)

2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR: Retry on read "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : Data error (cyclic redundancy check).

2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR: system : err=170002 errCode=23 freeSpace=1338803728384

2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR: "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : read s=155051954176 n=28672 ne=7, fai=0

2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR:             v[0]=12BF7000:4096

2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR:             v[1]=12C15000:4096

2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR:             v[2]=12C19000:4096

2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR:             v[3]=12C21000:4096

2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR:             v[4]=1557A000:4096

2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR:             v[5]=155B6000:4096

2015-09-07T15:40:14.712+02:00| vmx| I120: VMXAIOMGR:             v[6]=F179000:4096

2015-09-07T15:40:14.712+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 1.922 seconds (ok)

2015-09-07T15:40:14.713+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.269 seconds (ok)

2015-09-07T15:40:14.713+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.088 seconds (ok)

2015-09-07T15:40:14.713+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.079 seconds (ok)

2015-09-07T15:40:14.713+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.216 seconds (ok)

2015-09-07T15:40:14.713+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.101 seconds (ok)

2015-09-07T15:40:14.713+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.123 seconds (ok)

2015-09-07T15:40:17.648+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 1.194 seconds (ok)

2015-09-07T15:40:17.662+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.949 seconds (ok)

2015-09-07T15:40:17.677+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.963 seconds (ok)

2015-09-07T15:40:17.685+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.967 seconds (ok)

2015-09-07T15:40:17.694+02:00| vmx| I120: USBGW: Write arbitrator op:13 len:22

2015-09-07T15:40:17.703+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.987 seconds (ok)

2015-09-07T15:40:17.712+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.998 seconds (ok)

2015-09-07T15:40:17.778+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.058 seconds (ok)

2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR: Retry on read "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : Data error (cyclic redundancy check).

2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR: system : err=170002 errCode=23 freeSpace=1338803728384

2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR: "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : read s=155051954176 n=28672 ne=7, fai=0

2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR:             v[0]=12BF7000:4096

2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR:             v[1]=12C15000:4096

2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR:             v[2]=12C19000:4096

2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR:             v[3]=12C21000:4096

2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR:             v[4]=1557A000:4096

2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR:             v[5]=155B6000:4096

2015-09-07T15:40:20.864+02:00| vmx| I120: VMXAIOMGR:             v[6]=F179000:4096

2015-09-07T15:40:20.865+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.170 seconds (ok)

2015-09-07T15:40:20.865+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.086 seconds (ok)

2015-09-07T15:40:20.865+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.091 seconds (ok)

2015-09-07T15:40:20.867+02:00| vmx| I120: scsi0:0: Command READ(10) took 3.080 seconds (ok)

2015-09-07T15:40:20.989+02:00| vmx| I120: USBGW: Write arbitrator op:13 len:22

2015-09-07T15:40:21.181+02:00| vmx| I120: USBGW: Write arbitrator op:13 len:22

2015-09-07T15:40:21.237+02:00| vmx| I120: USBGW: Write arbitrator op:13 len:22

2015-09-07T15:40:21.325+02:00| vmx| I120: USBGW: Write arbitrator op:13 len:22

2015-09-07T15:40:21.805+02:00| vmx| I120: USBGW: Write arbitrator op:13 len:22

2015-09-07T15:40:23.764+02:00| vmx| I120: scsi0:0: Command READ(10) took 2.875 seconds (ok)

2015-09-07T15:40:23.764+02:00| vmx| I120: scsi0:0: Command WRITE(10) took 1.054 seconds (ok)

2015-09-07T15:40:23.783+02:00| vmx| I120: scsi0:0: Command READ(10) took 6.072 seconds (ok)

2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR: Retry on read "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : Data error (cyclic redundancy check).

2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR: system : err=170002 errCode=23 freeSpace=1338803728384

2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR: "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" : read s=155051954176 n=28672 ne=7, fai=0

2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR:             v[0]=12BF7000:4096

2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR:             v[1]=12C15000:4096

2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR:             v[2]=12C19000:4096

2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR:             v[3]=12C21000:4096

2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR:             v[4]=1557A000:4096

2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR:             v[5]=155B6000:4096

2015-09-07T15:40:26.752+02:00| vmx| I120: VMXAIOMGR:             v[6]=F179000:4096

2015-09-07T15:40:26.752+02:00| vmx| I120: Msg_Question:

2015-09-07T15:40:26.752+02:00| vmx| I120: [msg.vmxaiomgr.retrycontabort.rudeunplug] The operation on file "E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk" failed.

2015-09-07T15:40:26.752+02:00| vmx| I120+ If the file resides on a remote file system, make sure that the network connection and the server where this disk resides are functioning properly. If the file resides on removable media, reattach the media.

2015-09-07T15:40:26.752+02:00| vmx| I120+ Select Retry to attempt the operation again.

2015-09-07T15:40:26.752+02:00| vmx| I120+ Select Cancel to end this session.

2015-09-07T15:40:26.752+02:00| vmx| I120+ Select Continue to forward the error to the guest operating system.

2015-09-07T15:40:26.752+02:00| vmx| I120: ----------------------------------------

2015-09-07T15:41:43.780+02:00| vmx| I120: MsgQuestion: msg.vmxaiomgr.retrycontabort.rudeunplug reply=1

2015-09-07T15:41:43.780+02:00| vmx| I120: Msg_Post: Warning

2015-09-07T15:41:43.781+02:00| vmx| I120: [msg.vmxaiomgr.corrupted] VMware Player cannot synchronize with the disk before canceling. Disk E:\01-VirtualMachines\Win7Desktop\Windows 7 Desktop.vmdk may be inconsistent.

2015-09-07T15:41:43.781+02:00| vmx| I120: ----------------------------------------

2015-09-07T15:41:43.816+02:00| vmx| I120: User requested abort: Exiting because of failed disk operation.

2015-09-07T15:41:43.816+02:00| vmx| W110: Win32 object usage: GDI 13, USER 22

2015-09-07T15:41:43.816+02:00| vmx| W110: Writing monitor corefile "E:\01-VirtualMachines\Win7Desktop\vmmcores.gz"

2015-09-07T15:41:43.816+02:00| vmx| I120: Counting amount of anonymous memory

2015-09-07T15:41:43.826+02:00| vmx| I120: Total Count of Anon Pages and CR3 pages 7395

2015-09-07T15:41:43.826+02:00| vmx| W110: Dumping core for vcpu-0

2015-09-07T15:41:43.827+02:00| vmx| I120: Beginning monitor coredump

2015-09-07T15:41:44.470+02:00| vmx| I120: End monitor coredump

2015-09-07T15:41:44.470+02:00| vmx| W110: Dumping core for vcpu-1

2015-09-07T15:41:44.470+02:00| vmx| I120: Beginning monitor coredump

2015-09-07T15:41:45.106+02:00| vmx| I120: End monitor coredump

2015-09-07T15:41:45.106+02:00| vmx| W110: Dumping core for vcpu-2

2015-09-07T15:41:45.106+02:00| vmx| I120: Beginning monitor coredump

2015-09-07T15:41:45.747+02:00| vmx| I120: End monitor coredump

2015-09-07T15:41:45.747+02:00| vmx| W110: Dumping core for vcpu-3

2015-09-07T15:41:45.748+02:00| vmx| I120: Beginning monitor coredump

2015-09-07T15:41:46.387+02:00| vmx| I120: End monitor coredump

2015-09-07T15:41:46.387+02:00| vmx| W110: Dumping extended monitor data

2015-09-07T15:41:48.286+02:00| vmx| I120: CoreDump: ei->size 38719488 : len = 38719488

2015-09-07T15:41:48.287+02:00| vmx| I120: Backtrace:

2015-09-07T15:41:48.294+02:00| vmx| I120: backtrace[00] frame 0x0012e388 IP 0x13f9cf12e params 0 0x170002 0x2 0x124546 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x0004e12e]

2015-09-07T15:41:48.295+02:00| vmx| I120: backtrace[01] frame 0x0012ecb0 IP 0x13f9a92c0 params 0x1400d30a0 0xb09007a0017 0x3d0e080 0xffffffffff ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x000282c0]

2015-09-07T15:41:48.295+02:00| vmx| I120: backtrace[02] frame 0x0012ed60 IP 0x13fbc3272 params 0x17c7ae30 0x13fc011d4 0x137b6ebb000 0x7000 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x00242272]

2015-09-07T15:41:48.295+02:00| vmx| I120: backtrace[03] frame 0x0012edc0 IP 0x13fbc32dd params 0x183ac698 0x3a0420 0 0 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x002422dd]

2015-09-07T15:41:48.296+02:00| vmx| I120: backtrace[04] frame 0x0012edf0 IP 0x13fbc47ac params 0x39cf660 0 0x1f0 0x13f9a4744 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x002437ac]

2015-09-07T15:41:48.296+02:00| vmx| I120: backtrace[05] frame 0x0012ee20 IP 0x13fbc4d81 params 0x39cf660 0 0 0x13 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x00243d81]

2015-09-07T15:41:48.296+02:00| vmx| I120: backtrace[06] frame 0x0012ee50 IP 0x13f9e7634 params 0xffffffff 0x6 0 0x31c810 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x00066634]

2015-09-07T15:41:48.297+02:00| vmx| I120: backtrace[07] frame 0x0012f6c0 IP 0x13f9ea584 params 0x18169165b00 0 0x31c810 0x39cfca0 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x00069584]

2015-09-07T15:41:48.297+02:00| vmx| I120: backtrace[08] frame 0x0012f710 IP 0x13f9eab51 params 0 0 0x1403e2b30 0x13ff23e4e ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x00069b51]

2015-09-07T15:41:48.297+02:00| vmx| I120: backtrace[09] frame 0x0012f760 IP 0x13f9aa25d params 0x3997e70 0 0x489d00 0x3997ab0 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x0002925d]

2015-09-07T15:41:48.297+02:00| vmx| I120: backtrace[10] frame 0x0012f840 IP 0x13f9aa841 params 0x487d60 0x3997ab0 0x2 0x140038b88 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x00029841]

2015-09-07T15:41:48.298+02:00| vmx| I120: backtrace[11] frame 0x0012f870 IP 0x13f98318f params 0 0x1 0 0 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x0000218f]

2015-09-07T15:41:48.298+02:00| vmx| I120: backtrace[12] frame 0x0012f8c0 IP 0x13f983257 params 0 0 0 0 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x00002257]

2015-09-07T15:41:48.298+02:00| vmx| I120: backtrace[13] frame 0x0012f970 IP 0x13f9811de params 0 0 0 0 ??? [C:\Program Files (x86)\VMware\VMware Player\x64\vmware-vmx.exe base 0x13f980000 0x0001:0x000001de]

2015-09-07T15:41:48.300+02:00| vmx| I120: backtrace[14] frame 0x0012f978 IP 0x771959cd params 0 0 0 0 BaseThreadInitThunk + 0x000d [C:\Windows\system32\kernel32.dll base 0x77180000 0x0001:0x000149cd]

2015-09-07T15:41:48.302+02:00| vmx| I120: backtrace[15] frame 0x0012f9a8 IP 0x772cb981 params 0 0 0 0 RtlUserThreadStart + 0x0021 [C:\Windows\SYSTEM32\ntdll.dll base 0x772a0000 0x0001:0x0002a981]

2015-09-07T15:41:48.302+02:00| vmx| I120: Exiting

Hello,

my host system is a Linux Mint installation. I use a lot of VMs. Except of two of them, all are running Linux. Those machines never crashed. But both Windows machines instantly performed a shutdown, comparable to a power loss. Sometimes it happens when the host machine puts the monitor to standby mode, some happens performing usual tasks, like copy and paste in word or pressing a letter in the explorer, in order to search a file/folder.

My colleague has the same problem. He thinks it happens most times when he access the file system.

Kind regards

I have a single Fusion virtual machine installed on my Mac dedicated to Windows.  When I originally installed this VM  selected a 100GB partition on a Mac with a 750 GB hard drive.  I now have a Mac with a 256 GB SSD.  Disk space is getting tight and I would like to modify the amount taken by the VM.

Questions:

• When viewing disk storage statistics, is the number reported in "Other" based on the entire 100GB partition or just the amount actually used by the virtual machine, in my case about 48 GB?
• What is the best way to reduce the size of the partition?   Guessing create a new one and delete the old?

Thanks,

Message was edited by: Jim Hulburt Edited question #1 for clarity.

Hi! I'm trying to work out a suitable method to wait for a script to finish. I'm using 'run program in guest' to run a script on a VM which in turn triggers a CHEF-Client install. It's working well but its a "fire and forget" situation which isn't ideal, as I'd like to send a notification when it's completed. If I could wait for a service to be installed/started maybe, I could then notify the user when the install is complete. It takes approx 10 mins for the install to complete, but i'd rather not just use a wait timer in minutes.

Thanks for any advice on this one as always

Cheers

Steve

Hi,

I got a problem regarding WinRM and VMWare Orchestrator 5.5. and hope someone can help me.

When I add a powershell host using WinRM, HTTP I receive an error:

w:MaxEnvelopeSize xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" mustUnderstand="true">153600</w:MaxEnvelopeSize>

    <a:MessageID xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing">uuid:C3F974DC-F8C4-4AB5-A98F-3B3A29B25F08</a:MessageID>

    <w:Locale xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" mustUnderstand="false" xml:lang="en-US"/>

    <p:DataLocale xmlns:p="http://schemas.microsoft.com/wbem/wsman/1/wsman.xsd" mustUnderstand="false" xml:lang="en-US"/>

    <w:OperationTimeout xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd">PT180.000S</w:OperationTimeout>

    <a:Action xmlns:a="http://schemas.xmlsoap.org/ws/2004/08/addressing" mustUnderstand="true">http://schemas.xmlsoap.org/ws/2004/09/transfer/Create</a:Action>

    <w:ResourceURI xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd" mustUnderstand="true">http://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd</w:ResourceURI>

    <w:OptionSet xmlns:w="http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd">

      <w:Option Name="WINRS_NOPROFILE">FALSE</w:Option>

      <w:Option Name="WINRS_CODEPAGE">437</w:Option>

    </w:OptionSet>

  </env:Header>

  <env:Body>

    <rsp:Shell xmlns:rsp="http://schemas.microsoft.com/wbem/wsman/1/windows/shell">

      <rsp:InputStreams>stdin</rsp:InputStreams>

      <rsp:OutputStreams>stdout stderr</rsp:OutputStreams>

    </rsp:Shell>

  </env:Body>

</env:Envelope>

, document out [EMPTY], (Dynamic Script Module name : addPowerShellHost#16)

However I found out that it is working if I set the WinRm to "AllowUnencrypted" on the client.

Interestingly WinRM encrypted is working if I just remotely connect via powershell, therefore this seems to be a setting or limitation on the Orchestrator.

Is it by design not possible or do I miss a specific setting?

Has anyone had any problems installing the VOA vRealize reports PAK? I have installed these successfully in the Hands On Labs and this works fine, when I try and import in to my vRealize environment running VMware vSphere with Operations Management Enterprise Plus for vRealize Operations, it imports and uploads fine with no errors but none of the VOA reports are listed. I have followed the full and updated instructions along with the latest VOA_Reports-FINAL-v3.pak but no matter what I try it just does not appear? I have also tried the earlier PAK versions but they still do not appear. I am running vRealize Version 6.0.1.2523163 Build 2523163

Host:

VMWare Workstation 12

Arch Linux 64bit, kernel 4.1.6, NVIDIA graphics driver, Gnome 3.16

My Windows 7 64-bit guest works fine except for the following problem:

When I start up the VM and switch to full screen mode, I have a blank screen.  I have to toggle between center and stretch options to get the Windows 7 desktop to appear. Also, this happens after I log in, not during bootup.

In the VMWare settings, the resolution is set to auto.  Inside Windows 7, I have the resolution set to 1920x1080. I do this because my monitor is a 24" 4k monitor and I don't want to use the Guest at 4k because of poor HIDPI support.

I did try setting the resolution in the VMWare settings, but I get a warning notificatino about possible problems if you don't leave the setting on auto.  I assume this means the correct way is to set the resolution inside the guest OS?

Hey guys, wondering if you can help me out with this, I upgraded to windows 10 and having this annoying issue in vmware workstation 11

I want to make VMnet2 only use my MIFI wifi and not my regular internet so I went to the virtual network editor like I did before and added vmnet2 but when I check the box for bridged to select the wifi it says “cannot change network to bridged there are no un-bridged host network adapters” which has got me stumped >.<

Hello,

This video shows how to extend Partitions in OS X using Disk Utility:

17 Mac OS X Yosemite Tricks How to resize partitions with Disk Utility - YouTube

However, when I am logged in to Yosemite VM Image running in Fusion, it shows me a 42.09GByte "Macintosh HD" and 10GBytes of "Free Space" below that but the "Macintosh HD" partition cannot be modified -- cannot drag bottom right corner and the "Size" text field is greyed out.  How can this be done?

Thanks

DH

Hello, i am having an issue with VRO 6.0.2 integrating itself with vcenter server 6.0 . when trying to access vro from the web client, i see that my vcenetr server is not being managed by the VRO server and displays "N/A".  i have checked my extensions and it is correct, and can manually download the plugin just fine. the plugins are installed just fine as well. i have successfully ran the add vcenter workflow from the VRO client succesffully and all other settings work just fine with VRO just the integration to the web client.

Does anybody have a solution or know what it may be?

VM :  9.0.3 build-1410761

HOST: windows 7  64 bit

GUEST: Cent OS 6.5 64bit

Install VMware Tools 9.2.4 build-1398046 in the guest, but error

Detected X server version 1.15.0

Distribution provided drivers for Xorg X server are used.

Skipping X configuration because X drivers are not included.

I has installed xorg-x11-drv-vmware

Why ?

Dear Expert,

I have DELL T630 server and windows 2008 server is installed on it. On windows 2008 server I have created virtual machine of windows 2003 server and it is running perfectly. But my requirement is to create/interface the four network adapter from virtual server (windows 2003) to host server (windows 2008) and to network. DELL T630 server is equipped with four Ethernet adapters. How I can use these four physical network adapter through the virtual machine. I am beginner in vmware and I need to known how to do this. Please guide me through step by step for configuration of one Ethernet adapter, so that I can configure the remaining in the same way. I want to use 172.16.4.22/172.17.4.22/172.16.80.22/172.17.80.22 IP addresses to interface the virtual machine (windows 2003) Ethernet adapter with network switch.

Thanks,

Nisar Ahmed

Dear Community

I am trying to install the VMware VDP for SQL Server agent, however the installation fails before it actually starts with the following error

Microsoft.SqlServer.Smo.dll version does not match the latest SQL Server installation found on the system. Please update your SQL SMO DLL before running this installer again.

Required version: 10.x.x.x

The server has SQL Server Express 2008 R2 installed.

I have searched through the entire server and I have found the following versions of that particular DLL

C:\Program Files (x86)\Microsoft SQL Server\110\SDK\Assemblies: v11.0.2100.60

C:\Program Files\Microsoft SQL Server\110\SDK\Assemblies: v11.0.2100.60

C:\Program Files\Microsoft SQL Server\100\SDK\Assemblies: v10.0.1600.22

C:\Program Files (x86)\Microsoft SQL Server\100\SDK\Assemblies: v1.050.2500.0

As far as I know, only one version of SQL has been installed and it came with my Solarwinds Orion installation.

Some help is greatly appreciated.

Hi guys, I wanted to run something passed you, we recently noticed a one off slowness of a migration from SAS to SATA iSCSI, we have a shared iSCSI datastore which are available in both environments, we use this to move our Test/Dev machines after go live into our Live environments. A colleauge of mine actually powered the machien down prior to migration and then ran a SDRS, he said it took almost 8 hours to complete and the disk was only 100GB large. We have a 550GB machine which needs to be migrated over into the Live environment from SAS to SATA via iSCSI. My question is, should this be done outside of office hours?? Also if this does take forever to run, is it likely to have an impact on the virtual machine as it is a live machine which is currently in use by a number of users.

I wanted to run these passed you as I'm always doing SDRS inside of office hours which no issues, I DONT power down the virtual machine and I leave them on and have no issues with slowness or further issues with performance, it is just a colleauge that mentioned that he'd powered the machine down prior, I thought this could maybe have an affect on the virtual machines?

Any recommendations what time and the best way to move this over?

When ever I am launching either Windows 8.1 or Windows 10 VMs I get the following error in the system log:

Also both VMs are much slower with Hardware Version 12 that with 10.

Any solution?

30/8/15 10:55:15,528 μ.μ. VMware Fusion[2163]: ** OpenCL Error Notification: [CL_DEVICE_NOT_AVAILABLE] : OpenCL Error : Error: build program driver returned (-3) **

30/8/15 10:55:15,529 μ.μ. VMware Fusion[2163]: ** OpenCL Error Notification: OpenCL Warning : clBuildProgram failed: could not build program for 0xffffffff (Intel(R) Core(TM) M-5Y51 CPU @ 1.10GHz) (err:-3) **

30/8/15 10:55:15,529 μ.μ. VMware Fusion[2163]: ** OpenCL Error Notification: [CL_BUILD_ERROR] : OpenCL Build Error : Compiler build log:

No kernels or only kernel prototypes found when build executable.

**

30/8/15 10:55:15,529 μ.μ. VMware Fusion[2163]: Native OpenCL program build failed:

No kernels or only kernel prototypes found when build executable.

30/8/15 10:55:27,826 μ.μ. VMware Fusion[2163]: ** OpenCL Error Notification: [CL_DEVICE_NOT_AVAILABLE] : OpenCL Error : Error: build program driver returned (-3) **

30/8/15 10:55:27,826 μ.μ. VMware Fusion[2163]: ** OpenCL Error Notification: OpenCL Warning : clBuildProgram failed: could not build program for 0xffffffff (Intel(R) Core(TM) M-5Y51 CPU @ 1.10GHz) (err:-3) **

30/8/15 10:55:27,826 μ.μ. VMware Fusion[2163]: ** OpenCL Error Notification: [CL_BUILD_ERROR] : OpenCL Build Error : Compiler build log:

No kernels or only kernel prototypes found when build executable.

**

30/8/15 10:55:27,826 μ.μ. VMware Fusion[2163]: Native OpenCL program build failed:

No kernels or only kernel prototypes found when build executable.

Hi,

  Is there anyway I would be in a position to collect the % utilization of the resources on an hourly basis, as this is important for us to know the peak and off peak hours and the load during the peak hours