Is it possible to create VMware VRO client MSI? If someone has done before, please share the steps.

Thank you Scott,

According to the product page and the supported guest OS db search, OS X 10.6 (NONserver) IS supported, however, 10.8.1 (I just downloaded the trial) refuses to install from a non-server OS X 10.6.3 install dvd (the published, i.e. not bundled with a particular hw model version).

During machine creation, only OS X 10.6 Server is an offered option (no non-server); that refuses the non-server Snow Leopard install dvd.  I also tried creating a 10.7 machine; it still refused the 10.6 install dvd, complaining it was a non-server.  Also, creating a "Other 64-bit" machine, setting the dvd to SATA still resulted in not even seeing the install dvd.

(Other info: everything is 64-bit, host OS is El Capitan, hardware is MacBook 6,2 ...the one that won't boot the published, i.e. not bundled Snow Leopard install dvd; I installed the non-Pro trial, since that's what I'd prefer to purchase if it works....)

Does anyone know how to resolve this?

Thanks in advance.....

The slide shows the general IOPs and Read & Write throughput you can expect per spindle depending on the RAID configuration and/or drive type you have in your array.

These are not hard numbers, just an indication of what you should expect, but storage configuration vary and it all depends on how your storage is configured and how many disks (spindles) in your storage, and the type of raid configured.

Sorry to be the bearer of bad news: Only the "Server" variants of Mac OS X 10.5 and 10.6 are supported.  The information is in the VMware Compatibility Guide, although it isn't exactly obvious... In the OS Release column of the results list, click on the Mac OS X 10.6.x link and it'll take you to the details page which should say "Supported Variants: Server".  The Client version is not listed and not supported.

Cheers,

--

Darius

How can i Ping as my HP Server and DELL MD 3420 storage Array are connected using SAS cable.

also no LUN masking is applied even the connection path is not showing, i have attached a Image for the same.

Hi,

If i get a question to do some esxcli commands to gather infromation or status from ESXI for exampel. Do I need to save the commands and the output on a text file ? or Should keep the shell open and do not close it and use a new shell for the new question if there is ?

just came in my mind this question when I am testing in my lab.

Thank you

Hi

I have a vmware 5.1 cluster (2 ESX host and vcenter)

node1

node2

vcernter

Question :

I Must change DNS configuration (domain name and ip address of dns server)

I know how to change DNS configuration on the host

I know how to change DNS configuration on vcenter

HA is enabled and FT too.

If I change DNS config on ESX host, and after that I remove the host from vcernter and add the ESX host with newer fqdn in vcernter, All VM runnong on this host will continue to run, is correct ?

If I change DNS config in vcernter, no downtime or reboot needed, is correct ?

I already changed node1

Thank you for your help

Ce message a été modifié par : STEPHANE PURNELLE

皆様

お世話になります。

■環境
-------
・vCenter Server : 5.1.0
・VMwareESXi5.1.0 ×30台程度のクラスタ構成
・ストレージは NetAPP FAS3220A を使用
ESXiホストはNetApp上の一つNFS領域にマウントされています。

-------

上記環境にて、今年に入り十数回、ESXiホストとストレージの接続が断続的に失われて全パスがダウンする
現象（All Path Down）が発生していることが判明いたしました。
vCenterのイベントログには、下記のログがAPD発生時に記録されています。
(2015年は1回のみでした)

esx.problem.storage.apd.start
esx.clear.storage.apd.exit
com.vmware.vc.HA.HeartbeatDatastoreChanged

ESXi側のログは以下の様なメッセージが記録されています。
（※ESXiログはUTC表記）

ホストA 2016-03-15--04.18/var/run/log
vmkernel.log
+-----+-----+-----+-----+-----+-----+-----+-----+
2016-03-12T20:01:58.455Z cpu12:8204)StorageApdHandler: 248: APD Timer started for ident [ffa5674a-66b7bac5] 2016-03-12T20:01:58.455Z cpu12:8204)StorageApdHandler: 395: Device or filesystem with identifier [ffa5674a-66b7bac5] has entered the All Paths Down state.
2016-03-12T20:01:58.455Z cpu12:8204)StorageApdHandler: 846: APD Start for ident [ffa5674a-66b7bac5]!
2016-03-12T20:02:06.471Z cpu6:8198)NFSLock: 610: Stop accessing fd 0x410014240b28  3
：
2016-03-12T20:02:14.813Z cpu0:8224)NFSLock: 570: Start accessing fd 0x41000f3441f8 again 2016-03-12T20:02:16.541Z cpu12:8204)StorageApdHandler: 277: APD Timer killed for ident [ffa5674a-66b7bac5] 2016-03-12T20:02:16.541Z cpu12:8204)StorageApdHandler: 402: Device or filesystem with identifier [ffa5674a-66b7bac5] has exited the All Paths Down state.
2016-03-12T20:02:16.541Z cpu12:8204)StorageApdHandler: 902: APD Exit for ident [ffa5674a-66b7bac5]!
2016-03-12T20:32:11.504Z cpu14:8206)<4>hpsa 0000:02:00.0: Device:C4:B0:T0:L1 Command:0x85 CC:05/20/00 Illegal Request.
+-----+-----+-----+-----+-----+-----+-----+-----+

