We tried rebooting a new VM we just created from a physical server the other day and it fails when powering on. The event states:

An error was received from the ESX host while powering on VM Peterbuilt.

Failed to start the virtual machine.

Module DiskEarly power on failed.

Cannot open the disk '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1-000002.vmdk' or one of the snapshot disks it depends on.

5 (Input/output error)

The vmware.log from the first time it failed power on contains this:

2014-05-03T10:18:40.564Z| Worker#1| I120: DISK: OPEN scsi0:1 '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1-000002.vmdk' persistent R[]

2014-05-03T10:18:40.564Z| Worker#0| I120: DISK: OPEN scsi0:0 '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt-000002.vmdk' persistent R[]

2014-05-03T10:18:40.659Z| Worker#0| I120: DISKLIB-VMFS  : "vsan://1d846353-60b1-b2e4-7696-d4ae52836f43" : open successful (10) size = 32462929920, hd = 29894442. Type 8

2014-05-03T10:18:40.659Z| Worker#0| I120: DISKLIB-DSCPTR: Opened [0]: "vsan://1d846353-60b1-b2e4-7696-d4ae52836f43" (0xa)

2014-05-03T10:18:40.659Z| Worker#0| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt-000002.vmdk' (0xa): vmfsSparse, 62912512 sectors / 30 GB.

2014-05-03T10:18:40.671Z| Worker#1| I120: DISKLIB-VMFS  : "vsan://1f846353-d29f-90dd-fe1b-d4ae52836f43" : open successful (10) size = 576889700352, hd = 32384813. Type 8

2014-05-03T10:18:40.671Z| Worker#1| I120: DISKLIB-DSCPTR: Opened [0]: "vsan://1f846353-d29f-90dd-fe1b-d4ae52836f43" (0xa)

2014-05-03T10:18:40.671Z| Worker#1| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1-000002.vmdk' (0xa): vmfsSparse, 1118001152 sectors / 533.1 GB.

2014-05-03T10:18:40.683Z| Worker#1| I120: OBJLIB-VSANOBJ: VsanObjReadPolicy: failed to readPolicy for object: Input/output error (327682).

2014-05-03T10:18:40.683Z| Worker#1| I120: OBJLIB-VSANOBJ: VsanObjGetExtParams: Could not read policy for 'vsan://1eee6253-1e80-39fa-229e-842b2b78ebfb'.

2014-05-03T10:18:40.683Z| Worker#1| I120: OBJLIB-LIB: ObjLib_GetExtParams : Failed to get ext params : Input/output error (327684)

2014-05-03T10:18:40.683Z| Worker#1| I120: DISKLIB-VMFS  : "vsan://1eee6253-1e80-39fa-229e-842b2b78ebfb" : failed to open (Input/output error): . Type 3

2014-05-03T10:18:40.683Z| Worker#1| I120: DISKLIB-LINK  : "/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1.vmdk" : failed to open (Input/output error). 

2014-05-03T10:18:40.683Z| Worker#1| I120: DISKLIB-CHAIN :"/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1-000002.vmdk": Failed to open parent "/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1.vmdk": Input/output error.

2014-05-03T10:18:40.683Z| Worker#1| I120: DISKLIB-CHAIN : "/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1.vmdk" : failed to open (The parent of this virtual disk could not be opened).

2014-05-03T10:18:40.684Z| Worker#1| I120: DISKLIB-VMFS  : "vsan://1f846353-d29f-90dd-fe1b-d4ae52836f43" : closed.

2014-05-03T10:18:40.684Z| Worker#1| I120: DISKLIB-LIB   : Failed to open '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1-000002.vmdk' with flags 0xa The parent of this virtual disk could not be opened (23).

2014-05-03T10:18:40.704Z| Worker#0| I120: DISKLIB-VMFS  : "vsan://1cee6253-07b9-e212-6f6a-842b2b78ebfb" : open successful (14) size = 32211206144, hd = 32581421. Type 3

