Hello,
I'm struggling the last week with a problem that I can't create a Windows VM which runs Docker Linux Container.
I tried to install Windows 10 Enterprise (Build 1903) and also Windows Server 2019 Standard. But without success. On Windows 10 the Hyper V instance will not start and on Windows Server 2019 there will pull the image but then nothing happends...
Anyone have a running setup?
Thanks
I checked the video on you tube and followed the same instruction and also tried on different PC but the error is same.
I have ESXI 6.5 image on my Laptop folder which has four files *.ovf , *.vmdk,*.nvram, *.mf and when I try to export / import it , I get transfer failed error message after it starts writing to esxi host.
I keep getting the error below when i run my workflow :
[2019-06-23 12:29:13.783] [I] 1 match uuid: 50320c66-3431-ed1d-68ad-f96256cf4290
[2019-06-23 12:29:13.786] [I] Resolved vCAC VM: vROps-ap1
[2019-06-23 12:29:13.841] [E] Workflow execution stack:
***
item: 'Get Info/Shutdown (UC1)/item3', state: 'failed', business state: 'null', exception: 'TypeError: Cannot read property "virtualMachineID" from null (Dynamic Script Module name : getPropertiesFromVirtualMachine#1)'
workflow: 'Get Info/Shutdown (UC1)' (fd7316ef-7b9b-483a-b5df-5d5d07e45c1b)
| 'attribute': name=VMName type=string value=
| 'attribute': name=VMAddress type=string value=
| 'attribute': name=VMOwner type=string value=
| 'attribute': name=VMBsgroup type=string value=
| 'attribute': name=VMReservation type=string value=
| 'attribute': name=actionResult type=vCAC:VirtualMachine value=__NULL__
| 'attribute': name=vCACIaaSHost type=vCAC:VCACHost value=__NULL__
| 'attribute': name=errorCode type=string value=TypeError: Cannot read property "virtualMachineID" from null (Dynamic Script Module name : getPropertiesFromVirtualMachine#1)
| 'input': name=vCenterVm type=VC:VirtualMachine value=dunes://service.dunes.ch/CustomSDKObject?id='10.20.20.50%2Cid:vm-32'&dunesName='VC:VirtualMachine'
| 'output': name=actionResult1 type=vCAC:VirtualMachine value=dunes://service.dunes.ch/CustomSDKObject?id='31b63e72-1b20-4cc6-a61b-5af4db5f8ee3/ba9a8a14-17ae-45f4-abbe-dca45f3fc0d0'&dunesName='vCAC:VirtualMachine'
*** End of execution stack.
Flow chart is as below:
Code from QCgetvCACVmFromvC action:
//Auto generated script, cannot be modified !
actionResult = System.getModule("org.company.mymodule").QCgetvCACVmFromvCenterVmUuid(vCenterVm) ;
Code from show info:
//Gets the IP Address Of the VM
vCACVmExtendedProps = System.getModule("com.vmware.library.vcac").getPropertiesFromVirtualMachine(vCACIaaSHost,vCACVM);
VMAddress = vCACVmExtendedProps.get("__datacollected_ipaddress");
//Gets the name of VM
VMHostname = vCACVM.vmDNSName;
//Gets the owner of VM
VMOwner = vCACCAFEFilterParam.substringOf("owners/ref",vCACCAFEFilterParam.string("user@domain.com"));
//Gets the Business Group of the VM
var VMBsgroup = System.getContext().getParameter("_asd_subTenantref")
//Gets the Reservation of the VM
var id = virtualMachine.getEntity().getProperty("HostReservationID");
var entity;
var idprop = new Properties( {
"HostReservationID" : id
});
if (!id || id == "") throw "Error getting Reservation ID of VM.";
if (host != null) {
entity = vCACEntityManager.readModelEntity(host.id, "ManagementModelEntities.svc", "HostReservations", idprop, null);
} else {
var hosts = Server.findAllForType("vCAC:VCACHost");
System.debug("hosts: " + hosts);
for each (var host in hosts) {
try {
entity = vCACEntityManager.readModelEntity(host.id, "ManagementModelEntities.svc", "HostReservations", idprop, null);
} catch (e) {
throw "Error reading model entity.";
}
}
}
VMReservation = entity.getInventoryObject();
//Return Values
Server.log("Hostname : " + VMHostname);
Server.log("IP Address : " + VMAddress);
Server.log("Owner : " + VMOwner);
System.log("Business Group name: " + VMBsgroup);
System.log("Reservation of VM: " + VMReservation);
I'm not sure what the issue might be?
I am hoping to upgrade my VCSA appliance from 6.0 U3H to 6.7 but with no support for the direct upgrade currently i'm not sure what the best option is to be,
1. Wait for another update for 6.0 that will allow a direct upgrade (If one is due?)
2. Build a new VCSA 6.7 and migrate across (If this is the only option has anyone done this and how did they go about migrating)
Hello,
We are currently using VMware Horizon Client, version 5.0.0 build-12606690. Host OS Version: Windows 10 Enterprise 10.0.17763
Some of our colleagues are experiencing difficulties when it comes to Chrome and some standard Windows functions.
When the VMware client is hosted on a laptop, it works perfectly fine, but when hosted on a thin or thick client (a stationary PC) Google Chrome crashes quite often. When this problem occurs, our quick fix is to download a fresh/new version of Chrome. This solution last for about two days before the application once more won't open at all. Is there any other solution than downloading Chrome over and over again each time this happens?
We also experience problems with some standard Windows functions like using the Windows(flag) button and the search bar. Neither of the two will open, which brings us to the point where we have to detach the existing VMware machine and give out a new one. The way we do this now is just silly and complicated. Is there any other way to permanently solve these problems?
Best Regards.
vSAN Health Statusスクリプトとは、vSANの健全性サービスの状態をCLIで出力させるスクリプトです。
vSAN健全性の項目でアラートが出ている場合などにおいて、取得・解析が有効なログとなります。
1. sshでvCenter Server Applianceへログイン(root)する。
2. デフォルト設定では、Appliance Shell にログインするため、BASHに遷移する。
Command> shell.set --enabled True <---BASHを有効にする
Command> shell <---BASHに遷移する
Shell access is granted to root
root@vc [ ~ ]#
ESXi6.5(VxRail 4.5)の場合は、rootユーザのBASHはデフォルトで有効なため、"shell.set --enabled True"の実行は不要
デフォルトのシェルをBASHにしたい場合は下記をご参照ください。
https://kb.vmware.com/s/article/2100508
3. 下記コマンドを実行
# python /usr/lib/vmware-vpx/vsan-health/vsan-vc-health-status.py > /tmp/vsan-vc-health-status.txt
4. 生成されたファイル(/tmp/vsan-vc-health-status.txt)をファイル転送サービス(WinSCPなど)で取得
デフォルト設定では、VCSAにログインするとAppliance Shellと呼ばれるシェルにログインする仕様になっています。
Appliance ShellはSFTPやSCPに対応していないため、WinSCP等のファイル転送ソフトでVCSAにログインしてもログを作業端末にダウンロードすることができません。
クライアント側からファイル転送ソフトやscpコマンドを使用してファイルを受信したい場合は、
下記のKBを実施してVCSAのデフォルトシェルをBashに変更する必要があります。
WinSCP を使用してファイルを vCenter Server Appliance にアップロードするとエラーが発生する (2147941)
https://kb.vmware.com/s/article/2147941
または、VCSAのローカル側からsftpコマンドやscpコマンドを使用して、リモートホストにファイルを送信する方法もあります。
こちらの手順では、コマンドはVCSAのBash Shell上で発行されるため、デフォルトシェルを変更する必要はありません。
リモートホストがSFTPやSCPに対応している必要がありますが、一旦リモートホストにログを転送すれば、WinSCPでファイルをWindows端末などにダウンロードすることができます。
以下の手順でログを出力させることも可能です。
3'. ターミナルソフトウェアのロギング機能を使用する
4'. 下記コマンドを実行
# python /usr/lib/vmware-vpx/vsan-health/vsan-vc-health-status.py
ターミナルソフトウェアのロギング機能で生成されたログファイルを送付してください。
###参考情報########
vSAN 健全性サービス - クラスタの健全性 - vSAN 健全性サービスの最新状態 (2148709)
https://kb.vmware.com/s/article/2148709
vSAN Health Service - Cluster Health - vSAN Health Service up-do-date (2107705)
Hello,
Traffic filtering and marking not visible on port group level even in flash web client (vSphere 6.5 )
Hello,
I'm looking for way how to schedule a VM re-config workflow on VM power cycle. Is there a way how to do this using vRO or is anybody aware of other option? The goal is to apply the specific VM configuration change (or run PowerCLI script to do the same) anytime when user decides to reboot his/her VM.
Thanks.
PCOIP session freezing intermittently for users.
A closer look into the PCOIP server logs revealed the error code pointing to the error "PCoIP session terminated due to login from an alternate location". Any ideas on resolution.
Hi All
Thought I'd have a dabble in the ESXi world, have installed 5.5 U3 on a Dell Poweredge T110 which (currently) only has one integrated NIC.
I've tried various OS installs and what seems to be happening is that any OS install that has the option to set a static IP at installation becomes immediatly available to the rest of the network (Ubuntu Server for instance), whereas any OS that initially gets it's IP details from DHCP is NOT visible to the rest of the network.
Update: Just logged onto the Ubuntu server VM and it CAN ping the other VMs on the host......but all other VMs bar the ubuntu server are NOT visible to the rest of the network
I'm stumped and would welcome any suggestions.
Thanks in advance.
Hi Everyone,
I need to create desktop pool of windows 10 with build 1803.
from this article VMware Knowledge Base it seems that I need Horizon Agent with version 7.3.2 or newer.
My question is if connection server 7.0.2 can manage desktop clones with newer Horizon Agent version ?
is there any compatibility matrix for that ?
I have a dell SERVER and I just got PSOD. I need help to diagnose the issue.
Following are the details from the log file.
2019-06-22T16:03:53.820Z cpu5:2097701)@BlueScreen: #PF Exception 14 in world 2097701:tq:tcpip4 IP 0x418037903c05 addr 0x0
PTEs:0x0;
2019-06-22T16:03:53.820Z cpu5:2097701)Code start: 0x418036c00000 VMK uptime: 45:20:42:53.329
2019-06-22T16:03:53.821Z cpu5:2097701)0x451a0b81bb80:[0x418037903c05]flowtable_purge@(tcpip4)#<None>+0x31 stack: 0x418036d44250
2019-06-22T16:03:53.821Z cpu5:2097701)0x451a0b81bc20:[0x418037905d7a]flowtable_route_flush@(tcpip4)#<None>+0x27 stack: 0x430a1e72af60
2019-06-22T16:03:53.821Z cpu5:2097701)0x451a0b81bc40:[0x418037860a33]rtrequest1_fib@(tcpip4)#<None>+0x54c stack: 0x417fcca1b620
2019-06-22T16:03:53.821Z cpu5:2097701)0x451a0b81bd20:[0x4180378614d8]rtrequest_fib@(tcpip4)#<None>+0x81 stack: 0x4004001741400000
2019-06-22T16:03:53.822Z cpu5:2097701)0x451a0b81bdc0:[0x418037880a88]in_rtqkill@(tcpip4)#<None>+0x5d stack: 0x0
2019-06-22T16:03:53.822Z cpu5:2097701)0x451a0b81be10:[0x41803785e084]rn_walktree@(tcpip4)#<None>+0x7d stack: 0x0
2019-06-22T16:03:53.822Z cpu5:2097701)0x451a0b81be40:[0x41803788062b]in_rtqtimo@(tcpip4)#<None>+0x140 stack: 0x417fcca20f60
2019-06-22T16:03:53.823Z cpu5:2097701)0x451a0b81bee0:[0x41803782c589]callout_timer@(tcpip4)#<None>+0x23e stack: 0xffffffffffffffff
2019-06-22T16:03:53.823Z cpu5:2097701)0x451a0b81bf30:[0x418036c3d95d]VmkTimerQueueWorldFunc@vmkernel#nover+0x27e stack: 0x0
2019-06-22T16:03:53.823Z cpu5:2097701)0x451a0b81bfe0:[0x418036f081f2]CpuSched_StartWorld@vmkernel#nover+0x77 stack: 0x0
2019-06-22T16:03:53.829Z cpu5:2097701)base fs=0x0 gs=0x418041400000 Kgs=0x0
2019-06-22T16:03:53.829Z cpu5:2097701)vmkernel 0x0 .data 0x0 .bss 0x0
2019-06-22T16:03:53.829Z cpu5:2097701)chardevs 0x418037328000 .data 0x417fc0000000 .bss 0x417fc0000440
2019-06-22T16:03:53.829Z cpu5:2097701)user 0x418037330000 .data 0x417fc0400000 .bss 0x417fc0410a00
2019-06-22T16:03:53.829Z cpu5:2097701)procfs 0x41803742a000 .data 0x417fc0a00000 .bss 0x417fc0a00240
2019-06-22T16:03:53.829Z cpu5:2097701)lfHelper 0x41803742d000 .data 0x417fc0e00000 .bss 0x417fc0e03500
2019-06-22T16:03:53.829Z cpu5:2097701)vsanapi 0x418037433000 .data 0x417fc1200000 .bss 0x417fc12035c0
2019-06-22T16:03:53.829Z cpu5:2097701)vsanbase 0x41803744a000 .data 0x417fc1600000 .bss 0x417fc160ca20
2019-06-22T16:03:53.829Z cpu5:2097701)vprobe 0x41803745b000 .data 0x417fc1a00000 .bss 0x417fc1a11d00
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_mgmt 0x4180374a8000 .data 0x417fc1e00000 .bss 0x417fc1e00200
2019-06-22T16:03:53.829Z cpu5:2097701)iodm 0x4180374ae000 .data 0x417fc2200000 .bss 0x417fc2200128
2019-06-22T16:03:53.829Z cpu5:2097701)dma_mapper_iommu 0x4180374b3000 .data 0x417fc2600000 .bss 0x417fc2600080
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_4_0_0_mgmt_shim 0x4180374b7000 .data 0x417fc2a00000 .bss 0x417fc2a002e8
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_3_0_0_mgmt_shim 0x4180374b8000 .data 0x417fc2e00000 .bss 0x417fc2e00180
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_2_0_0_mgmt_shim 0x4180374b9000 .data 0x417fc3200000 .bss 0x417fc32001a0
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_2_0_0_vmkernel_shim 0x4180374ba000 .data 0x417fc3600000 .bss 0x417fc360c9c0
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_4_0_0_vmkernel_shim 0x4180374c2000 .data 0x417fc3a00000 .bss 0x417fc3a12bc0
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_3_0_0_vmkernel_shim 0x4180374c8000 .data 0x417fc3e00000 .bss 0x417fc3e0ff20
2019-06-22T16:03:53.829Z cpu5:2097701)vmkbsd 0x4180374d1000 .data 0x417fc4200000 .bss 0x417fc4207100
2019-06-22T16:03:53.829Z cpu5:2097701)vmkusb 0x41803751a000 .data 0x417fc4600000 .bss 0x417fc4607a20
2019-06-22T16:03:53.829Z cpu5:2097701)vmw_ahci 0x418037592000 .data 0x417fc4a00000 .bss 0x417fc4a005c0
2019-06-22T16:03:53.829Z cpu5:2097701)ntg3 0x4180375b3000 .data 0x417fc4e00000 .bss 0x417fc4e002a0
2019-06-22T16:03:53.829Z cpu5:2097701)lsi_mr3 0x4180375bf000 .data 0x417fc5200000 .bss 0x417fc5200400
2019-06-22T16:03:53.829Z cpu5:2097701)iscsi_trans 0x4180375e7000 .data 0x417fc5600000 .bss 0x417fc5601740
2019-06-22T16:03:53.829Z cpu5:2097701)iscsi_trans_compat_shim 0x4180375fb000 .data 0x417fc5a00000 .bss 0x417fc5a01148
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_2_0_0_iscsiInc_shim 0x4180375fc000 .data 0x417fc5e00000 .bss 0x417fc5e00850
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_3_0_0_iscsiInc_shim 0x418037600000 .data 0x417fc6200000 .bss 0x417fc6200850
2019-06-22T16:03:53.829Z cpu5:2097701)etherswitch 0x418037605000 .data 0x417fc6600000 .bss 0x417fc6617e40
2019-06-22T16:03:53.829Z cpu5:2097701)portcfg 0x418037653000 .data 0x417fc6a00000 .bss 0x417fc6a16e00
2019-06-22T16:03:53.829Z cpu5:2097701)vswitch 0x418037671000 .data 0x417fc6e00000 .bss 0x417fc6e00640
2019-06-22T16:03:53.829Z cpu5:2097701)netsched_fifo 0x4180376c0000 .data 0x417fc7200000 .bss 0x417fc7200060
2019-06-22T16:03:53.829Z cpu5:2097701)netsched_hclk 0x4180376c2000 .data 0x417fc7600000 .bss 0x417fc7603ec0
2019-06-22T16:03:53.829Z cpu5:2097701)netioc 0x4180376d2000 .data 0x417fc7a00000 .bss 0x417fc7a000a0
2019-06-22T16:03:53.829Z cpu5:2097701)lb_netqueue_bal 0x4180376d9000 .data 0x417fc7e00000 .bss 0x417fc7e00388
2019-06-22T16:03:53.829Z cpu5:2097701)dm 0x4180376e0000 .data 0x417fc8200000 .bss 0x417fc8200000
2019-06-22T16:03:53.829Z cpu5:2097701)nmp 0x4180376e3000 .data 0x417fc8600000 .bss 0x417fc8604630
2019-06-22T16:03:53.829Z cpu5:2097701)hpp 0x418037714000 .data 0x417fc8a00000 .bss 0x417fc8a02bf8
2019-06-22T16:03:53.829Z cpu5:2097701)vmw_satp_local 0x41803771e000 .data 0x417fc8e00000 .bss 0x417fc8e00020
2019-06-22T16:03:53.829Z cpu5:2097701)vmw_satp_default_aa 0x418037721000 .data 0x417fc9200000 .bss 0x417fc9200000
2019-06-22T16:03:53.829Z cpu5:2097701)vmw_psp_lib 0x418037723000 .data 0x417fc9600000 .bss 0x417fc9600290
2019-06-22T16:03:53.829Z cpu5:2097701)vmw_psp_fixed 0x418037725000 .data 0x417fc9a00000 .bss 0x417fc9a00000
2019-06-22T16:03:53.829Z cpu5:2097701)vmw_psp_rr 0x418037728000 .data 0x417fc9e00000 .bss 0x417fc9e00060
2019-06-22T16:03:53.829Z cpu5:2097701)vmw_psp_mru 0x41803772d000 .data 0x417fca200000 .bss 0x417fca200000
2019-06-22T16:03:53.829Z cpu5:2097701)vmci 0x41803772f000 .data 0x417fca600000 .bss 0x417fca608440
2019-06-22T16:03:53.829Z cpu5:2097701)healthchk 0x41803775a000 .data 0x417fcaa00000 .bss 0x417fcaa15b60
2019-06-22T16:03:53.829Z cpu5:2097701)teamcheck 0x418037775000 .data 0x417fcae00000 .bss 0x417fcae16080
2019-06-22T16:03:53.829Z cpu5:2097701)vlanmtucheck 0x41803778c000 .data 0x417fcb200000 .bss 0x417fcb215ec0
2019-06-22T16:03:53.829Z cpu5:2097701)heartbeat 0x4180377a7000 .data 0x417fcb600000 .bss 0x417fcb615f80
2019-06-22T16:03:53.829Z cpu5:2097701)shaper 0x4180377c0000 .data 0x417fcba00000 .bss 0x417fcba17cd0
2019-06-22T16:03:53.829Z cpu5:2097701)lldp 0x4180377d9000 .data 0x417fcbe00000 .bss 0x417fcbe00040
2019-06-22T16:03:53.829Z cpu5:2097701)cdp 0x4180377df000 .data 0x417fcc200000 .bss 0x417fcc2171c0
2019-06-22T16:03:53.829Z cpu5:2097701)ipfix 0x4180377fd000 .data 0x417fcc600000 .bss 0x417fcc6165c0
2019-06-22T16:03:53.829Z cpu5:2097701)tcpip4 0x41803781c000 .data 0x417fcca00000 .bss 0x417fcca18180
2019-06-22T16:03:53.829Z cpu5:2097701)dvsdev 0x418037975000 .data 0x417fcce00000 .bss 0x417fcce00030
2019-06-22T16:03:53.829Z cpu5:2097701)dvfilter 0x418037978000 .data 0x417fcd200000 .bss 0x417fcd200ac0
2019-06-22T16:03:53.829Z cpu5:2097701)lacp 0x41803799d000 .data 0x417fcd600000 .bss 0x417fcd600140
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_4_0_0_dvfilter_shim 0x4180379ab000 .data 0x417fcda00000 .bss 0x417fcda009e8
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_2_0_0_dvfilter_shim 0x4180379ac000 .data 0x417fcde00000 .bss 0x417fcde009f0
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_3_0_0_dvfilter_shim 0x4180379ad000 .data 0x417fce200000 .bss 0x417fce2009e8
2019-06-22T16:03:53.829Z cpu5:2097701)crypto_fips 0x4180379ae000 .data 0x417fce600000 .bss 0x417fce6019a0
2019-06-22T16:03:53.829Z cpu5:2097701)esxfw 0x4180379dc000 .data 0x417fcea00000 .bss 0x417fcea16a80
2019-06-22T16:03:53.829Z cpu5:2097701)dvfilter-generic-fastpath 0x4180379f7000 .data 0x417fcee00000 .bss 0x417fcee162b0
2019-06-22T16:03:53.829Z cpu5:2097701)vmkibft 0x418037a18000 .data 0x417fcf200000 .bss 0x417fcf2039c0
2019-06-22T16:03:53.829Z cpu5:2097701)vfat 0x418037a1c000 .data 0x417fcf600000 .bss 0x417fcf602820
2019-06-22T16:03:53.829Z cpu5:2097701)lvmdriver 0x418037a28000 .data 0x417fcfa00000 .bss 0x417fcfa03a40
2019-06-22T16:03:53.829Z cpu5:2097701)deltadisk 0x418037a49000 .data 0x417fcfe00000 .bss 0x417fcfe07e80
2019-06-22T16:03:53.829Z cpu5:2097701)vdfm 0x418037a83000 .data 0x417fd0200000 .bss 0x417fd02001c0
2019-06-22T16:03:53.829Z cpu5:2097701)gss 0x418037a88000 .data 0x417fd0600000 .bss 0x417fd0602b18
2019-06-22T16:03:53.829Z cpu5:2097701)vmfs3 0x418037ab0000 .data 0x417fd0a00000 .bss 0x417fd0a072c0
2019-06-22T16:03:53.829Z cpu5:2097701)sunrpc 0x418037bd0000 .data 0x417fd0e00000 .bss 0x417fd0e03b40
2019-06-22T16:03:53.829Z cpu5:2097701)vmklink_mpi 0x418037bee000 .data 0x417fd1200000 .bss 0x417fd1202600
2019-06-22T16:03:53.829Z cpu5:2097701)swapobj 0x418037bf4000 .data 0x417fd1600000 .bss 0x417fd16032f8
2019-06-22T16:03:53.829Z cpu5:2097701)nfsclient 0x418037bfe000 .data 0x417fd1a00000 .bss 0x417fd1a04340
2019-06-22T16:03:53.829Z cpu5:2097701)nfs41client 0x418037c20000 .data 0x417fd1e00000 .bss 0x417fd1e05700
2019-06-22T16:03:53.829Z cpu5:2097701)pciPassthru 0x418037c90000 .data 0x417fd2200000 .bss 0x417fd2202f00
2019-06-22T16:03:53.829Z cpu5:2097701)vflash 0x418037ca0000 .data 0x417fd2600000 .bss 0x417fd2603740
2019-06-22T16:03:53.829Z cpu5:2097701)dell 0x418037cac000 .data 0x417fd2a00000 .bss 0x417fd2a02a60
2019-06-22T16:03:53.829Z cpu5:2097701)procMisc 0x418037cb0000 .data 0x417fd2e00000 .bss 0x417fd2e00000
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapei 0x418037cb1000 .data 0x417fd3200000 .bss 0x417fd3200bc0
2019-06-22T16:03:53.829Z cpu5:2097701)nrdma 0x418037cbb000 .data 0x417fd3600000 .bss 0x417fd3617e40
2019-06-22T16:03:53.829Z cpu5:2097701)nrdma_vmkapi_shim 0x418037d03000 .data 0x417fd3a00000 .bss 0x417fd3a012b8
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_4_0_0_rdma_shim 0x418037d04000 .data 0x417fd3e00000 .bss 0x417fd3e01370
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_3_0_0_rdma_shim 0x418037d05000 .data 0x417fd4200000 .bss 0x417fd4200fc0
2019-06-22T16:03:53.829Z cpu5:2097701)ipmi 0x418037d07000 .data 0x417fd4600000 .bss 0x417fd4600c20
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_3_0_0_nmp_shim 0x418037d1d000 .data 0x417fd4a00000 .bss 0x417fd4a00df0
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_4_0_0_nmp_shim 0x418037d1e000 .data 0x417fd4e00000 .bss 0x417fd4e00df0
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_2_0_0_nmp_shim 0x418037d1f000 .data 0x417fd5200000 .bss 0x417fd5200d68
2019-06-22T16:03:53.829Z cpu5:2097701)vrdma 0x418037d20000 .data 0x417fd5600000 .bss 0x417fd5602580
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_4_0_0_iscsi_shim 0x418037d40000 .data 0x417fd5a00000 .bss 0x417fd5a01240
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_3_0_0_iscsi_shim 0x418037d41000 .data 0x417fd5e00000 .bss 0x417fd5e00970
2019-06-22T16:03:53.829Z cpu5:2097701)vmkapi_v2_2_0_0_iscsi_shim 0x418037d42000 .data 0x417fd6200000 .bss 0x417fd6200970
2019-06-22T16:03:53.829Z cpu5:2097701)balloonVMCI 0x418037d43000 .data 0x417fd6600000 .bss 0x417fd6600000
2019-06-22T16:03:53.829Z cpu5:2097701)hbr_filter 0x418037d44000 .data 0x417fd6a00000 .bss 0x417fd6a00300
2019-06-22T16:03:53.829Z cpu5:2097701)ftcpt 0x418037d75000 .data 0x417fd6e00000 .bss 0x417fd6e02fc0
2019-06-22T16:03:53.829Z cpu5:2097701)filtmod 0x418037dc2000 .data 0x417fd7200000 .bss 0x417fd7204180
2019-06-22T16:03:53.829Z cpu5:2097701)svmmirror 0x418037dd4000 .data 0x417fd7600000 .bss 0x417fd7600100
2019-06-22T16:03:53.829Z cpu5:2097701)cbt 0x418037de1000 .data 0x417fd7a00000 .bss 0x417fd7a000c0
2019-06-22T16:03:53.829Z cpu5:2097701)migrate 0x418037de4000 .data 0x417fd7e00000 .bss 0x417fd7e05380
2019-06-22T16:03:53.829Z cpu5:2097701)vfc 0x418037e61000 .data 0x417fd8200000 .bss 0x417fd8202cc0
2019-06-22T16:03:53.829Z cpu5:2097701)dcism_module 0x418037e87000 .data 0x417fd8600000 .bss 0x417fd86000a0
Coredump to disk.
2019-06-22T16:03:53.880Z cpu5:2097701)Slot 1 of 1 on device naa.6b083fe0dcdb050020c471bf0de1a793:9.
2019-06-22T16:03:53.880Z cpu5:2097701)Dump: 474: Using dump slot size 2684354560.
2019-06-22T16:03:53.882Z cpu5:2097701)Dump: 2845: Using dump buffer size 98304
DumpProgress: Faulting world regs Faulting world regs (01/14)
Hi all,
I am first time installed and want to use VMware in my Windows 10 machine. But after several process done, getting below error on Powe ON
Loading Boot logo...
bootlogo: invalid file format
Error setting up gfxboot
PFA for more details.
My PC details are:
VMware details:
On Powering:
Settings:
Any help to resolve will be appreciated.
Thank you.
We are on Horizon View 6 (6.2.3 build 4126346) and are encountering issues with remote users who are using the HTML client (where the Horizon View Client isn't an option) having their C:\ drives get filled up with Blast log files. I've not had any luck with googling a solution as there doesn't seem to be a simple way to minimize or stop blast logging. The logs are the in 'C:\programdata\vmware\vmware blast' folder and consume gigabytes of space (see attached). Is there any easy way to limit the file size and number of logs ?
I need to have an inactive collector removed from our account. I've seen in other posts where this can be done via a request.
It is from a failed deployment that I no longer have access to.
From what I have read in the VMware documentation, it looks like yes, ESXi Hardware Requirements . But do any of you in practice use a USB drive that has the ESXi server on it, but maybe the scratch drive on the local disk (or in the RAM)? It seems so foreign to me to put an OS on a flash drive, except in hobby type labs, but I think I am stuck in the olden days. What if the flash drive dies? Can you just put a new one in and install ESXi again and it mount the clustered datastore (or maybe you have a duplicate drive standing by).
I have local drives and iSCSI drives. My local drives are 500GB, but I don't want to put ESXi on those, if I can use them for a datastore (mirrored and backed up, etc.)
I have scripted out setting all of our relevant alerts for trigger actions to email my distribution list but it doesn't seem to do anything in terms of Reset actions. I have looked through the commands and whenever I do Get-AlarmAction, it will show the SendEmail for the alert but not for the reset rule. Does anyone know how I can see the Reset Rules to add email notifications? Thanks in advance
Hi all.
I just inherited this vcenter 5.5 system and am tasked to get it 6.0 (going from Windows server to VCSA appliance). I've started with the convenient U2M package and have the Migration Assistant running on the existing server, and when I run the actual migration tool, I get stuck on step 6 where I select the appliance size. It comes up with an error 'Error in populating profiles' and won't let me select the appliance size. I can't seem to find where the log files are that will help me on this, or a good answer from searching on how to get past that error. Any ideas ?
Hello,
Opened ticket with VMware support regarding host PSOD. We have had 3 random host crashes over the past 5 weeks.
Support is telling me PSOD is the result of bnx2fc driver causing deadlock contention. We have HP ProLiant DL380 Gen9 servers with 4 CNA adapters, two for network two for storage. With FCoE enabled on ports ESXi is trying to discover FCoE vlan and targets, when ESXi doesn’t discover FCoE connection it continues to have driver discover again. Support is indicating during the discovery process bnx2fc is causing deadlock contention and that is causing the PSOD, do to faulty driver code.
I am being told there is no KB or advisory, that its only documented internally. When searching I found the following kb, based on what support sent me the symptoms and workaround are almost identical to what is outlined in kb - https://kb.vmware.com/s/article/2120523
I also found other third party sites discussing issue
https://www.teimouri.net/retry-vlan-discovery/
None of these make mention of bnx2fc driver causing contention during the discovery. I would think this driver was known to cause PSOD it would be documented. Wanted to post see if anyone had feedback. Support is recommending I run the following command esxcfg-module -s "bnx2fc_default_vlan=0" bnx2fc
My understanding is that command is used for managing the kernel module drivers. If we set the default vlan = 0 what the ramifications would be for adapters that are connected to storage.
Any in-site is appreciated.
Thanks,
Hello, hope you are well.
I am wondering if anybody can help me. I am running a VMware vCenter Appliance with embedded Platform Services Controller.
Version 6.5.0 Build 12863991
I was running an old version of vSphere Replication server but have decommissioned it and wanting to deploy a clean install of vSphere Replication 8.2. The problems I am having are:-
1. Once I deploy a new Replication Appliance and connect to the VAMI, if I click on the configuration tab under VRS, I see a pop up box with an error saying "local variable 'host' referenced before assignment". See attached picture:-
When this happens the VAMI interface seems to hang and I can't seem to do much in terms of configuration. I have tried using IE 11 and Chrome. Also in the right corning of the browser it shows a timer saying gathering isolation info (Or something like that).
2. The second problem is when I deploy an additional vSphere Replication Server 8.2. I get the exact same issues as above on a new appliance, but on the additional server, if I try to generate and install a new certificate, it seems to act like it has done this, but the new certificate is still using the IP Address as the name on it instead of the servers configured hostname.
Any help would be greatly appreciated.
Regards,
Dave