Hi All,

Just trying to install ESXi5.1 Upate 1 on new i7-4770k with Gigabyte GA-Z87-D3HP motherboard. The install hangs on "initializing IOV". Any idea's?

Many Thanks,

George

Hi,

We are about to make a file server in VMWare, but have one question.

If we are replacing a physical server, which has HBAs which connect to our 8GB SAN, how do we replicate this in VMWare? Our underlying data is served via DataCore. We have VMWare datastores with the data on, not RDM. We backup to tape using NetVault. We want our backup to continue in the same way and not backup via VRanger for large data stores, some can be as large as many TB. With the physical server, it could talk directly to the tape drives through the SAN. I guess we want a host to have direct access to its own HBA, but not a port shared with accessing hard drives.

Thanks

Hi folks,

I recently patched all of my esxi 5.1 hosts and went to do a tools upgrade last night on a couple of VM's. When I try to update via right click and automatic install it simply errors out.

So I decide to go to the console and do an interactive update. It mounts the installer and when I run I get this

The VM in question is running Windows Server 2008R2. It is currently hardware version 7 and I found that if I upgrade virtual hardware sometimes I am able to then install the tools sometimes not.

This is the first time I have seen a minimum virtual hardware version for tools to be updated. Has anyone else seen this and is there a workaround? I have 500+ vms and dont have the ability to shut them all down and upgrade hw.

Thanks!

Hello,

I am running ESXi 5.5 and I am having an issue when trying to set an ipv4 address on a separate vswitch.  When I try to add the vmkernel with a static IP, I get the following error:

Operation failed, diagnostics report: /usr/lib/vmware/rp/bin/configRP decreaseRPMemMaxSize dhclient 9 :failed

VMware KB: Attempts to remove VMkernel network interface result in error

I scoured around, but I could not find anything besides this KB article to address this error, but it does not help me.

I was able to add the vmkernel by not setting an IP and selecting DHCP, but I continue getting errors when I make any changes to the ipv4 addresses or if I try to remove the vmkernel.  I have no issues making changes to the ipv6 address.  I have rebooted the ESXi host and also tried creating a new vswitch with a new vmkernel, but ran into the same problem.

Here is the output from the configRP.log:

1392127426: Execute ['increaseRPMemMaxSize', 'dhclientrelease', '9']

1392127426: Increase resource pool size for host/vim/vmvisor: ['min=9', 'max=9']

1392127426: Get group ID of host/vim/vmvisor

1392127426: Increase resource pool size for host/vim/vmvisor/dhclientrelease: ['min=0', 'max=9']

1392127426: Get group ID of host/vim/vmvisor/dhclientrelease

1392127426: increaseRPMemMaxSize took 0.000543117523193 seconds

1392127431: Execute ['decreaseRPMemMaxSize', 'dhclient', '9']

1392127431: Decrease resource pool size for host/vim/vmvisor/dhclient: ['min=0', 'max=9']

1392127431: Get group ID of host/vim/vmvisor/dhclient

1392127431: Could not decrease reservation of host/vim/vmvisor/dhclient by 9 MB.

1392127431: Traceback (most recent call last):

  File "/usr/lib/vmware/rp/bin/configRP", line 909, in <module>

    eval(sys.argv[1])(sys.argv[2:])

  File "/usr/lib/vmware/rp/bin/configRP", line 852, in decreaseRPMemMaxSize

    raise e

ValueError: Bad parameter

I have attached the configRP.log and the configRP script that it references.

Hopefully someone can help me out. I've been wrestling with this for days.

Hi, we are having some iscsi problems with 2 vms. The 2 vms (SCCM servers) have both their dedicated host. And are in a dedicated cluster in vcenter. But since a couple of days the vm's freezes, most of the times it happens at night or early in the morning.

When i look in the log file of one of the host i see allot of waring messages:

the hosts are HP DL380G5 6x interfaces (2 Broadcom NC373i Intergrated Multifunction Gigabit adapter and quad port Intel 82571EB Gigabit adapater)

