Quantcast
Channel: VMware Communities: Message List - ESXi
Viewing all 28826 articles
Browse latest View live

Re: bootbank cannot be found at path /bootbank

$
0
0

Yep im running into the exact same issue now. I was getting error 30 when trying to remediate hosts and taking a look at the esxupdate.log I can see stuff like "HostImage: INFO: Installer <class 'vmware.esximage.Installer.BootBankInstaller.BootBankInstaller'> was not initiated - reason: bootbank is invalid: /bootbank is not a directory!" so taking a look then at the vmkernel.log I saw a lot of "Bootbank cannot be found at path '/bootbank'" I am still messing around trying to see if I can clear this up somehow, or if there is a way to see what is causing it.

 

 

 

 

 

 

Hosts:

Apple MacPro 6,1 64GB

ESXi 6.5U1 Build 5969303


Re: bootbank cannot be found at path /bootbank

$
0
0

Running "vmkfstools -P /altbootbank" on a host that was failing to remediate and I get "Could not open /altbootbank Error: Unable to access device, please check your connection to the device." and all the ones that had no issues come up with:

 

 

vfat-0.04 (Raw Major Version: 0) file system spanning 1 partitions.

File system label (if any):

Mode: private

Capacity 261853184 (63929 file blocks * 4096), 107085824 (26144 blocks) avail, max supported file size 0

UUID: 60bb93e2-bae9cfea-08ce-a7ad0878d60f

Partitions spanned (on "disks"):

  t10.SanDisk00Ultra_Fit000000000000004C530001240407120381:5

Is Native Snapshot Capable: NO

 

 

Re: About VMWare

$
0
0

1. Create your home lab - and begin from deploying hypervisor, running web appliance for,configuring v center

2. Learn about P2V conversions,try one,learn about snapshots,live backup of vms by external programs

3.learn and practice about vkernel ports and practice

 

and again...even best training available is not worthy if you are not able to practice it live :]

Re: bootbank cannot be found at path /bootbank

$
0
0

Got same issue - all redirects and folders on these bootbank werenot accesible.

So I was not able even to upgrade/install VM tools,which were stored there.

Resolution were only to make shortcut to another folder on datastore like workaround or reinstall hypervisor on new sd card

000.JPG

The operation on file "/vmfs/devices/deltadisks/test.vmdk" failed. ESXi 6.0

$
0
0

Hi,

 

I'm using a image created using qemu-img and I get "The operation on file "/vmfs/devices/deltadisks/test.vmdk" failed. ...." in the WebUI and I can see this errors in VMWare log in the host

2018-01-18T14:17:51.553Z| Worker#0| I120: FileIOErrno2Result: Unexpected errno=12, Cannot allocate memory 

2018-01-18T14:17:51.553Z| vmx| I120: VMXAIOMGR: Retry on read "/vmfs/devices/deltadisks/2828f296-test-s001.vmdk" : Cannot allocate memory. 

2018-01-18T14:17:51.553Z| vmx| I120: VMXAIOMGR: system : err=c0002 errCode=12 freeSpace=0 

2018-01-18T14:17:51.553Z| vmx| I120: VMXAIOMGR: "/vmfs/devices/deltadisks/2828f296-test-s001.vmdk" : read s=42949279744 n=131072 ne=1, fai=0 

2018-01-18T14:17:51.553Z| vmx| I120: VMXAIOMGR: v[0]=B802B9B8000:131072 

The image sometimes start the boot process and hang before is fully booted, other times it gives this error immediately before even GRUB finished loading.

Using vmkfstools -x check show no errors in the disk image. Also importing the image makes the image work, but I want to get the image working from the original.

 

For context, the image is using the IDE controller, and was created with monolithicSparse type. One other detail is that when I run the image the system split the disk  metadata automatically moving the main image to a file suffixed with "-s001" in the file name and it changes the metadata from createType="monolithicSparse" to createType="twoGbMaxExtentSparse".

 

Does anyone have any pointers on how to figure out what the problem is exactly?

Re: The operation on file "/vmfs/devices/deltadisks/test.vmdk" failed. ESXi 6.0

