Hello.

Please help me find the cause of the error.

Hi everyone,

This question may be trivial, but as a new user to vmware, I have no clue about it.

The point is the following: we have 4 PCs at home, and instead of renewing all of them, I would like to build a multihead system running ESXI in order to vitualize 4 vms, one for each PC we actually have. Each vm will have a head consisting of a dedicated monitor (with GPU passthrough) and USB hub (for connecting mouse and keyboard), and each head will be in a different room. And because of this, it is a requirement that I can start a vm from the heads; this is, with just the keyboard and mouse.

My concern is: is it possible to do that, or do I need to interact with the server through vmware Sphere client -or something alike- if I want to power up a vm?

As I said, I have no experience with ESXI. I do plan on installing it in a spare computer and trying everything I've mentioned, but I haven't done it yet. So any help would be much appreciated.

Best regards

Hi Folks, we have over 500 hosts in our infra. Currently we are patching every quarter using update manager. However, it feels tiresome at point. What is the best and efficient way to do patching of ESXi hosts in this case?

Thanks,

Hari.

I have to update the LSI_SAS driver because of a problem in the virtual machine. ı cant driver for windows 2012. how do I find the latest driver? ESXi 6.5 u1 and os is windows 2012 .

this device driver comes in windows or if vmware tools is installed ?

Hello,

I am trying to learn ESXI so I set up an ESXI inside a VMware Workstation Player, the network is `NAT`

So far I set up a static IP v4 address for ESXI in VmWare Workstation Player, I set it like this

IPV4 Address 192.168.201.3
Subnet mask 255.255.255.0
Default gateway 192.168.201.2

With this for the DNS

Primary 8.8.8.8
Alternate 4.4.4.4
Hostame localhost

When I do a `ip a` on the host machine, I have this

4: vmnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000    link/ether 00:50:56:c0:00:01 brd ff:ff:ff:ff:ff:ff    inet 172.16.1.1/24 brd 172.16.1.255 scope global vmnet1       valid_lft forever preferred_lft forever    inet6 fe80::250:56ff:fec0:1/64 scope link        valid_lft forever preferred_lft forever
5: vmnet8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000    link/ether 00:50:56:c0:00:08 brd ff:ff:ff:ff:ff:ff    inet 192.168.201.1/24 brd 192.168.201.255 scope global vmnet8       valid_lft forever preferred_lft forever    inet6 fe80::250:56ff:fec0:8/64 scope link        valid_lft forever preferred_lft forever

So far so good, I can access esxi.

Now when I create a vm on ESXI (a debian), they are connected to the `VM Network`, I don't have `DHCP` during the installation of Debian but I guess it's normal.

Later after the installation of Debian, I tried to set up a static ip address in the same range of `192.168.201.0/24`, I can ping the vm from the esxi vm installed in VMware Player. But I can not ping the debian vm installed in esxi from my host and I can not access internet in the debian vm. Also when I set the gateway on the debian vm, I cannot access it so I suppose something is really wrong in the way I configure the static ip address on the debian vm.

Here is my config for the debian vm

cat /etc/network/interfaces
allow-hotplug ens192
iface ens192 inet static     address 192.168.201.11/24     gateway 192.168.201.2

ip r
default via 192.168.201.2 dev ens192 onlink
192.168.201.0/24 dev ens192 proto kernel scope link src 192.168.201.11

I don't understand, I guess I probably miss configured something maybe.

Thank you in advance for your help