And we use software iscsi 2 nic's on of each card. With round robin.The switch ports are configured with lacp active and jumbo frames

We have ESXi 5.5 and vCenter 5.5

2014-02-11T07:17:09.793Z cpu6:32795)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e807fad40, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-02-11T07:17:09.793Z cpu6:32795)ScsiDeviceIO: 2337: Cmd(0x412e807fad40) 0x1a, CmdSN 0x125da from world 0 to dev "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2014-02-11T07:17:14.540Z cpu7:32796)WARNING: ScsiDeviceIO: 1223: Device naa.203c001378ae0119 performance has deteriorated. I/O latency increased from average value of 44255 microseconds to 900981 microseconds.

2014-02-11T07:17:15.957Z cpu2:974617)ScsiDeviceIO: 1203: Device naa.203c001378ae0119 performance has improved. I/O latency reduced from 900981 microseconds to 178170 microseconds.

2014-02-11T07:17:17.429Z cpu3:32792)ScsiDeviceIO: 1203: Device naa.203c001378ae0119 performance has improved. I/O latency reduced from 178170 microseconds to 87376 microseconds.

2014-02-11T07:18:53.757Z cpu4:32793)WARNING: ScsiDeviceIO: 1223: Device naa.203c001378ae0119 performance has deteriorated. I/O latency increased from average value of 44196 microseconds to 1140127 microseconds.

2014-02-11T07:18:54.629Z cpu6:32795)ScsiDeviceIO: 1203: Device naa.203c001378ae0119 performance has improved. I/O latency reduced from 1140127 microseconds to 226372 microseconds.

2014-02-11T07:19:23.457Z cpu0:32789)ScsiDeviceIO: 1203: Device naa.203c001378ae0119 performance has improved. I/O latency reduced from 226372 microseconds to 86809 microseconds.

2014-02-11T07:20:35.057Z cpu5:32794)WARNING: ScsiDeviceIO: 1223: Device naa.203c001378ae0119 performance has deteriorated. I/O latency increased from average value of 44174 microseconds to 988170 microseconds.

2014-02-11T07:20:35.988Z cpu3:32792)ScsiDeviceIO: 1203: Device naa.203c001378ae0119 performance has improved. I/O latency reduced from 988170 microseconds to 195084 microseconds.

2014-02-11T07:20:41.225Z cpu2:974612)ScsiDeviceIO: 1203: Device naa.203c001378ae0119 performance has improved. I/O latency reduced from 195084 microseconds to 86788 microseconds.

2014-02-11T07:20:54.754Z cpu2:32791)WARNING: ScsiDeviceIO: 1223: Device naa.203c001378ae0119 performance has deteriorated. I/O latency increased from average value of 44170 microseconds to 1059866 microseconds.

2014-02-11T07:20:56.654Z cpu2:974616)ScsiDeviceIO: 1203: Device naa.203c001378ae0119 performance has improved. I/O latency reduced from 1059866 microseconds to 207657 microseconds.

2014-02-11T07:20:59.739Z cpu2:32791)ScsiDeviceIO: 1203: Device naa.203c001378ae0119 performance has improved. I/O latency reduced from 207657 microseconds to 88011 microseconds.

2014-02-11T07:21:45.652Z cpu5:32794)WARNING: ScsiDeviceIO: 1223: Device naa.203c001378ae0119 performance has deteriorated. I/O latency increased from average value of 44157 microseconds to 900933 microseconds.

2014-02-11T07:21:48.533Z cpu2:974609)ScsiDeviceIO: 1203: Device naa.203c001378ae0119 performance has improved. I/O latency reduced from 900933 microseconds to 177646 microseconds.

2014-02-11T07:21:51.843Z cpu2:32791)ScsiDeviceIO: 1203: Device naa.203c001378ae0119 performance has improved. I/O latency reduced from 177646 microseconds to 86080 microseconds.

