Has anyone been able to use high sierra on 6.5update1 w/ all patches to date?  Upgrades of vms from 10.12 to 10.13 result in an error in booting represented by a circle with a cross through it.  Creating a brand new guest and booting from the installation media causes Disk  Utility to display a disk labeled disk1s1 with a size of 32KB.  It is not format-able.  The vm's are set to version 13 and the guest os is the highest available in the menu "10.12". 

Hello all,

I'm an ESXi beginner trying to get my graphics cards to passthrough my VM. In ESXi under Host>Manage> under the "hardware tab">PCI Devices, it states the device is not capable for passthrough. At first, I suspected that the hardware wasn't passthrough capable. The first card I tried was a Asus RX550 4G. Called Asus, they could not tell me whether or not it would work.  I then tried a XFX- AMD Radeon HD 7970, this shows the same, Not Capable. I cannot add a PCI Device, this is greyed out. I have scoured the Bios settings for the board and ensured all settings for VT-D are enabled.

Hoping to find help on the next steps or direction here, currently at a loss.

My specs are:

ASUS P9X79-E WS

Intel Xeon Processor E5-2695 v2

CORSAIR Vengeance 32GB (4 x 8GB)

Samsung 850 EVO 1 TB SSD

I truly appreciate any help on this, thanks!

Chris

Current configuration: 

HP Proliant ML350e with Smart Array card

ESXi 5.5 from HP Custom ROM

Boot from 4GB SataDOM

Two logical arrays on Smart Array (LUN 0/Datastore 1 and 1/Datastore 2)

Windows Server 2012 (DC) installed on Datastore 1

Windows Server 2012 (TS) installed on Datastore 2

I have installed a new server from the HP custom ROM and on reboot Datastore 1 is not mounted.  The datastore can be found then mounted by adding storage and keeping the signatures.  Datastore 2 is mounted on boot and loads the VM. 

Searching found the the following KB article, but that did not resolve my issue: 

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2052164

Hello,

After a fresh install of esxi 5.5 my system doesn't seem to work properly after rebooting the host.

When all setup was done with datastores and other settings I wanted to passthrough my graphics card and therefore rebooting the host before adding the card to the host

was necessary.

The problem is now that when esxi is loading/starting all the systemfiles it just stucks on "vmkapei loaded successfully" and manually rebooting doesn't seem to help either.

Same problem occurs on both usb stick and SSD

I also used "formatwithmbr" to even be able to install esxi.

Server specifications;

Mobo: Asus P9D WS

CPU: Intel Xeon 1220v3

RAM: Crucial DDR3 ECC 2x8GB (CT2KIT102472BD160B)

GFX: Gigabyte Radeon R7 250 1GB

SSD: Samsung SSD EVO Basic 840-Series 250GB

PSU: be quiet! Straight Power E9 500W 80+ Gold

Hello Friends,

I am in need of a little help.

have 2 esxi 5.0 host and a vcenter as VM.

My lab was working good since days, but all of a sudden not sure why I am not able to connect to ESXi Hosts using vSphere Client.

Error:: The request failed because the remote server took too long to respond.

Call "ServiceInstance.RetrieveContent" for object "ServiceInstance" on Server "192.168.1.101" failed.

Yes, I am able to connect to vCenter server, when connected to vCenter and opening the VM console, nothing shows up, its a Black screen, as if the VM is off. This is with all VMs on both hosts.

1st I thought it might have to do something with vCenter and I tried connecting to Host individually which I was not able to.

After going through some KBs on vmware and some articles, I checked the firewall state on both hosts.(attached screenshot)

Checked if my workstation can talk to esxi host on port 80, 443, 902. all ports are accessible.

Disabled Symantec endpoint protection and checked. no positive results.

Lastly, I tried browsing the ESXi host via web browser i.e., http://ESXi-IP-Address which redirects me to HTTPS connection with certificate error, when I continue with the cert error, the URL keeps loading and the Host page does not shows up as it should.