PS1: The `VM Network` is set with VLAN ID: 0`

PS2: I am running this on Arch Linux and I have this version of the kernel `5.1.5-arch1-2-ARCH`

Hi,

When I try to install ESXI 6.7u1 on a HPE BL360c gen8 blade it shows this error its the first time i've had an error on these machines i've installed this same version on 28 other blades exactly the same but this one doesn't want to work I have attached an image of the error. i'm assuming its something to do with the micro SD card in the system for install by the error?

Hi All,

I have one RAID-0 array in my server. I'd need to break it (decrease it by one disk) but do not want to lose any vms on this machine.

To be able to keep all existing machines I want to perform the following activities. Kindly ask to verify if it makes sense and does not break my ESXi setup.

1. I'll add new temporary disk which will be out of the RAID - new datastore

2. I'll migrate all virtual machines from existing datastore (RAID0) to new, temporary datastore

3. I'll rebuild old datastore (based on RAID0)

4. When already restored, I'll migrate all vms back

5. Will decommission temporary datastore

Is this list complete? Do virtual machines are the only entities that need to be migrated? Doesn't ESXi require any disk to be able to boot?

Will appreciate your help

Hi! I have a single ESXi host that rruns various VMs.

I found out that if I pass through an Emulex LPe11000 card, the guest crashes. Let me resume some facts:

- I have a linux VM with a PCIe ASMedia eSATA controller passed-through card that has been working for years

- I have a Windows 8.1 VM that I used for long time with an LSI SCSI controller in passtrough without problem

- I have replaced the LSI SCSI with the Emulex FC4. The VM boots normally. If I try to install the driver it powers off
- I have created a new VM; if the Emulex card is passed through, even the Windows boot disk (tried W7 and W10) makes the machine power off. Same problem if I try to boot with a live ISO of Ubuntu 18.04

If I boot with windows 8 on the physical hardware, the system goes up and I'm able to install the Emulex driver normally.

ESXi continues running flawlessly when the VM guest powers off.

So I'm wondering: why that issue only with that specific card? How to fix it? Any suggestion?

and sorry, I'm running 6.7.0 Update 2 (Build 13006603) on a Lenovo M93P.

Thanks!

Hello,

last August, I've updated our (Free) Esxi 5.5 to version 6.0.

First, everything seems to be working fine.

But after a while, I found out that configuration changes were not preserved after a reboot of the host.

Configuration changes are very rare in our company, for that it took a while to notice the problem, so I am not 100% sure, that this problem stems from the update.

Hardware Information:

ProLiant ML350p Gen8

iLO Self-Test Results:

Supported host

Power Management Controller         Version 3.3

....

Embedded Flash/SD-CARD         Controller firmware revision 2.10.00 /8 GB SD-CARD in internal slot

CPLD - PAL1         ProLiant ML350p Gen8 SAS Programmable Logic Device version 0x0C

CPLD - PAL0         ProLiant ML350p Gen8 System Programmable Logic Device version 0x4D

....

software information:

vmware -vl

VMware ESXi 6.0.0 build-9313334

VMware ESXi 6.0.0 Update 3

esxcfg-info -e

boot type: visor-usb

After doing some reading in the vmware kb I found out:

[root@esxi-hit:~] ls -la /*boot*

lrwxrwxrwx    1 root     root             4 Apr 23 13:19 /bootbank -> /tmp

-r--r--r--    1 root     root        332055 Jul 27  2018 /bootpart.gz

[root@esxi-hit:/etc/rc.local.d] vmkfstools -P /altbootbank

Could not open /altbootbank

Error: No such file or directory

[root@esxi-hit:/etc/rc.local.d] grep bootbank  /var/log/esxupdate.log

2019-04-23T06:44:12Z esxupdate: HostImage: INFO: Installer <class 'vmware.esximage.Installer.BootBankInstaller.BootBankInstaller'> was not initiated - reason: altbootbank is invalid: Error in loading boot.cfg from bootbank /bootbank: Error parsing bootbank boot.cfg file /bootbank/boot.cfg: [Errno 2] No such file or directory: '/bootbank/boot.cfg'

So, it seems that there is something wrong with the "Embedded Flash/SD-CARD"

What can I do to get rid of the problem?

Thanks in advance.

best regards from germany

Siegfried

Hello all,

I need your help about create datacenter and cluster settings on Esxi 6.7 u2. There is no option create datacenter or cluster option under actions menu. I am new on Vmware virtulazation software. Do I need vcenter server for this operations.

Thanks in advance for your support.

We set up a Mac Pro 2013 (MacPro6,1) as an ESXi host 6.7U2.

We confirmed the model and Boot ROM are compatible with the above.

We built the virtual machine (macOS Mojave 10.14.5) in VMware Fusion Pro 11.1.0 and uploaded to the ESXi host.

Tools were updated within VMware Fusion Pro 11.1.0 before uploading through the app to the ESXi host.

The virtual machine works beautifully, however ESXi complains the VMware Tools on the virtual machine need to be updated.

When I bring up the virtual machine an log in (since VMware Tools can't be installed on macOS without someone logged in), nothing happens.

If I try to update VMware Tools on the virtual machine using VMware Fusion Pro 11.1.0, I get this error, seems like something is missing on the ESXi host:

How can this be fixed so ESXi stops complaining about VMware Tools being out of date?

Thanks,
Don

Hi:

I have a server running ESXi 5.5 with (2) VMs:

VM1: Virtual Machine Version 8, Windows Server 2012 R2 Standard, E1000E network adapter

VM2: Virtual Machine Version 10 vmx-10, Windows Small Business Server 2011 Stadard, E1000 network adapter

Both VMs are on the same VMNetwork and both are showing network adapters connected at 1Gbps.

If I run an Internet speed test from VM1, it comes back around 500 Mbps (customer has fast fiber Internet connection)

If I run an Internet speed test from VM2, it comes back at only 15 Mbps

Any ideas as to why VM2 connects to Internet so much slower?

Thank you!

Bob H.

Hi there,

I have a problem, no storage devices are listed in both vcenter and vsphere when I try increasing the

size of a datastore, any pointers towards resolving this please, am running Esxi 6.0, 3620759

Hi all,

I have a very small, 2 host ESXi setup (vCenter Essentials Plus 6.7) and each host as 4 x 1Gbit NIC's (HP DL380 Gen10)

My question is, is this considered typical in terms of security?:

2 x NIC teamed for production, (static channel group on switch, no LACP due to licencing)

1 x NIC for management / vmk0 (physically separate to switch) different VLAN

1 x NIC for vMotion / vmk1 *

* for vMotion I have connected the two hosts ports with a single patch cable (no switch) and I'm using link-local addresses for vMotion.

I don't intend ever to have more than 2 hosts (unless migration upgrading), is this ok do to? It works as expected.

Throughput/Performance not an issue, I don't have 10Gb switches yet.

Cheers all,

Matt

Hi community,

its probably a simple fix but im having trouble trying to create a datastore on two hosts that were previously used?

when i try and create a datastore it shows this error (Either the selected disk already has a VMFS datastore or the host cannot perform a partition table conversion. Select another disk)

when i try to delete the exsisting partitions it just shows an error and wont delete them.

i have tried deleting the disk in the server raid controller i have it set up as "2x SSD's in a RAID 1"

Matto

The setup is a HPE ProLiant DL380 Gen10 server running ESXi 6.7 Hypervisor. There is no vCenter server. The server has dual power supplies. There is an APC Smart UPS (SMT1000RMI2UC) available.

Upon a power outage in the building, I'd like to have the ESXi host server automatically suspend all its VMs and shut itself down after the power has been gone for 5 minutes.

Can this be achieved without using a third-party server?

For example, maybe I could connect one of the server's power supplies to the UPS and the other to a power outlet. That way, the server should be able to detect if there's a power outage. Combining that with some scripting to suspend its VMs and power itself off  ... ?

I'm just connecting to the web GUI for the host, I don't have vCenter server.

When I go into the Host - Monitor - Hardware - Storage, I get the message "The Small Footprint CIM Broker Daemon (SFCBD) is running, but no data has been reported. You may need to install a CIM provider for your storage adapter." Below I see "No data available".

Hardware is a Dell PowerEdge R630 with Perc H730 Mini and a Raid 10 configuration with 8x 2.5" disks.

I am running “Dell Customized Image ESXi 6.5 Update 1 A05 (based on ESXi VMKernel Release Build 6765664)” which contains driver “Dell PERC Controller Drivers - lsi-mr3 - 7.700.50.00”

sfcbd-watchdog service ist running and System Sensors are working and viewable.

Dell VMWare OMSA is installed.

The system is working without any problems and I have Rebooted the host several times.

I would appreciate for any help/advice on how I can get my storage monitoring data visible?

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

Hello all, after when i`m add a new wirtual mashine i recived psod. I have new desctop hardware. Thanks all!

