Quantcast
Channel: VMware Communities : Discussion List - ESXi
Viewing all 8132 articles
Browse latest View live

ESXI 6.5 on Lenovo X3650M5 Grafik Beschleunigung

$
0
0

Hallo alle, Hello all

 

Ich habe einen ESXI auf einem Lenovo X3650M5 aufgesetzt. / I have installed an ESXI 6.5 on a Lenovo x3650M5 Server
Lizenz ist die Kostenfreie  /  It´s the Free Licence
Aktuell habe ich probehalber 4 Systeme Aufgesetzt, Win7Pro / Win10Pro / Srv 2012R2 und Srv2016/   I Installed 4 VM´s, Windows 7/10 and Server 2012R2/2016

 

Jetzt habe ich gemerkt das bei ALLEN Systemen die 3D Einstellung ausgegraut ist.  /  on ALL VM´s the 3D Grafik is grey
Dies liegt sicher daran das nur eine Matrox G200 onboard vorhanden ist.  /  I Thinks it´s because there is only a Matrox G200 onboard Graphic

 

Ich habe testweise eine Nvidia NVS 295 mal rein, diese wird unter Hardware aufgelistet und man kann theoretisch PassTrough aktivieren.
                         /  for Tests i build in a Quadro NVS295,

 

 

 

aber an den Grafikeinstellungen ändert dies nichts.  /  but it changed nothing on speed

 

Was ist die günstigste Lösung um eine Hardware Beschleunigung zu bekommen?   /  what is the cheepest Thing i can do to become Hardware Acceleration

 

 

 

 

 

Danke für eure Ideen schon mal im Vorraus / Thanks u all

 

 

Grüße

 

Bernd

 

Nachricht geändert durch Bernd Kübler


Poor performance w/ SATA disks & LSI SAS HBA (SOLVED - Finally!)

$
0
0

I just solved a long-standing storage performance issue when using cheap consumer SATA disks for ESXi 5.5.0 datastores through an LSI 9201-16i SAS HBA. Hopefully this helps somebody else.

 

Symptoms:

 

  • Sudden, extreme disk latency during I/O heavy operations, like:
    • Copying a large file in a VM with a freshly created thick-lazy_zero VMDK
    • Creating thick-eager_zero VMDKs
    • Creating storage pools in Server 2012's "Storage Spaces" feature
    • SMB shares under heavy write load would "disappear"
    • Windows resource monitor reporting 100% Disk Active Time but zero MB/sec
    • Using SSH/SCP to copy files to datastores

 

  • Disk I/O errors and degraded performance messages in /var/log/vmkernel.log
  • Disks will "disappear" completely from ESXi during high I/O, then eventually re-appear when the I/O stops
  • Only occurs with cheap SATA spinning disks (not SSDs or enterprise SAS)
  • Same disks work fine while connected to onboard AHCI (ex. Intel ICH) SATA, but choke when connected via the LSI HBA.
  • Controller and disks work fine when used with non-ESX (ex. Windows Server) on the bare metal.

 

Finally after a lot of pain I discovered how to fix it. As with so many things in IT, when you find the root cause it's very satisfying.

 

Root Cause:

 

  • The VAAI (vStorage APIs for Array Integration) storage acceleration feature in ESXi uses a special SCSI command 0x93 WRITE_SAME.
  • Cheap SATA disks often do not support WRITE_SAME.
  • When the 0x93 WRITE_SAME command hits the SATA disk, it hiccups, flushes its buffer, and causes a huge latency.
  • For whatever reason, SAS HBAs pass the 0x93s through to the disks (which start choking them) but AHCI SATA controllers do not. (Not sure why)
  • If the 0x93s come fast & heavy, the disk will "disappear" momentarily from ESXi, and eventually be discovered again when the 0x93s stop.
  • I suspect if the disks were connected with hardware RAID, the controller might think they're "failed" and start populating a hot spare.

 

Solution:

 

Disable VAAI on the ESXi host - Configuration -> Advanced Settings:

 

  • Set DataMover -> DataMover.HardwareAcceleratedInit = 0
  • Set DataMover -> DataMover.HardwareAccelerated Move = 0
  • Set VMFS3 -> VMFS3.HardwareAcceleratedLocking = 0

 

Depending on your setup, maybe only some of these features may need to be set. A reboot of the host is not required. See KB1033665.

 

Hopefully somebody will find this useful - Or perhaps somebody will tell me something I missed...

 

Regards,

 

Dave

vSphere Server 6.5 web client - endless session

$
0
0

I have installed vSphere Server 6.5 on Windows Server 2016

I need an endless session. I used this manual: Increasing the VMware vSphere Web Client session timeout period (2040626) | VMware KB

1. In the file C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\webclient.properties set "session.timeout = 0"

Once a day, the error "vsphere web client session is no longer authenticated"

In what there can be a reason and how to remove this error?

2. For vSphere HTML5 Client, you can not set an infinite session. By setting "session.timeout" = 0 or -1 I get the error "vsphere web client session is no longer authenticated" when trying to log in.

How do I set an infinite session for the HTML5 Client?

thanks for answers

Configured scratch location doesn't work after upgrade to ESXi 6.5

$
0
0

Hi,
My configured scratch location for some reason doesn't work after upgrading to ESXi 6.5.

I set up parameter ScratchConfig.ConfiguredScratchLocation to a persistent storage. The folder exists and worked before the upgrade.

After each reboot ScratchConfig.CurrentScratchLocation is always set to /scratch while ScratchConfig.ConfiguredScratchLocation is /vmfs/volumes/volume01/scratches/host01

I'm not sure if this is related but to upgrade ESXi I had to provide boot parameter preferVmklinux=TRUE as my USB drive wasn't visible and later I run these commands:

esxcli system settings kernel set -s preferVmklinux -v FALSE

esxcli system module set --enabled=false –m vmkusb

 

Thanks for your help in advance,

Lukasz

ESXI 6.0.0 purple diagnostic screen PCPU, TLB

$
0
0

Hallo!

Help me please!

Approximately 3-4 times a week (sometimes host work 2-3 weeks without violet screen), ESXI falls and a violet screen comes out. I can not understand the reason!

 

HOST: Supermicro X10DRI/2xCPU XEON E5-2630 V4/192Gb/LSI SAS 9271-8i/4xSAS 4000Gb in RAID 5

Vmware Esxi Update No Space Left On Device Error

$
0
0

Hello,

I'm trying to install updates from a zip file but always gives the same error. "No Space Left On Device"

But there is a plenty of space on Device.

When i try to run

esxcli software vib update -d /vmfs/volumes/datastore1/ESXi600-201703001.zip

it gives that error:

[InstallationError]

[Errno 28] No space left on device

       vibs = VMware_bootbank_misc-drivers_6.0.0-3.57.5050593

Please refer to the log file for more details.

 

And in the log file:

2017-04-02T00:13:50Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = 'localcli system visorfs ramdisk list |            grep /stagebootbank &&            localcli system visorfs ramdisk remove -t /tmp/stagebootbank', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2017-04-02T00:13:50Z esxupdate: BootBankInstaller.pyc: WARNING: Cannot remove staging directory: [Errno 16] Device or resource busy: '/tmp/stagebootbank'

2017-04-02T00:13:50Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = 'localcli system visorfs ramdisk list |            grep /stagebootbank &&            localcli system visorfs ramdisk remove -t /tmp/stagebootbank', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2017-04-02T00:13:51Z esxupdate: root: ERROR: Traceback (most recent call last):

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 462, in <module>

2017-04-02T00:13:51Z esxupdate: root: ERROR:     main()

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 453, in main

2017-04-02T00:13:51Z esxupdate: root: ERROR:     ret = CMDTABLE[command](options)

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 362, in VibInstallCmd

2017-04-02T00:13:51Z esxupdate: root: ERROR:     checkacceptance=checkacceptance)

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/Transaction.py", line 250, in InstallVibsFromSources

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/Transaction.py", line 356, in _installVibs

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/Transaction.py", line 399, in _validateAndInstallProfile

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/HostImage.py", line 710, in Stage

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/HostImage.py", line 483, in _download_and_stage

2017-04-02T00:13:51Z esxupdate: root: ERROR: InstallationError: ('VMware_bootbank_vsanhealth_6.0.0-3000000.3.0.3.58.5224738', '[Errno 28] No space left on device')

 

"vdf -h" Output

Ramdisk                   Size      Used Available Use% Mounted on

root                       32M      244K       31M   0% --

etc                        28M      204K       27M   0% --

opt                        32M        0B       32M   0% --

var                        48M      428K       47M   0% --

tmp                       256M       20K      255M   0% --

iofilters                  32M        0B       32M   0% --

hostdstats                303M        2M      300M   0% --

As you can see %0 is used on /tmp i dont know why gives that error.

 

How can i fix this problem ? I cant update my esxi 3620759 to 5224934.

Virtual machine disks consolidation failed / The virtual machine has exceeded the maximum downtime of 12 seconds for disk consolidation

$
0
0

For Community information or maybe somebody will advice something interesting.

 

My Environment:

ESXi 5.5 u2

vCenter 5.5 u2

only 1 VSAN datastore in cluster

2 cluster in vCenter

 

Hi.

 

We have VM which from some time cant be consolidated. What we know about alerts and this VM.

 

Screenshot_2a.png

 

Screenshot_1.png

 

Screenshot_2.png

 

Screenshot_5.png

Screenshot_3.png

 

Screenshot_6.png

Screenshot_7.png

 

 

Screenshot_8a.png

Screenshot_8.png

Screenshot_9.png

Screenshot_10.png

 

In logs on this VM (vmware.log) we found:

 

2016-05-04T20:03:57.420Z| vcpu-0| I120: DISKLIB-LIB  : Free disk space is less than imprecise space neeeded for combine (0x1fbd3800 < 0xd3714800, in sectors). Getting pre

cise space needed for combine...

2016-05-04T20:04:10.494Z| vcpu-0| I120: SnapshotVMXConsolidateHelperProgress: Stunned for 13 secs (max = 12 secs). Aborting consolidate.

2016-05-04T20:04:10.494Z| vcpu-0| I120: DISKLIB-LIB :DiskLibSpaceNeededForCombineInt: Cancelling space needed for combine calculation

2016-05-04T20:04:10.495Z| vcpu-0| I120: DISKLIB-LIB  : DiskLib_SpaceNeededForCombine: failed to get space for combine operation: Operation was canceled (33).

2016-05-04T20:04:10.495Z| vcpu-0| I120: DISKLIB-LIB  : Combine: Failed to get (precise) space requirements.

2016-05-04T20:04:10.495Z| vcpu-0| I120: DISKLIB-LIB  : Failed to combine : Operation was canceled (33).

2016-05-04T20:04:10.495Z| vcpu-0| I120: SNAPSHOT: SnapshotCombineDisks: Failed to combine: Operation was canceled (33).

 

After fast troubleshooting with Vmware engineer we receive summary:

 

"I tracked down that KB I mentioned, and it's somewhat related but it also seems to be related to a newer VSAN-specific bug.

I mentioned this calculation that must be done in certain cases.

When a consolidation is called, the host does a basic check - is the snapshot file larger than the amount of free space on the datastore. If there is definitely enough free space, itt proceeds with the consolidation.

However, if the snapshot file is larger than the amount of free space then we need to do a more detailed calculation to determine if we will be able to consolidate without filling up the datastore.

We allow 12 seconds to perform this calculation - if it takes any longer, then we abort the consolidation.

This is exactly what we see in your logs.

As we saw, there is more than enough free space on the VSAN datastore

Screenshot_9.png


so we should not need to be doing this precise calculation. I've found a bug in VSAN where there is a problem with the calculation, meaning that consolidation may fail for VMs with large snapshot files:

https://kb.vmware.com/kb/2118663

We don't see the exact symptoms here - your consolidation is not failing with 'insufficient space', it is failing with 'operation was cancelled'. But it seems to be related to the same root cause.

The fix for the problem went into 5.5U3b so obviously that is not an option right now.

As far as I know, the workaround mentioned in the KB may also not be an option as I don't think you would have a suitable datastore to send the clone to.

However, there is another workaround which has helped some other customers:

- Shut down the virtual machine

- Right-click the virtual machine and click Edit Settings.

- Click the Options tab.

- Under Advanced, click General.

- Click Configuration Parameters and add snapshot.maxConsolidateTime = 120

  This should allow more time for the calculation to complete and may allow consolidation to proceed."


After this investigation i additional KB which can confirm this way of working:



VMware KB:    Snapshot consolidation in VMware ESXi 5.5.x and ESXi 6.0.x  fails with the error: maximum consolidate ret…

If somebody was some similiar experience ? and can advice something?

We have only VSAN datastore then we cant migrate this VM to some other local datastore.

 

If i will have some updates i will put information on post.

 

Greetings

Sebastian    

Copying Patch Baselines in vCenter/ESXi 5.5

$
0
0

I am trying to determine if there is a simpler/faster way to copy a Patch Baseline as to not have to manually copy all of the patches into a 'new' baseline just to add any new additional released patches.

 

Currently running ESXi 5.5.0 Patch 10 but would like to create a baseline that would bring up the hosts to ESX 5.5.0 Patch 11 while maintaining the original Patch 10 baseline.

 

I am running vCenter Server 5.5.0 Update 3E and if it is possible through the vSphere client, that would be ideal but I can also use PowerCLI if that is the only way.


VMs slow and can't edit their settings

$
0
0

Similar to Cant Open edit setting of any vm but not quite and restart didn't work.

 

ESXi 5.5.0 host, all VMs suddenly started freezing, and I can't do anything via vSphere Client.

Can't even load the host's configuration - the tab is just blank
Right clicking any VM to edit its settings does this after freezing for a while


New VM Wizard does the same with a different error

 