This issues are on both hosts. :-(

Can you guys point me to right direction to troubleshoot this issue.

Thanks.

Hi

In vCenter for one of the ESXi server I am getting  error as "bootbank cannot be found at path /bootbank"

Reboot is temporary solution for this.

Out of two devices there is none USB device at boot time

vmhba32 usb-storage link-n/a usb.vmhba32 () USB

And below is the error details :-

SCSI Level: 2 Is Pseudo: false Status: dead timeout

Is RDM Capable: false Is Removable: true

Can some one please suggest permanent solution if any.

Thanks &  Regards

I've enabled SSH on ESXi 5.1.0 host but I can't access it. No open port 22 is visible via nmap contrary to other host I can access. Is any other way how to enable SSH? I can't reboot the host in the moment.

I'm running Vcenter 6 and ESXi 6 with Update 2 and want to install update 3.  Can I just run the setup on the vcenter server iso to update the server?

I have two HP DL380G6 servers running ESX4i. These servers are equipped with four 1-gigabit NICs. On Server1 all 4NICs are configured and running at 1000mbps.

However, Server2 indicates that one of the network cards is working at 100mbps instead of 1000mbps. 100mbps is listed for both the configured and actual speed, but I can't seem to change it within vSphere/vCenter. The other 3 NICs in server2 are running at 1000mbps.

Any advice would be greatly appreciated!

I first download VM ESXi4.0 file VMware-VMvisor-Installer-4.0.0-171294.x86_64.iso and install on DELL PE2950 Box.

After finish creating VM and open VM console(through vSphere Client, as root user account), I see the same error message: unable to connect to MKS:Could not connect to pipe
.\pipe\vmware-authdpipe the system cannot find the file specified.

Then I upgrade to the latest: VMware-VMvisor-Installer-4.0.0.Update01-208167.x86_64.iso, and vSphere Client also upgade to the latest.

And still met this error message, and cannot install guest os on the VM.

On my ESXi 5.5 U3 servers, I'm seeing regular messages in /var/log/vmkernel about failed valid sense data:

2017-02-23T14:08:16.307Z cpu2:34366)NMP: nmp_ThrottleLogForDevice:2458: Cmd 0x85 (0x412e86932dc0, 34608) to dev "naa.6c81f660d81ddf001a52e77d094d4447" on path "vmhba0:C2:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE

2017-02-23T14:08:16.307Z cpu2:34366)ScsiDeviceIO: 2369: Cmd(0x412e86932dc0) 0x4d, CmdSN 0x105a from world 34608 to dev "naa.6c81f660d81ddf001a52e77d094d4447" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2017-02-23T14:08:16.307Z cpu2:34366)ScsiDeviceIO: 2369: Cmd(0x412e86932dc0) 0x1a, CmdSN 0x105b from world 34608 to dev "naa.6c81f660d81ddf001a52e77d094d4447" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x24 0x0.

I thought this was due to the change in SCSI heartbeats (As per KB 2113956 ) I've applied the workaround:

# esxcli system settings advanced set -i 0 -o /VMFS3/UseATSForHBOnVMFS5

But I'm still seeing the errors. The disc is an onboard RAID card virtual drive:

# esxcli storage nmp device list

naa.6c81f660d81ddf001a52e77d094d4447

   Device Display Name: Local DELL Disk (naa.6c81f660d81ddf001a52e77d094d4447)

   Storage Array Type: VMW_SATP_LOCAL

   Storage Array Type Device Config: SATP VMW_SATP_LOCAL does not support device configuration.

   Path Selection Policy: VMW_PSP_FIXED

   Path Selection Policy Device Config: {preferred=vmhba0:C2:T0:L0;current=vmhba0:C2:T0:L0}

   Path Selection Policy Device Custom Config:

   Working Paths: vmhba0:C2:T0:L0

   Is Local SAS Device: false

   Is USB: false

   Is Boot USB Device: false

The hardware is a PowerEdge R720xd server with a PERC H710P Mini controller.

This is a really odd problem.  I inherited this vmware ESXi5.1 cluster when I was hired to manage the network of a small BioTech company.  Up until now the vCenter Server appliance has been fine.  Then last Friday morning I simply could not connect to the the appliance using the vSphere Client. I get 'An unknown connection error occurred.  (The request failed because of a connection error. (Unable to connect to the remote server))

This is what I /can/ do:

Connect to the host and view the console of the appliance.  I can also SSH into the appliance as well as get to the WebGUI of the appliance.

This is what I've done to diagnose the problem:

Restarted the appliance (multiple times). 

Tried to follow the vmware kb articles for diagnosing the problem, but I gotta say, the terminology used is beyond confusing.  I'm still trying to figure out if I have VIMA or VMA.  Regardless, all the documentation centers on the host and I can see the host, can get to it by SSH and telnet.  I've also restarted the management network on the host.

I've not made any changes to the appliance or the host.  I was planning on installing vCLI on the appliance and needed to upload the SLES 11 SP2 SDKS to it so I could install the pre-requisite devel rpms.  I encountered a bit of an issue getting the ISOs uploaded via WinSCP, but thought that might have been the fact that my laptop suspended after being idle for so long (I started the copy late and just left it overnight since the SDK ISOs are 9+GB total.) I've got plenty of drive space on the appliance but deleted the ISOs anyway. 

