Immediately after installing Win10 1903 Update on my 64x Win10 Pro host and doing the automatic reboot, my VM shows a completely black screen except for the title at the top and the single-line menu bar below the title.

I tried fixes other people have reported including updating host video driver and issuing Ctrl + Alt + Del key combo (on the host as well as on the guest) and multiple reboots. No joy.

I'm running VMware-player-14.1.7.

I notice some other people are reporting that the black screen problem which was caused by the 1903 Windows Update was corrected for users of VMware-workstation-full-15.1.0 but I don't see any solution for Player 14.1.7.

Any trouble-shooting ideas or fixes?

Thank you for you for help,

Ray

この記事ではvCenter Serverのログバンドル、通称vc-supportの作成方法を紹介します。

紹介している手順の内、どの方法でvc-supportを取得しても基本的に同じ情報を収集できますが、各手段には概ね以下のような違いがあります。

VAMI… 特にサポートエンジニアから手順について指示を受けていない場合はこの手段での取得が簡単です。また、同様の方法でPSCのログも取得可能です。

vSphere Web Client …vc-supportと同時にESXiログバンドル(vm-support)も生成・取得が可能です。

CLI …GUIが使用できない場合に利用してください。CLIの場合も、同様の方法でPSCのログを作成できます。また、VCSAがデフォルト設定の状態ではファイル転送ソフトが使用できないので、CLIでログを生成した場合のダウンロード手順もこのコミュニティで紹介しています。

1. GUIからのvc-support生成・取得

     1-1. VAMI

VAMI(Virtual Appliance Management Infrastructure)と呼ばれる、VCSA自体を管理するGUIからログを作成します。

vc-supportを単体で取得したい場合は、この取得方法がシンプルでお勧めです。

また、指定するIPを変えてPSCのVAMIにログインすれば、PSCのログも取得可能です。

ⅰ. https://vCenter_Server_IP_address:5480にWebブラウザでアクセス

ⅱ. rootにてログイン

ⅲ.  GUIのサマリ→"サポートバンドルの作成"をクリック

ⅳ. vm-support.tgzファイルが作成されるので、作業端末の任意のロケーションに保存

(ファイル名はvm-supportですが、中身はvc-supportです。)

※この手順でvc-supportを取得された場合は、アップロードの際にファイル名をvm-supportからvc-***やpsc-***等、分かりやすく変更いただけますと幸いです。

     1-2. vSphere Web Client

vSphere Web Clientからvc-supportを作成する場合は、同時にvm-supportも作成することができるので、

トラブルシュートに必要なログを一括で取得したい場合に便利です。

ⅰ. vSphere Web Clientにログイン

ⅱ. 左ペーンでvCenterインベントリ リストを選択

ⅲ. リスト内のリソースから"vCenter Serverを選択"

ⅳ. 対象のvCenterをクリック> 監視> システム ログ> システムログのエクスポート

ⅴ. vCenter Server および vSphere Web Client ログを含めますオプションを選択し、"次へ"をクリック

     ※この時、リストされているESXiをチェックすると、同時にESXiログバンドル(vm-support)も取得できます。

ⅵ. ログバンドルの生成をクリック

     ※"パフォーマンスデータの収集"は、特にサポートエンジニアの指示がなければ必要ありません。

ⅶ. ログの生成が完了すると、"ログバンドルのダウンロード"ボタンが表示されるので、クリックして任意のロケーションに保存

ⅷ. ダウンロードできたら、完了をクリック

2. CLIからのvc-support生成・取得

何らかの理由によりvSphere Web ClientやVAMI等のGUIサービスが使用できない場合は、コマンドラインでログを作成することができます。

また、sshでログインする対象をPSCにすれば、同様の手順でPSCのログバンドルを生成できます。

    2-1. コマンドラインでvc-supportの生成

ⅰ. VCSAにrootでssh接続

ⅱ. デフォルト設定ではAppliance Shellにログインするため、Bashに遷移

Command> shell.set --enabled True

Command> shell

Shell access is granted to root

root@vc [ ~ ]#

ⅲ. 下記のコマンドでログの生成を開始