2014-05-03T10:18:40.704Z| Worker#0| I120: DISKLIB-DSCPTR: Opened [0]: "vsan://1cee6253-07b9-e212-6f6a-842b2b78ebfb" (0xe)

2014-05-03T10:18:40.704Z| Worker#0| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt.vmdk' (0xe): vmfs, 62912512 sectors / 30 GB.

2014-05-03T10:18:40.704Z| Worker#0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 2, numSubChains = 1

2014-05-03T10:18:40.704Z| Worker#0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 32581421, extentType = 2

2014-05-03T10:18:40.704Z| Worker#0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(1) fid = 29894442, extentType = 0

2014-05-03T10:18:40.705Z| Worker#0| I120: DISKLIB-LIB   : Resuming change tracking.

2014-05-03T10:18:40.711Z| Worker#0| I120: DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 29894442.

2014-05-03T10:18:40.711Z| Worker#0| I120: DISKLIB-CBT   : Successfuly created cbt node 1ca272e-cbt.

2014-05-03T10:18:40.711Z| Worker#0| I120: DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/1ca272e-cbt

2014-05-03T10:18:40.711Z| Worker#0| I120: DISKLIB-LIB   : Opened "/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt-000002.vmdk" (flags 0xa, type vmfs).

2014-05-03T10:18:40.711Z| Worker#0| I120: DISK: Disk '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt-000002.vmdk' has UUID '60 00 c2 9c 4d 6e 95 99-d1 c1 5f c9 c0 e0 df e3'

2014-05-03T10:18:40.711Z| Worker#0| I120: DISK: OPEN '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt-000002.vmdk' Geo (3916/255/63) BIOS Geo (3916/255/63)

2014-05-03T10:18:40.717Z| Worker#1| I120: DISKLIB-VMFS  : "vsan://1f846353-d29f-90dd-fe1b-d4ae52836f43" : open successful (8) size = 576889700352, hd = 30091058. Type 8

2014-05-03T10:18:40.717Z| Worker#1| I120: DISKLIB-DSCPTR: Opened [0]: "vsan://1f846353-d29f-90dd-fe1b-d4ae52836f43" (0x8)

2014-05-03T10:18:40.717Z| Worker#1| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1-000002.vmdk' (0x8): vmfsSparse, 1118001152 sectors / 533.1 GB.

2014-05-03T10:18:40.717Z| Worker#1| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 1, numSubChains = 1

2014-05-03T10:18:40.717Z| Worker#1| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 30091058, extentType = 0

2014-05-03T10:18:40.718Z| Worker#1| I120: DISKLIB-LIB   : Resuming change tracking.

2014-05-03T10:18:40.722Z| Worker#1| I120: DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 30091058.

2014-05-03T10:18:40.723Z| Worker#1| I120: DISKLIB-CBT   : Successfuly created cbt node 233273a-cbt.

2014-05-03T10:18:40.723Z| Worker#1| I120: DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/233273a-cbt

2014-05-03T10:18:40.723Z| Worker#1| I120: DISKLIB-LIB   : Opened "/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1-000002.vmdk" (flags 0x8, type vmfsSparse).

2014-05-03T10:18:40.724Z| Worker#1| I120: OBJLIB-VSANOBJ: VsanObjReadPolicy: failed to readPolicy for object: Input/output error (327682).

2014-05-03T10:18:40.724Z| Worker#1| I120: OBJLIB-VSANOBJ: VsanObjGetExtParams: Could not read policy for 'vsan://1eee6253-1e80-39fa-229e-842b2b78ebfb'.

2014-05-03T10:18:40.724Z| Worker#1| I120: OBJLIB-LIB: ObjLib_GetExtParams : Failed to get ext params : Input/output error (327684)

2014-05-03T10:18:40.724Z| Worker#1| I120: DISKLIB-VMFS  : "vsan://1eee6253-1e80-39fa-229e-842b2b78ebfb" : failed to open (Input/output error): . Type 3

2014-05-03T10:18:40.724Z| Worker#1| I120: DISKLIB-LINK  : "/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1.vmdk" : failed to open (Input/output error). 

