Hello Experts,

I have a question about how does the PSP works. We have the below SATP list that should enforce EMC Symmetrix SAN to a default PSP of RoundRobin policy. Then i have decided to make a test of manually changing the LUNs multipath policy to Fixed then reboot the host to make sure it will come up and re-establish the LUN connection so it will apply the default PSP which is RR. However, it seems the default PSP was not applied and the LUN connection came up again as fixed with the same preferred path. Does anyone know if that's the expected behavior or if there is something wrong with my config? Below are the detailed steps. Thanks

[root@ESXi:~] esxcli storage nmp satp rule list | grep -i emc

VMW_SATP_SYMM                EMC      SYMMETRIX                                                        system                                                                     EMC Symmetrix

VMW_SATP_INV                 EMC      Invista                                                          system                                              

VMW_SATP_INV                 EMC      LUNZ                                                             system                                                                     Invista LUNZ

[root@ESXi:~] esxcli storage nmp satp list

Name                 Default PSP    Description

-------------------  -------------  ------------------------------------------

VMW_SATP_SYMM        VMW_PSP_RR     Supports EMC Symmetrix

VMW_SATP_MSA         VMW_PSP_MRU    Placeholder (plugin not loaded)

VMW_SATP_ALUA        VMW_PSP_MRU    Placeholder (plugin not loaded)

VMW_SATP_DEFAULT_AP  VMW_PSP_MRU    Placeholder (plugin not loaded)

VMW_SATP_SVC         VMW_PSP_FIXED  Placeholder (plugin not loaded)

VMW_SATP_EQL         VMW_PSP_FIXED  Placeholder (plugin not loaded)

VMW_SATP_INV         VMW_PSP_FIXED  Placeholder (plugin not loaded)

VMW_SATP_EVA         VMW_PSP_FIXED  Placeholder (plugin not loaded)

VMW_SATP_ALUA_CX     VMW_PSP_RR     Placeholder (plugin not loaded)

VMW_SATP_CX          VMW_PSP_MRU    Placeholder (plugin not loaded)

VMW_SATP_LSI         VMW_PSP_MRU    Placeholder (plugin not loaded)

VMW_SATP_DEFAULT_AA  VMW_PSP_FIXED  Supports non-specific active/active arrays

VMW_SATP_LOCAL       VMW_PSP_FIXED  Supports direct attached devices

[root@ESXi:~]

Below is how the LUN looked like before change

[root@ESXi:~] esxcli storage nmp device list

naa.60000970000192605421533033423833

   Device Display Name: EMC iSCSI Disk (naa.60000970000192605421533033423833)

   Storage Array Type: VMW_SATP_SYMM

   Storage Array Type Device Config: {action_OnRetryErrors=off}

   Path Selection Policy: VMW_PSP_RR

   Path Selection Policy Device Config: {policy=rr,iops=1000,bytes=10485760,useANO=0; lastPathIndex=2: NumIOsPending=0,numBytesPending=0}

   Path Selection Policy Device Custom Config:

   Working Paths: vmhba1:C0:T0:L3, vmhba1:C0:T1:L3, vmhba2:C0:T0:L3, vmhba2:C0:T1:L3

   Is USB: false

i have then decided to manually change this LUN to fixed using this script that i have created. Below is an excerept of the script using PowerCLI

$lunpath =(get-vmhosthba -VMhost $vmhost -Type IScsi | get-scsilun $lun | get-scsilunpath | Where-Object {$_.State -like "Active"} | Where-Object {$_.Name -match "$device"} | Select-Object -first 1).Name

if ($lunpath){

Get-VMHost $vmhost | Get-ScsiLun $lun| Set-Scsilun -MultiPathPolicy Fixed -PreferredPath $lunpath

Below is how the LUN looked like after change, Fixed with a preferred path

[root@ESXi:~] esxcli storage nmp device list

naa.60000970000192605421533033423833

   Device Display Name: EMC iSCSI Disk (naa.60000970000192605421533033423833)

   Storage Array Type: VMW_SATP_SYMM

   Storage Array Type Device Config: {action_OnRetryErrors=off}

   Path Selection Policy: VMW_PSP_FIXED

   Path Selection Policy Device Config: {preferred=vmhba1:C0:T1:L3;current=vmhba1:C0:T1:L3}

   Path Selection Policy Device Custom Config:

   Working Paths: vmhba1:C0:T1:L3

   Is USB: false

I have then decided to reboot the host to make sure that as soon as it comes up, the ESXi will set the LUN PSP to RoundRobin as illustrated by the default PSP in the SATP list, however,  i was surprised to find it still set to Fixed untill i manually changed it back to RoundRobin.

[root@ESXi:~]  esxcli storage nmp device list

naa.60000970000192605421533033423833

   Device Display Name: EMC iSCSI Disk (naa.60000970000192605421533033423833)

   Storage Array Type: VMW_SATP_SYMM

   Storage Array Type Device Config: {action_OnRetryErrors=off}

   Path Selection Policy: VMW_PSP_FIXED

   Path Selection Policy Device Config: {preferred=vmhba1:C0:T1:L3;current=vmhba1:C0:T1:L3}

   Path Selection Policy Device Custom Config:

   Working Paths: vmhba1:C0:T1:L3

   Is USB: false

Does anyone know why the PSP did not change to the default RR policy after reboot? is there anything wrong with my config? Thanks

I had an evaluation and it has ended or expired and I never was able to install etc..I had a catastrophic failure and have to get new hardware- how do I start over if I dont have any of the info or hardwaare?

Hi at all,

I'm trying repeatedly to delete name suffis dns on the host esxi. When I delete localdomain and for example add contoso.local, I press the button esc and I'm asked if to save change; I confirm with Y and when I return in custom suffis dns I find written localdomain, contoso.local. 

How can I delete localdomain suffis?

Hello,

All in title

I've installed a custom esxi on my hypervisor hardware 'cause one ethernet device was not supported, so i bring on it manually via mibs.

Is there a solution to update to latest upgrade on 6.0 branch or a possibility to upgrade to 6.5 ?

tks

Hi All,

We are trying to get lab environment to test GPU Roughcast to VM's working before going live.

I have built a HP DL380 G8 server which is fully up to date with bios patches/firmware etc. I have installed ESXI 6.5.0 as the host OS and under this we have a Windows VM running windows 10 fully up to date inc anniversary update.

I have created a pass-through for the Nvidia Quadro K2200 graphics card installed on the server and all is working fine from a VM point of view it sees the card all drives installed and works perfectly for our use.

The issue I have is if the VM runs for a few days and then we reboot (long term plan is scheduled reboots at night). The host goes into a complete panic and reboot's itself before the VM has even had a chance to shutdown obviously something is not right with the config.

I have done lots of research and have tried playing with various settings etc to try and make it stable for reboots but cannot seem to make it work. I have tried 6 initially and then went to 6.5 off the back of a forum post regarding instability on v6 which I did see during setup not just at reboot stage however 6.5 seems much better other than reboot.

Really after any advice from anyone which has tried to do the same on things for me to check.

Log files are not really giving me much around the reboot time it's like it simply stops dead.

I have passed the audio device through to the VM however on 6.5 it looks like you have to do this as it is a dependent (which was different from 6.0).

we are looking to try and use this in production come January next year so would love to iron out the kinks before we shell out for a live system as I cannot have it rebooting like this when live.

few forum posts suggest going back to 5.5 with the latest updates as this became alot more stable and win 10 is still supported as an OS.

I am willing to send log files etc to try and help solve the problem.

thanks

Lee

When HA failover occurs VM  gets power off and starts on other host in cluster, vm doesnot restart.

My current setup  DRS & HA both are enable.

It's been almost 3 years (1189 days to be exact) since kgottleib openly complained about the web client:

vSphere Web Client SUCKs so bad that my experience managing and supporting VMware has turn to SH**!

I was able to live with a slightly dysfunctional hybrid of old thick client, and the web UI, but as of 6.5 build 5969303, VMware has decided to fully deprecate the old thick client and it will NOT connect.

Despite promises to make the Web UI better, VMware seems incapable of actually delivering a reliable web product, and after 1189 days, 169365 views, and 213 Likes, I don't have any faith in VMware management to resolve this issue.

Instead, I'd like to ask the VMware community to petition Pat Gelsinger, CEO of VMware (actually - might as well petition the entire executive team and board), to Open Source the old thick client. I have far greater faith in the VMware community to create a reliable piece of software than this multi-billion dollar travesty. I'm sure it'd be quicker and cheaper to upload the source to GitHub than to continue this charade of broken promises. This would also free up VMware development and testing resources to focus on making their virtualization products great again - instead of trying to be a failed web company.

If you support this petition: Like this post or add your comments.

In a few weeks I'll hand deliver it to their Palo Alto office - that's how pissed off I am.

Regards,

Grant Henderson

Hello All,

After install ESXi 6.0 via "VMware-VMvisor-Installer-6.0.0.update02-4192238.x86_64-Dell_Customized-A04" on Dell PowerEdge R730, everything is okay !!!

But, if I try to install ESXi 6.5 via "VMware-VMvisor-Installer-6.5.0-4564106.x86_64-Dell_Customized-A00" on Dell PowerEdge R730, my vmnic0 and vmnic1 (Intel X710 DP 10Gb DA/SFP+) are not working !!!

Does anybody know the solution ?

Thanks for your reply.

[root@R730:~] esxcli network nic list

Name    PCI Device    Driver  Admin Status  Link Status  Speed  Duplex  MAC Address        MTU  Description                                          

------  ------------  ------  ------------  -----------  -----  ------  -----------------  ----  ---------------------------------------------------------

vmnic0  0000:01:00.0  i40en  Up            Up          10000  Full    f8:bc:12:05:85:d0  1500  Intel Corporation Ethernet Controller X710 for 10GbE SFP+

vmnic1  0000:01:00.1  i40en  Up            Up          10000  Full    f8:bc:12:05:85:d2  1500  Intel Corporation Ethernet Controller X710 for 10GbE SFP+

vmnic2  0000:0c:00.0  igbn    Up            Down            0  Half    f8:bc:12:05:85:f0  1500  Intel Corporation Gigabit 4P X710/I350 rNDC          

vmnic3  0000:0c:00.1  igbn    Up            Up            1000  Full    f8:bc:12:05:85:f1  1500  Intel Corporation Gigabit 4P X710/I350 rNDC          

vusb0  Pseudo        cdce    Up            Up            100  Full    18:fb:7b:5d:d5:ee  1500  DellTM iDRAC Virtual NIC USB Device              

[root@R730:~] esxcli network nic get -n vmnic0

  Advertised Auto Negotiation: false

  Advertised Link Modes: 1000BaseT/Full, 10000BaseT/Full, 10000BaseT/Full, 40000BaseCR4/Full, 40000BaseSR4/Full

  Auto Negotiation: false

  Cable Type:

  Current Message Level: -1

  Driver Info:

        Bus Info: 0000:01:00:0

        Driver: i40en

        Firmware Version: 5.04 0x800024bc 17.5.11

        Version: 1.1.0

  Link Detected: true

  Link Status: Up

  Name: vmnic0

  PHYAddress: 0

  Pause Autonegotiate: false

  Pause RX: false

  Pause TX: false

  Supported Ports:

  Supports Auto Negotiation: false

  Supports Pause: false

  Supports Wakeon: true

  Transceiver:

  Virtual Address: 00:50:56:52:57:61

  Wakeon: MagicPacket(tm)

Hi all!

Been struggling with updating my Hp Microservrer Gen8 with the VMware-ESXi-6.5.0-Update1-6765664-HPE-650.U1.9.6.5.1-Nov2017.iso.

It works well and the actual update starts and gets trough at least 20% before stopping with an error below. Can't seem to find any reliable info on it. ESXi is on an SD card in the machine, I mount the cd as a virtual drive in the ilo console.

Any ideas?

/Johan

In lab environment want to setup windows failover cluster in vsphere 6.5, need some articles or guidline.

I can't consolidate disks of virtual mashine after using of veeam backup software. Now I have following I/o error on 19% of consolidation. In log file I have following.

2018-03-29T02:57:07.685Z| vmx| I120: SnapshotVMX_Consolidate: Starting

2018-03-29T02:57:07.685Z| vmx| I120: SnapshotVMXConsolidateOnlineCB: nextState = 0 uid 0

2018-03-29T02:57:07.685Z| vmx| I120: Turning on snapshot info cache. VM=xyzDB.xyz.vmx.

2018-03-29T02:57:07.695Z| vmx| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003-delta.vmdk" : open successful (65557) size = 874046439424, hd = 0. Type 8

2018-03-29T02:57:07.695Z| vmx| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003-delta.vmdk" : closed.

2018-03-29T02:57:07.695Z| vmx| I120: SNAPSHOT: Turning on snapshot disk cache.

2018-03-29T02:57:07.696Z| vmx| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003-delta.vmdk" : open successful (21) size = 874046439424, hd = 0. Type 8

2018-03-29T02:57:07.696Z| vmx| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003-delta.vmdk" : closed.

2018-03-29T02:57:07.696Z| vmx| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000001-delta.vmdk" : open successful (21) size = 203125571584, hd = 0. Type 8

2018-03-29T02:57:07.696Z| vmx| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000001-delta.vmdk" : closed.

2018-03-29T02:57:07.696Z| vmx| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000002-delta.vmdk" : open successful (21) size = 38759186432, hd = 0. Type 8

2018-03-29T02:57:07.696Z| vmx| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000002-delta.vmdk" : closed.

2018-03-29T02:57:07.697Z| vmx| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-flat.vmdk" : open successful (21) size = 1999001092096, hd = 0. Type 3

2018-03-29T02:57:07.697Z| vmx| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-flat.vmdk" : closed.

2018-03-29T02:57:07.697Z| vmx| I120: Vix: [75543394 mainDispatch.c:3964]: VMAutomation_ReportPowerOpFinished: statevar=3, newAppState=1880, success=1 additionalError=0

2018-03-29T02:57:07.697Z| vcpu-0| I120: Destroying virtual dev for scsi0:0 vscsi=9177

2018-03-29T02:57:07.697Z| vcpu-0| I120: VMMon_VSCSIStopVports: No such target on adapter

2018-03-29T02:57:07.717Z| vcpu-0| I120: SnapshotVMXConsolidateOnlineCB: nextState = 1 uid 0

2018-03-29T02:57:07.717Z| vcpu-0| I120: Closing all the disks of the VM.

2018-03-29T02:57:07.717Z| vcpu-0| I120: Closing disk scsi0:0

2018-03-29T02:57:07.719Z| vcpu-0| I120: DISKLIB-CBT   : Shutting down change tracking for untracked fid 1019433325.

2018-03-29T02:57:07.719Z| vcpu-0| I120: DISKLIB-CBT   : Successfully disconnected CBT node.

2018-03-29T02:57:07.783Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003-delta.vmdk" : closed.

2018-03-29T02:57:07.795Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000001-delta.vmdk" : closed.

2018-03-29T02:57:07.803Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000002-delta.vmdk" : closed.

2018-03-29T02:57:07.811Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-flat.vmdk" : closed.

2018-03-29T02:57:07.811Z| vcpu-0| I120: SnapshotVMXConsolidateOnlineCB: nextState = 1 uid 0

2018-03-29T02:57:07.811Z| vcpu-0| I120: Checkpoint_Unstun: vm stopped for 114443 us

2018-03-29T02:57:07.812Z| vcpu-0| I120: SCSI: switching scsi0 to push completion mode

2018-03-29T02:57:07.813Z| vcpu-0| A115: ConfigDB: Setting scsi0:0.redo = ""

2018-03-29T02:57:07.813Z| vcpu-0| I120: DISK: OPEN scsi0:0 '/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003.vmdk' persistent R[]

2018-03-29T02:57:07.831Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003-delta.vmdk" : open successful (8) size = 874046439424, hd = 991842672. Type 8

2018-03-29T02:57:07.831Z| vcpu-0| I120: DISKLIB-DSCPTR: Opened [0]: "xyzDB.xyz-000003-delta.vmdk" (0x8)

2018-03-29T02:57:07.831Z| vcpu-0| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003.vmdk' (0x8): vmfsSparse, 3904299008 sectors / 1.8 TB.

2018-03-29T02:57:07.831Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 1, numSubChains = 1

2018-03-29T02:57:07.831Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 991842672, extentType = 0

2018-03-29T02:57:07.831Z| vcpu-0| I120: DISKLIB-LIB   : Resuming change tracking.

2018-03-29T02:57:07.845Z| vcpu-0| I120: DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 991842672.

2018-03-29T02:57:07.845Z| vcpu-0| I120: DISKLIB-CBT   : Successfuly created cbt node 39ca5171-cbt.

2018-03-29T02:57:07.845Z| vcpu-0| I120: DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/39ca5171-cbt

2018-03-29T02:57:07.845Z| vcpu-0| I120: DISKLIB-LIB   : Opened "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003.vmdk" (flags 0x8, type vmfsSparse).

2018-03-29T02:57:07.856Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000001-delta.vmdk" : open successful (8) size = 203125571584, hd = 962089332. Type 8

2018-03-29T02:57:07.856Z| vcpu-0| I120: DISKLIB-DSCPTR: Opened [0]: "xyzDB.xyz-000001-delta.vmdk" (0x8)

2018-03-29T02:57:07.856Z| vcpu-0| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000001.vmdk' (0x8): vmfsSparse, 3904299008 sectors / 1.8 TB.

2018-03-29T02:57:07.856Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 1, numSubChains = 1

2018-03-29T02:57:07.856Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 962089332, extentType = 0

2018-03-29T02:57:07.857Z| vcpu-0| I120: DISKLIB-LIB   : Resuming change tracking.

2018-03-29T02:57:07.864Z| vcpu-0| I120: DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 962089332.

2018-03-29T02:57:07.864Z| vcpu-0| I120: DISKLIB-CBT   : Successfuly created cbt node 38835175-cbt.

2018-03-29T02:57:07.864Z| vcpu-0| I120: DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/38835175-cbt

2018-03-29T02:57:07.864Z| vcpu-0| I120: DISKLIB-LIB   : Opened "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000001.vmdk" (flags 0x8, type vmfsSparse).

2018-03-29T02:57:07.866Z| vcpu-0| I120: DISKLIB-CBT   : Shutting down change tracking for untracked fid 991842672.

2018-03-29T02:57:07.866Z| vcpu-0| I120: DISKLIB-CBT   : Successfully disconnected CBT node.

2018-03-29T02:57:07.868Z| vcpu-0| I120: DISKLIB-CBT   : Shutting down change tracking for untracked fid 962089332.

2018-03-29T02:57:07.868Z| vcpu-0| I120: DISKLIB-CBT   : Successfully disconnected CBT node.

2018-03-29T02:57:07.885Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 2, numSubChains = 1

2018-03-29T02:57:07.885Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 962089332, extentType = 0

2018-03-29T02:57:07.885Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(1) fid = 991842672, extentType = 0

2018-03-29T02:57:07.885Z| vcpu-0| I120: DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 991842672.

2018-03-29T02:57:07.885Z| vcpu-0| I120: DISKLIB-CBT   : Successfuly created cbt node 38855175-cbt.

2018-03-29T02:57:07.886Z| vcpu-0| I120: DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/38855175-cbt

2018-03-29T02:57:07.916Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000002-delta.vmdk" : open successful (8) size = 38759186432, hd = 1004491128. Type 8

2018-03-29T02:57:07.916Z| vcpu-0| I120: DISKLIB-DSCPTR: Opened [0]: "xyzDB.xyz-000002-delta.vmdk" (0x8)

2018-03-29T02:57:07.916Z| vcpu-0| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000002.vmdk' (0x8): vmfsSparse, 3904299008 sectors / 1.8 TB.

2018-03-29T02:57:07.916Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 1, numSubChains = 1

2018-03-29T02:57:07.916Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 1004491128, extentType = 0

2018-03-29T02:57:07.917Z| vcpu-0| I120: DISKLIB-LIB   : Resuming change tracking.

2018-03-29T02:57:07.924Z| vcpu-0| I120: DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 1004491128.

2018-03-29T02:57:07.924Z| vcpu-0| I120: DISKLIB-CBT   : Successfuly created cbt node 3ac15179-cbt.

2018-03-29T02:57:07.924Z| vcpu-0| I120: DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/3ac15179-cbt

2018-03-29T02:57:07.924Z| vcpu-0| I120: DISKLIB-LIB   : Opened "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000002.vmdk" (flags 0x8, type vmfsSparse).

2018-03-29T02:57:07.926Z| vcpu-0| I120: DISKLIB-CBT   : Shutting down change tracking for untracked fid 991842672.

2018-03-29T02:57:07.926Z| vcpu-0| I120: DISKLIB-CBT   : Successfully disconnected CBT node.

2018-03-29T02:57:07.928Z| vcpu-0| I120: DISKLIB-CBT   : Shutting down change tracking for untracked fid 1004491128.

2018-03-29T02:57:07.928Z| vcpu-0| I120: DISKLIB-CBT   : Successfully disconnected CBT node.

2018-03-29T02:57:07.945Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 3, numSubChains = 1

2018-03-29T02:57:07.945Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 1004491128, extentType = 0

2018-03-29T02:57:07.945Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(1) fid = 962089332, extentType = 0

2018-03-29T02:57:07.945Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(2) fid = 991842672, extentType = 0

2018-03-29T02:57:07.946Z| vcpu-0| I120: DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 991842672.

2018-03-29T02:57:07.946Z| vcpu-0| I120: DISKLIB-CBT   : Successfuly created cbt node 3ac35179-cbt.

2018-03-29T02:57:07.946Z| vcpu-0| I120: DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/3ac35179-cbt

2018-03-29T02:57:07.986Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-flat.vmdk" : open successful (522) size = 1999001092096, hd = 988828027. Type 3

2018-03-29T02:57:07.986Z| vcpu-0| I120: DISKLIB-DSCPTR: Opened [0]: "xyzDB.xyz-flat.vmdk" (0x20a)

2018-03-29T02:57:07.986Z| vcpu-0| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz.vmdk' (0x20a): vmfs, 3904299008 sectors / 1.8 TB.

2018-03-29T02:57:07.986Z| vcpu-0| I120: DISKLIB-LIB   : Resuming change tracking.

2018-03-29T02:57:08.014Z| vcpu-0| I120: DISKLIB-CTK   : Could not open change tracking file "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-ctk.vmdk": Change tracking invalid or disk in use.

2018-03-29T02:57:08.014Z| vcpu-0| I120: DISKLIB-CTK   : Re-initializing change tracking.

2018-03-29T02:57:08.014Z| vcpu-0| I120: DISKLIB-CTK   : Auto blocksize for size 3904299008 is 2048.

2018-03-29T02:57:08.015Z| vcpu-0| I120: OBJLIB-FILEBE : Error creating file '/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-ctk.vmdk': 3 (The file already exists).

2018-03-29T02:57:08.015Z| vcpu-0| I120: DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 988828027.

2018-03-29T02:57:08.015Z| vcpu-0| I120: DISKLIB-CBT   : Successfuly created cbt node 3af0517b-cbt.

2018-03-29T02:57:08.015Z| vcpu-0| I120: DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/3af0517b-cbt

2018-03-29T02:57:08.015Z| vcpu-0| I120: DISKLIB-LIB   : Opened "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz.vmdk" (flags 0x20a, type vmfs).

2018-03-29T02:57:08.017Z| vcpu-0| I120: DISKLIB-CBT   : Shutting down change tracking for untracked fid 991842672.

2018-03-29T02:57:08.017Z| vcpu-0| I120: DISKLIB-CBT   : Successfully disconnected CBT node.

2018-03-29T02:57:08.019Z| vcpu-0| I120: DISKLIB-CBT   : Shutting down change tracking for untracked fid 988828027.

2018-03-29T02:57:08.019Z| vcpu-0| I120: DISKLIB-CBT   : Successfully disconnected CBT node.

2018-03-29T02:57:08.035Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 4, numSubChains = 1

2018-03-29T02:57:08.036Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 988828027, extentType = 2

2018-03-29T02:57:08.036Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(1) fid = 1004491128, extentType = 0

2018-03-29T02:57:08.036Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(2) fid = 962089332, extentType = 0

2018-03-29T02:57:08.036Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(3) fid = 991842672, extentType = 0

2018-03-29T02:57:08.054Z| vcpu-0| I120: DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 991842672.

2018-03-29T02:57:08.054Z| vcpu-0| I120: DISKLIB-CBT   : Successfuly created cbt node 3ac55179-cbt.

2018-03-29T02:57:08.054Z| vcpu-0| I120: DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/3ac55179-cbt

2018-03-29T02:57:08.055Z| vcpu-0| I120: DISK: Disk '/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003.vmdk' has UUID '60 00 c2 9f cd c1 d5 72-86 e5 29 ab e3 15 c6 f4'

2018-03-29T02:57:08.055Z| vcpu-0| I120: DISK: OPEN '/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003.vmdk' Geo (243031/255/63) BIOS Geo (0/0/0)

2018-03-29T02:57:08.055Z| vcpu-0| I120: Creating virtual dev for scsi0:0

2018-03-29T02:57:08.055Z| vcpu-0| I120: DumpDiskInfo: scsi0:0 createType=11, capacity = 3904299008, numLinks = 4, allocationType = 0

2018-03-29T02:57:08.055Z| vcpu-0| I120: SCSIDiskESXPopulateVDevDesc: Using FS backend

2018-03-29T02:57:08.055Z| vcpu-0| I120: DISKUTIL: scsi0:0 : geometry=243031/255/63

2018-03-29T02:57:08.057Z| vcpu-0| I120: SnapshotVMXConsolidateOnlineCB: nextState = 2 uid 0

2018-03-29T02:57:08.057Z| SnapshotVMXCombiner| I120: VTHREAD start thread 14 "SnapshotVMXCombiner" pid 75544762

2018-03-29T02:57:08.057Z| SnapshotVMXCombiner| I120: SnapshotVMXConsolidateOnlineCB: nextState = 3 uid 0

2018-03-29T02:57:08.057Z| SnapshotVMXCombiner| I120: SnapshotVMXConsolidateOnlineCB: Starting combine of scsi0:0 /vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003.vmdk. 3 links, starting from 1

2018-03-29T02:57:08.057Z| vcpu-0| I120: SnapshotVMXConsolidateOnlineCB: Created thread 14 for scsi0:0

2018-03-29T02:57:08.127Z| vcpu-6| I120: HBACommon: First write on scsi0:0.fileName='/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003.vmdk'

2018-03-29T02:57:08.127Z| vcpu-6| I120: DDB: "longContentID" = "ad5119fec08f0525a6c2ee87761ff5e5" (was "d1c3090360d1f9a387a1358d41957106")

2018-03-29T02:57:08.261Z| vcpu-6| I120: DISKLIB-CHAIN : DiskChainUpdateContentID: old=0x41957106, new=0x761ff5e5 (ad5119fec08f0525a6c2ee87761ff5e5)

2018-03-29T02:57:08.262Z| SnapshotVMXCombiner| I120: DISKLIB-LIB   : Upward Combine 3 links at 1. Need 1906396 MB of free space (2805172 MB available)

2018-03-29T02:57:08.298Z| SnapshotVMXCombiner| I120: DDB: "longContentID" = "f28f917eda5233e21d1803a81b19952e" (was "e3fb3a5abe350337d652bf02e93cac04")

2018-03-29T02:57:08.344Z| SnapshotVMXCombiner| I120: DDB: "longContentID" = "e3fb3a5abe350337d652bf02e93cac04" (was "f28f917eda5233e21d1803a81b19952e")

2018-03-29T03:37:28.739Z| SnapshotVMXCombiner| I120: OBJLIB-FILEBE : FileBEIoctl: ioctl operation failed on '/vmfs/devices/deltadisks/17ebc38d-xyzDB.xyz-000003-delta.vmdk' : Input/output error (327682)

2018-03-29T03:37:28.739Z| SnapshotVMXCombiner| I120: DISKLIB-VMFS_SPARSE : VmfsSparseExtentCombine: failed: for 2 level and start 615430 Input/output error.

2018-03-29T03:37:28.739Z| SnapshotVMXCombiner| I120: DISKLIB-CTK   : End Combine

2018-03-29T03:37:28.739Z| SnapshotVMXCombiner| I120: DISKLIB-CTK   : Attempting unlink of (null)

2018-03-29T03:37:28.739Z| SnapshotVMXCombiner| I120: SnapshotVMXCombineFinalCb: Done with combine of 3 links, starting from 1 in 2420682332 usec with error 0x50009: Input/output error

2018-03-29T03:37:31.752Z| vcpu-0| I120: Destroying virtual dev for scsi0:0 vscsi=9178

2018-03-29T03:37:31.752Z| vcpu-0| I120: VMMon_VSCSIStopVports: No such target on adapter

2018-03-29T03:37:31.809Z| vcpu-0| I120: SnapshotVMXConsolidateOnlineCB: nextState = 4 uid 0

2018-03-29T03:37:31.809Z| vcpu-0| I120: Closing disk scsi0:0

2018-03-29T03:37:31.811Z| vcpu-0| I120: DISKLIB-CBT   : Shutting down change tracking for untracked fid 991842672.

2018-03-29T03:37:31.812Z| vcpu-0| I120: DISKLIB-CBT   : Successfully disconnected CBT node.

2018-03-29T03:37:31.927Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003-delta.vmdk" : closed.

2018-03-29T03:37:31.928Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000001-delta.vmdk" : closed.

2018-03-29T03:37:31.928Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000002-delta.vmdk" : closed.

2018-03-29T03:37:31.928Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-flat.vmdk" : closed.

2018-03-29T03:37:31.928Z| vcpu-0| I120: SnapshotVMXNeedConsolidateIteration : Invalid consolidateRate (4294967296.000000 MBps), not branching any more

2018-03-29T03:37:31.928Z| vcpu-0| I120: SnapshotVMXNeedConsolidateIteration: Another iteration of helper branch is not needed.

2018-03-29T03:37:31.939Z| vcpu-0| I120: Checkpoint_Unstun: vm stopped for 3199928 us

2018-03-29T03:37:31.940Z| vcpu-0| I120: SCSI: switching scsi0 to push completion mode

2018-03-29T03:37:31.941Z| vcpu-0| A115: ConfigDB: Setting scsi0:0.redo = ""

2018-03-29T03:37:31.941Z| vcpu-0| I120: DISK: OPEN scsi0:0 '/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003.vmdk' persistent R[]

2018-03-29T03:37:31.967Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003-delta.vmdk" : open successful (10) size = 874063216640, hd = 988959099. Type 8

2018-03-29T03:37:31.967Z| vcpu-0| I120: DISKLIB-DSCPTR: Opened [0]: "xyzDB.xyz-000003-delta.vmdk" (0xa)

2018-03-29T03:37:31.967Z| vcpu-0| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003.vmdk' (0xa): vmfsSparse, 3904299008 sectors / 1.8 TB.

2018-03-29T03:37:31.984Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000001-delta.vmdk" : open successful (14) size = 203125571584, hd = 965431677. Type 8

2018-03-29T03:37:31.984Z| vcpu-0| I120: DISKLIB-DSCPTR: Opened [0]: "xyzDB.xyz-000001-delta.vmdk" (0xe)

2018-03-29T03:37:31.984Z| vcpu-0| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000001.vmdk' (0xe): vmfsSparse, 3904299008 sectors / 1.8 TB.

2018-03-29T03:37:32.019Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000002-delta.vmdk" : open successful (14) size = 38759186432, hd = 967463294. Type 8

2018-03-29T03:37:32.019Z| vcpu-0| I120: DISKLIB-DSCPTR: Opened [0]: "xyzDB.xyz-000002-delta.vmdk" (0xe)

2018-03-29T03:37:32.019Z| vcpu-0| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000002.vmdk' (0xe): vmfsSparse, 3904299008 sectors / 1.8 TB.

2018-03-29T03:37:32.048Z| vcpu-0| I120: DISKLIB-VMFS  : "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-flat.vmdk" : open successful (14) size = 1999001092096, hd = 976966015. Type 3

2018-03-29T03:37:32.048Z| vcpu-0| I120: DISKLIB-DSCPTR: Opened [0]: "xyzDB.xyz-flat.vmdk" (0xe)

2018-03-29T03:37:32.048Z| vcpu-0| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz.vmdk' (0xe): vmfs, 3904299008 sectors / 1.8 TB.

2018-03-29T03:37:32.048Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 4, numSubChains = 1

2018-03-29T03:37:32.048Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 976966015, extentType = 2

2018-03-29T03:37:32.048Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(1) fid = 967463294, extentType = 0

2018-03-29T03:37:32.048Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(2) fid = 965431677, extentType = 0

2018-03-29T03:37:32.048Z| vcpu-0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(3) fid = 988959099, extentType = 0

2018-03-29T03:37:32.058Z| vcpu-0| I120: DISKLIB-LIB   : Resuming change tracking.

2018-03-29T03:37:32.093Z| vcpu-0| I120: DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 988959099.

2018-03-29T03:37:32.093Z| vcpu-0| I120: DISKLIB-CBT   : Successfuly created cbt node 3a715180-cbt.

2018-03-29T03:37:32.093Z| vcpu-0| I120: DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/3a715180-cbt

2018-03-29T03:37:32.093Z| vcpu-0| I120: DISKLIB-LIB   : Opened "/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003.vmdk" (flags 0xa, type vmfs).

2018-03-29T03:37:32.093Z| vcpu-0| I120: DISK: Disk '/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003.vmdk' has UUID '60 00 c2 9f cd c1 d5 72-86 e5 29 ab e3 15 c6 f4'

2018-03-29T03:37:32.093Z| vcpu-0| I120: DISK: OPEN '/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003.vmdk' Geo (243031/255/63) BIOS Geo (0/0/0)

2018-03-29T03:37:32.094Z| vcpu-0| I120: Creating virtual dev for scsi0:0

2018-03-29T03:37:32.094Z| vcpu-0| I120: DumpDiskInfo: scsi0:0 createType=11, capacity = 3904299008, numLinks = 4, allocationType = 0

2018-03-29T03:37:32.094Z| vcpu-0| I120: SCSIDiskESXPopulateVDevDesc: Using FS backend

2018-03-29T03:37:32.094Z| vcpu-0| I120: DISKUTIL: scsi0:0 : geometry=243031/255/63

2018-03-29T03:37:32.095Z| vcpu-0| I120: SnapshotVMXConsolidateOnlineCB: nextState = 6 uid 0

2018-03-29T03:37:32.095Z| vcpu-0| I120: Vix: [75477874 mainDispatch.c:3964]: VMAutomation_ReportPowerOpFinished: statevar=3, newAppState=1881, success=1 additionalError=0

2018-03-29T03:37:32.096Z| vcpu-0| I120: Locale_Errno2LocalString: "C" locale found. LC_ALL=(null), LANG=C

2018-03-29T03:37:32.096Z| vcpu-0| I120: Locale_Errno2LocalString: locale(LC_ALL)=C locale(LC_MESSAGES)=C

2018-03-29T03:37:32.096Z| vcpu-0| I120: SnapshotVMXConsolidateOnlineCB: Destroying thread 14

2018-03-29T03:37:32.096Z| vcpu-0| I120: Turning off snapshot info cache.

2018-03-29T03:37:32.096Z| vcpu-0| I120: Turning off snapshot disk cache.

2018-03-29T03:37:32.096Z| vcpu-0| I120: SnapshotVMXConsolidateOnlineCB: Done with consolidate

2018-03-29T03:37:32.120Z| vcpu-5| I120: HBACommon: First write on scsi0:0.fileName='/vmfs/volumes/586e1ffe-3ca22b38-d90e-0cc47a7fdf12/xyzDB.xyz/xyzDB.xyz-000003.vmdk'

2018-03-29T03:37:32.120Z| vcpu-5| I120: DDB: "longContentID" = "1bcfb84029cef153c7ad4d5df8be99d5" (was "ad5119fec08f0525a6c2ee87761ff5e5")

2018-03-29T03:37:32.181Z| vcpu-5| I120: DISKLIB-CHAIN : DiskChainUpdateContentID: old=0x761ff5e5, new=0xf8be99d5 (1bcfb84029cef153c7ad4d5df8be99d5)

2018-03-29T03:38:32.183Z| vmx| I120: GuestRpcSendTimedOut: message to toolbox-dnd timed out.

Case Scenario:

- A Virtual Machine (VM) currently running on EXSi fails (e.g. system hacked, internal corruption, use your imagination...)

- A perfect backup of said VM is standing by in an external USB drive, ready to replace the fallen one.

Fact:

- Copying this VM (easily 8-10 GB) from a client PC would take ages, even if the client is in the LAN.

Question:

Is there a way to plug this USB drive to one of the USB ports in the host and transfer those files to the datastore directly over USB?

Brand new R330

PERC H730

5 X Disk SAS 931GB RAID 5 (Datastore1)

32GB USB Internal (ESXi)

32GB RAM

Very Typical small business setup.

Fresh ESXi 6.5.0 installed yesterday to internal USB drive, setup portal, login to portal locally using Edge, Chome, FF, IE, tried them all, edge works best. Added vm's, added new Datastore1-full partition, created new ISO folder in Datastore1, upload button, browse, choose Windows Server 2012R2 STD.ISO,  the upload gets to about 78% then hangs forever. Cannot ever finish any ISO, tried other ISO, and they all hang after a certain point.

Any ideas?

Tried different folders, sub folders, they all do the same thing. Smaller files work fine, I think it only happens when the files are larger than 4GB.

I added a screenshot, showing that vsphere is still "running" in the background at 79%, but the window opened thinks the upload finished and is only 4GB. This ISO is 5.6GB.

Hello,

Im really need your help with that issue...

Good afternoon.  This is probably an easy fix, so here it goes.  I have a requirement to have separate VLANS in my ESXi 6.5 environment that have to communicate with separate PCs on the outside.  I have only 1 NIC on the server so I've created 3 VLANS 101, 102, 103 inside the ESXI.  The problem I'm running into is that I can't seem to get the virtual machines in the VLANS on the ESXi to talk to the physical machines on the outside of the switch.  I've researched the different types of communications such as virtual switch tagging inside the ESXI, External Switch Tagging on the switch but both options don't seem to work.  The only reason I was looking at VST vs EST was because of only having 1 NIC on the server.  Any help would be appreciated.  Thanks.

I've been experimenting with FreeNAS and installed it in a VM along with a HBA and a Mellanox MNPA19-XTR (Connectex-2) 10 GB card both in passthrough mode.

I can see the HBA, but not the Mellanox card.  If I don't passthrough I can configure the NIC as a VM device, but I'm not getting good throughput so I want to passthrough.

Also, if I have it in passthrough I can see and use it in a Win 10 VM just fine.

Is there something special about FreeNAS for FreeBSD on which it is built?

Thanks.

Roveer

All,

We have always increased the number of virtual sockets instead of cores per socket. That has been the recommendation. I came across the following article which states to do the apposite.

Has VMware changed their recommendations in 6.5? That is what it seems like.

https://blogs.vmware.com/performance/2017/03/virtual-machine-vcpu-and-vnuma-rightsizing-rules-of-thumb.html#comment-112552

Dear All,

We bought a Supermicro E200-9B Server with the idea
to install ESXi 6.5 in a lab environment. We know this server is not on the HCL
of Vmware. However on the internet there are several blogs or discussion that
it should work.

Unfortunately we have an issue. The Installation
starts from the USB stick and get stuck at "relocating modules and
starting up the kernel". The message on screen before says "....firmware
services".

Various indication on the Internet says it is a
graphic issues. Indeed I think the bootloader is nearly finished before it
changes the screen in another mode. First thing we tried SHIFT+O
ignoreHeadless=TRUE

I tried several things to change settings in the
Bios and even removed the m.sata HD and memory. Installed ESXi 6.0. Nothing
helped.

Motherboard is: X11SBA-LN4F with Bios version 1.1
dated 01/23/2018

So I'm reaching out to you if you have another idea or experience with this model? I read there is a possiblitiy with serial cable to log the loader process. It seems quite complicated since there are only USB ports available.

Thanks,

Edy

Hi,

we are going to install some Dell T330 which have internal harddisk and a SD Card module. Our goal is to install ESXi6.5 on the SD Card with a pxe installation and a ks.cfg file.

One big problem is to define the target installation disk in the kickstart file:

The "install --firstdisk=local --overwritevmfs" option in the ks file does not work since firstdisk=local is interprated as the local harddisk.

I also tried "install --firstdisk=usb-storage --overwritevmfs", but this one fails with the error, that such disk does not exist.

So what would be the right parameter for the "install..." option?

I did a manual install and took a screenshot that shows how esx intereprets the storage.

See the screenshot attached.

Any help would be appreciated,

Chris

any idea why?