I've tried running it locally and in other 2 servers in different locations. I used my AD account, and the administrator@vsphere.local account and i still get the repeated ones.

I have been running Windows 7 guest OS on OSX 10.10.5 for quite a long time without issues.  Suddenly the mapped drives are behaving oddly and I'm trying to figure out what has changed.  I'm getting corrupted recycle bin errors with my shared download folder.  I had to disable that and delete the $RECYCLE.BIN file - just turned off the recycle bin entirely.  With local drives I have no issues copying, creating, and deleting files.

On the network drives, I can read and duplicate files, writing to the directory.  But, I cannot delete the copied file from the guest OS.  I have to delete it from OSX.  If I attempt to delete any file from the network drive from the guest OS it says, You require permission from S-1-1-0 to make changes to this file.  Yet, I can copy it and write it back to the folder.  All my accounts are Admin.

-rwxrwxrwx     1 myname  staff    242872 Jul 22  2008 3g_booster - Copy.pdf

-rw-r--r--     1 myname  staff    242872 Jul 22  2008 3g_booster.pdf

The copied file incorrectly sets the permission bits but the owner appears correct.  From OSX it does not give me any issues deleting files.  As for creating files, if I attempt to write a new file from notepad under the guest OS Win7 it creates a 0 byte file, this time with the correct permissions, and says, You don't have permissions to modify files in this network location.  There is no Security tab visible for network folders.

I've tried re-installing the tools, removing the anti-virus, the firewall is off.  I've tried changing the network adapter from bridge to NAT, re-mapping network drives, and numerous reboots.

I have a WinXP guest OS which works fine.  I went to a backup copy of my Win7 VM from 2 months ago and it has the same problems.  Is there anything I can try?  Download 8.4 maybe?

Thanks.

So everything will be in that Ubuntu folder - no other bits hidden around the computer? That's great; thanks.

I made a mistake there, try with these lines instead

This is the output:

Hi,

I checked vmkernel.log during boot and it doesn't look good.

Those are the last entries I see in vmkernel.log

2018-09-16T18:32:18.733Z cpu4:2099026)PLOG: PLOGMapMetadataPartition:2607: SSD acks (2) 1 healthy MDs

2018-09-16T18:32:18.735Z cpu4:2099026)PLOG: PLOGProbeDevice:5728: Probed plog device <t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:1> 0x430ab0920d40 exists.. continue with old entry

2018-09-16T18:32:18.735Z cpu4:2099026)WARNING: LSOMCommon: LSOM_DiskGroupCreate:1481: Disk group already created uuid: 522288b0-d99b-a8f8-6dd5-44b7ef7354e4

2018-09-16T18:32:18.735Z cpu4:2099026)LSOMCommon: SSDLOG_AddDisk:877: Existing ssd found t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00:2

2018-09-16T18:32:18.735Z cpu4:2099026)PLOG: PLOGAnnounceSSD:7268: Successfully added VSAN SSD (t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00:2) with UUID 522288b0-d99b-a8f8-6dd5-44b7ef7354e4. kt 1, en 0, enC 0.

2018-09-16T18:32:18.735Z cpu4:2099026)VSAN: Initializing SSD: 522288b0-d99b-a8f8-6dd5-44b7ef7354e4 Please wait...

2018-09-16T18:32:18.736Z cpu5:2098374)PLOG: PLOGNotifyDisks:4546: MD 0 with UUID 52c93db2-c879-ce09-ea2a-664a0ae10485 with state 0 formatVersion 5 backing SSD 522288b0-d99b-a8f8-6dd5-44b7ef7354e4 notified

2018-09-16T18:32:18.736Z cpu5:2098374)PLOG: PLOG_Recover:884: !!!! SSD 522288b0-d99b-a8f8-6dd5-44b7ef7354e4 already recovered

2018-09-16T18:32:18.736Z cpu4:2099026)VSAN: Successfully Initialized: 522288b0-d99b-a8f8-6dd5-44b7ef7354e4

2018-09-16T18:32:18.736Z cpu4:2099026)PLOG: PLOGOpenDevice:4238: Disk handle open failure for device t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2, status:Busy

2018-09-16T18:32:18.737Z cpu4:2099026)PLOG: PLOGInitAndAnnounceMD:7737: Successfully announced VSAN MD (t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2) with UUID: 52c93db2-c879-ce09-ea2a-664a0ae10485. kt 1, en 0, enC 0.

2018-09-16T18:32:18.821Z cpu2:2097312)PLOG: PLOGOpenDevice:4238: Disk handle open failure for device t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2, status:Busy

2018-09-16T18:32:18.821Z cpu2:2097312)PLOG: PLOGOpenDevice:4238: Disk handle open failure for device t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2, status:Busy

2018-09-16T18:32:18.821Z cpu2:2097312)Vol3: 2674: Could not open device 't10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2' for probing: Busy

2018-09-16T18:32:18.821Z cpu2:2097312)WARNING: NFS: 1227: Invalid volume UUID t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2

2018-09-16T18:32:18.821Z cpu2:2097312)PLOG: PLOGOpenDevice:4238: Disk handle open failure for device t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2, status:Busy

2018-09-16T18:32:18.822Z cpu2:2097312)PLOG: PLOGOpenDevice:4238: Disk handle open failure for device t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2, status:Busy

2018-09-16T18:32:18.822Z cpu2:2097312)Vol3: 1201: Could not open device 't10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2' for volume open: Busy

2018-09-16T18:32:18.822Z cpu2:2097312)PLOG: PLOGOpenDevice:4238: Disk handle open failure for device t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2, status:Busy

2018-09-16T18:32:18.822Z cpu2:2097312)Vol3: 1201: Could not open device 't10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2' for volume open: Busy

2018-09-16T18:32:18.823Z cpu2:2097312)PLOG: PLOGOpenDevice:4238: Disk handle open failure for device t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2, status:Busy

2018-09-16T18:32:18.823Z cpu2:2097312)Vol3: 1201: Could not open device 't10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2' for volume open: Busy

2018-09-16T18:32:18.823Z cpu2:2097312)PLOG: PLOGOpenDevice:4238: Disk handle open failure for device t10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2, status:Busy

2018-09-16T18:32:18.823Z cpu2:2097312)Vol3: 1201: Could not open device 't10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2' for volume open: Busy

2018-09-16T18:32:18.823Z cpu2:2097312)FSS: 6092: No FS driver claimed device 't10.ATA_____Crucial_CT2050MX300SSD1_________________________1651150F2144:2': No filesystem on the device

2018-09-16T18:32:19.077Z cpu3:2099026)VC: 4616: Device rescan time 102 msec (total number of devices 6)

2018-09-16T18:32:19.077Z cpu3:2099026)VC: 4619: Filesystem probe time 253 msec (devices probed 4 of 6)

2018-09-16T18:32:19.077Z cpu3:2099026)VC: 4621: Refresh open volume time 3 msec

2018-09-16T18:32:19.203Z cpu5:2099027)vmw_ahci[0000001f]: scsiDiscover:channel=0, target=2, lun=0, action=0

2018-09-16T18:32:19.203Z cpu5:2099027)vmw_ahci[0000001f]: scsiDiscover:No media

2018-09-16T18:32:19.203Z cpu5:2099027)vmw_ahci[0000001f]: scsiDiscover:channel=0, target=3, lun=0, action=0

2018-09-16T18:32:19.203Z cpu5:2099027)vmw_ahci[0000001f]: scsiDiscover:No media

2018-09-16T18:32:19.203Z cpu5:2099027)vmw_ahci[0000001f]: scsiDiscover:channel=0, target=4, lun=0, action=0

2018-09-16T18:32:19.203Z cpu5:2099027)vmw_ahci[0000001f]: scsiDiscover:No media

2018-09-16T18:32:19.203Z cpu5:2099027)vmw_ahci[0000001f]: scsiDiscover:channel=0, target=5, lun=0, action=0

2018-09-16T18:32:19.203Z cpu5:2099027)vmw_ahci[0000001f]: scsiDiscover:No media

 

And some here

2018-09-16T18:27:34.266Z cpu2:2097506)LSOMCommon: SSDLOGInitDescForIO:803: Recovery complete with Success... device: t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00:2

2018-09-16T18:27:34.266Z cpu1:2097600)ScsiDeviceIO: 3015: Cmd(0x459a40fae580) 0x85, CmdSN 0x0 from world 2097505 to dev "t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00" failed H:0x0 D:0x2 P:0x0 Valid sense data: 0x5 0x20 0x0.

2018-09-16T18:27:34.266Z cpu2:2097506)LSOMCommon: LSOM_RegisterDiskAttrHandle:124: t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00:2 is a non-SATA disk

2018-09-16T18:27:34.266Z cpu2:2097506)LSOMCommon: LSOM_RegisterDiskAttrHandle:131: DiskAttrHandle:0x4313fcf6c7a8 is added to disk:t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00:2 by module:lsomcommon

2018-09-16T18:27:34.266Z cpu2:2097506)PLOG: PLOG_DeviceCreateSSDLogHandle:1096: Registered APD callback for 522288b0-d99b-a8f8-6dd5-44b7ef7354e4

2018-09-16T18:27:34.266Z cpu2:2097506)LSOMCommon: IORETRY_Create:2585: An IORETRY queue for diskUUID 522288b0-d99b-a8f8-6dd5-44b7ef7354e4 (0x4313fcf7e850) is NOT encrypted

2018-09-16T18:27:34.266Z cpu2:2097506)LSOMCommon: IORETRY_Create:2624: Queue Depth for device 522288b0-d99b-a8f8-6dd5-44b7ef7354e4 set to 920

2018-09-16T18:27:34.266Z cpu2:2097506)ScsiEvents: 300: EventSubsystem: Device Events, Event Mask: 20, Parameter: 0x4313fcf7e850, Registered!

2018-09-16T18:27:34.267Z cpu2:2097506)Created VSAN Slab PLOGIORetry_slab_0000000000 (objSize=272 align=64 minObj=2500 maxObj=25000 overheadObj=0 minMemUsage=836k maxMemUsage=8336k)

2018-09-16T18:27:34.267Z cpu2:2097506)Created VSAN Slab PLOGIORetry_slab_0000000001 (objSize=272 align=64 minObj=2500 maxObj=25000 overheadObj=0 minMemUsage=836k maxMemUsage=8336k)

2018-09-16T18:27:35.267Z cpu2:2097506)PLOG: PLOGAnnounceSSD:7253: Trace task started for device 522288b0-d99b-a8f8-6dd5-44b7ef7354e4

2018-09-16T18:27:35.267Z cpu2:2097506)PLOG: PLOGAnnounceSSD:7268: Successfully added VSAN SSD (t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00:2) with UUID 522288b0-d99b-a8f8-6dd5-44b7ef7354e4. kt 1, en 0, enC 0.

2018-09-16T18:27:35.267Z cpu2:2097506)VSAN: Initializing SSD: 522288b0-d99b-a8f8-6dd5-44b7ef7354e4 Please wait...

2018-09-16T18:27:35.268Z cpu4:2098374)PLOG: PLOGNotifyDisks:4546: MD 0 with UUID 52c93db2-c879-ce09-ea2a-664a0ae10485 with state 0 formatVersion 5 backing SSD 522288b0-d99b-a8f8-6dd5-44b7ef7354e4 notified

2018-09-16T18:27:35.268Z cpu4:2098374)VSANServer: VSANServer_InstantiateServer:3380: Instantiated VSANServer 0x430ab0922e18

2018-09-16T18:27:35.269Z cpu5:2098134)Created VSAN Slab RcSsdParentsSlab_0x4313fcf83200 (objSize=208 align=64 minObj=2500 maxObj=25000 overheadObj=0 minMemUsage=668k maxMemUsage=6668k)

2018-09-16T18:27:35.270Z cpu5:2098134)Created VSAN Slab RcSsdIoSlab_0x4313fcf83200 (objSize=65536 align=64 minObj=64 maxObj=25000 overheadObj=0 minMemUsage=4352k maxMemUsage=1700000k)

2018-09-16T18:27:35.270Z cpu5:2098134)Created VSAN Slab RcSsdMdBElemSlab_0x4313fcf83200 (objSize=32 align=64 minObj=4 maxObj=4096 overheadObj=0 minMemUsage=4k maxMemUsage=264k)

2018-09-16T18:27:35.270Z cpu5:2098134)Created VSAN Slab RCInvBmapSlab_0x4313fcf83200 (objSize=56 align=64 minObj=1 maxObj=1 overheadObj=14 minMemUsage=4k maxMemUsage=4k)

2018-09-16T18:27:35.270Z cpu2:2098386)Global: Virsto_CreateInstance:163: INFO: Create new Virsto instance (heapName: virstoInstance_00000001)

2018-09-16T18:27:35.272Z cpu2:2098386)DOM: DOMDisk_GetServer:259: disk-group w/ SSD 522288b0-d99b-a8f8-6dd5-44b7ef7354e4 on dom/comp server 0

2018-09-16T18:27:35.272Z cpu2:2098386)LSOM: LSOMSendDiskStatusEvent:5424: Throttled: Unable to post disk status event for disk 522288b0-d99b-a8f8-6dd5-44b7ef7354e4: Not found

2018-09-16T18:27:35.447Z cpu0:2098099)LSOMCommon: SSDLOGLogEnumProgress:1406: Recovery progress: 1500 of ~502343 (0%) log blocks. 0s so far, ~58s left. device: t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00:2

vSAN CacheDisk t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00:2: Recovery progress: 1500 of ~502343 (0%)2018-09-16T18:27:35.612Z cpu3:2098099)LSOMCommon: SSDLOGLogEnumProgress:1406: Recovery progress: 3000 of ~502343 (0%) log blocks. 0s so far, ~56s left. device: t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00:2

vSAN CacheDisk t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00:2: Recovery progress: 3000 of ~502343 (0%)2018-09-16T18:27:35.775Z cpu2:2098099)LSOMCommon: SSDLOGLogEnumProgress:1406: Recovery progress: 4500 of ~502343 (0%) log blocks. 0s so far, ~55s left. device: t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00:2

vSAN CacheDisk t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00:2: Recovery progress: 4500 of ~502343 (0%)2018-09-16T18:27:35.937Z cpu2:2098099)LSOMCommon: SSDLOGLogEnumProgress:1406: Recovery progress: 6000 of ~502343 (1%) log blocks. 0s so far, ~55s left. device: t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00:2

vSAN CacheDisk t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00:2: Recovery progress: 6000 of ~502343 (1%)2018-09-16T18:27:36.102Z cpu3:2098099)LSOMCommon: SSDLOGLogEnumProgress:1406: Recovery progress: 7500 of ~502343 (1%) log blocks. 0s so far, ~54s left. device: t10.NVMe____WDC_WDS256G1X0C2D00ENX0__________________B10A46444A441B00:2

Any idea what might be going on?

Hi,

My host is Win 10 and has a guest OS Win Server 2012 running in VMWare Workstation 14.1.

I want to debug a user application runs in the Win Server 2012. The current plan is to run visual studio 2015 or 2017 on the host (Win10) and attach the process in the Win Server 2012 because I have a complete source code for the application. A dynamic debugging would be much help to find the root cause. I think this is possible for VMWare Workstation 9, here is the reference document: https://www.vmware.com/pdf/desktop/ws9_visualstudio_debug.pdf

But I did not find the visual studio plugin for VS 2015 or 2017, and also the latest above document for VMWare 14.

Would you please kindly tell me whether this feature is still available. If no, is there any other method to support attach a process in guest OS from the visual studio running in the host.

Thank you very much!

The answer is no.

For HA,vMotion there are few requirements

- Shared Storage!

- Essentials Plus license or higher (Standard, Enterprise+)

- vCenter

and maybe some more..... but your dealbreaker is vSphere Essentias which doenst come with HA. Take a look to  https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vsphere/vmware-vsphere-essentials-kits-datash… or just google for the vsphere essenials editions overview.

Regards,

Joerg

Therefore when a host is down or powered off, the VMs will stay on the same host in powered off state.

Correction: They will show in an *inaccessible* state. The host to which they are registered is offline. They cannot be powered on unless manually registered on a separate host. If those VMs are stored on local storage, they will remain inaccessible until the owning host returns to service.

All clones completed successfully with the only exception for mdServer-000006.vmdk.

Please see that attached zip that I assembled per your instructions.

Thanks!

With Essentials licensing and just two hosts, I was presuming it would be local datastores

Cheers,

Supreet

Hi,

Try switching to windowed mode and then back to full screen.

Also note that under Security&Privacy -> Privacy tab -> Accessibility  item -> you have to enable the vmware-tools-daemon

Click the lock to tick the checkbox. Sorry that last remark only makes sense for running as guest OS, not host.

--

Wil

I am also trying to run ESXi 6.7 on a server with that same motherboard but I have been unsuccessful despite the network controller being reported as supported by Compatibility Guide. I have also tried to run an image with the net-e1000e-3.1.0.2-glr2 driver in it but still no luck.

Davide

This is kind of an odd question to ask, but I have just installed vrealize operations manager 6.7 in my test lab to learn about it. I have it fully installed and I have added a dns entry for the vapp in my dc and everything is pingable by the fqdn. After the vapp boots up fully it is showing the host name as: https://vrealizeclusternode/.

VrealizeClusterNode is not the name that I assigned to the vapp. My assumption is that since this is the only instance it has to hold that default name, but if not, how can I make the fqdn that I assigned show up? I am including screenshots of what I see also I am adding a screenshot of the area where I think my issue is coming from.

Hello offsidex,

"My assumption here is that it would be the same as any object  however I have questions like: Is the whole content library considered to be one object? How would vSAN handle big content librarues etc..."

Content Libraries stored on vsanDatastore appear to consist of just a namespace Object (for each library) with the data stored inside it (in sub-directories) as non-Object file data - this implies that the max-size of a Content Library stored on vsanDatastore would be 255GB (the namespace Object max size) - yes, I am aware the only external documentation we have regarding max sizes of Content Libraries is 1TB max file size, I will be getting in touch with our Documentation team regarding the implied caveat for vsanDatastore here if this is indeed the case.

"I am curious to know how the storage policies would interact with the library"

Content Libraries are stored on vsanDatastore as namespace Objects which appear to have plain FTT=1 FTM=RAID1 attributes - no implicit spbmProfileName applied, this means you can't change them by changing a SP (Storage Policy).

This doesn't mean these Objects won't be repaired etc. when in reduced availability, just that they are limited from an spbm management perspective.

I tinkered with it a bit and found that there is no effect on how these are created by changing to FTT=0 the vsanDatastore default SP, changing the node-level default policy attributes for cluster and namespaces to FTT=0 etc. so it looks like it must be using some other default of its own.

Using objtool setPolicy to change the attributes of the Objects does of course work though.

I (sadly!) don't have a lab with 255GB SSD free at the moment (HDD slow writing data) to test the effects of this but I would imagine is same as any namespace and can't write past 255GB.

Bob

Not sure about the other person but I would like to use a Config element to generate Cluster names (like MSCS needs).  I need to ensure that the other nodes in the vRO cluster are not doing the same thing at the same time and I assign the same cluster name to two different clusters.  I am using a database sequence to do that now but it would be faster to use vRO config elements if I knew that it was safe.

Carl L

It's possible to get the exact creation date of a VM? Using vRA?

Yes, it's possible. This is the build date.

How/where are you deploying the OVA?

Assumptions are always dangerous even if they often turn out correct