2014-05-03T10:18:40.724Z| Worker#1| I120: DISKLIB-CHAIN : "/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1.vmdk" : failed to open (Input/output error).

2014-05-03T10:18:40.724Z| Worker#1| I120: DISKLIB-LIB   : Failed to open '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1.vmdk' with flags 0xe Input/output error (327689).

2014-05-03T10:18:40.724Z| Worker#1| I120: DISK: Cannot open disk "/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1.vmdk": Input/output error (327689).

2014-05-03T10:18:40.724Z| Worker#1| I120: DISK: Cannot open disk '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1.vmdk' : Input/output error.

2014-05-03T10:18:40.725Z| Worker#1| I120: DISKLIB-CBT   : Shutting down change tracking for untracked fid 30091058.

2014-05-03T10:18:40.725Z| Worker#1| I120: DISKLIB-CBT   : Successfully disconnected CBT node.

2014-05-03T10:18:40.737Z| Worker#1| I120: DISKLIB-VMFS  : "vsan://1f846353-d29f-90dd-fe1b-d4ae52836f43" : closed.

2014-05-03T10:18:40.742Z| vmx| I120: DISK: Opening disks took 179 ms.

2014-05-03T10:18:40.742Z| vmx| I120: Module DiskEarly power on failed.

2014-05-03T10:18:40.742Z| vmx| I120: VMX_PowerOn: ModuleTable_PowerOn = 0

2014-05-03T10:18:40.742Z| vmx| I120: scsi0:0: numIOs = 0 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)

2014-05-03T10:18:40.742Z| vmx| I120: Closing disk scsi0:0

2014-05-03T10:18:40.743Z| vmx| I120: DISKLIB-CBT   : Shutting down change tracking for untracked fid 29894442.

2014-05-03T10:18:40.743Z| vmx| I120: DISKLIB-CBT   : Successfully disconnected CBT node.

2014-05-03T10:18:40.748Z| vmx| I120: DISKLIB-VMFS  : "vsan://1d846353-60b1-b2e4-7696-d4ae52836f43" : closed.

2014-05-03T10:18:40.749Z| vmx| I120: DISKLIB-VMFS  : "vsan://1cee6253-07b9-e212-6f6a-842b2b78ebfb" : closed.

Hello,

For a while now I've experienced poor video performance under windows with VMware when using dual displays. A single display instance of VMware performed wonderfully, extending the session to two displays created significant interface lag.

I was able to resolve the performance problem by disabling "Sync to VBlank" in the NVIDIA X Server Settings. Performance across multiple displays is now good (feels the same as the performance of a single display). Thought this info might be useful to someone.

anyone selling vmware workstation  8 or higher that they no longer use?

I have just loaded Fusion on a Mac Pro with dual 4K displays. Everything works fine in full screen mode on a single display (resolution 3480x2160). However, when I change to use all displays in full screen mode, both monitors go black and the cursor flashes. Does fusion support dual 4K displays?

Hello,

There is no sound in my 10.6 Server virtual machine.   The little speaker icon on the menu bar in the virtual machine is greyed out.   When I press the sound key on the keyboard to increase the sound I get no sound.  All alert sound effects in System Preferences for the virtual machine are greyed out and there is no system wide sound for the virtual machine at all.  How can I enable sound for my virtual machine?  Please help.

Thanks.

Complete newbie here -- my apologies if this has been answered elsewhere.

I have an application running on Linux on a physical server.  We have an ESX4 server in our environment running a couple of dozen vm's.  Is it possible to somehow convert that physical server to a VM image, then deploy it on an ESX server at a customer site?   Can someone point me to documentation outlining how that could be done?

THANKS for any help you can offer....

I wrote up my findings so far:

TinkerTry IT @ home | VMware ESXi 5.5 Update 1 Driver Rollup 2 Released Apr 24 2014

http://TinkerTry.com/vmware-esxi-5-5-update-1-driver-rollup-2-released-apr-24-2014