ホストB 2016-03-15--04.34/var/run/log
vmkernel.log
+-----+-----+-----+-----+-----+-----+-----+-----+
2016-03-12T20:01:58.544Z cpu12:8204)StorageApdHandler: 248: APD Timer started for ident [ffa5674a-66b7bac5] 2016-03-12T20:01:58.544Z cpu12:8204)StorageApdHandler: 395: Device or filesystem with identifier [ffa5674a-66b7bac5] has entered the All Paths Down state.
2016-03-12T20:01:58.544Z cpu12:8204)StorageApdHandler: 846: APD Start for ident [ffa5674a-66b7bac5]!
2016-03-12T20:02:05.548Z cpu24:8216)NFSLock: 610: Stop accessing fd 0x41000f34bff8  3
：
2016-03-12T20:02:18.128Z cpu10:8229)StorageApdHandler: 277: APD Timer killed for ident [ffa5674a-66b7bac5] 2016-03-12T20:02:18.128Z cpu10:8229)StorageApdHandler: 402: Device or filesystem with identifier [ffa5674a-66b7bac5] has exited the All Paths Down state.
2016-03-12T20:02:18.128Z cpu10:8229)StorageApdHandler: 902: APD Exit for ident [ffa5674a-66b7bac5]!
2016-03-12T20:31:43.569Z cpu14:8206)<4>hpsa 0000:02:00.0: Device:C4:B0:T0:L1 Command:0x85 CC:05/20/00 Illegal Request.
+-----+-----+-----+-----+-----+-----+-----+-----+

ホストC 2016-03-15--04.48/var/run/log
vmkernel.log
+-----+-----+-----+-----+-----+-----+-----+-----+
2016-03-12T19:53:06.359Z cpu26:8189097)ScsiDeviceIO: 2331: Cmd(0x4124403b9780) 0x4d, CmdSN 0x3d06 from world 9475 to dev "naa.600508b1001c29e307916da17839669b" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.
2016-03-12T20:02:01.100Z cpu12:8204)StorageApdHandler: 248: APD Timer started for ident [ffa5674a-66b7bac5] 2016-03-12T20:02:01.100Z cpu12:8204)StorageApdHandler: 395: Device or filesystem with identifier [ffa5674a-66b7bac5] has entered the All Paths Down state.
2016-03-12T20:02:01.100Z cpu12:8204)StorageApdHandler: 846: APD Start for ident [ffa5674a-66b7bac5]!
2016-03-12T20:02:14.124Z cpu28:8220)NFSLock: 610: Stop accessing fd 0x41000f358778  3
：
2016-03-12T20:02:19.026Z cpu28:8189094)NFSLock: 570: Start accessing fd 0x410014234aa8 again 2016-03-12T20:02:19.119Z cpu3:8195)StorageApdHandler: 277: APD Timer killed for ident [ffa5674a-66b7bac5] 2016-03-12T20:02:19.119Z cpu3:8195)StorageApdHandler: 402: Device or filesystem with identifier [ffa5674a-66b7bac5] has exited the All Paths Down state.
2016-03-12T20:02:19.119Z cpu3:8195)StorageApdHandler: 902: APD Exit for ident [ffa5674a-66b7bac5]!
2016-03-12T20:23:06.400Z cpu29:7334673)<4>hpsa 0000:02:00.0: Device:C4:B0:T0:L1 Command:0x85 CC:05/20/00 Illegal Request.
+-----+-----+-----+-----+-----+-----+-----+-----+

なお、ストレージ側には、ハードウェア障害は発生してないことが確認できており、
APDは、日によって、複数台のホストで発生することもあれば、1台のみで発生することもあります。

VMwareのナレッジベースに、確証がとれませんが、本事象と類似する以下記事がありました。
内容的には、ESXiホストのNFS.MaxQueueDepth の値を大幅に低くする、という内容です。

■ESXi 5.x における NetApp NFS ファイラ上の NFS 接続の問題
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2092909

上記状況を踏まえ、以下質問内容です。

・APDの発生が同時多発的ではなく、1台のみで発生することもある為、
NW機器やストレージ側ではなく、ESXi側にあると推測しています。
上記ナレッジベースのNFS.MaxQueueDepthの変更には、
ESXiホストの再起動等、実サービスの影響が伴うものでしょうか、
また、NFS.MaxQueueDepthは具体的にはどのようなパラメータかわかる方がいたら、ご教示頂けますでしょうか。

・APDの発生要因について、ストレージ、経路上のNW機器の問題以外に、
他にどのような原因があるか、わかる方がいましたら、ご教示頂けますでしょうか。

I had almost the same issue. Although mine was when using Value Expressions.

When you select the custom property and view the value expression / value list, if you have a long entry in there for some reason the display shows </BR> in. So if you copy from this view to notepad to edit the entry the copy will take the </BR> across, and then when you copy your new result back you end up actually copying </BR> into your new value.

In my case I just selected to edit the entry and copied the value from there, it then doesn't take over the </BR> value. Stupid I know, but whenever I view the value expression it shows the </BR> but if I select to edit the value and view the text that's actually in the property field then they don't appear. (unless I have mistakenly ccopied them there.

Hope this helps

I have an ESXi 5.5.0 build 1331820 setup, with(as yet) no vCenter and manage it with vSphere Client 5.5.0 1993072 in Windows. This works OK.

I've consulted the compatibility chart and vSphere client 6U2 should be able to manage my hosts and VMs.

