Spoiler alert:  there is PLENTY disk-space available on the vsanDatastore...

Hello,

The VSAN System in our Lab is running into more and more problems when it comes to creating snapshots. At the moment, there are several VM's which whom it has become completely impossible to create snapshots at all.

It started out a few weeks ago when i notices strange retries in our Backup-software (Veeam v8 latest version). It needed 1 or sometimes 2 retries because it could not create a snapshot due to the mention error.

Then, over time, it took 2 or 3 retries. So it would fail to create a snapshot once, twice but the third time it would work just fine. Job retries are 5 minutes aparts. So all of this happens in a timeframe of say 15 to 20 minutes or so.

At the moment, several VM's cannot be backed up anymore because it has become impossible to create snapshots. The reason is always the same: "Insufficient disk space on datastore" which is totally bolloks as we have over 5 TB free.

At first, it thought it was due to a problem in Veeam but as it turns out, it has nothing to do with Veeam because I can't create snapshots in the VI /Web Client either. The problem lies in vSphere and Veeam is mere a victim.

Looking at logfiles, I always see this error when trying to consolidate snapshots:  "An error occurred while consolidating disks: msg.disklib.NOSPACE"

The error "msg.disklib.NOSPACE" is a generic error which i also see when i simply want to make a snaphot.

This lead me to KB Article VMware KB: Consolidating disks in VMware Virtual SAN fails with the error: An error occurred while consolidating dis…

None of the conditions like "When the disk being consolidated has more than 255GB data, consolidation fails." are valid in my environment.

Each and every blog-post or KB article I found has brought me nothing.

When i look inside such a VM's directory, there is carnage. A VM with two disks started out with names like the usual "vm01.vmdk" and "vm01_1.vmdk" (for the second disk). After a couple of days, it can look like ""vm01.vmdk" and "vm01_17.vmdk" and there are a lot of snapshots lying around. If also leads to the usual "VM need consolidation" messages which always fail due to locking problems ("Consolidation failed for disk node 'scsi0:1': msg.fileio.lock").

Consolidating a VM requires some handy work but I can always get them back on track. The wierd _17.vmdk names (or similar) I can fix by renaming the .vmdk and -flat.vmdk files to _1 again and editing the .vmdk file and change the _17 to _1  etc. etc. etc.

So I can always "repair" a VM and we never have dataloss. But it's pain in the bum and it requires downtime for the VM in question.

I can repair a VM and it will be able to make snapshots just fine but it will get into trouble within 3 or 4 days with the exact same problem. Sometimes i go as far as deleting the VM from the inventory, repair the VMDK names (when it went cookoo again and calls a disk _15.vmdk or whatever instead of the original _1.vmdk etc.) and creating a brand new VM and attach the old vmdk's. That "new" VM will then be quiet and fine and dandy for a few days before the same shit starts happening all over again, getting worse over time.

Each and every blog-post or KB article I found has brought me nothing.

I desperately need your help. The VSAN runs fine. But snapshots, and with that the backups, are getting more and more problematic as ever more VM's start suffering from this issue. I could move some low I/O VM's to a cheap NFS NAS and presto, all problems are gone. Move them back, fine for a few days and then the misery starts all over again, getting worse over time. it IS a VSAN problem.

VMware is not going to help me. Reason: this is not a production environment and there is no dataloss so they don't care. Period. I would end up with a level-1 support employee which starts asking all the basic questions which I am already way beyond and they will never escalate and allocate level-2 personell to my case, making the entire exercise frustrating, lengthy (weeks) and as useless as tits on a fish (pardon my french).

Help me Obi-Wan Kanobi.

i want to both networks are connected to one. (vswitch 1 to vswitch 2) . how to connect because there are 1 dc , 1 vcenter , 1 esx in virtual1 switch . there are  1 dc , 1 vcenter , 1 esx in virtual2 switch.

i will make a lab for site recovery manager.

I'm trying to use to the VRA 7 feature "external value" to get data for a property definition.  Any examples or guides?   I have quick action that returns string but I get this error

Hi

I am trying to call a VCO workflow from a python script on a ESXi 6.0 host. Hopefully this is the most appropriate forum. The below script works if I run it from a python install on my laptop. The expected out put is meant to be a listing of the Configure Mail workflow.

#! /bin/python
import urllib2
import base64
import ssl
import xml
from urlparse import urlparse


vroServer = '192.168.199.6:8281'
print vroServer
theurl = 'https://' + vroServer + '/vco/api/workflows/?conditions=name=Configure%20mail'
print theurl
username = 'vcoadmin@vsphere.local'
password = 'vcoadmin'

context = ssl.CERT_NONE
ssl._create_default_https_context = ssl._create_unverified_context