and am curious how others are doing with downloading and/or testing this rollup 2, that quietly arrived back on April 24th.

ESXi 5.xにてWindows Server 2008 R2 x64 仮想マシンがBSODになることがあるとのことです。Solaris 10 x64の仮想マシンの場合も同様にカーネルパニックに陥ることがあるようです。

原因は現在調査中で、以下のCPUを搭載しているサーバの場合、発生することが確認されたとのことです。

• Intel(R) Xeon(R) CPU E5-2670 v2
• Intel(R) Xeon(R) CPU E5-2680 v2
• Intel(R) Xeon(R) CPU E5-2690 v2
• Intel(R) Xeon(R) CPU E5-2697 v2

修正パッチが公開されるまで、該当仮想マシンの.vmxファイルにで下記の設定を”software”に変更することで回避できるということですので、本事象を経験している方は、下記のKBを元に設定を変更してみてください。

monitor.virtual_mmu = software

KB 2073791 Windows 2008 R2 and Solaris 10 64-bit virtual machines blue screen or kernel panic when running on ESXi 5.x with an Intel E5 v2 series processor

  Dear All,

I have installed Openstack Icehouse on ubuntu 14.04 LTS. i configured nova.conf according to openstack icehouse installation guide. but still i couldn't connect to vcenter. nova-compute log give following error.

nova-compute.log

root@IceHouse:/var/log/nova# tail -f nova-compute.log

2014-05-03 09:09:46.981 1127 TRACE nova.virt.vmwareapi.driver

2014-05-03 09:09:46.981 1127 TRACE nova.virt.vmwareapi.driver while parsing SOAP body

2014-05-03 09:09:46.981 1127 TRACE nova.virt.vmwareapi.driver at line 1, column 224

2014-05-03 09:09:46.981 1127 TRACE nova.virt.vmwareapi.driver

2014-05-03 09:09:46.981 1127 TRACE nova.virt.vmwareapi.driver while parsing SOAP envelope

2014-05-03 09:09:46.981 1127 TRACE nova.virt.vmwareapi.driver at line 1, column 38

2014-05-03 09:09:46.981 1127 TRACE nova.virt.vmwareapi.driver

2014-05-03 09:09:46.981 1127 TRACE nova.virt.vmwareapi.driver while parsing HTTP request before method was determined

2014-05-03 09:09:46.981 1127 TRACE nova.virt.vmwareapi.driver at line 1, column 0'

2014-05-03 09:09:46.981 1127 TRACE nova.virt.vmwareapi.driver

2014-05-03 09:10:54.387 1127 ERROR suds.client [-] <?xml version="1.0" encoding="UTF-8"?>

<SOAP-ENV:Envelope xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

   <ns1:Body>

      <ns0:RetrieveServiceContent>

         <_this type="ServiceInstance">ServiceInstance</_this>

      </ns0:RetrieveServiceContent>

   </ns1:Body>

</SOAP-ENV:Envelope>

2014-05-03 09:10:54.388 1127 CRITICAL nova.virt.vmwareapi.driver [-] Unable to connect to server at *.*.*.*, sleeping for 60 seconds

2014-05-03 09:10:54.388 1127 TRACE nova.virt.vmwareapi.driver Traceback (most recent call last):

2014-05-03 09:10:54.388 1127 TRACE nova.virt.vmwareapi.driver   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/driver.py", line 795, in _create_session

2014-05-03 09:10:54.388 1127 TRACE nova.virt.vmwareapi.driver     self.vim = self._get_vim_object()

2014-05-03 09:10:54.388 1127 TRACE nova.virt.vmwareapi.driver   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/driver.py", line 784, in _get_vim_object

2014-05-03 09:10:54.388 1127 TRACE nova.virt.vmwareapi.driver     return vim.Vim(protocol=self._scheme, host=self._host_ip)

2014-05-03 09:10:54.388 1127 TRACE nova.virt.vmwareapi.driver   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vim.py", line 117, in __init__