viclient log attached

OVF generated for Vcenter 6.5 has backward compatibility issues with 6.0

$
0
0

OVF generated with older versions of ovftool(less than 4.2 ) uses SHA1 for manifest file which works fine on Vcenter 6.0 but not on vcenter 6.5. Same with OVF generated with 4.2 version of ovftool uses SHA256(can be changed)  for manifest file which works fine on Vcenter 6.5 and not on 6.0 .

 

To summarise SHA1 works on 6.0 but not on 6.5 and SHA256 works on 6.5 but not on 6.0 .

 

Is there a way to generate common  OVF which works on both 6.0 and 6.5  ?

Install ESXi 6.5 on R730 with Intel X710

$
0
0

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)

Faster Way to Remount NFS Datastores?

$
0
0

We have a few NFS-based datastores (Server for NFS on Windows) that become inactive whenever we have to reboot the hosting server.  The only ways I can find to get the datastores to become active again are 1) restart the ESXi host, 2) unmount and remount the datastore in ESXi or vCenter, and 3) wait and it will apparently reactivate at some point on its own.  All of these have drawbacks.  #2 is the fastest I've found, but whenever I do that, I lose the vCenter permissions on the datastore, so I have to spend time reassigning permissions to ensure that users aren't able to accidentally create VMs on there.  Is there a different way to explicitly reactivate inactive NFS datastores without unmounting?  Or, alternatively, is there a way to force #3 to happen more quickly?

 

Thanks

 

Mike

 

catastrophic failure: many missing virtual machines (ESXi 6.0)

$
0
0

I returned to my lab to find that the majority of my virtual machines are missing. The host did not experience a power outage (checked the UPS) or hardware failure (checked iLO), the file systems are intact as there are a few virtual machines and these were not powered on at the time. I generated a support bundle before gracefully power cycling the server, however I don't see anything obvious to explain the loss. Before anyone asks, no,  there was no backup (and I hadn't gotten as far as implementing any kind of backup/replication yet). I'm now forced to rebuild my entire lab.

 

Is there any way to figure out what happened using the support bundle?

 

If I'm rebuilding the lab to study VCP6-DCV do I go with version 6.0 or 6.5? My training was on 6.0.

VMHosts don't restart in HA Cluster upon failure of host

$
0
0

Hi,

We have two hosts, ESXi v4.1 (vCenter 5), HA clustered.  One host shuts down periodically, and the VM's are migrated to the to the other host, but they don't automatically start up.  I thought in properly configured HA, vm's are powered back on another host in the cluster automatically.

 

My cluster settings:

vSphere HA is checked

DRS is NOT checked

Host monitoring is checked

Admission control is disabled

vm options:

vm restart priority is High

Host isolation response is "shutdown'

-- i suspect this option, but i've found this is correct option.

-- vSphere HA isolation response... which to use when? - VMware vSphere Blog

 

Any ideas on how to get hosts to restart automatically?

 

Thanks

Jason

Unable do set SR-IOV on a Dell R630 with Intel I350 nics

$
0
0

Hi,

 

I am trying to enable SR-IOV on my server.

 

I have a Dell R630 running the evaluation version of ESXi 6.0u3

# esxcli system version get   Product: VMware ESXi   Version: 6.0.0   Build: Releasebuild-5572656   Update: 3   Patch: 69

 

The two network cards are Intel I350-t (quad ports and dual ports) :

# esxcfg-nics -l
Name    PCI          Driver      Link Speed     Duplex MAC Address       MTU    Description                  
vmnic0  0000:01:00.0 igb         Up   1000Mbps  Full   24:6e:96:5f:aa:88 1500   Intel Corporation I350 Gigabit Network Connection
vmnic1  0000:01:00.1 igb         Up   1000Mbps  Full   24:6e:96:5f:aa:89 9000   Intel Corporation I350 Gigabit Network Connection
vmnic2  0000:01:00.2 igb         Up   1000Mbps  Full   24:6e:96:5f:aa:8a 1500   Intel Corporation I350 Gigabit Network Connection
vmnic3  0000:01:00.3 igb         Up   1000Mbps  Full   24:6e:96:5f:aa:8b 1500   Intel Corporation I350 Gigabit Network Connection
vmnic4  0000:04:00.0 igb         Up   1000Mbps  Full   a0:36:9f:e7:6a:e6 1500   Intel Corporation I350 Gigabit Network Connection
vmnic5  0000:04:00.1 igb         Up   1000Mbps  Full   a0:36:9f:e7:6a:e7 9000   Intel Corporation I350 Gigabit Network Connection

 

SR-IOV is enabled in the bios (globally, and for each devices). SR-IOV is marked as supported and disabled in vCenter.

 

I don't have a max_vfs parameter for the igb driver :

# esxcli system module parameters list -m igb
Name                   Type          Value  Description                                                                                        
---------------------  ------------  -----  ----------------------------------------------------------------------------------------------------
DMAC                   array of int         Disable or set latency for DMA Coalescing ((0=off, 1000-10000(msec), 250, 500 (usec))              
EEE                    array of int         Enable/disable on parts that support the feature                                                   
IntMode                array of int         Change Interrupt Mode (0=Legacy, 1=MSI, 2=MSI-X), default 2                                        
InterruptThrottleRate  array of int         Maximum interrupts per second, per vector, (max 100000), default 3=adaptive                        
LLIPort                array of int         Low Latency Interrupt TCP Port (0-65535), default 0=off                                            
LLIPush                array of int         Low Latency Interrupt on TCP Push flag (0,1), default 0=off                                        
LLISize                array of int         Low Latency Interrupt on Packet Size (0-1500), default 0=off                                       
MDD                    array of int         Malicious Driver Detection (0/1), default 1 = enabled. Only available when max_vfs is greater than 0
Node                   array of int         set the starting node to allocate memory on, default -1                                            
QueuePairs             array of int         Enable Tx/Rx queue pairs for interrupt handling (0,1), default 1=on                                
RSS                    array of int         Number of Receive-Side Scaling Descriptor Queues (0-8), default 1, 0=number of cpus                
VMDQ                   array of int         Number of Virtual Machine Device Queues: 0-1 = disable, 2-8 enable, default 0                      
debug                  int                  Debug level (0=none, ..., 16=all)                                                                  
heap_initial           int                  Initial heap size allocated for the driver.                                                        
heap_max               int                  Maximum attainable heap size for the driver.                                                       
skb_mpool_initial      int                  Driver's minimum private socket buffer memory pool size.                                           
skb_mpool_max          int                  Maximum attainable private socket buffer memory pool size for the driver.

 

If I try the esxcli command as described here, I have the following error :

# esxcli system module parameters set -m igb -p "max_vfs=0,1,0,0,1,0"
Unable to set module parameters the following params are invalid: max_vfs

 

The content of hostd.log :

2017-08-16T07:57:54.896Z error hostd[6AEC1B70] [Originator@6876 sub=Solo.VmwareCLI opID=esxcli-80-c95c user=root] GetPrimitiveParam: Cannot find (help)
2017-08-16T07:57:54.896Z info hostd[6AEC1B70] [Originator@6876 sub=Solo.VmwareCLI opID=esxcli-80-c95c user=root] Dispatch set
2017-08-16T07:57:54.897Z info hostd[6AEC1B70] [Originator@6876 sub=Solo.VmwareCLI opID=esxcli-80-c95c user=root] Dispatch set done
2017-08-16T07:57:54.897Z info hostd[6AEC1B70] [Originator@6876 sub=Solo.VmwareCLI opID=esxcli-80-c95c user=root] Dispatch set failed
2017-08-16T07:57:54.897Z info hostd[6AEC1B70] [Originator@6876 sub=Default opID=esxcli-80-c95c user=root] AdapterServer caught exception: vim.EsxCLI.CLIFault
2017-08-16T07:57:54.897Z info hostd[6AEC1B70] [Originator@6876 sub=Solo.Vmomi opID=esxcli-80-c95c user=root] Activation [N5Vmomi10ActivationE:0x6b1295d0] : Invoke done [set] on [vim.EsxCLI.system.module.parameters:ha-cli-handler-system-module-parameters]
2017-08-16T07:57:54.897Z verbose hostd[6AEC1B70] [Originator@6876 sub=Solo.Vmomi opID=esxcli-80-c95c user=root] Arg append:
--> (null)
2017-08-16T07:57:54.897Z verbose hostd[6AEC1B70] [Originator@6876 sub=Solo.Vmomi opID=esxcli-80-c95c user=root] Arg force:
--> (null)
2017-08-16T07:57:54.897Z verbose hostd[6AEC1B70] [Originator@6876 sub=Solo.Vmomi opID=esxcli-80-c95c user=root] Arg module:
--> "igb"
2017-08-16T07:57:54.897Z verbose hostd[6AEC1B70] [Originator@6876 sub=Solo.Vmomi opID=esxcli-80-c95c user=root] Arg parameterstring:
--> "max_vfs=0,1,0,0,1,0"
2017-08-16T07:57:54.897Z info hostd[6AEC1B70] [Originator@6876 sub=Solo.Vmomi opID=esxcli-80-c95c user=root] Throw vim.EsxCLI.CLIFault
2017-08-16T07:57:54.897Z info hostd[6AEC1B70] [Originator@6876 sub=Solo.Vmomi opID=esxcli-80-c95c user=root] Result:
--> (vim.EsxCLI.CLIFault) {
-->    faultCause = (vmodl.MethodFault) null,
-->    errMsg = (string) [
-->       "Unable to set module parameters the following params are invalid: max_vfs "
-->    ],
-->    msg = ""
--> }
2017-08-16T07:57:54.897Z warning hostd[6AEC1B70] [Originator@6876 sub=Locale opID=esxcli-80-c95c user=root] Resource module 'EsxCLI' not found.
2017-08-16T07:57:54.897Z warning hostd[6AEC1B70] [Originator@6876 sub=Locale opID=esxcli-80-c95c user=root] Resource module 'EsxCLI' not found.

 

When I try with the vSphere web client :

2017-08-16T08:03:57.907Z info hostd[69C80B70] [Originator@6876 sub=Hostsvc opID=3a8c2c12-a42b-4adf-822a-45e9a8818bbf-4287-ngc-f9-1b-c9fe user=vpxuser:xxx] Modifying SR-IOV Configuration of [igb]
2017-08-16T08:03:57.907Z error hostd[69C80B70] [Originator@6876 sub=Hostsvc opID=3a8c2c12-a42b-4adf-822a-45e9a8818bbf-4287-ngc-f9-1b-c9fe user=vpxuser:xxx] Failed to update SR-IOV configuration of module: igb
2017-08-16T08:03:57.908Z info hostd[69C80B70] [Originator@6876 sub=Default opID=3a8c2c12-a42b-4adf-822a-45e9a8818bbf-4287-ngc-f9-1b-c9fe user=vpxuser:xxx] AdapterServer caught exception: vim.fault.PlatformConfigFault
2017-08-16T08:03:57.908Z info hostd[69C80B70] [Originator@6876 sub=Vimsvc.TaskManager opID=3a8c2c12-a42b-4adf-822a-45e9a8818bbf-4287-ngc-f9-1b-c9fe user=vpxuser:xxx] Task Completed : haTask-ha-host-vim.host.PciPassthruSystem.updatePassthruConfig-66872711 Status error
2017-08-16T08:03:57.908Z info hostd[69C80B70] [Originator@6876 sub=Solo.Vmomi opID=3a8c2c12-a42b-4adf-822a-45e9a8818bbf-4287-ngc-f9-1b-c9fe user=vpxuser:xxx] Activation [N5Vmomi10ActivationE:0x69f22c00] : Invoke done [updatePassthruConfig] on [vim.host.PciPassthruSystem:ha-pcipassthrusystem]
2017-08-16T08:03:57.908Z verbose hostd[69C80B70] [Originator@6876 sub=Solo.Vmomi opID=3a8c2c12-a42b-4adf-822a-45e9a8818bbf-4287-ngc-f9-1b-c9fe user=vpxuser:xxx] Arg config:
--> (vim.host.PciPassthruConfig) [
-->    (vim.host.SriovConfig) {
-->       id = "0000:01:00.0",
-->       passthruEnabled = false,
-->       sriovEnabled = true,
-->       numVirtualFunction = 1
-->    }
--> ]
2017-08-16T08:03:57.908Z info hostd[69C80B70] [Originator@6876 sub=Solo.Vmomi opID=3a8c2c12-a42b-4adf-822a-45e9a8818bbf-4287-ngc-f9-1b-c9fe user=vpxuser:xxx] Throw vim.fault.PlatformConfigFault
2017-08-16T08:03:57.908Z info hostd[69C80B70] [Originator@6876 sub=Solo.Vmomi opID=3a8c2c12-a42b-4adf-822a-45e9a8818bbf-4287-ngc-f9-1b-c9fe user=vpxuser:xxx] Result:
--> (vim.fault.PlatformConfigFault) {
-->    faultCause = (vmodl.MethodFault) null,
-->    text = "Failed to update SR-IOV configuration of module(s): igb",
-->    msg = ""
--> }
2017-08-16T08:03:58.000Z info hostd[FFA0CB20] [Originator@6876 sub=Hostsvc.VmkVprobSource] VmkVprobSource::Post event: (vim.event.EventEx) {
-->    key = -1,
-->    chainId = 1952804399,
-->    createdTime = "1970-01-01T00:00:00Z",
-->    userName = "",
-->    datacenter = (vim.event.DatacenterEventArgument) null,
-->    computeResource = (vim.event.ComputeResourceEventArgument) null,
-->    host = (vim.event.HostEventArgument) {
-->       name = "host.tld",
-->       host = 'vim.HostSystem:ha-host'
-->    },
-->    vm = (vim.event.VmEventArgument) null,
-->    ds = (vim.event.DatastoreEventArgument) null,
-->    net = (vim.event.NetworkEventArgument) null,
-->    dvs = (vim.event.DvsEventArgument) null,
-->    fullFormattedMessage = <unset>,
-->    changeTag = <unset>,
-->    eventTypeId = "esx.problem.net.vmnic.linkstate.down",
-->    severity = <unset>,
-->    message = <unset>,
-->    arguments = (vmodl.KeyAnyValue) [
-->       (vmodl.KeyAnyValue) {
-->          key = "1",
-->          value = "vmnic0"
-->       }
-->    ],
-->    objectId = "ha-eventmgr",
-->    objectType = "vim.HostSystem",
-->    objectName = <unset>,
-->    fault = (vmodl.MethodFault) null
--> }
2017-08-16T08:03:58.000Z info hostd[FFA0CB20] [Originator@6876 sub=Vimsvc.ha-eventmgr] Event 2574 : Physical NIC vmnic0 linkstate is down.

 

I tried multiple drivers version :

  • igb 5.0.5.1
  • igb 5.3.3
  • igbn 1.3.1

And firmware versions :

  • firmware-version: 1.67, 0x80000d38, 17.5.10
  • firmware-version: 1.67, 0x80000d38, 18.0.16

 

I don't know what to try or where to look to go further...

 

Any idea ?

 

Thanks in advance !


esxi 6.5 domain join with smb 2.0?

$
0
0

host: esxi 6.5.0 vmkernel release build 5969303
domain controller: server 2016 standard with latest cumulative update
no firewall in place.

 

when adding the esxi host to the domain with SMB 1.0 protocol (default setting), there are no issues. it works fine, tested via webgui and via command line.


unfortunately in our environment we want to get rid of SMB 1.0 completely and uninstall it from the domain controllers. so we followed this (ESXi 6 hangs when joining Active Directory Domain ) post to modify likewise to use smb 2.0

 

 

after this change the domain join via webgui "hangs" and does not complete. then the entire webgui becomes unresponsive and from this moment on, we have to reboot the esxi host.

 

 

we followed various troubleshooting guides, like this one  (ESXi and Likewise – troubleshooting guide – part 2 – Virtual Village )
for example, we disabled ipv6 on the domain controller like suggested, we disabled the windows firewall on the DC, we disabled the esx firewall.... did not help. dns config, hosts file, etc.. should all be fine and good, as domain join with SMB1.0 works.

 

 

to get better debugging info we then tried a manual join with this procedure:

 

/usr/lib/vmware/likewise/bin/lwsm restart lwio
/etc/init.d/lwsmd stop
/etc/init.d/lwsmd start
esxcli network firewall unload
/usr/lib/vmware/likewise/bin/lwsm set-log file /var/log/likewise.log
/usr/lib/vmware/likewise/bin/lwsm set-log-level debug
/usr/lib/vmware/likewise/bin/domainjoin-cli join domain.local domainadmin@domain.local somepassword

 

the command prints two messages:

     Joining to AD Domain:   domain.local
     With Computer DNS Name: HV001.domain.local

 

and then just hangs.

 

after a failed join attempt like this we have to  ps | grep lwsmd  and kill -9 *pid* - otherwise, we can't interact with lwio/lsass anymore.


the verbose logging gives the following information:


20170814141140:DEBUG:lwio:IoCreateFile():ioapi.c:218: LEAVE: -> 0x00000103 (EE = 0)
20170814141140:DEBUG:lwio:IopIpcCreateFile():ioipc.c:438: LEAVE_IF: -> 0x00000103 (STATUS_PENDING) (EE = 0)
20170814141140:DEBUG:lwio:RdrResolveToDomain():driver.c:889: Error at ../lwio/server/rdr/driver.c:889 [status: STATUS_NOT_FOUND = 0xC0000225 (-1073741275)]
20170814141140:DEBUG:lwio:RdrSocketTaskConnect():socket.c:1019: Error at ../lwio/server/rdr/socket.c:1019 [status: STATUS_PENDING = 0x00000103 (259)]
20170814141140:DEBUG:lwio:RdrSocketTask():socket.c:1246: Error at ../lwio/server/rdr/socket.c:1246 [status: STATUS_PENDING = 0x00000103 (259)]
20170814141140:DEBUG:lwio:RdrSocketRead():socket.c:1773: Error at ../lwio/server/rdr/socket.c:1773 [status: STATUS_PENDING = 0x00000103 (259)]
20170814141140:DEBUG:lwio:RdrSocketReceivePacket():socket.c:701: Error at ../lwio/server/rdr/socket.c:701 [status: STATUS_PENDING = 0x00000103 (259)]
20170814141140:DEBUG:lwio:RdrSocketDispatchPacket2():socket.c:1423: Error at ../lwio/server/rdr/socket.c:1423 [status: STATUS_INVALID_NETWORK_RESPONSE = 0xC00000C3 (-1073741629)]
20170814141140:DEBUG:lwio:RdrSocketTaskTransceive():socket.c:1134: Error at ../lwio/server/rdr/socket.c:1134 [status: STATUS_INVALID_NETWORK_RESPONSE = 0xC00000C3 (-1073741629)]
20170814141140:DEBUG:lwio:RdrSocketTask():socket.c:1251: Error at ../lwio/server/rdr/socket.c:1251 [status: STATUS_INVALID_NETWORK_RESPONSE = 0xC00000C3 (-1073741629)]
20170814141223:VERBOSE:lsass:LsaSrvIpcCheckPermissions():ipc_state.c:79: Permission granted for (uid = 0, gid = 0, pid = 72438) to open LsaIpcServer
20170814141223:VERBOSE:lsass-ipc:lwmsg_peer_log_accept():peer-task.c:271: (session:04df4955d842942b-f5af40d405e6b03c) Accepted association 0xb1016b8
20170814141223:VERBOSE:lwreg:RegDbOpenKey():sqldb.c:1068: Registry::sqldb.c RegDbOpenKey() finished
20170814141223:DEBUG:lwreg:RegDbGetKeyValue_inlock():sqldb_p.c:1227: Error at ../lwreg/server/providers/sqlite/sqldb_p.c:1227 [status: LW_STATUS_OBJECT_NAME_NOT_FOUND = 0xC0000034 (-1073741772)]
20170814141223:DEBUG:lwreg:RegDbGetValueAttributes_inlock():sqldb_schema.c:846: Error at ../lwreg/server/providers/sqlite/sqldb_schema.c:846 [status: LW_STATUS_OBJECT_NAME_NOT_FOUND = 0xC0000034 (-1073741772)]

 

STATUS_INVALID_NETWORK_RESPONSE gives me no additional clue of what's going wrong except that this may simply be a bug in likewise or esxi.


is there any way to get domain join working with SMB 2.0 ?

Can't edit VM settings in ESXi 6.5 web client

$
0
0

It throws this javascript error in my browser.

I tried firefox, chrome, and IE; both Win 7 and Server 2012R2. No luck!

 

Haven't tried using VM Workstation to edit VM settings (if that is even possible, now that client vcenter exe is no longer.)

 

I can add new VM's however...

 

6.5 feels every beta at this point, web interface is totally unuseable IMO. I think I need to go back to 6.0 or 5.5 (those work!)

 

Cause: TypeError: $scope.hardwareStackView.hardDiskBlock is undefined

Version: 1.8.0

Build: 4516221

ESXi: 6.5.0

Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0

 

Exception stack:

 

@https://192.168.1.120/ui/scripts/main.js:315:946

f/<@https://192.168.1.120/ui/scripts/main.js:265:9465

Me/this.$get</k.prototype.$eval@https://192.168.1.120/ui/scripts/main.js:265:16488

Me/this.$get</k.prototype.$digest@https://192.168.1.120/ui/scripts/main.js:265:15039

Me/this.$get</k.prototype.$evalAsync/<@https://192.168.1.120/ui/scripts/main.js:265:16575

e@https://192.168.1.120/ui/scripts/main.js:264:5644

lf/m.defer/c<@https://192.168.1.120/ui/scripts/main.js:264:7652

tools install stuck?

$
0
0

I have an esxi server which I initiated a tools upgrade on a CentOS VM.

The tools install completed successfully on the VM, but I can't get it to stop/release on the esxi side.

From the console, im getting the error message:

 

Unable to connect to the MKS: Internal error

1.JPG

 

and it's not giving me a console and not releasing/stopping the tools install from the esxi side. This is preventing me from managing the VM properly.

2.JPG

Certain Keyboard Keys Not Working On My 4690OS VM

$
0
0

I need to use the alt and sysrq buttons to do certain functions in a 4690 os. How can I achieve this? Can I map keys or set it up somehow? I'm using Vsphere ESXI 6.5.

Update a stand alone (free) ESXi 5.1 to 6.5?

$
0
0

Hi there,

I have an ESXi 5.1.0 (799733) running fine here, and since I have some time, wanted to start planning an update to latest 6.5 Version.

 

I have the free Version.

Basically my System is a "PC" with several data stores and I am using an USB stick to start ESXi from.

 

What would be the easiest way to update the 5.1 to the 6.5U1 Version? (If possible with a possible fall back way in case of Trouble.)

Viewing all 8132 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>