If I try doing a clean install on a virgin PC it seems to install OK but when I try to connect I get the popup asking to d/l 'support files' from VMware,com, which then fails with a 404. (I gather this is a well known issue but I've not found any sensible way to resolve it.. any thoughts pls?)

If I do an upgrade on a system with 5.5.0 already installed, it starts in install but then fails and rolls back. Nothing sensible I can see in the windows logs. It claims to have been 'interrupted'...

I've tried both the above ideas on several machines and get consistent results. I've also checked the hash of the 6.0U2 download and it's OK.

Any pointers as to how to proceed would be very much appreciated.

TiA

David

hi,

everything went fine since using Win7 als VM on Linux since 1 Month. Suddenly Win7 won't start any longer: "machine in use".

Deleting all *.lck (even directory) had no effect. I moved "caches", but no success. First question when starting vmplayer

is always: "What to take ownership?".

A xubuntu 14.04 runs fine as VM on the same host. Only win7-prof won't start. A new vmem was

created once this morning. But then never again. I shut down xubuntu14.04, I stopped vmware rc-file,

I restartet vmware, I tried to start win7 only. No success, same error. I restarted xubuntu.

Very often no question "Take ownership .." appears. vmplayer just only starts a process that "hangs".

At command line start: no errors are reported.

Disk space is at 40% , some hundred gigabyte free.

vmware.log (the end:)

[...]

2016-09-01T11:14:41.044+02:00| vmx| I120: Successfully loaded worldswitch fault handlers from .switchNMI. Size = 128.

2016-09-01T11:14:41.044+02:00| vmx| I120: Successfully loaded worldswitch fault handlers from .switchNMI. Size = 128.

2016-09-01T11:14:41.044+02:00| vmx| I120: Successfully loaded worldswitch fault handlers from .switchNMI. Size = 128.

2016-09-01T11:14:41.044+02:00| vmx| I120: vmm64-modules: [vmm.vmm64, mmu-hwmmu.vmm64, vprobe-none.vmm64, hv-vt.vmm64, gphys-ept.vmm64, vmsafe-none.vmm64, callstack-none.vmm64, vmce-none.vmm64, vvtd-none.vmm64, ahci-ahci.vmm64, {SharedAreaReservations} .shared_per_vm_vmx:0x2ac0, {SharedInterVcpuVmxSection}, {SharedInterVcpuSection}, <MonSrcFile>, e1000Shared=0xfffffffffc0d4c00, ahciShared=0xfffffffffc0d4000, ahciRegs=0xfffffffffc0d3000, hvLoadedAsAddr=0x1, useNPTAsAddr=0x1, numVCPUsAsAddr=0x4, busmemFrameSizeLog2AsAddr=0x2, busmemFrameSizeAsAddr=0x4]

2016-09-01T11:14:41.044+02:00| vmx| I120: vmm64-vcpus: 4

2016-09-01T11:14:41.046+02:00| vmx| I120: KHZEstimate 3398368

2016-09-01T11:14:41.046+02:00| vmx| I120: MHZEstimate 3398

2016-09-01T11:14:41.046+02:00| vmx| I120: NumVCPUs 4

2016-09-01T11:14:41.046+02:00| vmx| I120: Guest OS (20497) not supported for replay debugging.

2016-09-01T11:14:41.047+02:00| vmx| I120: UUID: Unable to open /sys/firmware/efi/systab: No such file or directory

2016-09-01T11:14:41.047+02:00| vmx| I120: UUID: Found _DMI_ signature.

2016-09-01T11:14:41.047+02:00| vmx| I120: UUID: SMBIOS UUID is reported as 'fe e8 73 98 46 25 c3 99-e2 04 08 62 66 46 67 3e'.

2016-09-01T11:14:41.047+02:00| vmx| I120: UUID: location-UUID is 56 4d 93 52 19 f7 8f 23-40 eb 24 cc 2e de bb a2

2016-09-01T11:14:41.048+02:00| vmx| I120: AIOGNRC: numThreads=17 ide=0, scsi=1, passthru=0

2016-09-01T11:14:41.048+02:00| vmx| I120: WORKER: Creating new group with numThreads=17 (17)

2016-09-01T11:14:41.048+02:00| WT| I120: VTHREAD start thread 9 "WT" pid 23837

2016-09-01T11:14:41.048+02:00| vmx| A115: ConfigDB: Setting replay.supported = "FALSE"

2016-09-01T11:14:41.124+02:00| vmx| I120: StateLogger::Replay State = 0

2016-09-01T11:14:41.124+02:00| vmx| I120: StateLogger::minDEThreshold: 115

2016-09-01T11:14:41.124+02:00| vmx| A115: ConfigDB: Setting replay.filename = ""

2016-09-01T11:14:41.171+02:00| vmx| I120: WORKER: Creating new group with numThreads=1 (18)

2016-09-01T11:14:41.171+02:00| vmx| I120: MainMem: CPT Host WZ=0 PF=3072 D=0

2016-09-01T11:14:41.171+02:00| vmx| I120: MainMem: CPT PLS=1 PLR=1 BS=1 BlkP=32 Mult=4 W=50

2016-09-01T11:14:41.171+02:00| vmem| I120: VTHREAD start thread 10 "vmem" pid 23838

2016-09-01T11:14:41.171+02:00| vmem| I120: UUID: location-UUID is 56 4d 93 52 19 f7 8f 23-40 eb 24 cc 2e de bb a2

2016-09-01T11:14:41.171+02:00| vmx| I120: MainMem: Opened paging file, '/tmp/vmware-pc16/564d9352-19f7-8f23-40eb-24cc2edebba2/vmem' (swap).

2016-09-01T11:14:41.171+02:00| vmx| I120: MStat: Creating Stat vm.uptime

2016-09-01T11:14:41.171+02:00| vmx| I120: MStat: Creating Stat vm.suspendTime

2016-09-01T11:14:41.171+02:00| vmx| I120: MStat: Creating Stat vm.powerOnTimeStamp

2016-09-01T11:14:41.171+02:00| vmx| I120: VMXAIOMGR: Using: simple=Generic unbuf=Generic

2016-09-01T11:14:41.172+02:00| vmx| I120: WORKER: Creating new group with numThreads=1 (19)

2016-09-01T11:14:41.173+02:00| vmx| I120: WORKER: Creating new group with numThreads=16 (35)

2016-09-01T11:14:41.173+02:00| vmx| I120: MigrateResetStaleVMDBHostLog: Hostlog ./win7-prof64-b295f18f.hlog doesn't exist.

2016-09-01T11:14:41.173+02:00| vmx| I120: TimeTracker host to guest rate conversion 623768464 @ 3398368000Hz -> 0 @ 3398368000Hz

2016-09-01T11:14:41.173+02:00| vmx| I120: TimeTracker host to guest rate conversion ((x * 2147483648) >> 31) + -623768464

2016-09-01T11:14:41.173+02:00| vmx| I120: Disabling TSC scaling since host does not support it.

2016-09-01T11:14:41.173+02:00| vmx| I120: TSC offsetting enabled.

2016-09-01T11:14:41.173+02:00| vmx| I120: timeTracker.globalProgressMaxAllowanceMS: 2000

2016-09-01T11:14:41.173+02:00| vmx| I120: timeTracker.globalProgressToAllowanceNS: 1000

2016-09-01T11:14:41.173+02:00| vmx| A115: ConfigDB: Setting scsi0:0.redo = ""

2016-09-01T11:14:41.173+02:00| vmx| I120: DISK: OPEN scsi0:0 '/sda4/vmachines/win7-prof64/win7-prof64.vmdk' persistent R[]

2016-09-01T11:14:41.174+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [0]: "win7-prof64-s001.vmdk" (0x1a)

2016-09-01T11:14:41.174+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [1]: "win7-prof64-s002.vmdk" (0x1a)

2016-09-01T11:14:41.174+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [2]: "win7-prof64-s003.vmdk" (0x1a)

2016-09-01T11:14:41.174+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [3]: "win7-prof64-s004.vmdk" (0x1a)

2016-09-01T11:14:41.174+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [4]: "win7-prof64-s005.vmdk" (0x1a)

2016-09-01T11:14:41.174+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [5]: "win7-prof64-s006.vmdk" (0x1a)

2016-09-01T11:14:41.174+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [6]: "win7-prof64-s007.vmdk" (0x1a)

2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [7]: "win7-prof64-s008.vmdk" (0x1a)

2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [8]: "win7-prof64-s009.vmdk" (0x1a)

2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [9]: "win7-prof64-s010.vmdk" (0x1a)

2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [10]: "win7-prof64-s011.vmdk" (0x1a)

2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [11]: "win7-prof64-s012.vmdk" (0x1a)

2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [12]: "win7-prof64-s013.vmdk" (0x1a)

2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [13]: "win7-prof64-s014.vmdk" (0x1a)

2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [14]: "win7-prof64-s015.vmdk" (0x1a)

2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [15]: "win7-prof64-s016.vmdk" (0x1a)

2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [16]: "win7-prof64-s017.vmdk" (0x1a)

2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [17]: "win7-prof64-s018.vmdk" (0x1a)

2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [18]: "win7-prof64-s019.vmdk" (0x1a)

2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [19]: "win7-prof64-s020.vmdk" (0x1a)

2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [20]: "win7-prof64-s021.vmdk" (0x1a)

2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [21]: "win7-prof64-s022.vmdk" (0x1a)

2016-09-01T11:14:41.175+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [22]: "win7-prof64-s023.vmdk" (0x1a)

2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [23]: "win7-prof64-s024.vmdk" (0x1a)

2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [24]: "win7-prof64-s025.vmdk" (0x1a)

2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [25]: "win7-prof64-s026.vmdk" (0x1a)

2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [26]: "win7-prof64-s027.vmdk" (0x1a)

2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [27]: "win7-prof64-s028.vmdk" (0x1a)

2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [28]: "win7-prof64-s029.vmdk" (0x1a)

2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [29]: "win7-prof64-s030.vmdk" (0x1a)

2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-DSCPTR: Opened [30]: "win7-prof64-s031.vmdk" (0x1a)

2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-LINK : Opened '/sda4/vmachines/win7-prof64/win7-prof64.vmdk' (0x1a): twoGbMaxExtentSparse, 251658240 sectors / 120 GB.

2016-09-01T11:14:41.176+02:00| vmx| I120: DISKLIB-LIB : Opened "/sda4/vmachines/win7-prof64/win7-prof64.vmdk" (flags 0x1a, type twoGbMaxExtentSparse).

2016-09-01T11:14:41.176+02:00| vmx| I120: DiskGetGeometry: Reading of disk partition table

2016-09-01T11:14:41.176+02:00| vthread-10| I120: VTHREAD start thread 10 "vthread-10" pid 23839

2016-09-01T11:14:41.176+02:00| vmx| I120: DISK: Disk '/sda4/vmachines/win7-prof64/win7-prof64.vmdk' has UUID '60 00 c2 9e 63 06 32 cd-37 c7 f1 91 77 ce 3b 52'

2016-09-01T11:14:41.176+02:00| vmx| I120: DISK: OPEN '/sda4/vmachines/win7-prof64/win7-prof64.vmdk' Geo (15665/255/63) BIOS Geo (15665/255/63)

2016-09-01T11:14:41.224+02:00| vmx| I120: DISK: Opening disks took 50 ms.

2016-09-01T11:14:41.224+02:00| vmx| I120: SOCKET creating new socket, connecting to /var/run/vmware/usbarbitrator-socket

2016-09-01T11:14:41.224+02:00| vmx| I120: USB: Initializing 'Virtual Hub' backend

2016-09-01T11:14:41.224+02:00| vmx| I120: USB: Initializing 'Generic' backend

2016-09-01T11:14:41.224+02:00| vmx| I120: USB: Initializing 'Virtual HID' backend

2016-09-01T11:14:41.224+02:00| vmx| I120: USB: Initializing 'Remote Device' backend

2016-09-01T11:14:41.225+02:00| vmx| I120: RemoteUSBVMX: Retrieved hostId [fe e8 73 98 46 25 c3 99-e2 04 08 62 66 46 67 3e]

2016-09-01T11:14:41.225+02:00| vmx| I120: RemoteUSBVMX: Protocol version min:15 current:16

2016-09-01T11:14:41.225+02:00| vmx| I120: RemoteUSBVMX: no delay setting is TRUE.

2016-09-01T11:14:41.225+02:00| vmx| I120: USB: Initializing 'Virtual Mass Storage' backend

2016-09-01T11:14:41.225+02:00| vmx| I120: USB: Initializing 'Virtual CCID' backend

2016-09-01T11:14:41.225+02:00| vmx| I120: USB-CCID: dlopened default libpcsclite.so.1.

2016-09-01T11:14:41.225+02:00| vmx| I120: USB-CCID: Could not establish context: SCARD_E_NO_SERVICE(0x8010001d).

2016-09-01T11:14:41.225+02:00| vmx| W110: Could not initialize emulated USB smart card subsystem.

2016-09-01T11:14:41.225+02:00| vmx| I120: USB: Unable to initialize 'Virtual CCID' backend

2016-09-01T11:14:41.225+02:00| vmx| I120: USB: Initializing 'Virtual Bluetooth' backend

2016-09-01T11:14:41.225+02:00| vmx| I120: USB: Initializing 'Virtual Audio' backend

2016-09-01T11:14:41.225+02:00| vmx| I120: USB: Initializing 'Virtual Video' backend

2016-09-01T11:14:41.227+02:00| vmx| I120: MKS PowerOn

2016-09-01T11:14:41.227+02:00| mks| I120: VTHREAD start thread 2 "mks" pid 23840

2016-09-01T11:14:41.227+02:00| mks| I120: MKS thread is alive

2016-09-01T11:14:41.227+02:00| mks| I120: MKS-RenderMain: RenderMain: PowerOn allowed 0 1 0 1 0

2016-09-01T11:14:41.227+02:00| mks| I120: MKS-RenderMain: Collecting RenderOps caps...

2016-09-01T11:14:41.231+02:00| mks| I120: Printing loaded objects

2016-09-01T11:14:41.231+02:00| mks| I120: [0x400000-0x113560C): /usr/lib/vmware/bin/vmware-vmx

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FFF5D3FF000-0x7FFF5D3FF890): <no name>

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7ABD3A000-0x7FF7ABD8D780): /lib64/libm.so.6

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7ABB36000-0x7FF7ABB37E78): /lib64/libdl.so.2

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AB91A000-0x7FF7AB930000): /lib64/libpthread.so.0

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AB711000-0x7FF7AB7180BC): /lib64/librt.so.1

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AB3D5000-0x7FF7AB50AA84): /usr/lib64/libX11.so.6

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AB1CE000-0x7FF7AB1D2E34): /usr/lib64/libXtst.so.6

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AAFBC000-0x7FF7AAFCCB1C): /usr/lib64/libXext.so.6

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AADB1000-0x7FF7AADB9E34): /usr/lib64/libXcursor.so.1

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AABAB000-0x7FF7AABAFA0C): /usr/lib64/libXfixes.so.3

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AA9A8000-0x7FF7AA9A9824): /usr/lib64/libXinerama.so.1

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AA79E000-0x7FF7AA7A6BEC): /usr/lib64/libXrender.so.1

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AA593000-0x7FF7AA59BDEC): /usr/lib64/libXi.so.6

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AA37D000-0x7FF7AA390F94): /lib64/libz.so.1

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7AA166000-0x7FF7AA17B474): /lib64/libgcc_s.so.1

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7A9E0B000-0x7FF7A9F5BC00): /lib64/libc.so.6

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7ABF8F000-0x7FF7ABFAC1F0): /lib64/ld-linux-x86-64.so.2

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7A9BEE000-0x7FF7A9C08E7C): /usr/lib64/libxcb.so.1

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7A99EA000-0x7FF7A99EBE2C): /usr/lib64/libXau.so.6

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7A8AFE000-0x7FF7A8C96314): /usr/lib/vmware/lib/libcrypto.so.1.0.1/libcrypto.so.1.0.1

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7A8897000-0x7FF7A88F3DAC): /usr/lib/vmware/lib/libssl.so.1.0.1/libssl.so.1.0.1

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7A868E000-0x7FF7A86951CC): /usr/lib64/libnuma.so.1

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF7A7A1A000-0x7FF7A7A1A980): /lib64/libaio.so.1

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF6E5FF3000-0x7FF6E60979D5): /usr/lib64/libGL.so.1

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF6E4B96000-0x7FF6E5A60B04): /usr/lib64/libGLcore.so.1

