Am able to ping host ip but can not ping VM client-There are four VM and all connected through VLAN
We need to install a NVidia P2000 (Q0V77A) on a HP ML 360 Gen10 with VMWare esxi 6.5 and pass it in passthrough to a Win2016 Virtual Machine already working.
I found fragmentary information on the internet (no precise and complete official VMWare article) explaining how to configure the video card to be viewed and managed directly by V.M. and the part that worried me is that someone says that the V.M. must be configured with the Bios in EFI mode while the V.M. which I have already operative from the customer is definitely installed in normal Bios mode, being also the mode recommended by VMWare during installation.
The problem is that if i change the Bios in EFI mode, the V.M. not boot anymore.
If the Bios in EFI is an essential prerequisite for the correct operation of the video card, this would mean having to reinstall the virtual machine, the terminal server, the ERP software. Can you give me more precise information?
Thanks a lot.
・ESXi 6.5 U2
・HPE 3PAR StoreServ is connected with iSCSI
・vSAN is also connected
・We are doing troubleshooting on performance and we are trying to change the value of QFullSampleSize
and QFullThreshold (default is 0,8) to 32,4
・Do we need to reboot before we set up all these stuff
I’m really a newbie, so I may be asking something stupid, but I hope you can help me.
I downloaded and installed the HPE Custom Image for ESXi 6.7 GA Install CD on a HPE Proliant Microserver Gen 10 and everything went smoothly.
The thing now is about monitoring.
On the web client I go to Host > Monitor and the system says: This system has no IPMI capabilities, you may need to install a driver to enable sensor data to be retrieved.
Since here https://www.hpe.com/it/it/servers/hpe-esxi.html you can read (in Italian) “it supports Gen 9 and newer servers”
My understanding was that using this image I would not need to install anything else to monitor stuff like the RAID controller status.
Can you help me?
The final goal is to get to know ESXi, in order to make a step forward and offer our customers a better service but I am moving my first steps in this V-world and everything is really interesting but overwhelming.
Thanks in advance.
Hello, I am very new to the community.
I am working on new installing and configure the VCSA , to get Vsphere running receiving an error in the process. I am building the VCSA VM on HP Blade Gen 10 6.7EXSI host
“An error occurred while starting service ‘sps’ VMware vSphere Profile-Driven Storage failed to start”
I will appreciate any help…Thank you
I’m taking the VMware vSphere Deploy, Manage course and was confused about this:
- In one slide, the instructor showed that vCenter Server communicated with the ESXi host using vSphere APi/SDK (The VMware Host Client also communicated using this)
- In another slide, the instructor showed that the vCenter Server communicated with a vCenter agent living on the ESXi host (vpxa). This then communicated with another process called hostd, which then executed commands at the hypervisor…
With the second bullet point in mind, where does the vSphere API/SDK fit in? Is hostd the item that houses the vSphere API? Does vCenter communicate with vpxa, which then communicates with hostd using the vSphere API/SDK?
Clarification would be much appreciated.
So this seems to only happen on certain ESXi versions;
I know the root password I have set during install, and I have tested it to be sure by using keyboard on host directly. But when trying to add to Vcenter or login from web client it says password incorrect.
I have tried changing my windows keyboard and even sopping out special characters with the ones they could be; eg ‘ instead of @ but no joy.
Please, I need to add this host to the vcenter. The ESXi version on there is 6.5U2. The other host with 6.7 and exact same root password and even same physical keyboard used to set password works…
Host affected: HP DL380 Gen8 ESXi 6.5U2
Working host: HP DL380 Gen10 ESXi 6.7
The upgrade and migration path for vCenter Server 6.0 Update 3g and Update 3h has an important note that you may need to consider. There is currently no upgrade or migration path to vCenter Server 6.5 or 6.7 if you deployed vCenter Server Update 3g or 3h with the embedded Postgres DB. We have noted
The post vCenter Server 6.0 Update 3g/3h Upgrade or Migration Path appeared first on VMware Support Insider.
I am trying to add more cores to a VM client running on the following HP Server and I am getting the following error:
Feature ‘Hot-Pluggable virtual HW’ is not licensed with this edition.
What do I need to purchase in order to add more cores? The server has 1 CPU and 6 cores?
Product: VMware vSphere 6 Hypervisor Licensed for 1 physical CPUs (unlimited cores per CPU)
License Key: H129K-0UL9L-28Y88-XXXX-XXXX
Up to 8-way virtual SMP