$
0
0

Please check the KB article as the error out of memory messages is similar to the below kb

FileIOErrno2Result: Unexpected errno=12, Cannot allocate memory

 

VMware Knowledge Base

 

Thanks,

MS

Re: PCPU : no heartbeat

$
0
0

I am running 6.5 and all 6 hosts all have  been crashing as of late.  Trying to figure out if its a vm issue or hardware issue and VMware nor Dell can figure it out.

 

ESXi 6.5 Build 5969303

Re: The operation on file "/vmfs/devices/deltadisks/test.vmdk" failed. ESXi 6.0

$
0
0

Thanks for the answer, the system is a test system has no other VM's running at the moment, and I checked the heap size, is in the default of 256 mb


Re: The operation on file "/vmfs/devices/deltadisks/test.vmdk" failed. ESXi 6.0

$
0
0

Can you check the vmkernel and hostd log when trying to power on ..which can give us some more information about why it is failing to power on

 

Thanks,

MS

Re: pCPU vs vCPU - Relation/Ratio

$
0
0

I'd like to extend this question specifically as it relates to HA. In a small environment (2 hosts), if you've oversubscribed at say a 3:1 ratio are you going to kill your server if one goes down? (We have 3 hosts but the third is offsite for replication at another office.) So I have two usable servers on site. Right now I'm running a 1:1 ratio so that if a host goes down, I don't kill the performance on the other server. And I have tested this setup and nobody even realized we were running on one host. Any input would be appreciated.

Re: pCPU vs vCPU - Relation/Ratio

$
0
0

The answer is, of course, it depends. While optimum design is n-1, budgets often make this impossible. I shoot for as close to that as possible, but in the event of over-committed hosts, I'm ready to first shut down any non-critical guests and I have no issue standing in the boss' office explaining why we are running a bit slower. That will trigger one of 2 things. 1) He'll accept it. oor 2) tell me to get what I need so it does not happen again.

HBA - Disks not showing up

$
0
0

I have a freshly updated supermicro X11SSL -cF motherboard with onboard LSI Logic Fusion-MPT 12GSAS SAS3008 PCI-Express controller flashed to IT mode. In esxi web, I see the controller and am able to enable passthrough for it. However, the drives attached to the controller do not show up. They didn't show up before or after upgrading bios on motherboard or firmware on controller. I even installed latest driver VIB into esxi which I downloaded from VMware Compatibility Guide - I/O Device Search.

 

   VIBs Installed: Avago_bootbank_lsi-msgpt3_16.00.00.00-1OEM.650.0.0.4598673

   VIBs Removed: VMW_bootbank_lsi-msgpt3_12.00.02.00-11vmw.650.0.0.4564106

 

The controller does list the drives during boot and I've checked the drives and cables.

 

I've been digging into this for days now and would very much appreciate any tips here.

 

Thank you.

Re: ESXi host vswitch bottlenecks

$
0
0

Thanks for your response. The issue is not with physical switch. There is no broadcast traffic observed on physical switch. The unicast traffic which is generated, reaches the vswitch on ESXi host. But the vswitch is able to switch only up to certain extent. Following are example results.

 

(1) Using 64 Byte packets, with 4 vCPUs and 4 vNICs inside VM, Tx perf is 3.4MPPS and Rx perf is 870KPPS.

(2) Using 64 Byte packets, with 8 vCPUs and 4 vNICs inside VM, Tx perf is 4.9MPPS and Rx perf is 1.15MPPS

 

From my analysis, it looks like host vswitch is becoming the bottleneck. Kindly let me know if anybody has made similar observations.

 

Also, do anybody has performance results for DPDK based L2 forward, running in a VM that is using vmxnet3 PMD?

 

Thanks in advance.

Re: HBA - Disks not showing up

Re: HBA - Disks not showing up


Re: Error:Unexpected character '' (code 65279 / 0xfeff) in prolog; expected '

$
0
0

I realize this is a bit old but for those whom are still struggling with this, below is the short answer (English).

 

Do this: Workaround