2016-09-01T11:14:41.231+02:00| mks| I120: [0x7FF6E4A94000-0x7FF6E4A94DD0): /usr/lib64/tls/libnvidia-tls.so.1

2016-09-01T11:14:41.231+02:00| mks| I120: End printing loaded objects

2016-09-01T11:14:41.258+02:00| mks| I120: MKS-X: XI major version 1, minor version 4

2016-09-01T11:14:41.271+02:00| mks| I120: GLHostX11: DISPLAY: "localhost:10.0" only supports GLX 1.2, GLBE requires GLX 1.3 or higher.

2016-09-01T11:14:41.301+02:00| mks| I120: GLHostX11: DISPLAY: "localhost:10.0" only supports GLX 1.2, GLBE requires GLX 1.3 or higher.

2016-09-01T11:14:41.308+02:00| mks| I120: GLHostX11: Created context with GL 2.1, core: 0, robust: 0

The error "GLBE requires GLX 1.3 or higher" was no problem so far. Win7 started perfectly.

BTW: Host ist Suse 11.2,  2.6.31.5-0.1-desktop, no other host system possible due to a commercial program.

vmware-0.log

===========

[...]

2016-09-01T11:09:45.061+02:00| vmx| I120: CPU4: PMC: IA32, Nehalem-C or later PMC: smmFrz (hw): (1)

