Dear Friends,

Anyone please share UEM Application Template for Office 2013? I see one for Office 2016 in VMware community site but looking for 2013.

Last week I patched our (7) lab ESXi 6.5 servers to the current patch level (Build 5146846 - from March 9, 2017).  The (5) Dell servers have been running flawlessly on this new patch level.  However, the (2) Cisco UCS B200 M4 servers have been crashing constantly with Purple Screen of Death (PSOD).  I verified that the Cisco UCS servers are running the current firmware (BIOS & VIC) supported by Cisco with ESXi 6.5, and I also used Update Manager to apply the current Cisco Image Profile ("Vmware-ESXi-6.5a.0-4887370-Custom-Cisco-6.5.0.2-Bundle.zip" from 2017-03-14), to get the current drivers, but that did not help -- PSODs continued.  The PSODs keep occurring on both ESXi hosts in the 2-node Cisco cluster, rendering a complete cluster outage.  First, one ESXi host PSODs.  Then a little while later, the second ESXi host PSODs.  Sometimes the PSOD takes 5 hours to occur, sometimes it only takes 25 minutes.  (Another PSOD occurred while I was typing this post, after a reboot of the blade just about 25 minutes earlier.)  I've captured dozens of PSOD screen shots, and every single one contains the following lines:

NOT_IMPLEMENTED bora/vmkernel/sched/cpusched.c:9581

On each PSOD, a different VM name is listed two lines below the above error code, so there is no consistency as to which VM triggers this panic. 

The interesting thing is that the (5) Dell servers are humming along without issue on this patch level.  The Cisco servers are using Intel(R) Xeon(R) CPU E5-2670 v3 CPUs, while the Dell servers are using earlier generation CPUs (Sandy Bridge or Westmere).  Both the Dell servers and Cisco servers are using vSphere Replication 6.5.  The Cisco servers are running a heavier load of VMs, many of which are using multiple vCPUs, so perhaps there is another vCPU scheduling bug that is being triggered? 

We have vRealize Log Insight running, and the following are some of the last messages sent by the ESXi host after PSOD:

[Originator@6876 sub=VpxaHalCnxHostagent opID=WFU-491dcb0b] Applying updates from 215636 to 215637 (at 215636)

[Originator@6876 sub=PropertyProvider] RecordOp ASSIGN: guest, 45. Sent notification immediately.

The vRealize Log Insight VM is running in the Cisco cluster, so I might be missing some of the most important log entries right at the time of the PSOD.

Anyone else running into this??  (Note that this is a "lab" environment, so it's not production impacting.  This is exactly why we have a "lab" environment!!!)

Below is one screen shot example of the PSOD.  They all pretty much look like this:

trying to install a second network adapter to give internal acces to internet but device administration even recognice this  second adapter

I hope I am posting in the right place

I have provision ESXI, and I am logging into the web interface to manage my VM's, is there a way to edit the port on this? I would rather it be running on a non-standard port for added security instead of just 443.

Thanks in advance!

IN SHORT:

I have MIGRATED a large Windows 2012 R2 VM (11TB: C: 200gb D: 10.8tb) which has noticeable deteriorated performances after migrating to ESXi 6.0U2 including:

delays, unresponsive, dragging, network shared folder connectivity delay like it fell asleep etc.

CPU, Memory utilization and Disk space appears to be normal. Please see below VMware event logs attached.

For example, trying to open apps like event viewer, and experience delays in just opening Control panel or any other window on its desktop screen. Takes 5 seconds to respond to mouse action. Delays trying to access files from client to shared folder on Windows Server in question. Basically, click and wait. It's like Server was asleep and when you click on shared folder takes a few seconds to wake up. Reboot fixes the issue temporarily then it returns again.

WHAT CHANGED:

Moved VM from 5.5 to 6.0U2 using simple SCP command.

It was moved from HP G7 blade to HP G8 DL360p Server (firmware up to date).

Increased CPU 4 to 10 cores. Increased Memory to 24gb.

After move encountered major Network issues (Network down) until upgraded VMware Tools.

Upgraded to latest VMware tools which resolved network NIC connectivity issues.

Upgraded HW to version 11.

Updated Windows: ran Windows update several times.

VMware tools were upgraded to newest version 10.1.5

The VM is showing CURRENT VMWARE TOOLS. see log below:

Any ideas and advise is greatly appreciated.

Thanks in advance.

Hello,

May i have an advice about SRM configuration with  2 Vcenter Server configured without external plateform Service on SITE1???

Thanks.!!

I have vCenter Appliance Server 6.0U2a running on ESXi 6.0U2 host which hosts about 15 VMs.

Also on the same host, I have an Active Directory Windows 2012 R2 VM Server which is also a DNS server.

At the moment, this is the only Physical server on the network. There are no other hosts or servers.

For some reason, when I need to shut down this physical server: First, I shut down all the VMs on the server.

Second, I shut down my Active Directory/DNS server and Finally I shut down vCenter.

Then I shut down my physical server by shutting down my host and all of this done through a vSphere Client or Web client.

However, when I shut down my Active Directory/DNS server somehow it loses connection to all VMs on the host including vCENTER which  is still powered on.

I am seeing all VMs are listed as disconnected. I am then forced to shut down the host through a vSphere web client and I am not sure if the vCenter was shutdown gracefully or if it had any issues restarting.

IN MY CASE, WHAT IS THE PROPER WAY TO SHUT DOWN vCENTER?

PLEASE LIST STEP BY STEP INSTRUCTIONS.

Thanks in advance...

PS. on reboot I get this screen. What is happening here?

Hi All,

I have 3 ESXi host  in a cluster having

     2 ESXi  (name: ESXi-A & ESXi-B) host with the management IP 192.168.0.1 and

     1 ESXi (name: ESXi-C) host with the management IP 172.0.0.1

But my vMotion Network are configured on different vSwitch and are having the same IP address 172.0.3.x by all the 3 ESXi host.

Now Can I do a vMotion between ESXi-C to (ESXi A or ESXi-B) having different management networks ?

I am running VMware Workstation Pro 12.5.4 build-5192485 on a Lenovo W541 laptop with Windows 7 Professional (Service pack 1) O/S.

I have 32 GB internal memory, with 24GB reserved for VMWare images. The images I run use no more than  16GB memory. Very often my laptop becomes so slow as to e non responsive. Usually this happens after the VMWare image had bee running for an hour or more.

has anyone any idea as to what the issue could be?  

Hi,

If I run a VM from a NAS, I get and error "Cannot open the disk '/Volumes/Me/VM/Mine/MyDisk.vmdk' or one of the snapshot disks it depends on."

This is odd because it only fails over an SMB connection. If I connect to the NAS using AFP (Apple File Protocol), it runs fine. Copying the VM to my local machine also works fine.

I found a few threads referring to this error, but none of the solutions worked: deleting lck files and folders, removing and reattaching disks, and I have no snapshots.

Since it works over AFP, I suspect it has to do with SMB protocol, or something internal to VMWare.

Looking at the logs (selection posted below), I see there are definitely some SMB-specifics in there, so VMWare is definitively 'aware' of what network it's using. Over AFP only one instead of four lock folders are created. Full permissions are granted on the entire VM folder.

Systems: Fusion 8.5.6 on OSX 10.12 (Sierra), QNAP NAS with SSD caches and dual gigabit network.

Any help would be much appreciated.

2017-03-29T21:29:13.198Z| vmx| I125: FILE: FileLockScanDirectory discarding .smbdeleteAAA6c20cf4 from /Volumes/Me/VM/WinXP_Sandbox/WinXP_Pro.vmsd.lck'; invalid file name.
2017-03-29T21:29:13.200Z| vmx| W115: FILE: FileLockRemoveLockingFile of '/Volumes/Me/VM/WinXP_Sandbox/WinXP_Pro.vmsd.lck/.smbdeleteAAA6c20cf4' failed: Resource busy
...
2017-03-29T21:29:13.213Z| vmx| I125: DISK: OPEN ide0:0 '/Volumes/Me/VM/WinXP_Sandbox/WinXP_Pro_SP3.vmdk' persistent R[]
2017-03-29T21:29:13.309Z| vmx| I125: FILE: FileLockScanDirectory discarding .smbdeleteAAA6c20cf5 from /Volumes/Me/VM/WinXP_Sandbox/WinXP_Pro_SP3.vmdk.lck'; invalid file name.
2017-03-29T21:29:13.310Z| vmx| W115: FILE: FileLockRemoveLockingFile of '/Volumes/Me/VM/WinXP_Sandbox/WinXP_Pro_SP3.vmdk.lck/.smbdeleteAAA6c20cf5' failed: Resource busy
2017-03-29T21:29:13.316Z| vmx| W115: FILE: FileIO_Lock on '/Volumes/Me/VM/WinXP_Sandbox/WinXP_Pro_SP3.vmdk' failed: Resource busy
2017-03-29T21:29:13.316Z| vmx| I125: DISKLIB-DSCPTR: Couldn't lock descriptor file /Volumes/Me/VM/WinXP_Sandbox/WinXP_Pro_SP3.vmdk: Error (2).
2017-03-29T21:29:13.316Z| vmx| I125: DISKLIB-LINK  : "/Volumes/Me/VM/WinXP_Sandbox/WinXP_Pro_SP3.vmdk" : failed to open (Directory not empty). 
2017-03-29T21:29:13.316Z| vmx| I125: DISKLIB-CHAIN : "/Volumes/Me/VM/WinXP_Sandbox/WinXP_Pro_SP3.vmdk" : failed to open (Directory not empty).
2017-03-29T21:29:13.316Z| vmx| I125: DISKLIB-LIB   : Failed to open '/Volumes/Me/VM/WinXP_Sandbox/WinXP_Pro_SP3.vmdk' with flags 0x1a Directory not empty (4325385).
2017-03-29T21:29:13.316Z| vmx| I125: DISK: Cannot open disk '/Volumes/Me/VM/WinXP_Sandbox/WinXP_Pro_SP3.vmdk': Directory not empty (4325385).
2017-03-29T21:29:13.316Z| vmx| I125: DISK: Opening disks took 104 ms.
2017-03-29T21:29:13.316Z| vmx| I125: Module 'Disk' power on failed.
2017-03-29T21:29:13.316Z| vmx| I125: VMX_PowerOn: ModuleTable_PowerOn = 0
2017-03-29T21:29:13.384Z| vmx| I125: Vix: [775 mainDispatch.c:1179]: VMAutomationPowerOff: Powering off.
2017-03-29T21:29:13.385Z| vmx| W115: /Volumes/Me/VM/WinXP_Sandbox/WinXP_Pro.vmx: Cannot remove symlink /var/run/vmware/501/113808639716_7377/configFile: No such file or directory
2017-03-29T21:29:13.386Z| vmx| I125: Policy_SavePolicyFile: invalid arguments to function.
2017-03-29T21:29:13.386Z| vmx| I125: PolicyVMX_Exit: Could not write out policies: 15.
2017-03-29T21:29:13.387Z| vmx| I125: WORKER: asyncOps=1 maxActiveOps=1 maxPending=0 maxCompleted=0
2017-03-29T21:29:13.390Z| vmx| I125: Vix: [775 mainDispatch.c:4238]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0
2017-03-29T21:29:13.391Z| vmx| I125: Msg_Post: Error
2017-03-29T21:29:13.391Z| vmx| I125: [msg.literal] Directory not empty
2017-03-29T21:29:13.391Z| vmx| I125: [msg.disk.noBackEnd] Cannot open the disk '/Volumes/Me/VM/WinXP_Sandbox/WinXP_Pro_SP3.vmdk' or one of the snapshot disks it depends on.
2017-03-29T21:29:13.391Z| vmx| I125: [msg.moduletable.powerOnFailed] Module 'Disk' power on failed.

Hi, when I use vRA REST API to update a composite blueprint, as the following shows, there is a disk id attribute that I need to provide. Where can I get this id? thanks in advance.

Note: I can get the vm template using https://vrahost/iaas-proxy-provider/api/source-machines/{source-machinesId}/?platformTypeId=Infrastructure.CatalogItem.Machine.Virtual.vSphere. but there is no such Integer type disk id.

Background snapshots are painfully slow so I always uncheck this option under priority. Every time I upgrade to the latest version this option is checked again by the installer. Very annoying. Is there anything I can do about it or is this a feature request?

We tried rebooting a new VM we just created from a physical server the other day and it fails when powering on. The event states:

An error was received from the ESX host while powering on VM Peterbuilt.

Failed to start the virtual machine.

Module DiskEarly power on failed.

Cannot open the disk '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1-000002.vmdk' or one of the snapshot disks it depends on.

5 (Input/output error)

The vmware.log from the first time it failed power on contains this:

2014-05-03T10:18:40.564Z| Worker#1| I120: DISK: OPEN scsi0:1 '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1-000002.vmdk' persistent R[]

2014-05-03T10:18:40.564Z| Worker#0| I120: DISK: OPEN scsi0:0 '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt-000002.vmdk' persistent R[]

2014-05-03T10:18:40.659Z| Worker#0| I120: DISKLIB-VMFS  : "vsan://1d846353-60b1-b2e4-7696-d4ae52836f43" : open successful (10) size = 32462929920, hd = 29894442. Type 8

2014-05-03T10:18:40.659Z| Worker#0| I120: DISKLIB-DSCPTR: Opened [0]: "vsan://1d846353-60b1-b2e4-7696-d4ae52836f43" (0xa)

2014-05-03T10:18:40.659Z| Worker#0| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt-000002.vmdk' (0xa): vmfsSparse, 62912512 sectors / 30 GB.

2014-05-03T10:18:40.671Z| Worker#1| I120: DISKLIB-VMFS  : "vsan://1f846353-d29f-90dd-fe1b-d4ae52836f43" : open successful (10) size = 576889700352, hd = 32384813. Type 8

2014-05-03T10:18:40.671Z| Worker#1| I120: DISKLIB-DSCPTR: Opened [0]: "vsan://1f846353-d29f-90dd-fe1b-d4ae52836f43" (0xa)

2014-05-03T10:18:40.671Z| Worker#1| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1-000002.vmdk' (0xa): vmfsSparse, 1118001152 sectors / 533.1 GB.

2014-05-03T10:18:40.683Z| Worker#1| I120: OBJLIB-VSANOBJ: VsanObjReadPolicy: failed to readPolicy for object: Input/output error (327682).

2014-05-03T10:18:40.683Z| Worker#1| I120: OBJLIB-VSANOBJ: VsanObjGetExtParams: Could not read policy for 'vsan://1eee6253-1e80-39fa-229e-842b2b78ebfb'.

2014-05-03T10:18:40.683Z| Worker#1| I120: OBJLIB-LIB: ObjLib_GetExtParams : Failed to get ext params : Input/output error (327684)

2014-05-03T10:18:40.683Z| Worker#1| I120: DISKLIB-VMFS  : "vsan://1eee6253-1e80-39fa-229e-842b2b78ebfb" : failed to open (Input/output error): . Type 3

2014-05-03T10:18:40.683Z| Worker#1| I120: DISKLIB-LINK  : "/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1.vmdk" : failed to open (Input/output error). 

2014-05-03T10:18:40.683Z| Worker#1| I120: DISKLIB-CHAIN :"/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1-000002.vmdk": Failed to open parent "/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1.vmdk": Input/output error.

2014-05-03T10:18:40.683Z| Worker#1| I120: DISKLIB-CHAIN : "/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1.vmdk" : failed to open (The parent of this virtual disk could not be opened).

2014-05-03T10:18:40.684Z| Worker#1| I120: DISKLIB-VMFS  : "vsan://1f846353-d29f-90dd-fe1b-d4ae52836f43" : closed.

2014-05-03T10:18:40.684Z| Worker#1| I120: DISKLIB-LIB   : Failed to open '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1-000002.vmdk' with flags 0xa The parent of this virtual disk could not be opened (23).

2014-05-03T10:18:40.704Z| Worker#0| I120: DISKLIB-VMFS  : "vsan://1cee6253-07b9-e212-6f6a-842b2b78ebfb" : open successful (14) size = 32211206144, hd = 32581421. Type 3

2014-05-03T10:18:40.704Z| Worker#0| I120: DISKLIB-DSCPTR: Opened [0]: "vsan://1cee6253-07b9-e212-6f6a-842b2b78ebfb" (0xe)

2014-05-03T10:18:40.704Z| Worker#0| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt.vmdk' (0xe): vmfs, 62912512 sectors / 30 GB.

2014-05-03T10:18:40.704Z| Worker#0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 2, numSubChains = 1

2014-05-03T10:18:40.704Z| Worker#0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 32581421, extentType = 2

2014-05-03T10:18:40.704Z| Worker#0| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(1) fid = 29894442, extentType = 0

2014-05-03T10:18:40.705Z| Worker#0| I120: DISKLIB-LIB   : Resuming change tracking.

2014-05-03T10:18:40.711Z| Worker#0| I120: DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 29894442.

2014-05-03T10:18:40.711Z| Worker#0| I120: DISKLIB-CBT   : Successfuly created cbt node 1ca272e-cbt.

2014-05-03T10:18:40.711Z| Worker#0| I120: DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/1ca272e-cbt

2014-05-03T10:18:40.711Z| Worker#0| I120: DISKLIB-LIB   : Opened "/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt-000002.vmdk" (flags 0xa, type vmfs).

2014-05-03T10:18:40.711Z| Worker#0| I120: DISK: Disk '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt-000002.vmdk' has UUID '60 00 c2 9c 4d 6e 95 99-d1 c1 5f c9 c0 e0 df e3'

2014-05-03T10:18:40.711Z| Worker#0| I120: DISK: OPEN '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt-000002.vmdk' Geo (3916/255/63) BIOS Geo (3916/255/63)

2014-05-03T10:18:40.717Z| Worker#1| I120: DISKLIB-VMFS  : "vsan://1f846353-d29f-90dd-fe1b-d4ae52836f43" : open successful (8) size = 576889700352, hd = 30091058. Type 8

2014-05-03T10:18:40.717Z| Worker#1| I120: DISKLIB-DSCPTR: Opened [0]: "vsan://1f846353-d29f-90dd-fe1b-d4ae52836f43" (0x8)

2014-05-03T10:18:40.717Z| Worker#1| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1-000002.vmdk' (0x8): vmfsSparse, 1118001152 sectors / 533.1 GB.

2014-05-03T10:18:40.717Z| Worker#1| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain: numLinks = 1, numSubChains = 1

2014-05-03T10:18:40.717Z| Worker#1| I120: DISKLIB-CHAINESX : ChainESXOpenSubChain:(0) fid = 30091058, extentType = 0

2014-05-03T10:18:40.718Z| Worker#1| I120: DISKLIB-LIB   : Resuming change tracking.

2014-05-03T10:18:40.722Z| Worker#1| I120: DISKLIB-CBT   : Initializing ESX kernel change tracking for fid 30091058.

2014-05-03T10:18:40.723Z| Worker#1| I120: DISKLIB-CBT   : Successfuly created cbt node 233273a-cbt.

2014-05-03T10:18:40.723Z| Worker#1| I120: DISKLIB-CBT   : Opening cbt node /vmfs/devices/cbt/233273a-cbt

2014-05-03T10:18:40.723Z| Worker#1| I120: DISKLIB-LIB   : Opened "/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1-000002.vmdk" (flags 0x8, type vmfsSparse).

2014-05-03T10:18:40.724Z| Worker#1| I120: OBJLIB-VSANOBJ: VsanObjReadPolicy: failed to readPolicy for object: Input/output error (327682).

2014-05-03T10:18:40.724Z| Worker#1| I120: OBJLIB-VSANOBJ: VsanObjGetExtParams: Could not read policy for 'vsan://1eee6253-1e80-39fa-229e-842b2b78ebfb'.

2014-05-03T10:18:40.724Z| Worker#1| I120: OBJLIB-LIB: ObjLib_GetExtParams : Failed to get ext params : Input/output error (327684)

2014-05-03T10:18:40.724Z| Worker#1| I120: DISKLIB-VMFS  : "vsan://1eee6253-1e80-39fa-229e-842b2b78ebfb" : failed to open (Input/output error): . Type 3

2014-05-03T10:18:40.724Z| Worker#1| I120: DISKLIB-LINK  : "/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1.vmdk" : failed to open (Input/output error). 

2014-05-03T10:18:40.724Z| Worker#1| I120: DISKLIB-CHAIN : "/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1.vmdk" : failed to open (Input/output error).

2014-05-03T10:18:40.724Z| Worker#1| I120: DISKLIB-LIB   : Failed to open '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1.vmdk' with flags 0xe Input/output error (327689).

2014-05-03T10:18:40.724Z| Worker#1| I120: DISK: Cannot open disk "/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1.vmdk": Input/output error (327689).

2014-05-03T10:18:40.724Z| Worker#1| I120: DISK: Cannot open disk '/vmfs/volumes/vsan:528a8f794664ebd8-6300c6c1887b898b/17ee6253-9171-b202-26f4-842b2b78ebfb/Peterbuilt_1.vmdk' : Input/output error.

2014-05-03T10:18:40.725Z| Worker#1| I120: DISKLIB-CBT   : Shutting down change tracking for untracked fid 30091058.

2014-05-03T10:18:40.725Z| Worker#1| I120: DISKLIB-CBT   : Successfully disconnected CBT node.

2014-05-03T10:18:40.737Z| Worker#1| I120: DISKLIB-VMFS  : "vsan://1f846353-d29f-90dd-fe1b-d4ae52836f43" : closed.

2014-05-03T10:18:40.742Z| vmx| I120: DISK: Opening disks took 179 ms.

2014-05-03T10:18:40.742Z| vmx| I120: Module DiskEarly power on failed.

2014-05-03T10:18:40.742Z| vmx| I120: VMX_PowerOn: ModuleTable_PowerOn = 0

2014-05-03T10:18:40.742Z| vmx| I120: scsi0:0: numIOs = 0 numMergedIOs = 0 numSplitIOs = 0 ( 0.0%)

2014-05-03T10:18:40.742Z| vmx| I120: Closing disk scsi0:0

2014-05-03T10:18:40.743Z| vmx| I120: DISKLIB-CBT   : Shutting down change tracking for untracked fid 29894442.

2014-05-03T10:18:40.743Z| vmx| I120: DISKLIB-CBT   : Successfully disconnected CBT node.

2014-05-03T10:18:40.748Z| vmx| I120: DISKLIB-VMFS  : "vsan://1d846353-60b1-b2e4-7696-d4ae52836f43" : closed.

2014-05-03T10:18:40.749Z| vmx| I120: DISKLIB-VMFS  : "vsan://1cee6253-07b9-e212-6f6a-842b2b78ebfb" : closed.

I am now trying to create a Windows Server 2008R2/2012R2 image template.

I followed the below links to setup the base image:

Windows Images in Your OpenStack Cloud - OpenStack Blog for VMware - VMware Blogs

VMware Integrated OpenStack Documentation

https://www.youtube.com/watch?v=KvYMOXjus_Y

After importing and updating metadata on VIO image page.

Metadata set:

vmware_ostype = windows7Server64Guest (For Server 2008R2)

hw_vif_model= VirtualVmxnet3

vmware_adaptertype = lsiLogicsas

windows_join_workgroup = VIOGroup

(Though I cannot find one for setting Administrator password)

I provisioned instance with the template and saw that it was customized by guest customization on vCenter.

By then when I tried to login to the instance, I found that the administrator password was reset to others but not the one I set.

I added 1 more metadata "windows_auto_logon" which allows the automatic logon after provisioning and figured out the administrator password was randomly set and Windows Workgroup is set to "VIOGroup".

May I know if there is anyone who tried to setup Windows image template?

Any metadata for setting Administrator password? Or any way to retrieve the randomly set password?

Have anyone tried to install Cloudbase Init? I tried to install it with default setting but provisioned Windows instance cannot boot up normally.

Hi all,

  Doing a deployment of a new vCenter 6.0 U3a  we are getting Failed to initialize VMware Certificate Authority - Error 100004  ( popup title install.vmafd.vmca_selfcafailed ) . Not gonna paste from the logs unless needed.  . We checked DNS entries/ DB connection / everything else that we could think of ,

  I think I found the issue. We are able to install on the same OS / same settings vCenter 6.0 U2a . Done several revert to snapshot and reproduced the scenario several times -  each time getting the same conclusion : vCenter 6.0U2a works , u3/u3a does not Work.

So what I saw is that openssl version was changed. My ideea is that we are missing a hotfix on the Windows VM ( which  is Windows 2008 R2 patched with security hotfixes only ) . So now I'm trying to see what might be the hotfix that we need ( taking in consideration that we can't just  put all patches ) .

Have also a SR opened to VMware, so far no solution .

Any ideas, anyone ?

Thank you.

Hi,

  I create and new VM and deployed an application that I want to access from outside VM.

My Laptop operating system : Windows 7

VMware version: Workstation Pro 12

VM settings

Results from ifconfig

[root@localhost hyder]# ifconfig

docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500

        inet 172.17.0.1  netmask 255.255.0.0  broadcast 0.0.0.0

        ether 02:42:16:93:7c:fa  txqueuelen 0  (Ethernet)

        RX packets 0  bytes 0 (0.0 B)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 0  bytes 0 (0.0 B)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

eno16777736: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.85.155  netmask 255.255.255.0  broadcast 192.168.85.255

        inet6 fe80::20c:29ff:fe54:dd3e  prefixlen 64  scopeid 0x20<link>

        ether 00:0c:29:54:dd:3e  txqueuelen 1000  (Ethernet)

        RX packets 5552  bytes 7247079 (6.9 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 2898  bytes 307666 (300.4 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

ens37: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.17.130  netmask 255.255.255.0  broadcast 192.168.17.255

        inet6 fe80::20c:29ff:fe54:dd48  prefixlen 64  scopeid 0x20<link>

        ether 00:0c:29:54:dd:48  txqueuelen 1000  (Ethernet)

        RX packets 1380  bytes 196227 (191.6 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 365  bytes 34395 (33.5 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

 

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536

        inet 127.0.0.1  netmask 255.0.0.0

        inet6 ::1  prefixlen 128  scopeid 0x10<host>

        loop  txqueuelen 0  (Local Loopback)

        RX packets 97609  bytes 26460105 (25.2 MiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 97609  bytes 26460105 (25.2 MiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I am able to access my application inside VM using browser at address https://192.168.85.155:8443/

Can someone please help advise how to configure the network?.

Thanks

Aali

Morning all,

Am trying to script some vMotions for lots of our VMs that we are moving to a new vSAN cluster.  VMs in the same vCenter are fine and complete without any issues.  VMs in the other vCenter (same SSO domain behind LB PSC) fail though with the following error:

Move-VM : 01/04/2017 08:52:41    Move-VM        The operation for the entity "TSTLDNVET1" failed with the following message: "A general system error occurred: Host not found (authoritative)"

At line:29 char:1

+ Move-VM -vm $drvm -Destination $destcluster -VMotionPriority High -Da ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Move-VM], SystemError

    + FullyQualifiedErrorId : Client20_TaskServiceImpl_CheckServerSideTaskUpdates_OperationFailed,VMware.VimAutomation.ViCore.Cmdlets.Commands.MoveVM

The command I am running (as part of a bigger script block):

elseif($vm.ParentHost -like "drldne*")

  {

  $drvm = Get-VM $vm.name -Server $SourceVCConn

  $targetPort = Get-VDPortGroup -VDSwitch $switch -Name $vm.DestinationPortGroup -Server $TarVCConn

  Move-VM -vm $drvm -Destination $destcluster -VMotionPriority High -Datastore $destinationDatastore -PortGroup $targetPort

  }

This vmotion works though through the Web Client.  Anyone seen this error before?  I cannot seem to see anything else in teh detail of it that can tell me why it is breaking.

hi everyone,

Please check out this new tool called "HTML Client Plugin Seed" to help you make the transition to HTML plugins:

• It is based on HTML SDK 6.5, so the generated plugin is compatible with both HTML Client 6.5 and Flex Client 6.0 or 6.5.
• The UI is 100% based on the Clarity Design System, a VMware open-source project.
• It uses the Angular 2+ framework and the Typescript language which have become industry standard for modern web applications.
• It comes with utilities and development tools that will speed up your development cycles, help you start with a good architecture and show you many best practices and patterns.

I look forward to your feedback!

(Check out the small survey at the very end of the PDF doc)

--Laurent

Message was edited by: Laurent Delamare plugin-seed.zip was missing some files. Please update to the correct version (242 KB)

Hi all experts,

Has any of you experts come across a step by step user guide or manual on how to change VLAN ID and IP addresses on a vCloud Suite Environment?

Or if you have any tips and trix you can share...all is helpful.

vCenter server is MS Windows 2008R2

SQL server is MS Windows 2008R2

vCloud Director is RedHat 6.x

vShield Manager for vCloud is Linux

NFS server for vCloud Director is MS Windows 2008R2

It is all vlans that we need to change.

vCloud access vlan

vCloud vMotion vlan

vCloud vxlan vlan

Management vlan (core mgmt vlan for vCenter/vCloud/vcns/sql/nfs servers)

Thank you in advance

/Tony

Buongiorno a tutti,

sono nuovo della community, così come del mondo vmware. Spero possiate aiutarmi.

Ho "ereditato" una macchina virtuale  windows xp che veniva utilizzata, e deve essere ora usata da me, dal mio predecessore in ufficio per effettuare connessioni ai clienti e, naturalmente, sviluppo.

La suddetta macchina ha un problema di fondo. Utilizza sempre la cpu al 100%. E non si tratta di un processo specifico, ma vari che, a turno, vanno a cannibalizzare le risorse.

Ciò comporta il fatto che, naturalmente, la macchina sia abbastanza lenta, ma a volte totalmente inutilizzabile (anche se solo nell'uso di alcune applicazioni, come ad esempio SonicWall VPN).

Sono vari giorni che ne sto provando di ogni, ma non  riesco a cavare un ragno dal buco. Workstation 11 è installato su una Workstation DELL con 16 GB di RAM, processore INTEL i7-4800MQ, anche se disco meccanico.

La cosa strana, è che questo problema ce l'ho solo con macchine virtuali XP (ho tentato di crearne una nuova, ma sembra avere lo stesso problema). Ho altre macchine Windows Server 2008 che invece vanno lisce come l'olio.

C'è qualche particolare impostazione che al momento ignoro?

Grazie mille.

Paolo