# vc-support -l

※例

ⅳ. 生成されたログは/storage/log/配下にvc-***(FQDN-日付).tgzとして保存される

     2-2. ファイルシステム内に作成されたvc-supportの取得方法

デフォルト設定では、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端末などにダウンロードすることができます。

※いずれの場合も2-1-ⅱの手順を参照し、Bash Shellにログインしてから実施します

scpコマンド例

# scp /storage/log/vc-***.tgz  リモートホストユーザ名@リモートホストIPアドレス:リモートホストディレクトリ

The authenticity of host '**.**.**.** (**.**.**.**)' can't be established.

ECDSA key fingerprint is SHA256:HBR8h9gdCT9Vd1HzOAH6WBgXNReE1YZ6vRO8e/agU40.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added '**.**.**.**' (ECDSA) to the list of known hosts.

Password:                                             ←リモートホストのパスワードを入力

vc-***.tgz                                                                                                              100%  400MB 175.7MB/s   00:02

root@vc [ ~ ]#

sftpコマンド例

# sftp リモートホストユーザ名@リモートホストIPアドレス

Password:                                              ←リモートホストのパスワードを入力

Connected to *****.

sftp>

sftp>

sftp> put /storage/log/vc-***.tgz               ←putコマンドでvc-supportをリモートホストに送信

Uploading /storage/log/vc-***.tgz to /***/vc-***.tgz

/storage/log/vc-***.tgz                                                                                              100%  400MB 127.1MB/s   00:03  

sftp> bye                                                ←byeでセッション終了

root@vc [ ~ ]#

3. 参考情報

     空き容量確認

vc-supportはファイルサイズが3GB以上になるケースがありますが、

多くは/storage/logおよび/storage/core 配下に溜まっている過去のサポートログやcoreファイルが要因となっています。

ファイルシステムの空き容量が不足している状態でvc-supportを作成し、パーティションの使用率が100%に達すると

vSphere Web Clientにアクセスできなくなるなどの事象が報告されています。

/storage/log配下に過去の不要なログが確認された場合は、削除してください。

また、vc-supportコマンドに -wオプションを付加することで、ログを生成するディレクトリを指定できます。

判断に迷った場合は、容量の空いているパーティションを特定し、該当のロケーションにvc-supportを作成することも可能です。

出典:

VMware vCenter Server 4.x, 5.x および 6.0 の診断情報の収集 (2079103)

https://kb.vmware.com/s/article/2079103

Hello,

how can I prevent an special usb device from autoconnecting to a virtual machine?

Hello, I got a problem after upgrade to Windows Insider Preview 1903 18362.30 x64 on host machine.

CPU : I5-8400

RAM : 16G

Host OS : Windows 10 1903 x64 18362.30 (Latest WIP)

VMWare Version : 15.0.4 build-12990004

Other Status :

"bcdedit /set hypervisorlaunchtype OFF"  (Means that Windows Native hypervisor already turned off)

"Memory integrity guard OFF"

"Credential Guard OFF"

Before I upgraded to Windows Insider Preview 18362.30, I was using Windows 10 RS5 x64 as a host operating system.

I could run any VM guest machine without any problem.

But, after I upgrade to Windows 10 1903, I cannot run any VM guest.

Guest screen only shows a black screen, and nothing happens.

What I can do is just rebooting machine. Cannot terminate vmware-vmx.exe process.

Anybody has same issue like this? And if anybody has solution it will be very thankful.

Thanks.

Hi

I am using ESXi 6.5.0 Update 1 host which runs on stateless disk. put host into maintenance mode and trying to install ESXi650-201801001.zip patch fails with below ERROR.

[root@localhost:/vmfs/volumes/5a674188-2b5d1eb0-89e1-a60dce9000d7] esxcli software vib update -d /vmfs/volumes/5a674188-2b5d1eb0-89e1-a60dce9000d7/ESXi650-201801001.zip

[StatelessError]