2016-09-01T11:09:45.061+02:00| vmx| I120:  [c:0 f:1 e:0]

2016-09-01T11:09:45.061+02:00| vmx| I120: CPU5: PMC: IA32, Nehalem-C or later PMC: smmFrz (hw): (1)

2016-09-01T11:09:45.061+02:00| vmx| I120:  [c:0 f:1 e:0]

2016-09-01T11:09:45.061+02:00| vmx| I120: CPU6: PMC: IA32, Nehalem-C or later PMC: smmFrz (hw): (1)

2016-09-01T11:09:45.061+02:00| vmx| I120:  [c:0 f:1 e:0]

2016-09-01T11:09:45.061+02:00| vmx| I120: CPU7: PMC: IA32, Nehalem-C or later PMC: smmFrz (hw): (1)

2016-09-01T11:09:45.061+02:00| vmx| I120:  [c:0 f:1 e:0]

2016-09-01T11:09:45.061+02:00| vmx| I120: MONITOR MODE: allowed modes          : BT32 HV HWMMU

2016-09-01T11:09:45.061+02:00| vmx| I120: MONITOR MODE: user requested modes   : BT32 HV HWMMU

2016-09-01T11:09:45.061+02:00| vmx| I120: MONITOR MODE: guestOS preferred modes: HWMMU HV BT32

