Is it possible to have 3 nodes separated in 3 datacenters with VSAN ?

so every datacenters would contain

1 node

2 x 10 gbit switch

1 UPS

I have now a 3 node cluster in 1 datacenter but would like to spread them over 3 datacenters.

For me it looks the same as running them in one datacenter.

Correct ?? or what am I not seeing ???

Hello. Workstation 12.5.4. I have esxi6.5 and vCenter 6.5 all nested. When I go to run a VM within ESXi (even vCenter), it wont power on, hanging at some random point with an error in the events "Running VMware ESX in a virtual machine will result in degraded performance. Do you want to continue?". Obviously no way of answering this (I believe in 6.0 and earlier you could use the C# client but that's not there anymore in 6.5).

It was working for me real nice (I think until the update, or it may have been esxi 6.5). Any ideas?

Thanks

Hey all, was curious if the new Kaby lake processor supports Virtualized performance counters. 've been having some difficulties getting Mozilla's "rr" to run inside of a VMware Linux guest on a new laptop. Here's a more indepth summary:

• Got a work new laptop with a Kaby lake processor (Intel Core i7-7700HQ 2.60Ghz), and needed to clone a Linux VM that had my environment on it.
• rr was working great inside of the previous laptop (Skylake i7-6700HQ)
• The "Virtualize CPU Performance Counters" checkbox had to be turned off in the new laptop or else it wouldn't boot:
  • Error Message: Virtualized performance counters are not supported on the host CPU type. Module 'VPMC' power on failed. Failed to start the virtual machine'
• Error message from 'rr':
  • # rr record ls rr:
  • Saving execution to trace directory `/root/.local/share/rr/ls-3'. [FATAL /root/gitstuff/rr/src/PerfCounters.cc:271:start_counter() errno: ENOENT] Unable to open performance counter with 'perf_event_open'; are perf events enabled? Try 'perf record'. Aborted
    • `strace` error: perf_event_open(0x7ffe5a41bde0, 0, -1, -1, 0) = -1 ENOENT (No such file or directory)
• But perf record works fine:
  • # perf record ls
  • perf record: Woken up 1 times to write data ] [ perf record: Captured and wrote 0.014 MB perf.data (~596 samples) ]
• It's a Dell XPS 15 Touch. Checked my BIOS settings and there doesn't seem to be any more virtualization options that I can turn on

Granted, this is probably just because the "Virtualize CPU Perfomance Counters" checkbox is not checked, maybe I just didn't see an option in the BIOS.

Any help would be greatly appreciated, thanks!

VMware vSphere 6 не видит жесткий диск ,решил собрать небольшой сервак на пк но возникла проблема не видит сата жд кто может подсказать в деталях что делать?

Hi,

The virtual machine cannot display the output in the absence of an external monitor,  if the external monitor is connected to the notebook, then the virtual machine display output is normal.

My notebook is MacBook Pro(2016), OS is Sierra 10.12.4, Fusion version is 8.5.6.

Has anyone ever had this problem?

Why the host device is showing no status. It should show the VMFS file path to its directory ?

Hello,

I'm trying to install updates from a zip file but always gives the same error. "No Space Left On Device"

But there is a plenty of space on Device.

When i try to run

esxcli software vib update -d /vmfs/volumes/datastore1/ESXi600-201703001.zip

it gives that error:

[InstallationError]

[Errno 28] No space left on device

       vibs = VMware_bootbank_misc-drivers_6.0.0-3.57.5050593

Please refer to the log file for more details.

And in the log file:

2017-04-02T00:13:50Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = 'localcli system visorfs ramdisk list |            grep /stagebootbank &&            localcli system visorfs ramdisk remove -t /tmp/stagebootbank', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2017-04-02T00:13:50Z esxupdate: BootBankInstaller.pyc: WARNING: Cannot remove staging directory: [Errno 16] Device or resource busy: '/tmp/stagebootbank'

2017-04-02T00:13:50Z esxupdate: vmware.runcommand: INFO: runcommand called with: args = 'localcli system visorfs ramdisk list |            grep /stagebootbank &&            localcli system visorfs ramdisk remove -t /tmp/stagebootbank', outfile = 'None', returnoutput = 'True', timeout = '0.0'.

2017-04-02T00:13:51Z esxupdate: root: ERROR: Traceback (most recent call last):

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 462, in <module>

2017-04-02T00:13:51Z esxupdate: root: ERROR:     main()

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 453, in main

2017-04-02T00:13:51Z esxupdate: root: ERROR:     ret = CMDTABLE[command](options)

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 362, in VibInstallCmd

2017-04-02T00:13:51Z esxupdate: root: ERROR:     checkacceptance=checkacceptance)

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/Transaction.py", line 250, in InstallVibsFromSources

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/Transaction.py", line 356, in _installVibs

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/Transaction.py", line 399, in _validateAndInstallProfile

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/HostImage.py", line 710, in Stage

2017-04-02T00:13:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-3620759/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/site-packages/vmware/esximage/HostImage.py", line 483, in _download_and_stage

2017-04-02T00:13:51Z esxupdate: root: ERROR: InstallationError: ('VMware_bootbank_vsanhealth_6.0.0-3000000.3.0.3.58.5224738', '[Errno 28] No space left on device')

"vdf -h" Output

Ramdisk                   Size      Used Available Use% Mounted on

root                       32M      244K       31M   0% --

etc                        28M      204K       27M   0% --

opt                        32M        0B       32M   0% --

var                        48M      428K       47M   0% --

tmp                       256M       20K      255M   0% --

iofilters                  32M        0B       32M   0% --

hostdstats                303M        2M      300M   0% --

As you can see %0 is used on /tmp i dont know why gives that error.

How can i fix this problem ? I cant update my esxi 3620759 to 5224934.

Hi guys,

i am wondering the difference between vCenter Standard and VCenter Standard for Horizon

As i see in my download section:

In the vCenter for Horizon Tab the Version 6.0.0B ist Show as the last one.

In vCenter Standard i see the 6.5 as the last Version.

So... i noticed that the VMware download Website is sometime not full up to date and you have to search for the "real" latest version.

Can i use the standard 6.5 for my horizon environment or do i need to download the 6.0.0B Version from the horizon section?

Since updating to macOS 10.12.4, most of the VMs in VMWare Fusion 8.5.5 start/resume with black/blank screen. I can SSH into the VM and they seem functional, but nothing is rendering in most of these VMs.

Hi，

Will the refresh and recompose activities impact the Windows and Office Product Activation inside the desktop virtual machines ? Will these cause to lost the activiation information ?

Please see the snapshot given below;

d

any suggestion will be appreciated....

Thanks..

This is in a VDI environment and the users have the horizon view client 4.3.0.

Hi All,

On my VMware Workstation pro 12 I have setup NSX lab

for my esxi VM's (created on VM Workstation) I have changed the default NICS to vmxnet3

I am able to ping VTEP's between esxi05 and esxi07 from vmkping command

I have attached snapshot for VTEP's configured

However when I try to test the connectivity from the GUI it fails

Is there a way to specify the TCP/IP stack to use for below window

Any suggestions why this might be failing

Thanks

Hello All,

I have two desktop’s at my place for home lab. Let’s call them new-desktop and old-desktop

Old-desktop boots from pen drive which has which ESXi 6 installed on it

New-desktop has windows 7 as base OS. I am running VMware Workstation 12 and have configured my lab in it.

On new-desktop in Workstation I have created a Widows 2003 DHCP machine/VM

Old-desktop and new-desktop are connected to connected to Huawei router (this has been given to me by my ISP)

old-desktop when it boots up always gets the IP (192.168.0.xx) from Huawei router instead of getting IP (10.1.1.xx) from DHCP windows server (running on new-desktop as a VM in Workstation)

I would like my old-desktop to get DHCP IP from DHCP Server (windows 2003) running on new-desktop in Workstation 12 as a VM and not from Huawei router

Please suggest what settings I need to change or view here

Thanks in advance

Hi Community,

I have been problems with my host ESXi when migrations task are executed, I have two error:

Loss of upper network link redundancy

Insufficient failover resources

Please your comments

Hi, folks. I have some issues with esxi 6.5, i.e. can't start vm after adding passthoug pci device 8 Series/C220 Series Chipset Family USB EHCI. It crashes couple seconds after start, but grub is working... Any ideas? HW - HP proliant gen 6 dl320e

esxi log:

2017-04-01T18:29:10.777Z| vcpu-0| I125: UHCI: HCReset

2017-04-01T18:29:11.277Z| vcpu-1| I125: UHCI: HCReset

2017-04-01T18:29:11.587Z| vmx| E105: PANIC: PCI passthru device 0000:00:1a.0 caused an IOMMU fault type 12 at address 0x350aa000.  Powering off the virtual machine.  If the problem persists please contact the device's vendor.A core file is available in "/vmfs/volumes/5896268d-375f0480-af0f-6451060dad88/wifi_sms/vmx-zdump.002"

2017-04-01T18:29:12.264Z| mks| W115: Panic in progress... ungrabbing

2017-04-01T18:29:12.264Z| mks| I125: MKS: Release starting (Panic)

2017-04-01T18:29:12.264Z| mks| I125: MKS: Release finished (Panic)

2017-04-01T18:29:12.269Z| vmx| I125: Writing monitor file `vmmcores.gz`

2017-04-01T18:29:12.269Z| vmx| W115: Dumping core for vcpu-0

2017-04-01T18:29:12.269Z| vmx| I125: CoreDump: dumping core with superuser privileges

2017-04-01T18:29:12.269Z| vmx| I125: VMK Stack for vcpu 0 is at 0x439149c93000

2017-04-01T18:29:12.269Z| vmx| I125: Beginning monitor coredump

2017-04-01T18:29:12.690Z| vmx| I125: End monitor coredump

2017-04-01T18:29:12.690Z| vmx| W115: Dumping core for vcpu-1

2017-04-01T18:29:12.690Z| vmx| I125: CoreDump: dumping core with superuser privileges

2017-04-01T18:29:12.690Z| vmx| I125: VMK Stack for vcpu 1 is at 0x439149e13000

2017-04-01T18:29:12.690Z| vmx| I125: Beginning monitor coredump

2017-04-01T18:29:13.099Z| vmx| I125: End monitor coredump

2017-04-01T18:29:13.260Z| mks| W115: Panic in progress... ungrabbing

2017-04-01T18:29:13.260Z| mks| I125: MKS: Release starting (Panic)

2017-04-01T18:29:13.260Z| mks| I125: MKS: Release finished (Panic)

2017-04-01T18:29:13.375Z| vmx| I125: Printing loaded objects

2017-04-01T18:29:13.375Z| vmx| I125: [0x4EEF331000-0x4EF03E737C): /bin/vmx

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F309E1000-0x4F309F8448): /lib64/libpthread.so.0

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F30BFE000-0x4F30BFFF00): /lib64/libdl.so.2

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F30E02000-0x4F30E0AF9C): /lib64/librt.so.1

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F3101E000-0x4F312B31C4): /lib64/libcrypto.so.1.0.2

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F314E4000-0x4F3154CB1C): /lib64/libssl.so.1.0.2

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F31758000-0x4F3186C4DC): /lib64/libX11.so.6

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F31A73000-0x4F31A8201C): /lib64/libXext.so.6

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F31C83000-0x4F31D67341): /lib64/libstdc++.so.6

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F31F86000-0x4F32005DA4): /lib64/libm.so.6

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F32208000-0x4F3221CBC4): /lib64/libgcc_s.so.1

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F3241E000-0x4F3257EDD4): /lib64/libc.so.6

2017-04-01T18:29:13.375Z| vmx| I125: [0x4EF07C0000-0x4EF07DD7D8): /lib64/ld-linux-x86-64.so.2

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F32789000-0x4F327A3634): /lib64/libxcb.so.1

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F329A5000-0x4F329A695C): /lib64/libXau.so.6

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F32F75000-0x4F3300A4B4): /usr/lib64/vmware/plugin/objLib/upitObjBE.so

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F33223000-0x4F33378F64): /usr/lib64/vmware/plugin/objLib/vsanObjBE.so

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F33610000-0x4F33624F94): /lib64/libz.so.1

2017-04-01T18:29:13.375Z| vmx| I125: [0x4F33A6F000-0x4F33A7A1D0): /lib64/libnss_files.so.2

2017-04-01T18:29:13.375Z| vmx| I125: End printing loaded objects

2017-04-01T18:29:13.375Z| vmx| I125: Backtrace:

2017-04-01T18:29:13.375Z| vmx| I125: Backtrace[0] 000003299a402160 rip=0000004eef9aaaa7 rbx=0000004eef9aa5a0 rbp=000003299a402180 r12=0000000000000000 r13=0000000000000001 r14=0000000000000000 r15=0000000000000000

2017-04-01T18:29:13.375Z| vmx| I125: Backtrace[1] 000003299a402190 rip=0000004eef4efa8c rbx=000003299a4021b0 rbp=000003299a402690 r12=0000004ef063fb70 r13=0000000000000001 r14=0000000000000000 r15=0000000000000000

2017-04-01T18:29:13.375Z| vmx| I125: Backtrace[2] 000003299a4026a0 rip=0000004eef5ede99 rbx=000003299a4026e0 rbp=000003299a4026b0 r12=0000004eef5edcb0 r13=0000004ef0d17070 r14=0000000000000000 r15=0000000000000000

2017-04-01T18:29:13.375Z| vmx| I125: Backtrace[3] 000003299a4026c0 rip=0000004eef59dcc4 rbx=000003299a4026e0 rbp=000003299a402910 r12=0000004eef5edcb0 r13=0000004ef0d17070 r14=0000000000000000 r15=0000000000000000

2017-04-01T18:29:13.375Z| vmx| I125: Backtrace[4] 000003299a402920 rip=0000004eef4ea33c rbx=0000004f32baa010 rbp=000003299a4029b0 r12=0000004ef0d1a430 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000

2017-04-01T18:29:13.375Z| vmx| I125: Backtrace[5] 000003299a4029c0 rip=0000004eef4ea953 rbx=000003299a402a10 rbp=000003299a405a60 r12=0000000000000001 r13=0000000000000000 r14=0000000000000007 r15=0000000000000001

2017-04-01T18:29:13.375Z| vmx| I125: Backtrace[6] 000003299a405a70 rip=0000004eef4eade2 rbx=00000000000003da rbp=000003299a405b30 r12=0000004f32baa010 r13=0000004ef0d4c210 r14=0000004ef0d4c2f0 r15=0000000000000000

2017-04-01T18:29:13.375Z| vmx| I125: Backtrace[7] 000003299a405b40 rip=0000004eef4f0590 rbx=0000004ef063fba0 rbp=000003299a405c60 r12=0000004ef0d17070 r13=0000004ef0b60190 r14=0000000000000000 r15=0000004ef0b60190

2017-04-01T18:29:13.375Z| vmx| I125: Backtrace[8] 000003299a405c70 rip=0000004eef4e3ca6 rbx=0000000000000003 rbp=000003299a405cf0 r12=0000000000000000 r13=0000004eeff6fb11 r14=0000004ef03e9c80 r15=0000000000000000

2017-04-01T18:29:13.375Z| vmx| I125: Backtrace[9] 000003299a405d00 rip=0000004f3243e8cd rbx=0000000000000000 rbp=0000000000000000 r12=0000004eef4e4618 r13=000003299a405dd0 r14=0000000000000000 r15=0000000000000000

2017-04-01T18:29:13.375Z| vmx| I125: Backtrace[10] 000003299a405dc0 rip=0000004eef4e4641 rbx=0000000000000000 rbp=0000000000000000 r12=0000004eef4e4618 r13=000003299a405dd0 r14=0000000000000000 r15=0000000000000000

2017-04-01T18:29:13.375Z| vmx| I125: SymBacktrace[0] 000003299a402160 rip=0000004eef9aaaa7 in function (null) in object /bin/vmx loaded at 0000004eef331000

2017-04-01T18:29:13.375Z| vmx| I125: SymBacktrace[1] 000003299a402190 rip=0000004eef4efa8c in function (null) in object /bin/vmx loaded at 0000004eef331000

2017-04-01T18:29:13.375Z| vmx| I125: SymBacktrace[2] 000003299a4026a0 rip=0000004eef5ede99 in function (null) in object /bin/vmx loaded at 0000004eef331000

2017-04-01T18:29:13.375Z| vmx| I125: SymBacktrace[3] 000003299a4026c0 rip=0000004eef59dcc4 in function (null) in object /bin/vmx loaded at 0000004eef331000

2017-04-01T18:29:13.375Z| vmx| I125: SymBacktrace[4] 000003299a402920 rip=0000004eef4ea33c in function (null) in object /bin/vmx loaded at 0000004eef331000

2017-04-01T18:29:13.375Z| vmx| I125: SymBacktrace[5] 000003299a4029c0 rip=0000004eef4ea953 in function (null) in object /bin/vmx loaded at 0000004eef331000

2017-04-01T18:29:13.375Z| vmx| I125: SymBacktrace[6] 000003299a405a70 rip=0000004eef4eade2 in function (null) in object /bin/vmx loaded at 0000004eef331000

2017-04-01T18:29:13.375Z| vmx| I125: SymBacktrace[7] 000003299a405b40 rip=0000004eef4f0590 in function (null) in object /bin/vmx loaded at 0000004eef331000

2017-04-01T18:29:13.375Z| vmx| I125: SymBacktrace[8] 000003299a405c70 rip=0000004eef4e3ca6 in function main in object /bin/vmx loaded at 0000004eef331000

2017-04-01T18:29:13.375Z| vmx| I125: SymBacktrace[9] 000003299a405d00 rip=0000004f3243e8cd in function __libc_start_main in object /lib64/libc.so.6 loaded at 0000004f3241e000

2017-04-01T18:29:13.375Z| vmx| I125: SymBacktrace[10] 000003299a405dc0 rip=0000004eef4e4641 in function (null) in object /bin/vmx loaded at 0000004eef331000

2017-04-01T18:29:13.375Z| vmx| I125: Msg_Post: Error

2017-04-01T18:29:13.375Z| vmx| I125: [msg.log.error.unrecoverable] VMware ESX unrecoverable error: (vmx)

2017-04-01T18:29:13.375Z| vmx| I125+ PCI passthru device 0000:00:1a.0 caused an IOMMU fault type 12 at address 0x350aa000.  Powering off the virtual machine.  If the problem persists please contact the device's vendor.

2017-04-01T18:29:13.375Z| vmx| I125: [msg.panic.haveLog] A log file is available in "/vmfs/volumes/5896268d-375f0480-af0f-6451060dad88/wifi_sms/vmware.log". 

2017-04-01T18:29:13.375Z| vmx| I125: [msg.panic.requestSupport.withoutLog] You can request support. 

2017-04-01T18:29:13.375Z| vmx| I125: [msg.panic.requestSupport.vmSupport.vmx86]

2017-04-01T18:29:13.375Z| vmx| I125+ To collect data to submit to VMware technical support, run "vm-support".

2017-04-01T18:29:13.375Z| vmx| I125: [msg.panic.response] We will respond on the basis of your support entitlement.

2017-04-01T18:29:13.375Z| vmx| I125: ----------------------------------------

2017-04-01T18:29:13.376Z| vmx| I125: Exiting

There is an error in thre implementation of the usbccid of Workstation, and Fusion.  Look at the bold quote below.

https://pcsclite.alioth.debian.org/ccid/unsupported.html#0x0E0F0x0004

USB descriptor: readers/VMware_Virtual_USB_CCID2.txt

Features: PIN Verification, PIN Modification

Limitations: No extended APDU

The dwFeatures looks to be incorrect. IFSD negoctiation by the driver is rejected. After a change to add CCID_CLASS_AUTO_IFSD then PC_to_RDR_GetSlotStatus fails with LIBUSB_ERROR_TIMEOUT. This reader is found in VMware workstation player 12 64 bit on Windows 7.

In CCID release: 1.4.23

VMWare virtual CCID reader bugs

MickFlemm

Hello all,

I'm using the latest VMWare Fusion Pro (8.5.0) and when I try to use my smartcard on a Linux guest (tried with both debian and gentoo) the virtual CCID reader presented to the guest machine doesn't work with PCSC-lite. The reason is that the reader announces a wrong set of features on its descriptor and also the PC_to_RDR_GetSlotStatus command sometimes gets ignored and results a usb read timeout. I came up with a workaround and submitted a patch to the maintainer of the CCID driver for pcsc (note that same driver is used on mac OS), you can get it here -> Add some workarounds to make VMWARE CCID work by mickflemm · Pull Request #24 · LudovicRousseau/CCID · GitHub. However the maintainer won't include this patch upstream because he insists that this is a software bug and should be fixed by VMWare. Without PCSC support I can't use my smartcard as an HSM or for logging in to my machine, this is a serious issue for me and from what I see there is no way to disable that behavior on Fusion (there is an option on workstation to disable the shared ccid reader and present the standard usb reader to the guest). Is there a bug tracker for VMWare products, does support deal with such issues ?

Thanks for your time

Nick

Hi Guys ,

I configured an host and then extracted an Host-Profile from it, in order to attach it to the rest of the hosts, that should look just like this host .

When attaching the Host-Profile to other host, and "Remediate" - I can see "Non Compliant" error with strange details [see screenshot below ]

Most of the configurations succeeded [like VDS ,vmks , syslogDir , NFS mounts etc.  ]

The strange issue with those errors is that IPv6 is disabled on the host , and the DNS is succeeded with the config .

so i can't understand why am i getting the errors ??

[BTW - also, something that the host didn't succeded with taking from the Host-Profile, is the swap location . i'll be glad if you can tell me when can i check]

Appreciate your fast assistant, because this environment needs to be in production in few days

Thanks in advance ,

Ron

even though options to copy/pasted are selected properly, copy/paste does not work between the host Mac Sierra machine and the guest windows 10 OS.

Please see collected logs attached.