Member Login | Register
Navigation
  • Home
  • Blog
  • Forums
  • FAQ
Home : All Forums : Software : Others
Recent Posts My Posts My Subscriptions

ESXi 6.5.0 crashes when trying to run the installer (APU2C4)

Subscribe New Topic Reply
    Next
    1 2
  • QuoteRate
    My Posts

    Posts: 105
    mikeboss - Posted Nov 24th 2016

     

    just as the thread title suggests: ESXi 6.5.0 crashes when trying to run the installer on APU2C4. ESXi 6.0 U2 works just fine. any ideas? heres the log:

    VMware ESXi 6.5.0 [Releasebuild-4564106 x86_64]
    FAILED TO MEM_MAP PCI BAR 0
    cr0=0x80010031 cr2=0x5a58600 cr3=0x83876000 cr4=0x40768
    *PCPU3:65874/vmkdevmgr
    PCPU  0: UIUU
    Code start: 0x418013800000 VMK uptime: 0:00:01:32.547
    0x4390ca91b1c0:[0x4180138ec611]PanicvPanicInt@vmkernel#nover+0x545 stack: 0x4180
    138ec611
    ~0x4390ca91b260:[0x4180138ec9a7]Panic_vPanic@vmkernel#nover+0x23 stack: 0x43043a
    5a1480
    ~0x4390ca91b280:[0x4180139005e1]vmk_PanicWithModuleID@vmkernel#nover+0x41 stack:
     0x4390ca91b2e0
    ~0x4390ca91b2e0:[0x41801417d918]pcidrv_alloc_resource@(vmkusb)#+0x410 stac
    k: 0x1417a436
    ~0x4390ca91b3e0:[0x41801417843b]bus_alloc_resource@(vmkusb)#+0x67 stack: 0
    x4
    ~0x4390ca91b440:[0x418014154763]xhci_pci_attach@(vmkusb)#+0x83 stack: 0xon
    e>+0x23 stack: 0x0
    0x4390ca91b4c0:[0x418014162d9e]USBDeviceAttach@(vmkusb)#+0x106 stack: 0x15
    ~0x4390ca91b4f0:[0x418013820584]Driver_AnnounceDevice@vmkernel#nover+0xfc stack:
     0x430200000015
    ~0x4390ca91b560:[0x41801381e34c]DeviceBind@vmkernel#nover+0x15c stack: 0xbad0007
    0x4390ca91b5a0:[0x41801381f13e]DeviceVSIBind@vmkernel#nover+0xc2 stack: 0x0
    0x4390ca91b5d0:[0x418013801f95]VSI_SetInfo@vmkernel#nover+0x369 stack: 0x4390ca9
    1b6b0
    ~0x4390ca91b650:[0x418013f16df4]UWVMKSyscallUnpackVSI_Set@(user)#+0x308 st
    ack: 0x0
    ~0x439te_entry_@vmkernel#nover+0x0 stack: 0x0
    base fs=0x0 gs=0x418040c00000 Kgs=0x0
    No place on disk to dump data.
    No file configured to dump data.
    No vsan object configured to dump data.
    No port for remote debugger.


    Post last edited Nov 24th 2016
  • QuoteRate
    My Posts

    Posts: 12
    Laurens - Posted Dec 1st 2016

    I have the same issue!

  • QuoteRate
    My Posts

    Posts: 1
    nyebi - Posted Dec 12th 2016

    The same here with an apu2c2 board.
     

  • QuoteRate
    My Posts

    Posts: 4
    Rayures - Posted Jan 14th 2017

    same here.

    tried to update 6.0 u2 via cli. updating went fine, but after reboot the error ( "VMware ESXi 6.5.0 [Releasebuild-4564106 x86_64] ; FAILED TO MEM_MAP PCI BAR 0").

    tried clean install via image on usb; installer crash.

     

    sounds like a missing driver. Hope someone knows more or can fix this.

  • QuoteRate
    My Posts

    Posts: 105
    mikeboss - Posted Jan 14th 2017

     

    for ESXi 6.5.0, I switched to a Shuttle DX30 -> http://us.shuttle.com/products/dx30/

    single-thread performance is about 3 to 4 times as fast, price is more or less in the same range as the APU2.

    I paid CHF 180.00 (sans RAM)

    it runs NVMexpress SSDs, too ;-) and 8GB of RAM.

    http://browser.geekbench.com/v4/cpu/1466686
    http://browser.geekbench.com/v4/cpu/1466793

    https://twitter.com/mibosshard/status/814882046166310916

  • QuoteRate
    My Posts

    Posts: 2
    Locutus73 - Posted Jan 27th 2017

    Hi,

    it seems to me that this problem could be resolved disabling the new vmkusb driver as suggested here

    https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2147650

    you should try to boot the USB/SD elsewhere (i.e. VMware Workstation on a PC) and run esxcli system module set -m=vmkusb -e=FALSE 

     

    I had similar issues (the system booted, but it had bad disk performances) with the new vmw_ahci driver on my APU1D4 and I resolved following this article

    http://www.nxhut.com/2016/11/fix-slow-disk-performance-vmwahci.html

     

    Let me know if this trick resoves the issue, since I'm very interested in upgrading to APU2C4 or APU3A4

     

    Best regards

    Locutus73

  • QuoteRate
    My Posts

    Posts: 4
    Rayures - Posted Jan 29th 2017

    Locutus73 - Posted 48 Hours Ago

    it seems to me that this problem could be resolved disabling the new vmkusb driver as suggested here

    https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2147650

    you should try to boot the USB/SD elsewhere (i.e. VMware Workstation on a PC) and run esxcli system module set -m=vmkusb -e=FALSE 

     

    I had similar issues (the system booted, but it had bad disk performances) with the new vmw_ahci driver on my APU1D4 and I resolved following this article

    http://www.nxhut.com/2016/11/fix-slow-disk-performance-vmwahci.html

     

     


    hi there,

    interesting info, tnx!

    unfortionately i have esxi installed on a msata drive and have no options to boot it in another machine. tried some things to get it running but no luck :-(

  • QuoteRate
    My Posts

    Posts: 2
    Locutus73 - Posted Jan 29th 2017

    Rayures - Posted 5 Hours Ago

    hi there,

    interesting info, tnx!

    unfortionately i have esxi installed on a msata drive and have no options to boot it in another machine. tried some things to get it running but no luck :-(

     


    Can't you somehow use the msata drive as the "phisical drive" of a VMware Workstation virtual machie on a PC? I followed this path in order to install and cofigure ESXi 6.0 on a SD that I subsequently used on my APU1D4. I use my entire msata drive as datastore booting ESXi from the SD.

    Alternatively can you try to install again ESXi 6.0 on your APU2C4, then upgrade to 6.5 via Offline Bundle (see http://www.vladan.fr/how-to-upgrade-esxi-6-0-to-esxi-6-5-via-offline-bundle/ ) and then disable vmkusb just before rebooting?

     

    Best regards

    Locutus73

  • QuoteRate
    My Posts

    Posts: 4
    Rayures - Posted Jan 29th 2017

    Locutus73 - Posted 4 Hours Ago

     


    Rayures - Posted 5 Hours Ago

    hi there,

    interesting info, tnx!

    unfortionately i have esxi installed on a msata drive and have no options to boot it in another machine. tried some things to get it running but no luck :-(

     


    Can't you somehow use the msata drive as the "phisical drive" of a VMware Workstation virtual machie on a PC? I followed this path in order to install and cofigure ESXi 6.0 on a SD that I subsequently used on my APU1D4. I use my entire msata drive as datastore booting ESXi from the SD.

    Alternatively can you try to install again ESXi 6.0 on your APU2C4, then upgrade to 6.5 via Offline Bundle (see http://www.vladan.fr/how-to-upgrade-esxi-6-0-to-esxi-6-5-via-offline-bundle/ ) and then disable vmkusb just before rebooting?

     

    Best regards

    Locutus73

     


    hi there,

    i installed esxi 6.0 directly on the msata drive in the apu2c4 via serial. And at the moment i cant attach a msata drive to a desktop (no msata slot on mobo), but i ordered a msata to sata adapter :-)

    i already tried the offline update. update installs, but can not set the vmkusb. says module not found.

  • QuoteRate
    My Posts

    Posts: 2
    chelmi - Posted Feb 13th 2017

    I was able to circumvent this issue quite easily by creating a custom esxi 6.5 installer ISO.

    You can do this with the tools of your choice and if you're a unix guy at heart you may not like this, but v-front has a very convenient powershell script you can use to produce such images.

    All you need to do is download their script and VMWare PowerCLI on a Windows machine: https://www.v-front.de/p/esxi-customizer-ps.html

     

    I simply ran the script with a remove option: .\ESXi-Customizer-PS-v2.5.ps1 -remove vmkusb

    After a while you'll find an ISO file in your running folder that you'll be able to boot from and install ESX 6.5. Don't forget to add the kernel option to the boot.cfg on the stick otherwise you won't see the output of your console.

    The installation seems to hang at 27%, but be patient as is it actually copying the files over to your storage.

    After that I recommend SSHing into vmware to edit boot.cfg rather than booting tinycore, as this screwed by installation.

     

    If you need help or even the produced ISO file just let me know

     

     


    Post last edited Feb 13th 2017
Next
1 2
Subscribe

Rules: