Hi Guys,
i've been looking anywhere but cannot find an answer to my question.
so for lab purposes i installed ESXi 6.0 under a laptop run by a processor i5-5200U
hyperthreading is already on.
this processor supposed to have 4 cores in one socket but in the information i only see 2 on "Processor Cores per socket".
someone have any input of what am i missing here? i was expecting 8 vCPU with 4 cores processor and hyperthreading on.
here is the screenshot:
regards,
Ricky Lee
Hello,
Is it possible to ssh a guest VM from host (esxi) cli.
For example: I have a VM running on an esxi host, after I ssh to the host, I need to ssh to the VM directly from the host cli.
We have 7 brand new HPE DL380 Gen10 servers. We would like to install ESXi 6.7 on them. I went here
https://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php
I entered this combination
It showed that ESXi 6.7.0 and Horizon 7.4.0 are compatible
I then entered this combination
There are no results shown!
ESXi 6.7.0 is compatible with Horizon 7.4.0
You cannot run ESXi 6.7.0 without running vCenter 6.7.0
Is vCenter 6.7.0 compatible with Horizon 7.4.0?
Hello
I'm looking to migrate an ESXi 6.0 estate to 6.5. Trying to plan the least downtime/impact so looking for a sanity check for the current plan:
1. Migrate vCenter 6.0 to vCenter Server Appliance 6.5
2. Upgrade BIOS firmware on hosts for meltdown/spectre
3. Upgrade ESXi 6.0 to 6.5
4. Upgrade vCenter to 6.5 U1g
5. Upgrade VMTools on VMs
I'm planing on using ESXi650-201803001 2018-03-20 7967591 as the image for the upgrade - is this OK to do?
Mant thanks
I've tried both the Intel NIC and the VMX NIC with the same issues.
If I run from a desktop running the same version of FreeBSD with the same patches, I get the speed I expect.
From ESXi
root@IPv6Router:/usr/home/carl # wget --no-check-certificate https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.16.2.tar.xz> /dev/null
--2018-04-17 13:23:17-- https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.16.2.tar.xz
Resolving cdn.kernel.org (cdn.kernel.org)... 2a04:4e42:2f::432, 151.101.201.176
Connecting to cdn.kernel.org (cdn.kernel.org)|2a04:4e42:2f::432|:443... connected.
WARNING: cannot verify cdn.kernel.org's certificate, issued by 'CN=GlobalSign Organization Validation CA - SHA256 - G2,O=GlobalSign nv-sa,C=BE':
Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: 103016908 (98M) [application/x-xz]
Saving to: 'linux-4.16.2.tar.xz.1'
linux-4.16.2.tar.xz.1 1%[> ] 1.39M 228KB/s eta 6m 58s
Code: [Select]
$ wget --no-check-certificate https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.16.2.tar.xz> /dev/null
--2018-04-17 09:26:08-- https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.16.2.tar.xz
Resolving cdn.kernel.org (cdn.kernel.org)... 2a04:4e42:8::432, 151.101.33.176
Connecting to cdn.kernel.org (cdn.kernel.org)|2a04:4e42:8::432|:443... connected.
WARNING: cannot verify cdn.kernel.org's certificate, issued by 'CN=GlobalSign Organization Validation CA - SHA256 - G2,O=GlobalSign nv-sa,C=BE':
Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: 103016908 (98M) [application/x-xz]
Saving to: 'linux-4.16.2.tar.xz'
linux-4.16.2.tar.xz 35%[=====================> ] 34.56M 9.52MB/s eta 9s To rule out FreeBSD, I've setup an OpenSUSE 42.3 tunnel and received the same results.
I suspect this is a VM setting somewhere, but don't have the first idea of where to look. I've verified that the MTUs on both ends match (1480)
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
Anyone know how to disassociate an ESXi 6.5 host from a vCenter server - without the server?
Spent several days duplicating our environment in a lab and someone took the server that was used for the vCenter and repurposed it and I don't have another box to use for a vCenter server at this time, but I don't want to lose all the work that was made on the hosts. I think I've seen this done on ESXi 5.x but not on 6.5. Anyone have any ideas?
I am seeing many of these in hostd.log. I have searched around but still not sure what they mean. Any ideas? Thank You
2018-04-06T14:42:00.005Z warning hostd[4BC40B70] [Originator@6876 sub=Statssvc.vim.PerformanceManager] Calculated read OIO 147 for scsi0:0 is out of range (1280), prevTime = 1523025700 curTime = 1523025720 previIOTime = 64598399curIOTime = 358782925
2018-04-15T19:13:20.103Z warning hostd[534C1B70] [Originator@6876 sub=Statssvc.vim.PerformanceManager] CollectDatastoreBasilStats: Basil read workload parameters for '5a6b9128-7999b837-93a5-000e1e460520' are out of range: oIO=9, ioSizeBytes=776479
2018-04-15T19:13:20.105Z warning hostd[534C1B70] [Originator@6876 sub=Statssvc.vim.PerformanceManager] CollectDatastoreBasilStats: Basil read workload parameters for '5a74e704-ae935a28-8bdc-000e1e460830' are out of range: oIO=6, ioSizeBytes=751044
2018-04-15T19:13:24.256Z info hostd[51281B70] [Originator@6876 sub=Snmpsvc] UpdateStats: report cimom converter stats started
Has anyone seen these event log entries on virtual windows servers - they seem to be floooding the application logs.
Where do they come from, what do they mean and can I stop them from being logged without missing any important information?
Log Name: Application
Source: vmStatsProvider
Date: 17/07/2013 09:02:06
Event ID: 258
Task Category: Guest Library API
Level: Information
Keywords: Classic
User: N/A
Computer:
Description:
The "vmGuestLibrary" is successfully initialized for this Virtual Machine.
Log Name: Application
Source: vmStatsProvider
Date: 17/07/2013 09:02:06
Event ID: 256
Task Category: General
Level: Information
Keywords: Classic
User: N/A
Computer:
Description:
The "vmStatsProvider" is successfully initialized for this Virtual Machine. WMI namespace: "root\cimv2".
** I've just noticed that they seem log every 30 minutes.
My environment:
Host:
HP z800 with internal SATA drives. No iSCSI or fiber or anything fancy.
ESXi 5.1.0,799733
Guests:
Windows Servers:
2008R2 (SBS)
2012
2012R2
Creating snapshots on the 2008r2 and the 2012 servers has always worked without any issues. However, whenever I create snapshots of the 2012r2 servers I always get the following error messages:
Log Name: System
Source: Ntfs
Date: 23/10/2014 12:26:19 PM
Event ID: 137
Task Category: (2)
Level: Error
Keywords: Classic
User: N/A
Computer: host.domain.local
Description:
The default transaction resource manager on volume \\?\Volume{4d63c1a0-5a35-11e4-80c8-000c293e51b6} encountered a non-retryable error and could not start. The data contains the error code.
Log Name: System
Source: Microsoft-Windows-Ntfs
Date: 23/10/2014 12:26:20 PM
Event ID: 140
Task Category: None
Level: Warning
Keywords: (8)
User: SYSTEM
Computer: host.domain.local
Description:
The system failed to flush data to the transaction log. Corruption may occur in VolumeId: \\?\Volume{4d63c1a0-5a35-11e4-80c8-000c293e51b6}, DeviceName: \Device\HarddiskVolume4.
(The specified request is not a valid operation for the target device.)
I have found the following VMware KB article that appears to cover this exact problem:
However, the article is missing some critical information on this issue... The article does not state whether these alerts indicate if there is likely to be any adverse effect on the systems in question or not. Is this a real issue, that requires remedial action, or simply the misreporting of a non-issue? Also, this article refers to two MS KB articles. However neither of these two articles are relevant to my environment.
So, do we have a problem that needs to be fixed or do we just have yet another Microsoft system log error/warning crying wolf that won't get fixed until Windows 10 Server, if we're very lucky or Fortune 100?
I know that the performance really varies based on the disk I/O activity of the VM's that you have, but I'm curious to know; Whats the common number of VM's per data store that most of us have?
In my case we usually have 5-7 VM's per data store.
Hi everyone.
After upgrading from 6.5 to 6.7 our host displays the above error in vCenter. Everything seems to work fine, but can't make to error disappear.
I can't seem to find the service under "services", so I can enable/configure it.
Any help is much appreciated.
Kindly
Kasper
Hello!
I've installed a Chelsio T320, dual 10gb nic and the vmware signed vib, everything went well. But, ESXi(5.1.0), only lets me use one of the two ports. It shows both under network adapters(vmnic2 and vmnic2b). But only vmnic2 is available for use under Networking->Add Networking. I took a look at /etc/vmware/esxi.conf and lspci, and noticed that the Chelsio card puts both ports under the same PCI port, 00.05.0, rather than one on 00:05.0 and the other on 00:05.1. At least that is the appearance.
Has anyone run into this before? Is there a way to manually or forceably inject vmnic2b into the system as a useable device?
Thanks,
Brad
I installed ESXi 6.5 HP OEM in my lab HP 380 G7 Server.
ISO:VMware-ESXi-6.5.0-OS-Release-4564106-HPE-650.9.6.0.28-Nov2016.iso
after installation ，esxi crash.
but VMware-VMvisor-Installer-6.5.0-4564106.x86_64.iso not have this issue.
Seeing something odd. We are finally upgrading from 5.5 to 6.5 and after migrating our hosts from one vCenter to another I noticed some standard switch port groups that remain listed under Networking even though none of the hosts have standard switches anymore.
To migrate we moved all networking to standard switches.
Then we disconnected our host from vCenter 5.5 and connected them to vCenter 6.5.
Finally we migrated everything from standard to the new distributed switches.
I think we may have deleted a standard switch without actually removing each of the port groups first and that may be why they are stuck there.
Anyone have any ideas on how to remove these. They aren't hurting anything but I like a clean view of my environment so would prefer to get rid of these.
Here is the switch view. Shows 3 extra groups there that should be gone. No VMs and no hosts assigned to them and I can't see a way to remove them.
Here the switch view for our hosts. They all look the same. There are no standard switches. These are all VDS.
need some help to remount datastore after synology reboot. the targets are still there in esxi > storage > adapters > configure iscsi. i've tried rebooting esxi and synology. ssh to root@esxi and executed esxcfg-volume -l but returns nothing.
I recently migrated my VMs to a new server featuring a Ryzen CPU (essentially same Zen architecture as EPYC.) One VM running Windows 8.1 started complaining about "unsupported hardware" and started refusing to download updates. (Thanks, Micro$oft. Insert your favorite expletive here.)
I've found a workaround called "WSUS Offline" and am in the process of testing it. However, it is unwieldy and I'm still not sure if it will actually work.
I know other hypervisors have the capability of hiding the host processor from the VM and mimicking other types of CPU. Does ESXi share this ability? In this particular scenario, that capability would make my life much easier.
Does anyone have information on an update to ESXi to support the new AMD CPUs? I have an 1800X crying to run ESXi. At this point I am forced to run VMware Workstation Pro on it due to incompatibility with ESXi.
Thank you for any info you may be able to share.
Eric
Hello,
Odd issue going on. We're working through upgrading our small cluster to newer hosts running ESXi 6.0. The hosts are Dell R630 1U boxes. There's a variety of wired NIC cards. I also have them loaded with Intel X520 DP 10Gb DA/SFP+ cards. Currently I don't have the 10Gb switching so it's my understanding that they can be used at 1000Mb speed with standard copper SFP modules. We build out the three servers. Our management and virtual machine network traffic use the same two physical ports(one tied to the X520 and the other one of the onboard ports) tied to a Cisco 4507 via etherchannel.
There was no issue getting the hosts online. We were able to bring them in and out of maintenance mode, reboot, patch, etc. No issues. However, after playing around with a template and spinning up a VM of Windows Server 2016, upon shut down, it will interrupt management traffic on the host. If we use one half of the ether-channel and just use the onboard NIC, there's no issue. If we use the X520 solely and shut down the guest, it will stop management traffic on that host. So we've isolated it to the X520 card. I read on intel's site that the SFP modules have to be Intel for the most case. I'm using some extra Cisco SFP modules I had laying around. The other odd thing is that the Vcenter will see the host as online(and will even ping with replies) while any workstation I have tested won't ping.
Has anyone seen something like this? I guess my only real option is to buy new SFP cards, but I hoping someone would have some further insight or confirmation that the module could cause problems like this.
SFP+ Modules, SFP Modules, and Cables Compatible with Intel® Ethernet...
Hi,
This is the specs of my homelab running ESXI 6.5
Mobo : Asus Z8NA-D6
CPU: 2 x Xeon L5460
RAM: 6 x 4GB DDR3
I want to monitor the temperatures of my CPUs and other parts but there is nothing is the "health status" section in vSphere client:
Nothing on the web client either:
https://i.imgur.com/hjXxGyw.png
I have tried restarting the CIM service but same thing.
Any idea?
p.s.
I also get this error if I try to refresh the sensor data:
Call "HostHealthStatusSystem.Refresh" for object "healthStatusSystem" on ESXi "192.168.1.10" failed.
same for reset :
Call "HostHealthStatusSystem.ResetSystemHealthInfo" for object "healthStatusSystem" on ESXi "192.168.1.10" failed.