I need to move some VMs that were created on 6.7 to 6.5 hosts.  I know I can't vMotion them and I know Veeam won't migrate them, but, can I create new VMs on the 6.5 hosts and point to the VMDKs of the 6.7 machines?  My storage is shared so I can "see" the VMDKs of the 6.7 machines.  I was hoping the difference in the 6.5 and the 6.7 is not in the VMDK but rather in the associated config files.

FYI - I've tried this and the VM on the 6.5 host is reporting no operating system found so I'm thinking I'm toast and wanted to ask here to be sure.

Thanks

PS - maybe I could use converter to convert them down...

Hi All,

We currently run VMware at two sites. Both sites use Dell SANS for storage. We have a few production vms that are managed from site 1 but the datastore is on site 2. The naming of the datastore to SAN volume do not match for many of the datastores. What is the easiest method to marry a VM datastore to its volume counterpart on the SAN?

Cheers,
Paul

I have VMware Workstation 14 Pro on Windows 10.  We exported a VM from an ESXi server (three files: dg.mf = 1 KB, dg.ovf = 10 KB, dg-disk1-vmdk = 53 GB) and I am trying to import it.  

"Failed to write content to disk C:\Virtual Machines\dg-disk1.vmdk. Reason: There is not enough space on the file system for the selected operation."

The three files together take 53 GB, while there are 145 GB free on the hard drive.  What could be the problem and how can I fix it?

Environment = Vcenter Version 6.7.0.20000 Build 10244845
ESXi, 6.5.0, 7967591

I shrank a flat-vmdk on a vm and now,  vcenter wont let me power on or storage migrate the VM.  

I followed this guide - https://virtualman.wordpress.com/2016/02/24/shrink-a-vmware-virtual-machine-disk-vmdk/
(I should never done it! Big mistake)  The guide seemed so straight forward and I did not think anything would happen.  

Error I get when I try to Storage Migrate the VM:

Error I get when I try to power on the VM:


Let me explain exactly what happen which may help you figuring out a solution:

1.)I Powered off the VM because memory hot add was not enabled and I needed to increase the RAM from 32gb to 228gb total.
When I went to increase the ram I mistakenly increased the Hard Disk from 80GB to 228GB and clicked ok!!!
With the VM still powered off, I decided to try and shrink the flat-vmdk following that above guide.

I followed the ONLY portion of the guide which shows how to edit the .vmdk descriptor file.

Keep in mind the VM was powered off the entire time.  So I skipped the first portion of that guide about shrinking the disk from Windows OS.  

I followed this guide exactly and successfully changed the flat-vmdk to show 80GB :)  But now I get those errors when trying either power on the VM or storage migrate it!!

Please help!

Environment = Vcenter Version 6.7.0.20000 Build 10244845
ESXi host version = 6.7 U1 11675023


We are trying to add a Host to a new cluster that was just created.
We are going through the process and the Host is on the network, it tests successfully in the ESXi console.  WE can ping the IP and the gateway and dns.


Here is the Issue:
When we go through the wizard to add a new host to this cluster we get the certificate warning, and select "Yes" and go through and select a license and finish.  The task gets to 100% and then fails with the following error:

Cant add Host to Cluster - A general system error occurred: Unable to get signed certificate forhost name 'ESXi1.mydomain.com' ip 'xx.xx.xx': Error: Failed to connect to the remote host, reason = rpc_s_no_memory (0x16c9a012). (382312466)

Never seen this before, any ideas?

If I unregister a VM from one Host, and then RE-register it to a completey different host, does it receive a new GUID? or whatever and potentially cause issues with Veeam backup of the VM for example?

The reason why I ask is because I am tasked with migrating VM's this way since there is no absolutely no other option available and I need to get certain VM's off of one host and onto another.  My only concern is perhaps the GUID of the VM or its ID will change and cause issues with Veeam backup.  Is this a valid presumption?

Is it safe to delete all the -aux.xml files I see left over from sVmotion'ing vm's?


I have seen a thread on here from earlier which shows that it is safe to delete, but I am noticing a whole lot of them being left over after I sVmotion vm's to other datastores.  

And the dates on them are 12/12/2018.  That's not that long ago so I am a little nervous to delete them.  I read somewhere that they are old ver 4.x descriptor files for snapshots and are no longer used in ver 5.x and above.  Can someone confirm this?

I would like to delete them all instead of moving each and every one of them to their VM folder on the destination datastore.

VMware workstation pro 14.  

Experts, how do I enable the ability to cut and paste from HOST to VM?

See screenshots of my VMs PREFERENCe < INPUT tab.

I am unable to cut and past from HOST to VM on text or applications.
vmware1.png
vmware2.png

I have a Ruckus ICX 7250 24 port switch with 8 Licensed 10 GB SFP+ ports and I will be getting a Dell EMC ME4024 Storage Array with 8 Port Dual Controller for iSCSI SFP+. I would like to know how to configure it on the switch and how to best use it with vmware vsphere 6.5.

Any help would be greatly appreciated as I've never had to configure one from scratch.

Thank you

Need a good P2V plan for a DC.

Here are the requirements:

Physical DC = server 2008 R2

Converted VM = needs to be server 2012R2

Needs to have the same name and IP as the physical dc.

What would be the best way to accomplish this task?

Here is my plan so far:

1.)      Transfer all FSMO rolls to another already running DC
2.)      Demote, and Decommission Physical DC, and shut down
3.)      Reset computer object in AD
4.)      In Vcenter, Stand up new vm
5.)      Make it a member server with same name as the physical
6.)      Give it same IP as old physical dc
8.)      Promote to DC

Will this work?  is there a better way?

your thoughts