The transaction is not supported: VIB VMW_bootbank_vmkusb_0.1-1vmw.650.1.36.7388607 cannot be live installed. VIB VMW_bootbank_ntg3_4.1.3.0-1vmw.650.1.36.7388607 cannot be live installed. VIB VMW_bootbank_nvme_1.2.0.32-5vmw.650.1.36.7388607 cannot be live installed. VIB VMW_bootbank_misc-drivers_6.5.0-1.36.7388607 cannot be live installed. VIB VMW_bootbank_nmlx4-core_3.16.0.0-1vmw.650.0.0.4564106 cannot be live installed. VIB VMW_bootbank_nmlx4-rdma_3.16.0.0-1vmw.650.0.0.4564106 cannot be live installed. VIB VMware_bootbank_esx-base_6.5.0-1.38.7526125 cannot be live installed. VIB VMW_bootbank_scsi-mpt2sas_19.00.00.00-1vmw.650.0.0.4564106 cannot be live installed. VIB VMW_bootbank_nmlx4-en_3.16.0.0-1vmw.650.0.0.4564106 cannot be live installed. VIB VMware_bootbank_vsan_6.5.0-1.38.7395176 cannot be live installed. VIB VMW_bootbank_igbn_0.1.0.0-15vmw.650.1.36.7388607 cannot be live installed. VIB VMW_bootbank_vmkata_0.1-1vmw.650.1.36.7388607 cannot be live installed. VIB VMW_bootbank_nvmxnet3_2.0.0.23-1vmw.650.1.36.7388607 cannot be live installed. VIB VMware_bootbank_cpu-microcode_6.5.0-1.38.7526125 cannot be live installed. VIB VMware_bootbank_esx-tboot_6.5.0-1.38.7526125 cannot be live installed. VIB VMware_bootbank_cpu-microcode_6.5.0-1.26.5969303 cannot be removed live. VIB VMware_bootbank_esx-dvfilter-generic-fastpath_6.5.0-1.26.5969303 cannot be removed live. VIB VMW_bootbank_nvmxnet3_2.0.0.22-1vmw.650.1.26.5969303 cannot be removed live. VIB VMW_bootbank_ntg3_4.1.2.0-1vmw.650.1.26.5969303 cannot be removed live. VIB VMware_bootbank_vsan_6.5.0-1.26.5912915 cannot be removed live. VIB MEL_bootbank_nmlx4-core_3.15.5.5-1OEM.600.0.0.2768847 cannot be removed live. VIB Avago_bootbank_scsi-mpt2sas_15.10.07.00-1OEM.550.0.0.1331820 cannot be removed live. VIB MEL_bootbank_nmlx4-rdma_3.15.5.5-1OEM.600.0.0.2768847 cannot be removed live. VIB VMW_bootbank_misc-drivers_6.5.0-1.26.5969303 cannot be removed live. VIB VMW_bootbank_nvme_1.2.0.32-4vmw.650.1.26.5969303 cannot be removed live. VIB VMware_bootbank_esx-base_6.5.0-1.26.5969303 cannot be removed live. VIB VMW_bootbank_igbn_0.1.0.0-14vmw.650.1.26.5969303 cannot be removed live. VIB VMware_bootbank_esx-tboot_6.5.0-1.26.5969303 cannot be removed live. VIB MEL_bootbank_nmlx4-en_3.15.5.5-1OEM.600.0.0.2768847 cannot be removed live.

Please refer to the log file for more details.

found one kb related to stateless host : VMware Knowledge Base

is this known issue? or am i missing something here?

I recently updated my MacBook Pro to Mojave.  Now my VM Horizon will not connect to the server.  All I get is couldn't connect to the server.  I have the exact same server name listed on my IPAD pro and it works fine.

Any tricks to get working with Mojave

=======update  fixed=======

I make a new directory named 172.31.18.143 in /vmfs/volumes/5bcf481f-70bab5a4-9131-c4b8b42ec002/,

[root@lscyy-server1:/vmfs/volumes/5bcf481f-70bab5a4-9131-c4b8b42ec002/172.31.18.143-Centos6.8-HDFS_HBASE(S)_zk] mv * ../172.31.18.143/

mv: can't rename '172.31.18.143-Centos6.8-HDFS_HBASE(S)_zk.vmx~': No such file or directory