2016-09-01T11:09:45.061+02:00| vmx| I120: MONITOR MODE: filtered list          : HWMMU HV BT32

2016-09-01T11:09:45.061+02:00| vmx| I120: HV Settings: virtual exec = 'hardware'; virtual mmu = 'hardware'

2016-09-01T11:09:45.065+02:00| vmx| I120: OvhdMem_PowerOn: initial admission: paged   569118 nonpaged     6073 anonymous     9947

2016-09-01T11:09:45.065+02:00| vmx| I120: VMMEM: Initial Reservation: 2285MB (MainMem=3072MB)

2016-09-01T11:09:45.065+02:00| vmx| I120: MemSched_PowerOn: balloon minGuestSize 209715 (80% of min required size 262144)

2016-09-01T11:09:45.065+02:00| vmx| I120: MemSched: reserved mem (in MB) min 128 max 6972 recommended 6972

2016-09-01T11:09:45.065+02:00| vmx| I120: MemSched: pg 569118 np 6073 anon 9947 mem 786432

2016-09-01T11:09:45.065+02:00| vmx| I120: MemSched: numvm 2 locked pages: num 399485 max 1768448

2016-09-01T11:09:45.065+02:00| vmx| I120: MemSched: locked Page Limit: host 1975122 config 1784832 dynam -1

2016-09-01T11:09:45.065+02:00| vmx| I120: MemSched: minmempct 50 minalloc 302522 admitted 1

2016-09-01T11:09:45.065+02:00| vmx| W110: NUMA: automatic VM sizing request ignored

2016-09-01T11:09:45.065+02:00| vmx| I120: Host: Disabling thread priority boosting to work around Linux SMP bug.

2016-09-01T11:09:45.065+02:00| vmx| I120: MsgHint: msg.hostposix.othervms

2016-09-01T11:09:45.065+02:00| vmx| I120+ It appears that other virtual machines are running. Some host devices may be unavailable to this virtual machine. Some host devices (such as CD-ROM drives) may be shared among several virtual machines by toggling the entries in the "VM > Removable Devices" menu.

2016-09-01T11:09:45.065+02:00| vmx| I120+ Select OK to continue, Cancel to power off.

2016-09-01T11:09:45.065+02:00| vmx| I120+ ---------------------------------------

2016-09-01T11:09:49.296+02:00| vmx| I120: Module Host power on failed.

2016-09-01T11:09:49.296+02:00| vmx| I120: VMX_PowerOn: ModuleTable_PowerOn = 0

2016-09-01T11:09:49.298+02:00| vmx| I120: Vix: [22455 mainDispatch.c:4291]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0

