Quantcast
Channel: VMware Communities: Message List
Viewing all 215174 articles
Browse latest View live
↧

Re: hpnmi failed to load

January 27, 2016, 3:51 pm
$
0
0

Had a PSOD support case with HP & VMware for some BL460 Gen8s and they specifically said to remove the HPNMI driver.  I recently rolled out some Gen9 servers and I saw the same "Kernel based module load of hpnmi failed..." error.  That being said,  the issue applies to Gen9 as well.  Some of the few official HP documents confirming this:

 

"HP NMI Sourcing Driver for VMware ESXi 5.0 is supported on all versions of VMware ESXi 5.x; but it is not supported on HP ProLiant Gen8 servers."

http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c01006246&DocLang=en&docLocale=en_US&jumpid=reg_r11944_u…

 

Under "Release Notes":

Important:

  • HP NMI Sourcing Driver is not needed on Gen8 and forward because the firmware catches and logs the NMI. 
  • Not intended for VMware ESX/ESXi 4.x, ESXi 5.0/vSphere 5.1 and vSphere 5.5

 

Drivers & Software - HP Support Center.


I'm not sure what's more work - downloading and installing the newest Custom HP ISO then removing the HPMNI driver each time or maintaining a fully custom ESXi ISO that excludes the HPNMI driver but has everything else injected.

 

esxcli software vib list | grep hpnmi

esxcli software vib remove -n hpnmi

↧
Search

Re: USBHDがゲストに認識されない

January 27, 2016, 4:00 pm
$
0
0

gowatana さん、レスありがとうございました。

ＵＳＢコントローラーがありませんでした。教えて頂いたとおり、追加したら無事認識されるようになりました。

どうもありがとうございました。

↧
↧

Adding memory to host

January 27, 2016, 4:11 pm
$
0
0


Hello,

 

I need some feedback here.  We have 5 hosts (each has about 128 GB memory) with a total of 96 VMs.  We need to bring each host down to add memory (can be done different days).  I generated a report from Veeam that tells me which host is the ideal candidate to bring down plus other factor such as the VMs could be shutdown during the process.

 

Host 1 has 19 VMs and is a candidate to take down first.  9 VMs can be shutdown during the whole process.

 

Here is my thought process:

 

1) Shutdown the 9 VMs on host 1

 

1A) Set HA to not shuffle the machines around since I am doing this manually.

 

2) VMotion 10 VMs to other hosts

     -  take down other VMs on other hosts to lessen resources (on other hosts, I also have the ability to take down a few VMs)

  

QUESTION: As the VMs are shutdown, the "Memory Usage" will reduce correct for each host?  But I still have to make sure the VMs total memory allocation is lower than the limit of 128 GB event hough some machines are powered down?

 

3) Put in maintenance mode and shutdown host

 

4) Add memory

 

5) Start host and turn on any down machines, VMotion, etc

 

I can have one host with the new added memory run (greater than other hosts) for days correct?  The hosts don't need to have equal memory?

↧

Re: Simple XaaS Items with objectless plugins

January 27, 2016, 4:16 pm
$
0
0

Sorry. I guess I do not have a create for the CE, only their attributes.  I know it can be done because I have seen it done.  We would need to figure that out for this to be viable.

↧

Re: VMMark starting error

January 27, 2016, 4:24 pm
$
0
0

The good news - when I went to check the version I realized I had 3 different versions installed.  So I uninstalled all 3, rebooted, loaded only the latest 64 bit, rebooted and got past my posted problem!!!

 

The bad news  - it just went to the next problem which reads:

java -Xms512m -Xmx1024m -jar c:\STAF\services\STAX\STAXMON.jar

STAXJobMonitor v3.5.16 requires STAF v3.3.3 or later to be running

 

My STAF version is 3.4.23 and as far as I can tell it is running

 

Any suggestions?

 

Thanks

↧
↧

Unable to add External vRO 7 endpoint to vRA 7

January 27, 2016, 4:26 pm
$
0
0

Hi,

 

When attempting to add and external vRO 7 instance to vRA 7 I get the following error: 'Cannot connect on port.'

 

The vRO 7 instance is already added to vRA in the Infrastructure > Endpoints section and data collection is successful.

 

Connectivity between vRA and vRO on 8281 is confirmed. The vRA 7 appliance is out of the box configuration albeit with the vRA plugin installed and activated. The Authentication has been changed to SSO (Legacy) to allow vSphere web client integration. The admin group is defined as a VRO admin group in the domain. I am able to login to the client with members of that group.

 

The vRO 7 appliance has had its SSL certificate replaced with one generated by our internal CA. All certificates in the topology have been imported as well as the vRA SSL certificate, vCenter and root CA.

 

The Administration > Events > Event Logs show the following repeatedly...

 

Request to VCO Failed. Error: 85021-Unable to establish connection to vCenter Orchestrator server

 

The VCAC Catalina.out shows the following error when I attempt the connection in the WEB-UI

 

Unable to connect on port: '8,281'. Message: read timed out.

 

Note the strange ',' (comma)?

 

So far I have tried reconfiguring the VRO 7 instance to use LDAP authentication. This made no difference.

I then have now deployed a completely new vRO 7 instance. Still no difference, same errors.

 

The connection string I'm using is the fully qualified hostname only. Port is 8281. Authentication is SSO although using BASIC results in the same problem.

 

Anyone out there using VRA7 with an External vRO 7 instance?

↧

Re: Phantom ARP Responder

January 27, 2016, 4:26 pm
$
0
0

Hello,

 

I know you're on Fusion, but it is the same in Workstation and there I knew where to find the details in the documentation:

VMware Workstation 12 Pro Documentation Center

 

In short, it is the DHCP server that is already assigned to the .254 address.

 

--
Wil

↧

Re: Script not performing Task for all objects using the Get-Content cmdlet

January 27, 2016, 4:27 pm
$
0
0

That worked. It now renames the log bundle correctly. Question: is the original cryptic file supposed to remain after the file is renamed? I'm seeing 2 files now. The cryptic named one and the host named one.

↧
Search

Cannot create datastore vCenter 5.5

January 27, 2016, 4:27 pm
$
0
0

I have a Drobo B1200i with 22TB of empty space on it connected by iScsi.  I created a 1TB volume on it, selecting the multi-host option.  I connected to it using the iSCSI Software Adapter.  It appears to connect and mount properly, both the Drobo Dashboard and the vSphere client show it is connected.  When I try to create a new datastore, it finds my LUN and I can select it, I chose the VMFS-5 file system, the current disk layout says there is only one primary partition.  After I click finish it spins for a while and then comes back with the following error.

 

Call "HostDatastoreSystem.CreateVmfsDatastore" for object "datastoreSystem-9" on vCenter Server "vcenter" failed.

 

What am I doing wrong?  Any advice would be very much appreciated.

↧
↧

Re: VMMark starting error

January 27, 2016, 4:30 pm
$
0
0

Do you see the STAFProc.exe process running in task manager?

↧

Re: vmware and kali could not conect real network

January 27, 2016, 4:36 pm
$
0
0

It makes no sense to use Kali like this.
To really investigate the traffic in the wireless network Kali needs exclusive access to the wireless adapter.
That means remove the networkcard from the VM and instead use a wireless-usb-adapter.
Every other approach gives you results that are influenced by the extra layer

↧

Re: Cannot create datastore vCenter 5.5

January 27, 2016, 4:43 pm
↧

Re: Adding memory to host

January 27, 2016, 5:01 pm
$
0
0

QUESTION: As the VMs are shutdown, the "Memory Usage" will reduce correct for each host?  But I still have to make sure the VMs total memory allocation is lower than the limit of 128 GB event hough some machines are powered down?

That's right, with every VM you shutdown it will reduce resource utilisation from available resources. you have mentioned HA in your discussion, but there's no mention of DRS, is it also enabled on your cluster? if so, best way to go about is, try to enter host in maintenance mode (disable HA Adminission control policy), DRS will help you to find best possible hosts among remaining 4 in your environment and do live migration of VMs from the host which you are entering in maintenance mode.

if you see that available resource are not enough to support all the VMs to migrate then you can make a decision to shutdown some VMs.