mv: can't rename 'vmware.log': No such file or directory

[root@lscyy-server1:/vmfs/volumes/5bcf481f-70bab5a4-9131-c4b8b42ec002/172.31.18.143-Centos6.8-HDFS_HBASE(S)_zk]

The output means all the normal files are moved successfully, except the unnormal files like '172.31.18.143-Centos6.8-HDFS_HBASE(S)_zk.vmx~'

In in other words, the new directory '172.31.18.143' can be used to register VM.

Then I unregister the stopped unnormal VM, and register it from the vmx file in new directory '172.31.18.143', the new VM starts successfuly.

=================================================

This problem occur due to the the power failed, when I try to start the VM, got this error:

https://i.imgur.com/0OeVi9Q.jpg

And I check the VM directory, there's no someting like "xxxx.vmk~"

Then I ssh to the ESXi server, run find / -name "*~", I do get this:

https://imgur.com/7JHJENO.jpg

I don't konw why there's no such file, but the server says "The file already exists"?

How can I fix this?

i will be appreciated if anyone could give me some help!

Hello Guys, I have installed vRA7.6 and all my provisions are failing. I am adding a network profile that is configured as external network and it has my DNS server settings in it. and also have a customisation spec for linux and windows. windows customization spec has the AD details and DHCP network configured in it. All my provisions go to the vcenter, get cloned, power on, power off and then get destroyed. I tried creating a windows 2016 and rhel blueprint with just the template of the VM and no network and no customization spec but same thing happens. _debug_deployment set to true does not help either and the VM gets destroyed. I tried creating a VM from my rhel template by cloning it to VM and applied to linux customisation spec and it turned out to be ok, the machine got added to my DNS zone as per the customisation spec. The same template/customization spec was working fine with vRA7.3. This is not a inplace upgrade but a fresh install of vra7.6. The error is see in vRA is "PowerOn : One or more errors occurred..", and that does not help either.

I am out of ideas. Any help is appreciated.

I am looking for a way, if there is one, to copy a vm from one cluster to another thin provisioned via host to host cli without using vcenter.

I have root for all hosts
There is no shared storage between clusters

all hosts can communicate over 443/22/902

The below command copies the vm folder and contents from source to target datastore but ends up moving it thick provisioned.

scp -r /vmfs/volumes/Source_Cluster_Datastore/vm_folder root@Target_Host_FQDN:/vmfs/volumes/Target_Datastore/

The below command copies the file from source to target datastore folder but ends up moving it thick provisioned.

scp /vmfs/volumes/Source_Cluster_Datastore/vm_folder/file root@Target_Host_FQDN:/vmfs/volumes/Target_Datastore/folder/

I saw this link but I was unable to get vmkfstools to copy between clusters.

https://serverfault.com/questions/372526/move-vmware-esxi-vm-to-new-datastore-preserve-thin-provisioning

Any help would be appreciated

Hey guys,

We have recently upgraded ESXi on all our servers in the cluster from ESXi 6.5 to ESXi 6.7 Update1 (EP7 build) and since then we are seeing issues on multiple VMs (linux vms) that are randomly getting restarted. These reboots were seen since the upgrade and also during vMotion of vms to other hosts during the upgrade. Even today, 4 days after the upgrade, some VMs are rebooting with the below error.

The error we have seen in the events are