req = urllib2.Request(theurl)
print req
base64string = base64.encodestring('%s:%s' % (username, password))[:-1]
authheader =  "Basic %s" % base64string
req.add_header('User-agent', 'Mozilla/5.0')
req.add_header('Content-Type','application/xml')
req.add_header('Accept','application/xml')
req.add_header('Authorization', authheader)
print req
handle = urllib2.urlopen(req)
thepage = handle.read()
print thepage

The output I get is below

Traceback (most recent call last):  File "./VCOTest.py", line 28, in <module>    handle = urllib2.urlopen(req)  File "/build/mts/release/bora-3247720/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/urllib2.py", line 154, in urlopen  File "/build/mts/release/bora-3247720/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/urllib2.py", line 431, in open  File "/build/mts/release/bora-3247720/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/urllib2.py", line 449, in _open  File "/build/mts/release/bora-3247720/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/urllib2.py", line 409, in _call_chain  File "/build/mts/release/bora-3247720/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/urllib2.py", line 1240, in https_open  File "/build/mts/release/bora-3247720/bora/build/esx/release/vmvisor/sys-boot/lib/python2.7/urllib2.py", line 1197, in do_open
urllib2.URLError: <urlopen error [Errno 110] Connection timed out>

Thanks .

My blog is at http://virtual-red-dot.info/

Thanks

e1

I have just installed a new 3 node cluster with vCenter Server Appliance 5.5 build 2001466.   2 ESXi nodes are 5.5 build 206810 and one is 5.5 build 1746018.  The servers are Dell R620s.

During testing, I have noticed that the network adapter information displayed in the vSphere Client is incorrect.

Each host has two vSwitches and each vSwitch has 2 physical NICs bound.  vSwitch0 is for management traffic and vSwitch1 is for VM port groups.  I have configured NIC teaming on each vSwitch to use 1 active adapter and 1 stand by adapter.

Here is a screenshot of the NIC configuration for one of the hosts:

The management IP address for this host is 192.168.199.26 and the vSphere client indicates that vmnic0 is the active adapter and vmnic1 is in stand by.

The problem I have encountered is that when I look at the mac address table in my switches to see which switch port is associated with the MAC address associated with 192.168.199.26, I see that MAC address associated with the port for vmnic1, not vmnic0.  So vSphere Client is telling me that vmnic1 is in stand by and vmnic0 is active,  but that is not correct based on what I see from the switches.

I have a Cisco 3850 switch stack with two switches in it.  For this specific host, vmnic0 is connected to GigabitEthernet1/0/1 and vmnic1 is connected to GigabitEthernet2/0/1

Here is a screenshot illustrating the MAC address for this host being associated with the wrong switch port:

I have verified the vmnic to switch port mapping by looking at the CDP info in the vSphere Client, by looking at the CDP info in the switches as well as physically inspecting the cabling.

I also did some troubleshooting by running a continuous ping to the hosts management address and unplugging the ethernet cable from vmnic0 (which vSphere Client shows as active) and I observed no lost pings.  Then I reconnected vmnic0 and disconnected vmnic1 and observed a few lost pings before they came back.  After doing that I checked the switches again and the MAC address had moved from vmnic1 to vmnic0, so fail over is working, but vSphere Client just isn't showing the correct active adapter.

So my question is: why is vSphere Client showing vmnic0 as active and vmnic1 as stand by when vmnic1 is actually the adapter that is being actively used for management traffic, and what can I do to fix this?

Wondering if anyone has very unresponsive and lagging performance running Windows 10 Pro on Fusion 8 with OSX 10.11.

I use a MBPro (Late 2013) 15" Retina with external 4K monitor, resolution is great but the performance of tabbing, moving the mouse, opening & closing programs is crippling.

On Fusion 7 with the same hardware i had Win 7 running perfectly, it did require a vmware hardware downgrade to 10 for it to work.

Have tried the same method on Win 10 but still not running as smooth as i am sure it can, anyone got any advice?

Thanks in advance!

I have added an authorized key for root (perms are correct) and yet when connecting a password prompt is still displayed even after the 'Authenticating with public key "imported-openssh-key"' message appears. A verbose ssh session shows the vcsa accepting the key, what else must be done to allow public key auth?

Thanks.

Hi community, this is Wang Ming.  I'm looking forward to build my new pc that will be dedicated for VMware workstation only. It will be running 24/7 with multiple Vmware instances with several mobile games on bluestacks, multiple online game clients with the lowest settings running on those instances. I will run as much as my new pc could handle.

Here is my new pc specs:

Intel Core i7-5820K 3.3GHz 6-Core Processor