Total memory allocation can be overcommitted, but might give you negative impact on performance if services are going in higher utilisation, that's why earlier I mentioned that let the DRS do this for you.

I can have one host with the new added memory run (greater than other hosts) for days correct?  The hosts don't need to have equal memory?

yes, your cluster will still be operational. won't be a good idea to run your cluster like that for long but in your case since you are upgrading RAM in your hosts, should be ok for a day or two.

↧
↧

Re: vRealize Orchestrator Endpoint error - (7.0)

January 27, 2016, 5:02 pm
$
0
0

Hi Grant,

 

I'm using vRA 7 and an External instance of vRO 7. In our environment not using adding the port 8281 causes the endpoint not to function and data collection to fail. I still need therefore to add 8281 in the string as per the below!

 

https://vROServerFullyQualified:8281/vco

 

Not sure what could be different for us!

 

Cheers

↧

WSX with Workstation Pro 12.1.0 stopped working

January 27, 2016, 5:05 pm
$
0
0

I'm currently using VMWare Workstation Pro 12.1.0.

Unfortunately WSX stopped working after I upgraded my vmware workstation. I'm pretty sure it did work with version 11 because I used to use it all the time.

 

After I log in using FireFox browser, I can no longer be able to see shared virtual machines under "Shared VMs (localhost)" node on the left pane.

I already tried to drop the VM and add it again, but it didn't help.

 

Anybody who's having this problem?

Any temporary work-around?

 

I really want the feature back because it's a very nice feature to have.

↧
Search

Multiple hosts on a single workstation

January 27, 2016, 5:09 pm
$
0
0

Howdy,

 

I'm running multiple VM machines on a single system(Windows 7 64bit) using VMWare Workstation Player 12, and trying to figure out the best was to configure the network adapters in each of the hosts.  I'm a developer and I use Windows7 (both 32 & 64bit) on a couple of systems, Windows Server 2003 on another and Windows Server 2008 on another.  I usually only have two of these systems running at the same time, but sometimes 3.  Each of these needs its own IP address on my network.  Can somebody point me to a white paper or explain the best way to configure each of these so they run properly.

 

One other note I do use a couple of these system to VPN into other networks.

 

Thanks

 

David

↧

VM Attached to Datastore, but not in config

January 27, 2016, 5:22 pm
$
0
0

I have a few VMs that show they are attached to a datastore, but when you look at the settings both in the client and in the vmx file there is nothing that is referring to that datastore.  And, to top it off, the datastore is just a file-like repository that I only upload iso files to to mount to the cd roms.  I've made sure that the iso isn't mounted on the machine (of course) and have poured through every other part of the config, but yet it shows attached to that datastore, both through the client and through a powercli script.

 

When you browse the datastore, there are no folders or files on there that are referring to that virtual machine.  I have about 10 machines all in this predicament.  Any ideas?

 

Thanks!

↧
↧

Re: Cannot create datastore vCenter 5.5

January 27, 2016, 5:22 pm
$
0
0

The GUI does not allow you to create 2 VMFS partition on a single LUN.
You could work around that by creating the second partition via vmkfstools.
But though that is possible I would not recommend it
If the 22tb LUN can be resized - create a second LUN and use the new LUN for the second VMFS-volume.
If you dont have any VMs in the first LUN - delete the LUN and create new volumes and new iscsi-targets.

↧

Re: Help! Vertual machine will not open

January 27, 2016, 5:30 pm
$
0
0

I guess we just found the problem: the VM uses compressed NTFS.
Vdiskmanager from WS 7 failed - so for now I assume NTFS-compression is the root problem.
Removing the compression fails and locks up explorer.
We run chkdsk /f /x /r d: over night in the hope to remove the compression after that.

↧

Re: WSX with Workstation Pro 12.1.0 stopped working

January 27, 2016, 5:36 pm
$
0
0

If you have not done that already destroy the WSX-instance that you use to connect to the host with WS 12.
Create a new instance and check for error messages along the way.
Are you sure that the WSX build you use is supporting WS 12 at all ?

↧
Viewing all 215174 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>