To temporarily disable the secure mode described in this article, click the appropriate link to download a .reg file, and then double-click the downloaded .reg file to make the registry changes.

For applications targeting the Microsoft .NET Framework 3.5:

Download Download the ManualOptOutSchSendAuxRecord20.reg file now.

 

Details:

https://support.microsoft.com/en-us/help/3155464/ms16-065-description-of-the-tls-ssl-protocol-information-disclosure-vu

 

--Jody

Re: ESXi 6.5U1 vulnerability to Spectre with unpatched BIOS

$
0
0

Hi,

I think, the patch has been fixed the issue for you and there is no need to apply BIOS patch.

Also patching the BIOS will make sure about full protection.

Re: ESXi 6.5U1 vulnerability to Spectre with unpatched BIOS

$
0
0

Just ran a tool called InSpectre (read about it here: InSpectre: See whether your PC's protected from Meltdown and Spectre | Computerworld )

in a patched Windows VM. Here are the results I received:

 

Spectre & Meltdown Vulnerability

and Performance Status

 

Vulnerable to Meltdown: NO

Vulnerable to Spectre: YES!

Performance: SLOWER

 

This system's present situation:

 

This 64-bit version of Windows has been updated for full awareness of both the Spectre and the Meltdown vulnerabilities. If the system's hardware (see below) has also been updated, this system will not be vulnerable to these attacks.

 

This system's hardware has not been updated with new features required to allow its operating system to protect against the Spectre vulnerabilities and/or to minimize their impact upon the system's performance. (Protection from the Meltdown vulnerability does not require BIOS or processor updates.)

 

This system's Intel processor does not provide high-performance protection from the Meltdown vulnerability. The use of Meltdown protection on this system will incur some corresponding performance penalty.

 

This system's older Intel processor does not provide high-performance protection from the Meltdown vulnerability. Windows is therefore doing the best job it can to protect the system, though with a possibly significant performance penalty. You may wish to considering disabling this system's Meltdown protection until it is offered at lower system performance cost.

 

So it seems even with the ESXi patch I'm still vulnerable to Spectre, as well as taking a performance hit due to the Meltdown patch.

AMD Ryzen для исполнения ESXi, Workstation

$
0
0

1.Стоит ли покупать процессор AMD Ryzen 5 для оснащения ПК, если планируется запустить на данном ПК гипервизор ESXi ?

Инструмент "VMware Compatibility Guide" (https://www.vmware.com/resources/compatibility/search.php) говорит, что ESXi совместим только с процессорами серии Opteron.

 

2. Подойдет ли процессор AMD Ryzen 5 для исполнения продукта VMWare Workstation ?

VMware Compatibility Guide

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

$
0
0

THANK YOU THANK YOU THANK YOU

In my case we have recently installed vmware 6.0 U3 that caused this problem

 

Your solution worked! FINALY, I have performed it a little bit and here is my recipe:

 

1. You may use putty so first enable SSH on affected host

2. Login to MyVMWARE and access the link https://my.vmware.com/group/vmware/details?downloadGroup=DT-ESXI60-EMULEX-BE2ISCSI-11411780&productId=491

3. Extract zip, and all zip inside.

4. Find both VIB:

   - EMU_bootbank_ima-be2iscsi_11.4.1178.0-1OEM.600.0.0.2494585.vib

   - EMU_bootbank_scsi-be2iscsi_11.4.1178.0-1OEM.600.0.0.2494585.vib

     COPY both VIB to affected host into/var/log/vmware AND NOT TO TMP LIKE SAYED IN README

5. Execute on each affected host:

    - esxcli software vib install -v EMU_bootbank_ima-be2iscsi_11.4.1178.0-1OEM.600.0.0.2494585.vib

    - esxcli software vib install -v EMU_bootbank_scsi-be2iscsi_11.4.1178.0-1OEM.600.0.0.2494585.vib

6. THE PROBLEM IS GONE even no need to restart the host

7. Option, you may apply this article to configure a persistent location VMware Knowledge Base

 

 

Have FUN !

Viewing all 28826 articles
Browse latest View live


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