Cooler Master Hyper 212 EVO 82.9 CFM Sleeve Bearing CPU Cooler

MSI X99A SLI PLUS ATX LGA2011-3 Motherboard

G.Skill Ripjaws 4 series 32GB (4 x 8GB) DDR4-3000 Memory

G.Skill Ripjaws 4 series 32GB (4 x 8GB) DDR4-3000 Memory

Samsung 950 PRO 512GB M.2-2280 Solid State Drive

I've several questions about hardware for Vmware workstation.

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

Between these Cpus, which is the best for running several vmware instances? Which one would you recommend?

1.I7 5820K 6 Cores 12 threads 3.3K speed

2.I7 6700K 4 Cores 8 Threads 4K speed

3.AMD FX 9590 8 Cores 8 Threads 4.7K speed

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

Do clockspeed and CL in DDR4 important in Vmware? Is it overkill to buy expensive DDR4 with very high clockspeed or will the cheap DDR3 will do just fine?

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

Does VGA matter in Vmware? If not, should I run my pc without installing a graphic card or should I buy a cheap one?

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

In SSD, do reading and writing speed matter for running Vmware? Or should I buy normal hard disk instead.

Thank you!!!

Wang Ming

Setup:

Mac osx Yosemite

Fusion 8.0.x Pro -> 8.10 Pro upgrade

Removed Vmtools from Win 10 virtual machine, reboot, install, reboot

USB 3.0 controller emulation

Hypothesis:

USB 3.0 emulation and VMware tool drivers have changed some timing parameters that are causing timeouts or errors for the scansnap Fujitsu hardware or driver running in Win 10 VM

Symptoms:

- Scansnap Fujitsu S1300i scanner connects correctly

- Application in Win 10 initiates scan

- Scanner light blinks and then the application crashes (disappears)

- Scanner light keeps on blinking

- Close scanner / power off, the application window returns with an error that scanner was unplugged

Correct Behavior (worked correctly till this upgrade)

- Scansnap Fujitsu S1300i scanner connects correctly

- Application in Win 10 initiates scan

- Scanner light blinks and then feeds the paper thru and scans

- Application windows opens with the scan preview

Workaround

- Power off Win 10 VM

- Removed USB 3.0 controller for the Win 10 VM

- Boot the Win 10 VM and login

- Power off Win 10 VM

- Add USB 2.0 controller to the Win 10 VM

- Boot the Win 10 VM and login

- Power on the scanner and the scanner drivers are now attached to the USB 2.0 controller in the Win 10 Device Manager

Issue 1: I am forced to run all my other USB3.0 peripherals at USB 2.0 speed, which will be slow for all the USB 3.0 HDD connected to the Win 10 VM.

Issue 2: Everything was working correctly before but the VMware tools upgrade broke stuff. Clearly, something is not correct here and I am concerned that my other peripherals will face USB 3.0 issues. All my devices are USB 3.0 now and not sure what Pandora's box I am opening by running them with USB 3.0.

Please help on how to fix this issue?

Message was edited by: Fu FU Clarified that it was Fusion 8.0 Pro

After setting up the vmca as a subordinate CA for an Active Directory Enterprise CA in a lab setup, the certificate generated for the web client has a subject with the dn's cn being the company name and not the fqdn. The cert is trusted by Active Directory clients and the certificates subject alternative name has a DNS Name set to the correct fqdn, IE clients accept the certificate however chrome clients do not.

Can the web servers certificate be regenerated independently?

Thanks

Anyone had a similar issue?

Host has a PERC H730p controller. Looks like the disks were resetting prior to the crash according to the system's lifecycle controller.

On call with Dell Support. Planning on a VMware support call too.

Thanks in advance!

Justin

Dear Guys,

I've just updated my Windows 10 last night (December Major Update 2015). Unfortunately, I'm strongly believes that the updates have disrupted my VMware Workstation 12 Pro Configuration.

What I found today were:

1) My virtual NIC are not working in all of my VM collection (Windows Server 2008/2012).

2) All of my VM required me to update "The keyboard hook timeout value is not set to the value recommended by VMWare Workstation. This can cause keystrokes  to be lost when the host is under stress. We recommend that you allow this application to update the value. Once this value is updated, you must log out and log in again in order to have the value take effect. Press "OK" to update the value, "Cancel" to leave it unchanged."

And I opt for cancel.

To restore the NIC issues, I've just reinstalled the VMware Workstation. However, I'm still experienced the "The keyboard hook timeout .... " . I'm not sure whether to click ok or not due to the issues happened not because of the VMware Workstation, but the Windows itself.

Anyone experienced the same? Please do advice what should I do to resolve this.

Thank you

Can the function "Capture movie" be set in detail,such as the fps,the maxsize of the target video and so on?