2016-09-01T11:09:49.300+02:00| vmx| I120: Vix: [22455 mainDispatch.c:4291]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0

2016-09-01T11:09:49.300+02:00| vmx| I120: Transitioned vmx/execState/val to poweredOff

2016-09-01T11:09:49.300+02:00| vmx| I120: Vix: [22455 mainDispatch.c:4291]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=0 additionalError=0

2016-09-01T11:09:49.300+02:00| vmx| I120: Vix: [22455 mainDispatch.c:4330]: Error VIX_E_FAIL in VMAutomation_ReportPowerOpFinished(): Unknown error

2016-09-01T11:09:49.303+02:00| vmx| I120: Vix: [22455 mainDispatch.c:4291]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0

2016-09-01T11:09:49.303+02:00| vmx| I120: Transitioned vmx/execState/val to poweredOff

2016-09-01T11:09:49.303+02:00| vmx| I120: VMIOP: Exit

2016-09-01T11:09:49.304+02:00| vmx| I120: Vix: [22455 mainDispatch.c:842]: VMAutomation_LateShutdown()

2016-09-01T11:09:49.304+02:00| vmx| I120: Vix: [22455 mainDispatch.c:792]: VMAutomationCloseListenerSocket. Closing listener socket.

2016-09-01T11:09:49.305+02:00| vmx| I120: Flushing VMX VMDB connections

2016-09-01T11:09:49.306+02:00| vmx| I120: VmdbDbRemoveCnx: Removing Cnx from Db for '/db/connection/#1/'

2016-09-01T11:09:49.306+02:00| vmx| I120: VmdbCnxDisconnect: Disconnect: closed pipe for pub cnx '/db/connection/#1/' (0)

2016-09-01T11:09:49.306+02:00| vmx| I120: VigorTransport_ServerDestroy: server destroyed.

2016-09-01T11:09:49.308+02:00| vmx| I120: VMX exit (0).

2016-09-01T11:09:49.308+02:00| vmx| I120: OBJLIB-LIB: ObjLib cleanup done.

2016-09-01T11:09:49.308+02:00| vmx| I120: FileTrack_Exit: done

xubuntu14.04 starts automatically at boot time using Vix .... . But does it have some effekt to Win7?

Memory is rare, I kow, but at the moment 4 GB is free and Win7 gets 3072 MB, that was enough so far:

#!/usr/bin/vmware

.encoding = "ISO-8859-1"

config.version = "8"

virtualHW.version = "11"

numvcpus = "4"

cpuid.coresPerSocket = "4"

scsi0.present = "TRUE"

scsi0.virtualDev = "lsisas1068"

sata0.present = "TRUE"

memsize = "3072"

mem.hotadd = "TRUE"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "win7-prof64.vmdk"

sata0:1.present = "TRUE"

sata0:1.fileName = "/dev/sr0"

sata0:1.deviceType = "cdrom-raw"

ethernet0.present = "TRUE"

ethernet0.virtualDev = "e1000"

ethernet0.wakeOnPcktRcv = "FALSE"

ethernet0.addressType = "generated"

usb.present = "TRUE"

usb.generic.autoconnect = "FALSE"

ehci.pciSlotNumber = "-1"

mks.enable3d = "TRUE"

svga.graphicsMemoryKB = "262144"

pciBridge0.present = "TRUE"

pciBridge4.present = "TRUE"

pciBridge4.virtualDev = "pcieRootPort"

pciBridge4.functions = "8"

pciBridge5.present = "TRUE"

pciBridge5.virtualDev = "pcieRootPort"

pciBridge5.functions = "8"

pciBridge6.present = "TRUE"

pciBridge6.virtualDev = "pcieRootPort"

pciBridge6.functions = "8"

pciBridge7.present = "TRUE"

pciBridge7.virtualDev = "pcieRootPort"

pciBridge7.functions = "8"

vmci0.present = "TRUE"

hpet0.present = "TRUE"

displayName = "win7-prof64"

guestOS = "windows7-64"

nvram = "win7-prof64.nvram"

virtualHW.productCompatibility = "hosted"

gui.exitOnCLIHLT = "TRUE"

powerType.powerOff = "soft"

powerType.powerOn = "soft"

powerType.suspend = "soft"

powerType.reset = "soft"

extendedConfigFile = "win7-prof64.vmxf"

uuid.bios = "56 4d 93 52 19 f7 8f 23-40 eb 24 cc 2e de bb a2"

uuid.location = "56 4d 93 52 19 f7 8f 23-40 eb 24 cc 2e de bb a2"

replay.supported = "FALSE"

replay.filename = ""

migrate.hostlog = "./win7-prof64-b295f18f.hlog"

scsi0:0.redo = ""

ethernet0.connectionType = "bridged"

ethernet0.startConnected = "TRUE"

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

scsi0.pciSlotNumber = "160"

usb.pciSlotNumber = "32"

ethernet0.pciSlotNumber = "33"

vmci0.pciSlotNumber = "34"

sata0.pciSlotNumber = "35"

scsi0.sasWWID = "50 05 05 62 19 f7 8f 20"

ethernet0.generatedAddress = "00:0C:29:DE:BB:A2"

ethernet0.generatedAddressOffset = "0"

vmci0.id = "786348962"

monitor.phys_bits_used = "42"

vmotion.checkpointFBSize = "8388608"

vmotion.checkpointSVGAPrimarySize = "33554432"

cleanShutdown = "FALSE"

softPowerOff = "TRUE"

usb:1.speed = "2"