vmware esx unrecoverable error (vcpu-2) vmk: unable to decompress BPN (I've attached a screenshot as well)

Has anyone come across this?

Cheers,

Onil Varghese

I am having troubles figuring out what i'm doing wrong with networking to my ESXI host, and onward to the VMs within from my internet gateway / home router. 

I have an ESXI host with 3 vms connected to a network switch which is directly connected to my home router to get to internet.  On the same switch i have a stand-alone file server and multiple home pcs.  All of the home pcs and the standalone file server show ports open to the outside when port checking after setting up port forwardings to them on the router, however nothing that i setup for port forwardings for any of the VMs within the ESXI host environment will show open to internet.  

I have the network setup as follows within ESXI:

ESXI host (192.168.x.30)  connects to vswitch0 for "management network" (VLAN 0)   - uplinks to vmnic0

VMs (192.168.x.5 / 6 / 7) all connect to vswitch1 for "VM network' (VLAN 0) - uplinks to vmnic1

i also had these original setup to the same vswitch, but was reading that management and vm network needed to be on their own uplink / vswitch (not sure if that is actually true).

I cannot for the life of me get the port forwardings to work, but within the VM environment - i can get to the internet, show proper IP DHCP or Static from the router (outside ESXI network) and ping to internet / show i'm on internet.  So it looks like it just isn't passing port forwardings through from VMs to ESXI and thus services can't get out to internet or internet get back to them.

What am i possibly doing wrong?  (i have network background as i work as a network administrator/tech for a career), but can't figure if this is something i don't understand in the VMware / ESXI environment doing this.

looking for expert guidance here.

-Mike

Getting some storage performance event from one ESXi,messages as below, would like to collect Log of RAID controller，however it hung when run command "df" or  "storcli show"

＂esxcli storage filesystem list＂　list the mount point without problems。How do I strace what it hang when run command "df" or "storcli show"？

2019-06-16T22:43:15.458Z cpu0:32815)ScsiDeviceIO: 2595: Cmd(0x43a60e45d740) 0x2a, CmdSN 0xfb from world 40433067 to dev "naa.6c00709558c783d0208980f904975886" failed H:0x8 D:0x0 P:0x0

2019-06-16T22:43:15.458Z cpu0:32815)ScsiDeviceIO: 2595: Cmd(0x43a61040ae00) 0x2a, CmdSN 0x54 from world 40433067 to dev "naa.6c00709558c783d0208980f904975886" failed H:0x8 D:0x0 P:0x0

2019-06-16T22:43:15.458Z cpu0:32815)ScsiDeviceIO: 2595: Cmd(0x43a600149d40) 0x8a, CmdSN 0x38 from world 40433067 to dev "naa.6c00709558c783d0208980f904975886" failed H:0x8 D:0x0 P:0x0

2019-06-16T22:43:15.458Z cpu0:32815)ScsiDeviceIO: 2595: Cmd(0x43a6002099c0) 0x2a, CmdSN 0x12 from world 40433067 to dev "naa.6c00709558c783d0208980f904975886" failed H:0x8 D:0x0 P:0x0

2019-06-16T22:43:15.458Z cpu0:32858)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237: NMP device "naa.6c00709558c783d0208980f904975886" state in doubt; requested fast path state update...

2019-06-16T22:43:15.458Z cpu0:32858)ScsiDeviceIO: 2595: Cmd(0x43a60006bac0) 0x8a, CmdSN 0xf4 from world 40433067 to dev "naa.6c00709558c783d0208980f904975886" failed H:0x8 D:0x0 P:0x0

2019-06-16T22:43:15.458Z cpu0:32858)NMP: nmp_ThrottleLogForDevice:3219: last error status from device naa.6c00709558c783d0208980f904975886 repeated 10 times

2019-06-16T22:43:15.458Z cpu26:32857)FS3Misc: 1759: Long VMFS rsv time on 'DataStore-10.100.31.74' (held for 22030 msecs). # R: 1, # W: 1 bytesXfer: 2 sectors

2019-06-16T22:43:15.458Z cpu0:32858)lsi_mr3: mfi_TaskMgmt:254: Processing taskMgmt virt reset for device: vmhba2:C2:T1:L0

2019-06-16T22:43:15.458Z cpu0:32858)lsi_mr3: mfi_TaskMgmt:258: VIRT_RESET cmd # 74427698

2019-06-16T22:43:15.458Z cpu0:32858)lsi_mr3: mfi_TaskMgmt:262: ABORT

2019-06-16T22:43:16.459Z cpu0:32858)lsi_mr3: fusionWaitForOutstanding:2531: megasas: [ 0]waiting for 21 commands to complete

2019-06-16T22:43:16.639Z cpu0:19978690)HBX: 2802: 'Data-10.100.31.74': HB at offset 3424256 - Waiting for timed out HB:

2019-06-16T22:43:16.639Z cpu0:19978690)  [HB state abcdef02 offset 3424256 gen 3 stampUS 51822000695098 uuid 59f077b3-5f00d7bc-deb9-883fd3332128 jrnl <FB 14474800> drv 14.61 lockImpl 3]

2019-06-16T22:43:17.461Z cpu0:32858)lsi_mr3: mfi_TaskMgmt:254: Processing taskMgmt virt reset for device: vmhba2:C2:T1:L0

2019-06-16T22:43:17.461Z cpu0:32858)lsi_mr3: mfi_TaskMgmt:258: VIRT_RESET cmd # 74427698

2019-06-16T22:43:17.461Z cpu0:32858)lsi_mr3: mfi_TaskMgmt:262: ABORT

[root@SZEsxi001:~] ps -Tcjstv |head -1; ps -Tcjstv |grep storcli

WID       CID       WorldName                                                                    GID      Type    State   Wait    CPU   Time          Command

42853668  42853668  storcli                                                                      42853668  User,Native    WAIT    NOEVQ   0-31      0.141628  ./storcli show

42853669  42853668  storcli                                                                      42853668  User,Clone,Native    WAIT    UPOL    0-31      0.34      ./storcli show

42853854  42853854  grep                                                                         42853854  User,Native    WAIT    UPIPER  0-31      0.0       grep storcli

[root@SZEsxi001:~] ps -Tcjstv |head -1; ps -Tcjstv |grep df

WID       CID       WorldName                                                                    GID      Type    State   Wait    CPU   Time          Command

42852168  42852168  python                                                                       42852168  User,Native    WAIT    NOEVQ   0-31      0.364534  python /bin/df

42852169  42852168  python                                                                       42852168  User,Clone,Native    WAIT    UPOL    0-31      0.42      python /bin/df

42852567  42852567  grep                                                                         42852567  User,Native    WAIT    UPIPER  0-31      0.0       grep df

[root@SZEsxi001:~]

Hi

Is that possible to implement and configure ELM (Enhance Link Mode) between two vCenters after vcsa installation or it is mandatory to config it during vsca installation ?

BR

Babak

i hav installed unity 3d software! when the installation process is over, i launched the software. it says peer certificate cannot be authenticated. now what should i do??? please help.

Hi

I am evaluating VM Ware workstation Pro 15 on windows 10.

When I trying to share a VM, getting the bellow error:

I checked VM ware services, all services are running.

Can anyone please help me, if I am missing anything.

I get the following error when trying to add a vROM to the skyline configuration.

"Endpoint test failed. -> cannot retry due to server authentication, in streaming mode"

The skyline user I setup in vROM has only Read Only permissions assigned to it in vROM.

I am at vROM v7.0

Thanks

Chad

Hi,

Can someone please help me out with identifying inactive/idle vms within my vmware environment? It can either be from vSphere Client or vRops. I did o through the existing posts but couldn't find much.

Thanks,

Mustafa.

Dear All

Do you know when Horizon 7.9 will be released?

Regards,

Balan V

If i open them manually works good, but if i use rest api for load them i get black screen in all machines.

Vmware workstation: 15.1.0 build-13591040

Windows10 version 1809 ( Compilation of OS 17763.557)

Api version: VMware Workstation REST API //vmrest 1.2.0 build-13591040

Virtual Machine OS: Windows 7

I have these python script for run the api and run the vms with api

[Python] import requests  import subprocess  from requests.auth import HTTPBasicAuth  imp - Pastebin.com

wich I call from a .bat file from task scheduler, like these vms start when i need them with a simple job

For start =

cd "C:\Users\localhost\PycharmProjects\Scripts Python\VM_Manager"
set VAR_1=On
python Main.py %1 %VAR_1%

for switch them off

cd "C:\Users\localhost\PycharmProjects\Scripts Python\VM_Manager"
set VAR_1=off
python Main.py %1 %VAR_1%

start task scheduler windows job