2014-05-03 09:10:54.388 1127 TRACE nova.virt.vmwareapi.driver     self._service_content = self.retrieve_service_content()

2014-05-03 09:10:54.388 1127 TRACE nova.virt.vmwareapi.driver   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vim.py", line 120, in retrieve_service_content

2014-05-03 09:10:54.388 1127 TRACE nova.virt.vmwareapi.driver     return self.RetrieveServiceContent("ServiceInstance")

2014-05-03 09:10:54.388 1127 TRACE nova.virt.vmwareapi.driver   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vim.py", line 196, in vim_request_handler

2014-05-03 09:10:54.388 1127 TRACE nova.virt.vmwareapi.driver     raise error_util.VimFaultException(fault_list, excep)

2014-05-03 09:10:54.388 1127 TRACE nova.virt.vmwareapi.driver VimFaultException: Server raised fault: 'Element tag ns0:RetrieveServiceContent uses an undefined namespace prefix ns0

Here is my nova.conf

[DEFAULT]

flat_interface = eth1

host = controller

flat_network_bridge = br100

vlan_interface = eth0

public_interface = eth0

network_manager = nova.network.manager.FlatDHCPManager

dhcpbridge_flagfile = /etc/nova/nova.conf

dhcpbridge = /usr/bin/nova-dhcpbridge

logdir = /var/log/nova

state_path = /var/lib/nova

lock_path = /var/lock/nova

force_dhcp_release = True

compute_driver = vmwareapi.VMwareVCDriver

iscsi_helper = tgtadm

root_helper = sudo nova-rootwrap /etc/nova/rootwrap.conf

verbose = True

ec2_private_dns_show_ip = True

api_paste_config = /etc/nova/api-paste.ini

volumes_path = /var/lib/nova/volumes

enabled_apis = ec2,osapi_compute,metadata

rpc_backend = rabbit

rabbit_host = controller

rabbit_password = nova

my_ip = *.*.*.*

vncserver_listen = *.*.*.*

vncserver_proxyclient_address = *.*.*.*

auth_strategy = keystone

network_api_class = nova.network.api.API

security_group_api = nova

[database]

connection = mysql://nova:nova@controller/nova

[keystone_authtoken]

auth_uri = http://controller:5000

auth_host = controller

auth_port = 35357

auth_protocol = http

admin_tenant_name = service

admin_user = nova

admin_password = nova

[vmware]

host_password = password

host_username = username

host_ip = vcenter IP address

#datastore_regex = NOT DEFINED

cluster_name = cluster name

please help me to fix this issue.

Thanks and Regards,

Lasantha.

Dear Gurus,

I have raised a Priority 2 ticket for this issue but its appalling to see that my support request takes time to give me a call.

I made that statement because I love VMware and its products, so dont just drop the ball when it comes to customer service.

Leaving that aside, I will post my question.

The cluster I manage has 5 physical hosts a vCenter Appliance running as a VM backed by a Oracle Database.

The setup was on Initial release of 5.1.

There was a vm-vm affinity rule to keep 6 virtual machines together at any given time on the same physical host.

It was working perfectly fine up until I was forced to upgrade my VI Infrastructure to 5.1 Update 2 and the VCSA's to 5.5 update 1 and SRM to 5.5.1.

Before the upgrade when I vMotion one vm from those 6 vm's it moves others also, but now it doesnt.

Seeking your invaluable advice.

Cheers!

RRZ

Maybe this was asked, i reading things for 4 days now, and its very confusing, but i got this situation, some admin sabotaged the virtual machines and backups, he turned of machines and issued Delete from Disk command in vSphere Web Client, and everything gone, its there a way to recover any of this VMs?

Some VMs are thin provisioned, other are thick

All the folders gone, no archive left

Nothing has been written on datastore

using esxi 5.5 and vSphere Web Client 5.5.

The backup got overwritten and useless

Anyone have an idea how to recover this VMs?

Hello, i need your help i will appreciate it. I can't see the vm its unknow and inaccesible. So i found that the datastore is missing is not connected. I tried to mount it with ssh with the command esxcfg-volume -M and the UDID like this