usb:1.present = "TRUE"

usb:1.deviceType = "hub"

usb:1.port = "1"

usb:1.parent = "-1"

sata0:1.autodetect = "FALSE"

toolsInstallManager.updateCounter = "1"

tools.syncTime = "TRUE"

unity.wasCapable = "FALSE"

svga.guestBackedPrimaryAware = "TRUE"

checkpoint.vmState = ""

sound.present = "FALSE"

serial0.present = "FALSE"

floppy0.present = "FALSE"

usb:0.present = "TRUE"

usb:0.deviceType = "hid"

usb:0.port = "0"

usb:0.parent = "-1"

[...]

tia

Eckard

Hi,

We are about to change the vCenter certificate from self-signed to a official certificate. We haven't been able to find information of what, if any, consequences changing the certificate have for other services like vRealize Operations Manager and vRealize Automation. Do we have to reconnect those services with vCenter? When we upgraded vCenter to 6.x we lost all historical data in Operations, any chance that will happen again?

Any insight and information regarding this will be greatly appreciated.

Thanks in advance.

GB

Note that the product page

Mac Virtualization for Everyone: VMware Fusion

Lists both:

"

Guest Operating Systems

More than 200 operating systems are supported, including:

[...]

• Mac OS X 10.6 Snow Leopard
• Mac OS X 10.6 Snow Leopard Server

"

So if that's in error, it's a prominently displayed one, though you're right, I missed the "Variants" entry....

From other searches, I understand this to be a holdover from Apple's earlier licensing policy forbidding virtual copies.  My particular case (actually my girlfriend's...it's her machine) is that Apple itself can't come up with a published version or a copy of the bundled install disk for Macbook 6,2 which has hardware issues only resolved in 10.6.8 (which is not a published install dvd release, but an update to the published 10.6.3.)  Hours have been sent with Applecare...they actually tried but they couldn't come up with anything.  In other words, even though the hardware shipped with OS X 10.6, Apple is unable to provide a 10.6 install dvd that will install to it.  The use case is one copy, since the host will not run this and the point is only to run some legacy PPC apps on the most recent OS that will run them...i.e. one copy on one machine, in full compliance with Apple's older restrictive licensing terms.

VMWare ESXi 6.0.0: jak zmniejszyć rozmiar dysku wirtualnego?

Mam maszynę wirtualną na bazie systemu Windows, czy wystarczy użyć opcji "zmniejsz wolumin" w Zarządzaniu dyskami?

Can anyone confirm if this is still true?  HTTP-REST plugin version 1.0.8 on vCO5.5.3, I am trying to use proxy setting to add a host and consistently failing on remote host's cert validation step. This connection uses SSL.

Thanks.

こんにちは。

NFS.MaxQueueDepth についてですが、

ESXi 5.1 の環境が手元になかったので ESXi 6.0の環境ですが、説明（Description）を見ると

NFSボリューム（NFSデータストア）あたりでIOコマンドを受け付けるキューの深さ（コマンド数）を設定するパラメータのようです。

[root@hv-i22:~] vmware -vl

VMware ESXi 6.0.0 build-4192238

VMware ESXi 6.0.0 Update 2

[root@hv-i22:~] esxcli system  settings advanced list -o /NFS/MaxQueueDepth

   Path: /NFS/MaxQueueDepth

   Type: integer

   Int Value: 4294967295

   Default Int Value: 4294967295

   Min Value: 1

   Max Value: 4294967295

   String Value:

   Default String Value:

   Valid Characters:

   Description: Maximum per-Volume queue depth

NFS.MaxQueueDepth の設定変更についてですが、KBでは下記のように記載があります。

変更を有効にするために、ホストを再起動します。

設定変更ではESXiの再起動が必要なので、vMotionでVMを対比するか、VMをシャットダウンが必要になります。

ただし、Storage I/O Control  が利用可能（Enterprise Plusライセンス）であれば、

Storage I/O Control  を有効化するだけで、上記のパラメータ設定変更が不要になるのでESXiの再起動は不要になるはずです。

APDの発生要因についてですが、

もし特定のESXiだけで発生するようであれば、下記のあたりも確認してみるとよいと思いました。

• VMのワークロード
  • そのホストだけDisk I/O負荷が高かったりしないか。
    ※キューを絞ると改善する問題なので、I/O負荷が極端に高いVMがいないか。
• 物理スイッチ側
  • ESXiの物理NICが接続されている、物理スイッチポート側でエラーカウンタが上がっていないか。
• ESXiホストのHW
  • HW的に構成に差異がないか？ 問題ないサーバと同じモデルのサーバ？
  • NICがハードウェア的に故障していなそうか。（たとえばサーバの管理ボードなどでステータスを見てみるとか・・・）
• ESXiのソフトウェア
  • ESXi の物理NICでパケットドロップが発生していたり、エラーカウンタが上がっていないか。
  • ESXiのバージョン（Build）に違いがないか。
  • NICのドライバがそのESXiだけ違ったりしないか。
  • ESXiで不審なログが出ていないか・・・

以上です。ご参考まで・・・

ただ、VMware プロダクトサポートにSRしたほうがよいかもしれません。

i too am having this issue. Any help would be much appreciated!

i can't find anything on google in relation to this. this was the only thing i found and the question hasn't been answered....

~sigh~

So this appears to be an issue with all deploys now.  Not sure what changed or how to fix it.  I can't get the vRA agent to initialize and label the disks at deploy.   Anyone come across this before?