EESXi version:

6.7.0

EESXi build number:

8169922

Log

2019-06-05T10:16:07.202Z cpu12:2099602)@BlueScreen: #PF Exception 14 in world 2099602:vmm1:UFS IP 0x418006e8063f addr 0x436083938028

PTEs:0x1004ce023;0x0;

2019-06-05T10:16:07.202Z cpu12:2099602)Code start: 0x418006e00000 VMK uptime: 0:02:01:08.016

2019-06-05T10:16:07.203Z cpu12:2099602)0x451a1cf1bad8:[0x418006e8063f]CPUTopology_AreRelated@vmkernel#nover+0x2b stack: 0x0

2019-06-05T10:16:07.203Z cpu12:2099602)0x451a1cf1bae0:[0x418007113771]CpuSchedRebalance_StickySysCyclesAdd@vmkernel#nover+0x42 stack: 0x43006a0d04b0

2019-06-05T10:16:07.203Z cpu12:2099602)0x451a1cf1bb10:[0x418006eedbac]IntrCookie_DoInterrupt@vmkernel#nover+0x1ed stack: 0x7780

2019-06-05T10:16:07.204Z cpu12:2099602)0x451a1cf1bbc0:[0x418006eee0f1]IntrCookie_VmkernelInterrupt@vmkernel#nover+0x3a stack: 0xffffffffffffffef

2019-06-05T10:16:07.204Z cpu12:2099602)0x451a1cf1bbe0:[0x418006f442ec]IDT_IntrHandler@vmkernel#nover+0x9d stack: 0x0

2019-06-05T10:16:07.204Z cpu12:2099602)0x451a1cf1bc00:[0x418006f5e066]gate_entry@vmkernel#nover+0x67 stack: 0x0