2014-02-11T07:22:09.804Z cpu4:32793)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e80878900, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-02-11T07:22:09.804Z cpu4:32793)ScsiDeviceIO: 2337: Cmd(0x412e80878900) 0x1a, CmdSN 0x126bc from world 0 to dev "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2014-02-11T07:22:26.543Z cpu7:32796)WARNING: ScsiDeviceIO: 1223: Device naa.203c001378ae0119 performance has deteriorated. I/O latency increased from average value of 44149 microseconds to 916920 microseconds.

2014-02-11T07:22:27.729Z cpu7:974614)ScsiDeviceIO: 1203: Device naa.203c001378ae0119 performance has improved. I/O latency reduced from 916920 microseconds to 181764 microseconds.

2014-02-11T07:22:30.592Z cpu3:32792)ScsiDeviceIO: 1203: Device naa.203c001378ae0119 performance has improved. I/O latency reduced from 181764 microseconds to 86366 microseconds.

2014-02-11T07:23:25.682Z cpu7:1146088)FS3Misc: 1565: Long VMFS rsv time on 'THSLOW-DATA01' (held for 243 msecs). # R: 1, # W: 1 bytesXfer: 2 sectors

2014-02-11T07:23:29.352Z cpu4:1146119)FS3Misc: 1565: Long VMFS rsv time on 'THSLOW-DATA01' (held for 245 msecs). # R: 1, # W: 1 bytesXfer: 2 sectors

2014-02-11T07:23:51.612Z cpu5:1146119)FS3Misc: 1565: Long VMFS rsv time on 'THSLOW-DATA01' (held for 533 msecs). # R: 1, # W: 1 bytesXfer: 2 sectors

2014-02-11T07:23:53.492Z cpu4:1146119)FS3Misc: 1565: Long VMFS rsv time on 'THSLOW-DATA01' (held for 246 msecs). # R: 1, # W: 1 bytesXfer: 2 sectors

2014-02-11T07:25:29.229Z cpu5:32794)WARNING: ScsiDeviceIO: 1223: Device naa.203c001378ae0119 performance has deteriorated. I/O latency increased from average value of 44090 microseconds to 977489 microseconds.

2014-02-11T07:25:31.187Z cpu0:32789)ScsiDeviceIO: 1203: Device naa.203c001378ae0119 performance has improved. I/O latency reduced from 977489 microseconds to 190612 microseconds.

2014-02-11T07:25:39.470Z cpu3:974615)ScsiDeviceIO: 1203: Device naa.203c001378ae0119 performance has improved. I/O latency reduced from 190612 microseconds to 87346 microseconds.

2014-02-11T07:26:26.384Z cpu1:1146119)FS3Misc: 1565: Long VMFS rsv time on 'THSLOW-DATA01' (held for 263 msecs). # R: 1, # W: 1 bytesXfer: 2 sectors