<?xml version="1.0" encoding="UTF-16"?><Task version="1.4" xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task">  <RegistrationInfo>    <Date>2019-06-08T02:08:37.8509653</Date>    <Author>DESKTOP-09RV55J\localhost</Author>    <URI>\Microsoft\Windows\UserTasks\Start1</URI>  </RegistrationInfo>  <Triggers>    <CalendarTrigger>      <StartBoundary>2019-06-08T01:05:27</StartBoundary>      <Enabled>true</Enabled>      <ScheduleByDay>        <DaysInterval>1</DaysInterval>      </ScheduleByDay>    </CalendarTrigger>  </Triggers>  <Principals>    <Principal id="Author">      <UserId>S-1-5-21-12982169-1001</UserId>      <LogonType>S4U</LogonType>      <RunLevel>HighestAvailable</RunLevel>    </Principal>  </Principals>  <Settings>    <MultipleInstancesPolicy>IgnoreNew</MultipleInstancesPolicy>    <DisallowStartIfOnBatteries>true</DisallowStartIfOnBatteries>    <StopIfGoingOnBatteries>true</StopIfGoingOnBatteries>    <AllowHardTerminate>true</AllowHardTerminate>    <StartWhenAvailable>false</StartWhenAvailable>    <RunOnlyIfNetworkAvailable>false</RunOnlyIfNetworkAvailable>    <IdleSettings>      <StopOnIdleEnd>true</StopOnIdleEnd>      <RestartOnIdle>false</RestartOnIdle>    </IdleSettings>    <AllowStartOnDemand>true</AllowStartOnDemand>    <Enabled>true</Enabled>    <Hidden>false</Hidden>    <RunOnlyIfIdle>false</RunOnlyIfIdle>    <DisallowStartOnRemoteAppSession>false</DisallowStartOnRemoteAppSession>    <UseUnifiedSchedulingEngine>true</UseUnifiedSchedulingEngine>    <WakeToRun>false</WakeToRun>    <ExecutionTimeLimit>PT72H</ExecutionTimeLimit>    <Priority>7</Priority>  </Settings>  <Actions Context="Author">    <Exec>      <Command>"D:\Virtual Machines\StartAll.bat"</Command>    </Exec>  </Actions></Task>

Hi guys,

Is it possible to use vdbench with cross platforms(Linux to windows)? I am trying to initiate vdbench from Linux host (Master) and run it on Windows host(slave) ended up with below error. Any leads on this ?

The same param file is working when initiated  from windows host.

03:19:10.431 input argument scanned: '-fwin'

03:19:10.535 Starting slave: c:\vdbench\vdbench SlaveJvm -m 10.XX.XX.XX -n 10.XX.XX.XX-10-190624-03.19.10.405 -l hd1-0 -p 5570

03:19:10.542 Successfully connected to the Vdbench rsh daemon on host 10.XX.XX.XX

03:19:10.542 RSH Connection to 10.XX.XX.XX using port 5560 successful

03:19:12.126

03:19:12.126 findSlave() Unable to find slave: rsh_to_client

03:19:12.126

1. java.lang.RuntimeException: findSlave() Unable to find slave: rsh_to_client

        at Vdb.common.failure(common.java:335)

        at Vdb.SlaveList.findSlaveLabel(SlaveList.java:64)

        at Vdb.SlaveSocket.getMessage(SlaveSocket.java:215)

        at Vdb.Rsh.getRemoteOutput(Rsh.java:105)

        at Vdb.Rsh.issueCommand(Rsh.java:204)

        at Vdb.SlaveStarter.startJvm(SlaveStarter.java:238)

        at Vdb.SlaveStarter.startSlave(SlaveStarter.java:174)

        at Vdb.SlaveStarter.run(SlaveStarter.java:47)

Param file content:

===================

hd=default,vdbench=c:\vdbench,shell=vdbench

hd=hd1,system=10.XX.XX.XX

************************************************************************************

sd=default,size=1g

sd=sd1,host=hd1,lun=\\.\PhysicalDrive1,openflags=directio

***********************************************************************************

wd=wd1,sd=(sd1),rdpct=100,rhpct=0,whpct=0,xfersize=64k,seekpct=100

****************************************************************************************

rd=rd1,wd=(wd1),interval=1,iorate=max,elapsed=40000,warmup=1,forthreads=1024