2019-06-05T10:16:07.204Z cpu12:2099602)0x451a1cf1bcc0:[0x418006e9ac48]Power_ArchSetCState@vmkernel#nover+0x15c stack: 0x0

2019-06-05T10:16:07.205Z cpu12:2099602)0x451a1cf1bcf0:[0x418007103302]CpuSchedIdleLoopInt@vmkernel#nover+0x333 stack: 0x450184afa000

2019-06-05T10:16:07.205Z cpu12:2099602)0x451a1cf1bd60:[0x418007105fd5]CpuSchedDispatch@vmkernel#nover+0x12aa stack: 0x451a00000001

2019-06-05T10:16:07.205Z cpu12:2099602)0x451a1cf1beb0:[0x4180071074bb]CpuSchedWait@vmkernel#nover+0x2f4 stack: 0x450100000000

2019-06-05T10:16:07.205Z cpu12:2099602)0x451a1cf1bf40:[0x418007107c34]CpuSched_VcpuHalt@vmkernel#nover+0x12d stack: 0x0

2019-06-05T10:16:07.206Z cpu12:2099602)0x451a1cf1bfa0:[0x418006f335a6]VMMVMKCall_Call@vmkernel#nover+0xf7 stack: 0x0

2019-06-05T10:16:07.206Z cpu12:2099602)0x451a1cf1bfe0:[0x418006f57cdd]VMKVMM_ArchEnterVMKernel@vmkernel#nover+0xe stack: 0x0

2019-06-05T10:16:07.208Z cpu12:2099602)base fs=0x0 gs=0x418043000000 Kgs=0x0

2019-06-05T10:16:07.208Z cpu12:2099602)vmkernel             0x0 .data 0x0 .bss 0x0

2019-06-05T10:16:07.208Z cpu12:2099602)chardevs             0x418007528000 .data 0x417fc0000000 .bss 0x417fc0000440

2019-06-05T10:16:07.208Z cpu12:2099602)user                 0x418007530000 .data 0x417fc0400000 .bss 0x417fc0410a00

2019-06-05T10:16:07.208Z cpu12:2099602)procfs               0x41800762a000 .data 0x417fc0a00000 .bss 0x417fc0a00240

Hi,

I am trying to update HPE Microserver with ESXi 6.0 U2 to ESXi 6.5 U2 - I am using HPE custom image (VMware-ESXi-6.5.0-Update2-9298722-HPE-preGen9-650.U2.9.6.8.3-Sep2018.iso)

During the update process I am getting OSError [Errno 39] Directory not empty: '/vmfs/volumes/<something>System Volume Information'

I was checking for state.xxx folders in /bootbank and /newbank but nothing is there

This is contents of /altbootbank

total 257

drwxr-xr-x    1 root     root           512 Jun  5 18:05 ..

drwxr-xr-x    1 root     root             8 Jun  5 12:15 System Volume Information

-rwx------    1 root     root           184 Jun  5 17:45 imgdb.tgz

Here is the upgrade log:

2019-06-05T17:28:49Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-06-05T17:28:49Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-06-05T17:28:49Z esxupdate: imageprofile: INFO: Adding VIB VMware_locker_tools-light_6.0.0-2.34.3620759 to ImageProfile (Updated) HPE-ESXi-6.0.0-Update2-iso-600.9.6.0.49

2019-06-05T17:28:49Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-U', 'host-acceptance-level', '-G']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-06-05T17:28:49Z esxupdate: root: DEBUG: Finished execution of command = profile.setacceptance

2019-06-05T17:28:49Z esxupdate: root: DEBUG: Completed esxcli output, going to exit esxcli-softwareinternal

2019-06-05T17:45:28Z esxupdate: root: INFO: Command = profile.setacceptance

2019-06-05T17:45:28Z esxupdate: root: INFO: Options = {}

2019-06-05T17:45:28Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-rp']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-06-05T17:45:28Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/bootOption', '-ro']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-06-05T17:45:28Z esxupdate: imageprofile: INFO: Adding VIB VMware_locker_tools-light_6.0.0-2.34.3620759 to ImageProfile (Updated) HPE-ESXi-6.0.0-Update2-iso-600.9.6.0.49

2019-06-05T17:45:28Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = '['/sbin/esxcfg-advcfg', '-U', 'host-acceptance-level', '-G']', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2019-06-05T17:45:28Z esxupdate: root: DEBUG: Finished execution of command = profile.setacceptance

2019-06-05T17:45:28Z esxupdate: root: DEBUG: Completed esxcli output, going to exit esxcli-softwareinternal

Any idea how to fix this?

Thanx,

D