I used the "Capture movie" to record my screen of my virtual guest in model low quality.But it created a very large file only of a few minutes.

I suppose that the VM can add more setting functions for users to customize the target movie files.

Hi,

Below is hardware configuration i am having where I m installing vmware 6.0.

CPU: AMD FX(tm)-6300 six-core processor

Motherboard: Gigabyte 78LMT-USB3

RAM: 16 GB

HDD: 1 TB.

Can anyone, please suggest how i can install vmware 6.0 on above hardware configuration.

Error:

=====

No network adapters  were detected. Either no network adapters are physically connected to the system, or a suitable driver could not be located. A third party driver may be required.

Ensure that there is at least one network adapter physically connected to the system before attempting installation. If the problem persists, consult the VMware Knowledge Base.

Regards,

Sonu Chauhan

i've got an ibm m1115 flashed to the lsi 9211-8i it firmware

running esxi 5.1u1

i've setup pci passthrough on two controllers, the above mentioned and an older lsi 3081e-r which has been flashed to it mode

one thing to note is that the lsi 9211-8i uses mpt2sas drivers whereas the 3081e-r uses mptsas drivers in esxi

it appears whilst the 3081e-r controller will passthrough to a vm fine when set with boot firmware to be efi

the 9211-8i doesn't let me start the vm at all, i can't even force it to the efi setup

that being said if i passthrough the 9211-8i to a vm which has the boot firmware set to bios it functions as it should

has anyone come across this problem before? unfortunately the vm's require efi so going moving to a bios option is not an option

some additional specs of the whitebox if it matters:

asus p8z77-v pro

i7 2600

lsi 9211-8i in ir mode(used to run raid1 ssd's for the datastore)

lsi 9211-8i in it mode

lsi 3081e-r in it mode

clean install of esxi 5.1u1

update;

dug around the events a bit looks like it returns an error when i add the pci passthrough:

Warning message from localhost.localdomain: No operating system was found. If you have an operating system installation disc, you can insert the disc into the system's CD-ROM drive and restart the virtual machine.

only seems to give that error on select vm's, tested it on one setup for windows and it doesn't spit an error but still doesn't start

remove the controller and it boots straight into the os

Hello!

I am having an issue with how ESXi handles IPMI. The system process' vmklinux_9:ipmi_thread constantly utilizes a full CPU core. This bug seems to have been fixed in ESXi 5.5U1 (KB 2065824, PR 1075046). However, it now happens for me on version 6.0 build 3247720. As a workaround I tried disabling IPMI (setting VMkernel.boot.ipmiEnabled to false), yet after a reboot IPMI is still used for some reason. Motherboard and IPMI controller BIOS/firmware are latest versions.

Hardware configuration:

• ASUS TS300-E8-PS4 server platform
• ASUS ASMB7-iKVM IPMI controller

This is probably a developer question, but here goes.

I have 3.5 working on Centos7/RHEL7, but I need to get it working on Thinstation which used busybox rather than glibc.

When the client connects, it makes it past the welcome screen after login, then black, then disconnects.  The error in the log file is this:

rmksContainer(4772): ERROR: /build/mts/release/bora-2967609/bora/apps/rde/mksvchan/client/../common/mksvchanClipboardX11.c:75:MKSVchan_RequestTextCb: assertion failed: (g_helperThread == g_thread_self())

g_thread_self if part of glibc, but I don't know if it's used in busybox - that may be why it's failing.

Thanks

Hi,

After logging in with my account, all lab content disappears and is unavailable. (See attached screenshot)

Other users' accounts work okay, and I've tried different browsers. The problem appears to be related to my account.

Help please!

Cheers,

Chris Garrett

Running host: Rosa Linux R6 2014.1 x86_64

After my latest upgrade to Workstation Pro 12.1.0 (from 12.x.x), launching "vmware" always fail.

Running "vmware" a console I get this couple of lines and nothing more:

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

Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory

Gtk-Message: Failed to load module "canberra-gtk-module": libcanberra-gtk-module.so: cannot open shared object file: No such file or directory

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

But I have installed that library both for gtk 2.0 and for gtk 3.0:

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

giovanni@Rivendell ~ $ locate libcanberra-gtk-module.so

/home/giovanni/.local/share/Steam/ubuntu12_32/steam-runtime/i386/usr/lib/i386-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so

/home/giovanni/.local/share/Steam/ubuntu12_32/steam-runtime.old/i386/usr/lib/i386-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so

/usr/lib64/gtk-2.0/modules/libcanberra-gtk-module.so

/usr/lib64/gtk-3.0/modules/libcanberra-gtk-module.so

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

So what is going wrong here?

TIA

GvM