What else can I try to get this fixed? Without the vSphere client I can't manage my cluster effectively.

Dear team,

in my environment i have esx 3.5.0 (64607),4.0,4.1 hosts, just want to know is there any impact if i restart management service on production esx hosts 3.5.0, 4.0,4.1

be fore restarting this service do i need to take check anything, is there any pre-requisite ?????

regards

Mr VMware

I setup the defualt Datastore Usage on Disk alarm to email when it triggers.

Now my understanding of the alarm is, if Datastore uses more than 75% of its space it will trigger then email me.  Actually 75% to warn, 85% to alert.

The alarm triggered. as one of my datastores actually is using above 90% of the space.

But the email confused me

Brand new R330

PERC H730

5 X Disk SAS 931GB RAID 5 (Datastore1)

32GB USB Internal (ESXi)

32GB RAM

Very Typical small business setup.

Fresh ESXi 6.5.0 installed yesterday to internal USB drive, setup portal, login to portal locally using Edge, Chome, FF, IE, tried them all, edge works best. Added vm's, added new Datastore1-full partition, created new ISO folder in Datastore1, upload button, browse, choose Windows Server 2012R2 STD.ISO,  the upload gets to about 78% then hangs forever. Cannot ever finish any ISO, tried other ISO, and they all hang after a certain point.

Any ideas?

Tried different folders, sub folders, they all do the same thing. Smaller files work fine, I think it only happens when the files are larger than 4GB.

I added a screenshot, showing that vsphere is still "running" in the background at 79%, but the window opened thinks the upload finished and is only 4GB. This ISO is 5.6GB.

I've upgrade to Esxi 5.5 already and created a vmdk to 4.7 Tb and would like to expand it to 5.6 Tb.  I get the following error message when I attempt to expand it and I don't know why or how to bypass it: Hot-extend was invoked with size (12025908428 sectors) >= 2TB. Hot-extend beyond or equal to 2TB is not supported.

We are having a problem with some of our virtual machines intermittently losing communication with each other, and I’m at a loss as to the source.

We have about 250 VM’s running on about 20 HP BL465C blades installed on two HP C7000 chassis, using the HP Virtual Connect interconnect modules.  The blade chassis are connected to our core Cisco 6500 switches.  The VMWare hosts are at 5.0, the guest VM’s are a mix on Windows 2003, 2008, and 2008R2.

What’s going on is that everything seems to be OK, but then out of nowhere, we will get communication failures between specific machines.    It looks like it’s an ARP issue.  Using PING, it works fine in one direction, but we get an “unreachable” error when going the other way, unless we ping from the target back to the source first.

For example: we have servers, “A” and “B”.   Ping A to B fails with “unreachable”. Ping “B” to “A” works fine.   However after pinging “B” to “A”, we can now ping “A” to “B”, at least for a while until the entry falls out of the ARP cache.  If we go into server “A” and set a static ARP entry (“arp –s”) for server “B”, everything works OK.  Through all this both server “A” and server “B” have no issues communicating with any other machines.

We tried using vMotion to move the servers to a different host, different blade chassis, etc.  Nothing worked except when we put both VM’s on the same host.  Then everything worked OK.  Moving one of the servers to a different host and the problem came back.

It seems like either the ARP broadcast from the one server, or the reply back from the target isn't making it through.  However, according to our networking group, there are no issues showing up Cisco switches.

Early this year, we had an issue where it happened on about a third of machines at the same time (it caused significant outages to production systems!).   It seemed like it was limited to machines on one chassis (but not all of the machines on that chassis).  At that time, we opened up tickets with VMWare and HP.  Neither found anything wrong with our configurations, but somewhere in the various server moves, configuration resets, etc., everything started working.

Since that time we’ve seen it very intermittently on a few machines, but then it seems to go away after a few days.

The issue we found today was that the server we’re using for the Microsoft WSUS server hadn’t been receiving updates from a couple of the member servers.  We could ping from the WSUS to the member server, but not back from the member server unless we put a static ARP entry in the member server.  The member servers are working fine otherwise, talking to other machines OK, etc.   They are a production environment, so we’re limited on the testing we can do.

Also, when it has happened, it seems like always been between machines on the same subnet.  However, most of our servers are on the same subnet, so it might just be coincidence.

I’ve done a lot of internet searching, and have found some postings with similar issues, but haven’t found any solution.  I don’t know if it’s a VMWare issue, HP, Cisco, or Windows issue.

