Hello people.
I want to install EsXi 7.0.
I have a "cpu e5520" processor and a "supermicro x8dt3" motherboard that supports 7.0 such computer specifications?
And is there a link where you can see esxi 7.0 compatibility with the processor and motherboard?
I recently bought myself a simple USB 3.1 gen 2 external disk enclosure (4 bays; no raid; JBOD) to connect to my ESXi 7.0 host, and passthrough the disks to a VM.
The problem I experience is that when the host is running, and I connect the enclosure, the disks constantly spin up and down... I suspect something caused by power saving. If I do a LSUSB I see the disks, but it looks like they are rescanned al the time, as I see the number going up and down via the LSUSB command.
The strange thing is that when I reboot my ESXi host during the up and down spinning of my disks, the disks become stable (stay up) during the reboot process.
Once the ESXi is started up, the disks stay spinning, and are fully operational and working. After reboot the LSUSB results are also stable.
It is only after I shutdown and start the enclosure again, the problem starts again.
I have the issue on all my USB ports (3.1 gen 1 & gen 2).
When connecting the enclosure to a Windows or Linux host, everything works perfectly.
Anyone experience with this?
/J
Hi All,
Thanks for looking into my query below.
There was a command I remembered that tells which ISO Image was used during the ESXi Install time if any of you have it can you please share it.
Reason for above is - in some vendors they have their own customer ESXi Image and I often see customers use different ISO Image rather than dedicated assigned ISO Image (vendor specific).
Regards,
S Pavan Kumar
we recently buy a Dell R640 server with ESXi
and one Broadcom NetXtreme BCM5720 dual port Gigabit Ethernet
and one Broadcom BCM57416 NetXtreme-E dual port 10GBASE-T
i create a Vswitch0 with the two gigabit ethernet card for management
i create a Vswitch1 with the two 10GBASE-T card for all virtuals machines (actually just one vm)
firmware ok, driver ok, ESXi version ok, linkspeed auto-negotiation enable
everything seems to be ok but i can't ping my only virtual machine
thx for your ideas
Where do I begin.
I feel like I am always a newbie with VMware, despite working in it for a few years. We are running a VSAN environment on 6.5, performing backups with Veeam. About 2 weeks ago, some of our vm's in the backup started throwing errors. Due to some events outside of my control, I just started looking at this today. Veeam support said the error was because the VMX file was corrupt, recommended solution was to shutdown machine, remove from inventory, create new machine using the existing disks, bring it back up. We performed this solution on a non critical machine, and it worked great. Did it to a semi-critical machine, and worked great again. Did it to our Exchange server and.. it wasn't great.
The server came back up, however after a few hours of operation, a large amount of people reported missing about 2 weeks of email. We had the machine up for about 5 hours poking around at logs before I shut it down to focus on the VMware side of things. After a ton of digging on the guest as well as in the host environment, I figured out the root cause- despite there being no snapshots in the snapshot manager, the system was running off of a snapshot due to the failed backup. I made the mistake of mounting the original vmdk files on booting rather than the 000001.vmdk file. My own mistake of making assumptions, thinking those files were somehow orphaned since the snapshot manager listed no snapshots. The previous, successful machines either didn't have a snapshot file, or historical data didn't matter on that guest.
After talking with VMware support, they basically said since the original vmdk's were booted, the damage is done, consider the data lost. They did say I can try to remove the drives from the guest, and try to re-add the snapshot versions, but had little faith that it would work, and warned of a high chance of corruption of both the vmdk and the snapshot vmdk. Since the last shutdown, I've kept the server powered off and have been seeking any type of option to try and get this machine back to life with its current data, and have ran into a brick wall every time. Mostly being cautious on any steps tried from this point due to the corruption warnings, I've copied out all files save for the snapshot files from the original location of the datastore to a different location to mitigate risk of further corruption. The snapshot files however, will simply not budge. Web client copy, SSH copy, vmkfstools -i, nothing will get those files to somewhere else in their original size (though I can download what looks to be the header with WinSCP).
I'm desperately trying to safeguard the snapshot data before doing something that may corrupt the whole guest and get this thing back in an up to date, running condition. Since this is an Exchange server, the files are quite large. Just copying out the files took 3hrs. I'm now attempting a clone as I've read a clone may merge snapshot files automatically, with the hope that it won't impact the original files. If the clone doesn't work, I'd be at the last straw to try to boot off of the snapshots, knowing I may lose everything. Finally I've landed here, seeing some users get success by some of you truly amazing experts here. The final kick in the rear, is our management is getting ready to suffer the data loss just to get the server back on and email flowing, so their patience is thin. Casting out a bottle in the sea here, hoping it comes back with some much needed help in time. Attaching relevant info that I've seen requested in other posts:
Directory ls -lh of original files:
-rw-r--r-- 1 root root 92 Oct 24 2018 CAKEXK01-8d4db6ef.hlog
-rw------- 1 root root 32.6K Nov 15 08:02 CAKEXK01-Snapshot557.vmsn
-rw-r--r-- 1 root root 13 May 8 2019 CAKEXK01-aux.xml
-rw------- 1 root root 8.5K Nov 14 08:12 CAKEXK01.nvram
-rw------- 1 root root 45 Nov 14 08:12 CAKEXK01.vmsd
-rwx------ 1 root root 4.6K Dec 6 21:22 CAKEXK01.vmx
-rw------- 1 root root 3.3K May 17 2018 CAKEXK01.vmxf
-rw------- 1 root root 5.0M Dec 6 21:22 CAKEXK01_3-000001-ctk.vmdk
-rw------- 1 root root 408 Nov 15 08:02 CAKEXK01_3-000001.vmdk
-rw------- 1 root root 600 Dec 7 04:12 CAKEXK01_3.vmdk
-rw------- 1 root root 5.9M Dec 6 21:22 CAKEXK01_4-000001-ctk.vmdk
-rw------- 1 root root 409 Nov 15 08:02 CAKEXK01_4-000001.vmdk
-rw------- 1 root root 576 Dec 7 04:12 CAKEXK01_4.vmdk
-rw------- 1 root root 2.0M Dec 6 21:22 CAKEXK01_5-000001-ctk.vmdk
-rw------- 1 root root 407 Nov 15 08:09 CAKEXK01_5-000001.vmdk
-rw------- 1 root root 598 Dec 7 04:12 CAKEXK01_5.vmdk
drwxr-xr-x 1 root root 280 Dec 7 06:38 bak
-rw------- 1 root root 299.5K May 17 2018 vmware-3.log
-rw------- 1 root root 15.2M Sep 21 2018 vmware-4.log
-rw------- 1 root root 3.0M Oct 18 2018 vmware-5.log
-rw------- 1 root root 393.2K Oct 22 2018 vmware-6.log
-rw------- 1 root root 467.3K Oct 24 2018 vmware-7.log
-rw------- 1 root root 244.0K Oct 24 2018 vmware-8.log
-rw------- 1 root root 45.4M Dec 6 21:22 vmware.log
Directory ls -lh of newly created machine that is pointing to the above vmdk's:
-rw-r--r-- 1 root root 295 Dec 6 21:35 CAKEXK01-35be335f.hlog
-rw------- 1 root root 8.5K Dec 7 05:25 CAKEXK01.nvram
-rw-r--r-- 1 root root 0 Dec 6 21:35 CAKEXK01.vmsd
-rwxr-xr-x 1 root root 3.8K Dec 7 05:25 CAKEXK01.vmx
-rw------- 1 root root 3.1K Dec 6 21:45 CAKEXK01.vmxf
-rw-r--r-- 1 root root 1.0M Dec 7 03:08 vmware-1.log
-rw-r--r-- 1 root root 322.3K Dec 7 05:25 vmware.log
Hello,
I would like to advice with you.
I had datastore on RAID 0. I lost it after re-installation of my ESXi hypervisor. I made a mistake and recreated a new datastore on the place of old datastore. No data was not written on this datastore. I can say that I see it in ls vmfs/volumes..but it is empty.
Do you think that I have lost data definitely?
thank you very much, Olda
Background:
I am installing ESXi 6.7.0 on several MacPro 6,1 machines.
I am able to complete the installation and network configuration at the main screen. However, I have to jump back and forth between several of these machines to configure each one, or go back and reconfigure something.
I am using a crash cart (Keyboard, 4:3 Monitor) with a VGA to mini-DVI adapter in one of the Thunderbolt 2 ports to work with these. I am still procuring an HDMI to DVI connector to test whether the HDMI port has the same issue.
Issue:
When I disconnect video from a device, and connect to another, or reconnect to the same device, I see a black screen. No output from device and monitor goes to sleep.
No input or mouse movement can cause the display to wake-up.
I have tried this with different displays and all experience the same issue.
I get video if I reboot the device, either by hard reboot or by restarting the machine from muscle-memory (keyboard input is still plug-and-play, it seems).
Is this a known issue with ESXi 6.7 on MacPro 6,1 or is this just an issue with using the Thunderbolt port?
I'm trying to install the nvidia grid vib in my esxi 6.5 for a grid k2.
I'm following the instructions from nvidia to the letter but nope...
I run the following command:
esxcli software vib install -v /etc/vib/NVIDIA-vGPU-kepler-VMware_ESXi_6.5_Host_Driver_367.134-1OEM.650.0.0.4598673.vib
I get the following error:
[InstallationError]
Error -3 while decompressing data: invalid literal/lengths set
vibs = NVIDIA_bootbank_NVIDIA-kepler-VMware_ESXi_6.5_Host_Driver_367.134-1OEM.650.0.0.4598673
please refer to the log file for more details.
What is the problem? this is a fresh esxi install. I just downloaded the vib directly from NVIDIA I expect that following the instructions would lead to completion...
Thanks for any help...
Hi,
I have a HP Micro server at home. There are 4 4TB disk in it. I had a power failure and then the ESXI 5.5 wouldn't boot anymore. So I downloaded the image again and did an upgrade and now it boots again but my datastores are gone. I see in the Var/log/vmkernel.log that there is still something there because a vm that was running gives an error. I see the VM name in the error.
2020-06-12T21:05:19.876Z cpu0:36039)etherswitch: L2Sec_EnforcePortCompliance:155: client [servername] requested promiscuous mode on port 0x2000006, disallowed by vswitch policy
I also have this error:
2020-06-12T21:07:50.617Z cpu1:33325)NMP: nmp_ThrottleLogForDevice:2321: Cmd 0x85 (0x412e80885300, 34385) to dev "naa.600508b1001c27ae1dacdc4789853a81" on path "vmhba1:C0:T0:L0" Failed: H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0. Act:NONE
and
2020-06-12T21:07:50.617Z cpu1:33325)ScsiDeviceIO: 2337: Cmd(0x412e80885300) 0x85, CmdSN 0x403 from world 34385 to dev "naa.600508b1001c27ae1dacdc4789853a81" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
Any advice ?
Greetings
Close_Up
I just installed esxi 7.0 eval copy, on my lab vmware workstation pro 15.5, once I login in to the host there is 0 datastores the storage shows NaN%, when i browse for the datastores error unhanded exception pops up.
After spending the last two days upgrading a lot of ESXi servers on the last one I was tired already so I didn't back up its boot drive.
I started the upgrade from vCenter, staged it, pre-checked remediation, remediated--green checkmarks all around. When the server came back on though, it wasn't able to boot from the drive. It seems the bootloader got lost or something. I enabled BIOS booting (it was on EFI before) to see if it picked it up but still didn't boot.
I checked the drive on my computer and I got this:
bash-3.2# diskutil list /dev/disk4 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *15.8 GB disk4 1: EFI BOOT 104.9 MB disk4s1 2: Microsoft Basic Data BOOTBANK1 1.1 GB disk4s5 3: Microsoft Basic Data BOOTBANK2 1.1 GB disk4s6 4: 4EB2EA39-7855-4790-A79E-FAE495E21F8D 13.5 GB disk4s7
And with this info I found online it seems the data should be there either in diskXs5 or diskXs6. I also dded an image just in case:
bash-3.2# dd if=/dev/disk4 of=./hyperserver1.img bs=4096 3855360+0 records in 3855360+0 records out 15791554560 bytes transferred in 1292.042925 secs (12222159 bytes/sec)
Could I just reinstall ESXi from scratch so I get a drive with a good bootloader and then copy BOOTBANK1& BOOTBANK2 to it or is there some check that would let only ESXi write to it? From a Mac, ownership information just says _unknown so I'm not exactly sure how --if-- I can set it back:
bash-3.2# ls -l total 330624 drwxrwxrwx 1 _unknown _unknown 32768 Jun 14 11:19 .Spotlight-V100 drwxrwxrwx 1 _unknown _unknown 32768 Jun 14 11:19 .fseventsd drwxrwxrwx 1 _unknown _unknown 32768 Jun 14 2020 System Volume Information -rwxrwxrwx 1 _unknown _unknown 135334 Jun 14 2020 b.b00 -rwxrwxrwx 1 _unknown _unknown 197255 Jun 14 2020 bnxtnet.v00 -rwxrwxrwx 1 _unknown _unknown 93512 Jun 14 2020 bnxtroce.v00 -rwxrwxrwx 1 _unknown _unknown 1500 Jun 14 2020 boot.cfg -rwxrwxrwx 1 _unknown _unknown 600424 Jun 14 2020 brcmfcoe.v00 -rwxrwxrwx 1 _unknown _unknown 32244 Jun 14 2020 brcmnvme.v00 ...
If I can't recover, would the data on the disks be admitted back to the vSAN cluster if the host information is a "new" host?
Thanks for your help!
I have successfully installed ESXi 6.7U3 on a MacPro6,1. (also tried 6.5U3 and 7.0). The install was flawless however as soon as I unplug the Thunderbolt Display the ESXi is no longer reachable (ping fail) and I can not get it back even after reconnecting the display.
I saw a post on another forum suggesting an HDMI dummy dongle to keep the Display active, well, that did not work either.
Any help would be greatly appreciated. I'm at my wits end trying to figure this out. The HCL says it works, and I don't know what I'm doing wrong.
here is my configuration
CPU - Xeon E5-2697 - 12 core
RAM - 64GB
GPU - D300
I've already searched google and all forums I know, but their is no mention of this issue but there seems to be a lot of folks using the MacPro6,1 in home labs and such.
Regards.
Shyam
Is there a problem if in an esxi 6.5 I reset the evaluation licenses several times and then add a correct license?
Hello everyone,
I'm currently in the process of setting up a PXE server for installation of multiple linux distrons including ESXi 6.7. The server is set up to serve Legacy as well as UEFI installations.
Thanks to multiple guides I could find on the internet, including vmware.com, I could set up the server and the ESXi Legacy installation runs fine. However, there are 2 issues, I simply cannot find an answer for:
Legacy Boot:
Everytime I load the mboot.c32 I receive the message "Network Boot: MAC address not found. Add 'BOOTIF= ... Replace with MAC address of the boot interface"
Since the the server is meant to install the OS on always different host machines, which MAC address am I supposed to provide here and how? Or can this message be disregarded? Is there a way to mask the message entirely?
This is the code in the ipxe boot menu for legacy boot:
:esxi67vm
echo Starting VMWare ESXi 6.7 Installation
dhcp
kernel -n mboot.c32 http://${server}/vmware/esxi67/mboot.c32
imgargs mboot.c32 -c http://${server}/vmware/esxi67/boot.cfg
boot mboot.c32 || goto failed
UEFI Boot:
Booting the installer works fine but always hangs in the last step with the message : Shutting own firmware services... Using 'simple offset' UEFI RTS mapping policy
Is there something I'm missing?
This is the code in the ipxe boot menu for uefi boot:
:esxi67vm
echo Starting VMWare ESXi 6.7 Installation
dhcp
kernel -n mboot.efi http://${server}/vmware/esxi67/mboot.efi
imgargs mboot.efi -c http://${server}/vmware/esxi67/boot.cfg
boot mboot.efi || goto failed
Best Regards
Coredump file configured:
[root@zhost1:~] esxcli system coredump file get
Active: /vmfs/volumes/5c502d18-996b2376-d466-a41f72d330a9/vmkdump/zhost1-vmkdump.dumpfile
Configured: /vmfs/volumes/5c502d18-996b2376-d466-a41f72d330a9/vmkdump/zhost1-vmkdump.dumpfile
No coredump partition or network server configured:
[root@zhost1:~] esxcli system coredump partition get
Active:
Configured:
[root@zhost1:~] esxcli system coredump network get
Enabled: false
Host VNic:
Is Using IPv6: false
Network Server IP:
Network Server Port: 0
When I try to extract the vmkernel zdump:
[root@zhost1:~] esxcfg-dumppart --file --copy --devname /vmfs/volumes/5c502d18-996b2376-d466-a41f72d330a9/vmkdump/zhost1-vmkdump.dumpfile
--zdumpname /vmfs/volumes/STORE/zhost1-vmkernel-zdump
DiagnosticPartition: Unable to copy the dump file: WARNING: Start offset less than header size!
Host details:
ESXi670-201912001
Build 15160138
Configured coredump file by following https://kb.vmware.com/s/article/2077516 and tried to generate the log file by following https://kb.vmware.com/s/article/2081902
Does anyone know why I'm seeing that error and unable to extract the log?
Hi All
can you help me with some advice on how we can identify user IP connected to ESXi via SSH
Thanking you in advance.
Dear VMWare Community,
I have serious trouble with Windows 2016/2019 VM guests on ESXi 6.7. Every 3,4,5 days several VMs are unresponsible and hang. The only way to bring the VM back to life is the reset. The log is clean. I seems that the VM hangs without any error and the VMWare tools are unavailable.
2019-03-10T19:02:44.185Z| vcpu-3| I125: CDROM: Emulate GET CONFIGURATION RT 1 starting feature 0
2019-03-10T19:32:44.507Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 1 starting feature 0
2019-03-10T20:02:44.827Z| vcpu-4| I125: CDROM: Emulate GET CONFIGURATION RT 1 starting feature 0
2019-03-10T20:32:45.146Z| vcpu-2| I125: CDROM: Emulate GET CONFIGURATION RT 1 starting feature 0
2019-03-10T21:02:45.472Z| vcpu-3| I125: CDROM: Emulate GET CONFIGURATION RT 1 starting feature 0
2019-03-10T21:32:45.790Z| vcpu-4| I125: CDROM: Emulate GET CONFIGURATION RT 1 starting feature 0
2019-03-10T21:37:58.652Z| vmx| I125: GuestRpc: Got RPCI vsocket connection 270003, assigned to channel 1.
2019-03-10T21:37:59.654Z| vmx| I125: GuestRpc: Got error for channel 1 connection 270004: Remote disconnected
2019-03-10T21:37:59.654Z| vmx| I125: GuestRpc: Closing channel 1 connection 270004
2019-03-10T21:50:26.983Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox timed out.
2019-03-10T21:50:39.976Z| vcpu-0| I125: Tools: Tools heartbeat timeout.
2019-03-10T21:50:39.976Z| vcpu-0| I125: Tools: Running status rpc handler: 1 => 0.
2019-03-10T21:50:39.976Z| vcpu-0| I125: Tools: Changing running status: 1 => 0.
2019-03-10T21:50:46.987Z| vmx| I125: GuestRpcSendTimedOut: message to toolbox timed out.
2019-03-10T21:50:46.987Z| vmx| I125: GuestRpc: app toolbox's second ping timeout; assuming app is down
2019-03-10T21:50:46.988Z| vmx| I125: GuestRpc: Reinitializing Channel 0(toolbox)
2019-03-10T21:50:46.988Z| vmx| I125: GuestMsg: Channel 0, Cannot unpost because the previous post is already completed
2019-03-11T00:24:50.221Z| vmx| I125: GuestRpc: Got RPCI vsocket connection 280003, assigned to channel 1.
2019-03-11T00:24:51.221Z| vmx| I125: GuestRpc: Got error for channel 1 connection 280004: Remote disconnected
2019-03-11T00:24:51.221Z| vmx| I125: GuestRpc: Closing channel 1 connection 280004
2019-03-11T03:11:43.674Z| vmx| I125: GuestRpc: Got RPCI vsocket connection 290003, assigned to channel 1.
2019-03-11T03:11:44.675Z| vmx| I125: GuestRpc: Got error for channel 1 connection 290004: Remote disconnected
2019-03-11T03:11:44.675Z| vmx| I125: GuestRpc: Closing channel 1 connection 290004
2019-03-11T05:58:39.366Z| vmx| I125: GuestRpc: Got RPCI vsocket connection 300003, assigned to channel 1.
2019-03-11T05:58:40.366Z| vmx| I125: GuestRpc: Got error for channel 1 connection 300004: Remote disconnected
2019-03-11T05:58:40.366Z| vmx| I125: GuestRpc: Closing channel 1 connection 300004
This problem occurs on several ESXi machines. The configuration is similiar.
Intel S2600 Board (with newest firmware)
LSI Megaraid Controller (with newest firmware)
Intel Xeon Processors
ESXi 6.7.0 Update 1 (Build 11675023)
Am I the only one having this problem? :-)
Any ideas?
Thanks in advance
Greets from Germany
I am building a new Windows 10 1803 template and using the same guest customization that I have used with previous builds of Windows 10. The vm is cloned from the template and applies sysprep successfully but the machine never reboots/renames or gets added to the domain.
I have rebuilt the Guest Customization settings from scratch and still get the same result.
Any ideas?
Hi,
have here a brand new MacPro 2019 running with VSphere 6.7 U3 (latest) and try to get run our OSX VMs on the Mac.
We have currently MacPros 2012 with ESXi 6.5 (latest) to host our VMs and would like to migrate to newer ESXis.
This is a fine machine and works very well (with two Intel quad 10Gbit nics and a Samsung 1,6 TG NVME PCIe card).
It's superb to have so much PCIe slots and memory at a single Intel 16 core.
The Linux guests are okay, but I get this message, running an Apple MacOS 10.15 (even with 10.14) on a Apple MacPro 2019.
Do you have any (beta) update to bring the right SMC call simulation this machine?
Thanks a lot in advance
Henri
Hi,
I'm relatively new to ESXi. I've been running it as a home server for around 5 months, and so far it's been fantastic. I built my server on new hardware, including the following HBA which I pass through to a FreeNAS VM.
Today I thought I'd try the upgrade to ESXi 7.0, but the installer brings up a warning saying my host has unsupported hardware and logs the following:
[pciinfo 1000:0072 1000:3040]
By the looks of it, this represents my HBA card: https://pci-ids.ucw.cz/read/PC/1000/0072/10003040
I've cancelled the upgrade for now. I'm hoping someone can help me with a couple of questions:
1. Does this warning mean ESXi would not be able to pass this device through to a VM like I've been doing under 6.7?
2. Is there any hope of ESXi supporting this in the future, or does it generally mean they've dropped support for this device now?
Any advice is much appreciated!