2014-02-11T07:27:09.652Z cpu6:32795)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e80868080, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-02-11T07:27:09.652Z cpu6:32795)ScsiDeviceIO: 2337: Cmd(0x412e80868080) 0x1a, CmdSN 0x127a0 from world 0 to dev "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2014-02-11T07:32:09.405Z cpu7:32796)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e8080d840, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-02-11T07:32:09.405Z cpu7:32796)ScsiDeviceIO: 2337: Cmd(0x412e8080d840) 0x1a, CmdSN 0x127e6 from world 0 to dev "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2014-02-11T07:37:09.402Z cpu4:32793)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e808787c0, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-02-11T07:37:09.402Z cpu4:32793)ScsiDeviceIO: 2337: Cmd(0x412e808787c0) 0x1a, CmdSN 0x12800 from world 0 to dev "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2014-02-11T07:42:09.230Z cpu1:32790)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e80821480, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-02-11T07:42:09.230Z cpu1:32790)ScsiDeviceIO: 2337: Cmd(0x412e80821480) 0x1a, CmdSN 0x1281a from world 0 to dev "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2014-02-11T07:47:09.396Z cpu1:32790)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e807a3880, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-02-11T07:47:09.396Z cpu1:32790)ScsiDeviceIO: 2337: Cmd(0x412e807a3880) 0x1a, CmdSN 0x12854 from world 0 to dev "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2014-02-11T07:52:09.664Z cpu4:32793)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e80819d00, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-02-11T07:52:09.664Z cpu4:32793)ScsiDeviceIO: 2337: Cmd(0x412e80819d00) 0x1a, CmdSN 0x1286e from world 0 to dev "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2014-02-11T07:57:09.944Z cpu1:32790)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e8084d300, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-02-11T07:57:09.944Z cpu1:32790)ScsiDeviceIO: 2337: Cmd(0x412e8084d300) 0x1a, CmdSN 0x12888 from world 0 to dev "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2014-02-11T08:02:09.403Z cpu0:32789)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e80888e40, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-02-11T08:02:09.403Z cpu0:32789)ScsiDeviceIO: 2337: Cmd(0x412e80888e40) 0x1a, CmdSN 0x128ad from world 0 to dev "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2014-02-11T08:07:09.403Z cpu7:32796)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e808410c0, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-02-11T08:07:09.403Z cpu7:32796)ScsiDeviceIO: 2337: Cmd(0x412e808410c0) 0x1a, CmdSN 0x128c7 from world 0 to dev "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2014-02-11T08:12:09.394Z cpu0:32789)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e8082df80, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-02-11T08:12:09.394Z cpu0:32789)ScsiDeviceIO: 2337: Cmd(0x412e8082df80) 0x1a, CmdSN 0x128e1 from world 0 to dev "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2014-02-11T08:17:09.405Z cpu4:32793)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e808623c0, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-02-11T08:17:09.405Z cpu4:32793)ScsiDeviceIO: 2337: Cmd(0x412e808623c0) 0x1a, CmdSN 0x1291b from world 0 to dev "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2014-02-11T08:22:09.407Z cpu7:32796)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x1a (0x412e80856600, 0) to dev "mpx.vmhba0:C0:T0:L0" on path "vmhba0:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2014-02-11T08:22:09.407Z cpu7:32796)ScsiDeviceIO: 2337: Cmd(0x412e80856600) 0x1a, CmdSN 0x12944 from world 0 to dev "mpx.vmhba0:C0:T0:L0" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

I need some help figuring out what is wrong with this service.  It is set to start automatically, but never has after a reboot.  If I start it manually, it will stay started for 9 minutes, and then enter into a stopped state.  After it enters into a stopped state the following error is shown in the event viewer on the vCenter server:

The VMware vSphere Profile-Driven Storage Service service terminated with service-specific error Incorrect function..

Any ideas on where to start to troubleshoot this issue?  A google search doesn't return anything that is of much use.

I have a big problem with ospfs multicast traffic between ESXi 5.5 hosts on hp BL460c g7 servers. My configuration is as follows:

HP BL460c g7

ESXi 5.5.0, 1474528 (patch1)

Emulex_bootbank_elxnet_10.0.725.2-1OEM.550.0.0.1331820 network driver. See my other discission why (ESXi 5.5 P01 (1474528) PSOD HP BL460C G7)

vSwitches not dvSwitches

Different version of Clavister firewall and pfsense (Quagga OSPF) vms

I have noticed that ospfs multicast traffic can't leave the local vswitch. Placing the firewalls on the same host, adjencyn works as it should but as soon as they are on different hosts, they can not establish a 2-way state.

According to a packet dump from one of the pfSense machines, the pfsense can send Hello packets out from its vSwitch (Dest 224.0.0.5) but dosen't recive any at all externaly.

Anyone else experiencing similar problems?

Thanks

Hi All,

I am running in to a very interesting problem. I use vijava to perform config operations on my vm. The vm has 10 network adapters. Here is how config steps goes:

Step-1) First vm-host affinity drs rules are set for the vm.

Step-2) Followed by poweron operation for that vm. This makes the vm move to corresponding esx host. (vm normally takes < 2 minutes to boot completely)

Step-3) At this point when the vm is still booting, I start with configuring network for this vm. i.e. mapping virtual nics of the vm to the port groups present on the esx host.

Q1) Since the VM is still booting and has 10 network adapters, does configuring those adapters at this "in between boot" point can cause any delay in the boot ? I am actually experiencing large vm boot times going as max as 15 minutes and I doubt whether this is causing the delay in boot.

Q2) Is configuring network during vm boot recommended ?
Q3) In general, what are different ways to debug slow vm boot ?

Some more points:

- I am experiencing this issue on ESXi 5.1/5.5

- VM is based on SLES 11 SP3

- VM is sitting on its own unique datastore, which is coming from FC based array. (latency is not an issue)

- The ESXi host on which the VM is running does not have any resource crunch.
- The issue is not always reproducible. Hit rate 1/10 times.

- Tried with reserving the cpu and mem resources for the vm, but the issue still comes as before (1/10 times).

Thoughts ?

Thanks

Nikunj

Hi guys,

Question here regarding load balancing multiple NICs for Iscsi storage access.

I currently have two vmkernel ports configured for Iscsi storage access using two of my physical NICs in the host. I've noticed that even though both NICs show active in the Iscsi software adapter properties, multiple paths exist for every target, I still see most of the network load on one adapter when monitoring using esxtop. I'm curious if I'm missing something, or need to tweak something to get the load spread more evenly across the two NICs?

Thanks for any insight on this

Kevin

Source system:

Dell Equallogic PS Series SAN

ESXi 5 623860 (IBM Bladecenter)

Guests: a mix of VMDK and RDMs(Physical mode), VMFS3/5 (100% Thick provisioned)

Target system:

NetApp FAS3220

ESXi 5.5 1331820 (Cisco UCS)

NFS Datastores/VMDK (NO RDMS) (Thin provisioned)

I'm trying to wrap my head around the migration process here. I have a few guests on the source system that are Windows File servers with fairly large RDMs attached to them (1+TBs each). Every disk on the source side outside of the system disks are pRDMs (iSCSI) attached to the Dell.

With the new system, my goal is to have them migrated over on to NFS datastores with VMDKs only. Volume level (datastore) thick provisoned, VMDK think provisioned. I can see where its not possible to storage vMotion pRDMs to VMDKs on NFS. If this is the case, what are my best options here? V2V with disk conversion during that process?

Any ideas are greatly appreciated.

Does anyone have input what one can do in regards of Fan control/heat detection/dissipation in a (late 2012) mac-mini (6,2)?

Afaics ESXI does not check teh sensors nor controls the fan by itself?

is there maybe something one can do from teh commandline to up teh fac speed?

Hi guys,

In my lab I have a mix of physical and virtual machines, all on the 192.168.1.x (255.255.255.0) network using a DD-WRT router configured as the gateway (192.168.1.1).  I would like to create a new virtual environment that will be used to simulate a physically separate site in the 10.10.10.x (255.0.0.0) network.

Is there a simple way of doing this?  So far I have come up with this:

Deploy some kind of virtual gateway appliance in my virtual environment connecting to both 192.168.1.x and 10.10.10.x.

Suggestions on what to use?

Also, if I use a virtual gateway appliance for this purpose would I have to point my physical servers to it (They only have single NICs and are configured with 192.168.1.x) ?  Or install could I add some kind of a static route when I want one of my physical machines to connect to 10.10.10.x?

Or, would I point the DD-WRT router to the virtual gateway when a client attempts to connect to the 10.10.10.x network?

As I said, I could be just overthinking this and there is a much easier solution I'm just not seeing, I'm sure folks have accomplished what I'm trying to do before.

Many thanks.