esxcfg-volume -M 50105409-876f4320-030d-0010f3246b93 but i m getting an error timeout. Do you know what i have to do? Any idea? Thank you.

i logged with ssh and i dont see the datastore folder that it had...do you have any idea? I lost the data? Its very weird

Hi,

I installed ESXi5.1 on cisco UCS. and plan to configure sw iscsi on esxi5.1

The network configuration on UCS:

Create two vNIC under vNICs and bind the new vnic to vlan2000.

vlan 2000 with be binded to two Uplink Eth interfaces in fabric A and fabric B.

Network configuration on ESXi5.1:

Add vmkernel to sw iscsi:

Once configured two vmkernel to sw iscsi network, find the format disk in windows VM is very very slow.  If only one vmkernel added to network, then it works well.

Does anyone know why the performance is very slow?  How to modify the configuration?

Thanks.

Hypothetical situation but we face similar to this in our production environment on many occasions.

We receive a Health alert from a datastore investigation shows health has dropped due to upturn in anomalies, further investigation shows that the datastore was subject to high IOPS about an hour ago, a very sudden peak and then it fell away a few minutes later. The datastore contains 20 VM's any of which could of caused the high IO, how do we easily find the guilty VM without going through and looking at graphs of all 20 VM's seperatley?

Thanks in Advance.

Brett

i have schedule workflow for reset all vm's one time in week,

i take all vms from "vm folder" but i want to exclude vms from list of "array of virtualMachine".

is it possible?

My supervisor wants to move the vCenter server 5.5 we installed to a vm with Windows Datacenter Server 2012 to a vm with Windows Datacenter Server 2008?

Can i just delete the vCenter Server 5.5 vm and reinstall it with Windows Datacenter Server 2008?

We found out the application servers we need to run must be on Windows 2008.

I did not do the original 2012 vCenter Server install and don't have much installation experience.

I did mention that we could still install the Windows Server 2008 application vms with the current vCenter Server but he insisted on the change.

The vCenter Server is currently setup in a 2 host cluster as a vm.

Any help would be appreciated.

Title says it all. I'm setting up vShield and just wondering if I *need to* have a vCenter server, or whether vShield can interact directly with the ESXi host.

Thanks

I am new to the Vmware snapshot technology and I am somewhat confused.

In that in the Snapshot Manager, my base vmdk is denoted as a dot, while in images I saw online, it is denoted by the "3 squares VM icon" with the VM name underneath. See images below for a clearer explanation. I can't click on the dot as well, so I can't "Go to" the base vmdk..

The reason I wanted to "Go to" the base vmdk is to return my VM to the state of the base vmdk.

I have made changes in "Snapshot 1 Base" and I do not want the changes to be consolidated with the base vmdk.

I followed the instructions I found in one of the VMware docs..

"To prevent snapshot files from merging with the parent snapshot, for example in cases of failed updates or installations, first use the Go to command to restore to a previous snapshot. This action invalidates the snapshot delta disks and deletes the memory file. You can then use the Delete option to remove the snapshot and any associated files."

  << What is shown in my Snapshot Manager.

<< What is usually shown online. ( A is the Base vmdk )

hello together,

we have 5 ESXi 5.5 Hosts -

when we set one host in maintenance - the VMs will be shipped to other Hosts.

Thats ok, but we got messages of high RAM Usage and we see this.

For Example:

ESX1      CPU 30 %    RAM 50 %

...

ESX5     CPU 30 %     RAM 50 %

after maintenance ESX5 we have RAM Usage of one Host of 97 % - CPU 40 %,

but this HOST does not move VMs to another Host which have less RAM Usage...

Why ?

any ideas ?

Hi All,

Was just thinking about an scenario. and want to know your suggestions on it.

1) Assume a vmware cluster with 4 esxi on it. with all set.Only DRS is configured on it. Containing 100+ no of vms.

2) Now if HA will be configure in to that cluster what will be the impact on the vms? Any outage will be there?

Thanks.