Any assistance would be appreciated.

Mike O'Donnell

I took a minute to read the licensing guide for vSphere 5 and I'm still trying to pull my jaw off the floor. VMware has completely screwed their customers this time. Why?

What I used to be able to do with 2 CPU licenses now takes 4. Incredible.

Today

BL460c G7 with 2 sockets and 192G of memory = 2 vSphere Enterprise Plus licenses
DL585 G7 with 4 sockets and 256G of memory = 4 vSphere Enterprise Plus licenses

Tomorrow

BL460c G7 with 2 sockets and 192G of memory = 4 vSphere Enterprise Plus licenses
BL585 G7 with 4 sockets and 256G of memory = 6 vSphere Enterprise Plus licenses

So it's almost as if VMware is putting a penalty on density and encouraging users to buy hardware with more sockets rather than less.

I get that the vRAM entitlements are for what you use, not necessarily what you have, but who buys memory and doesn't use it?

Forget the hoopla about a VM with 1 TB of memory. Who in their right mind would deploy that using the new license model? It would take 22 licenses to accommodate! You could go out and buy the physical box for way less than that today, from any hardware vendor.

Anyone else completely shocked by this move?

Hello All,

After install ESXi 6.0 via "VMware-VMvisor-Installer-6.0.0.update02-4192238.x86_64-Dell_Customized-A04" on Dell PowerEdge R730, everything is okay !!!

But, if I try to install ESXi 6.5 via "VMware-VMvisor-Installer-6.5.0-4564106.x86_64-Dell_Customized-A00" on Dell PowerEdge R730, my vmnic0 and vmnic1 (Intel X710 DP 10Gb DA/SFP+) are not working !!!

Does anybody know the solution ?

Thanks for your reply.

[root@R730:~] esxcli network nic list

Name    PCI Device    Driver  Admin Status  Link Status  Speed  Duplex  MAC Address        MTU  Description                                          

------  ------------  ------  ------------  -----------  -----  ------  -----------------  ----  ---------------------------------------------------------

vmnic0  0000:01:00.0  i40en  Up            Up          10000  Full    f8:bc:12:05:85:d0  1500  Intel Corporation Ethernet Controller X710 for 10GbE SFP+

vmnic1  0000:01:00.1  i40en  Up            Up          10000  Full    f8:bc:12:05:85:d2  1500  Intel Corporation Ethernet Controller X710 for 10GbE SFP+

vmnic2  0000:0c:00.0  igbn    Up            Down            0  Half    f8:bc:12:05:85:f0  1500  Intel Corporation Gigabit 4P X710/I350 rNDC          

vmnic3  0000:0c:00.1  igbn    Up            Up            1000  Full    f8:bc:12:05:85:f1  1500  Intel Corporation Gigabit 4P X710/I350 rNDC          

vusb0  Pseudo        cdce    Up            Up            100  Full    18:fb:7b:5d:d5:ee  1500  DellTM iDRAC Virtual NIC USB Device              

[root@R730:~] esxcli network nic get -n vmnic0

  Advertised Auto Negotiation: false

  Advertised Link Modes: 1000BaseT/Full, 10000BaseT/Full, 10000BaseT/Full, 40000BaseCR4/Full, 40000BaseSR4/Full

  Auto Negotiation: false

  Cable Type:

  Current Message Level: -1

  Driver Info:

        Bus Info: 0000:01:00:0

        Driver: i40en

        Firmware Version: 5.04 0x800024bc 17.5.11

        Version: 1.1.0

  Link Detected: true

  Link Status: Up

  Name: vmnic0

  PHYAddress: 0

  Pause Autonegotiate: false

  Pause RX: false

  Pause TX: false

  Supported Ports:

  Supports Auto Negotiation: false

  Supports Pause: false

  Supports Wakeon: true

  Transceiver:

  Virtual Address: 00:50:56:52:57:61

  Wakeon: MagicPacket(tm)

Hi, I'm running esxi 6 and having trouble detecting disks. esx just can't see them at all whereas a ubuntu live disk can. I have an ssd and 2 hdd's connected through an adaptec 6405 raid contoller card in their own individual JBOD's, this is a configuration that works on two of our other servers. I have tried re-initialising disk and rebuilding partition table in gparted but nothing seems to work. Any ideas?

Raid controller is on HCL http://www.vmware.com/resources/compatibility/detail.php?deviceCategory=io&productid=20867&deviceCategory=io&details=1&partner=475&releases=273&keyword=6405&page=1&display_interval=10&sortColumn=Partner&sortOrder=Asc

Driver is installed