I have a group of ESXi 4.x hosts connected to a vCenter 4.1 Server.  I have another 5.1 vCenter Server managing 5.1 hosts.  I want to move my 4.1 ESXi hosts into my 5.1 vCenter Server and upgrade them to 5.1.

Since vCenter 5.1 can manage ESXi 4.x and 5.1 hosts in the same cluster (VMware KB: Upgrading to vCenter Server 5.1 best practices )

Could I add my 4.x hosts to vCenter 5.1, and put them in maintenance mode one-by-one, and then upgrade them?  Would I be able to vmotion the VMs between my 4.x and 5.1 ESXi hosts?

The goal is to reduce or if possible elimate downtime for the virtual machines.

Thanks!

I got a purple screen when I start up a vm with a pci device

With Esxi5 was working fine.

I tested it with 2 vm on different hosts ( but same hardware)

i7 2600 32gb

mb: dq67sw

What can I try

This is 5.5.0 build 1331820 hanging on "nfsclient loaded successfully". The host is part of a ESX cluster and was running fine until after we had to rebuild vCenter server. All other hosts and everything else in the cluster is working fine. Has anyone seen this issue? I tried letting it sit for 20 minutes, then cold booted again and still the same.

This is on an HP ProLiant.

Any ideas will be appreciated.

hello , recently esxi 5.0 has been installed , day ago there was power outage later which we are seeing this error message.

I guess this is the vmkernal issues, but not sure.

Any thoughts would be much appreciated

H/w: UCS c240 m3

Esxi: 5.0

Let me know the cause & how to fix this issue.

Thanks

Mannju

I am trying to allocate more RAM to one of our VM’s.

ESXi 5.5 Build 1474528

VM Version 10

The VM must be shut down to edit the settings.
With the VM shut down the vSphere Web Client is unavailable because the VMWare management databases are on this VM.

We have had serious Problems with one of our VMWare ESXi 5.5. Hosts.

there are 3 VMs running. SBS2k8, Win2012R2 with Exchange 2013 and one Win2012R2 becoming the new Domain Controller. the 3 machines were fine for 3 weeks, but have not had much load - except the SBS Server. migrating Exchange also was fine. we do use PPTP VPN through an SBS Network Interface what will be disabled and done through the new 2012 Server. initially the 2012 Server had one NIC Interface - the E1000 what is the Default Setting, but has a bug of not allowing PPTP packets. therefore we added a 2nd NIC - VMNet3 and PPTP was fine. over night the hypervisor shut down, when the Exchange Server made it's backup. as soon as there is load on the Network the hypervisor crashes... i have not taken a Picture of the Screen yet, but it's the partial dump - out of space message.we did shut down the 2nd 2012 Server and things are fine again since 2 days... can someone confirm, this is an error with the Network Cards. on the existing 2012 Server running Exchange we did disable RSS.

any Help appreciated.

Hello,

I just built a new domain controller running on Server 2012R2. I know that this version is support on ESXi 5.1.0, but I was concerned because 2012 R2 was not available in the drop down list when I created the VM, so I just used 2012. Is this OK? Should I worry about any of the drivers or other software in the VMware Tools install?

Thanks!

Hi,

I converted a VM from Hyper-V to vSphere. To eliminate any surprises during conversion of this critical machine I didn't want to resize huge D: partition that was initially 400GB. The only thing I adjusted was provisioning that I set to Thin. It is fine for this machine (no intensive activity).

The actual Data on partition is 40GB (over 2 years). So I shrinked the partition to 100GB within Windows DISKMGMT.

So I have 100GB partition on 400GB vmdk with Thin provisioning.

The questions:

1. Is there a way to resize the above vmdk to partition size without shutting down the server?

I guess not...

2. What will be the best (secure) way to proceed?

3. Is it correct that if current 400GB is on Thin provisioned vmdk the data store usage is equal to only actual VM(vmdk's and config) size?

If the above is correct there is probably no need to resize vmdk because this VM will never use more than defined Windows partitions. Right?

Thanks.