I have 1 physical machine with 2 datastores.
Today 2 machines on my datastore1 stalled due to running out of diskspace.
I chose a Windows 7 machine that I use for Spiceworks and a backup service, and tried to move the entire folder ("Windows7") to datastore2. In It didnt let me (I suspect because there was already a folder there of the same name) so I copied the main VMX file that then allowed my stalled machines to start.
My question then is if I copy the rest of the files into the Windows7 folder on datastore2, what is the configuration file I must change and how to make it work once again? (Is it the vmx file?)
In the datastore1 folder initially there was (Windows7.vmdk, .log, .nvram, .vmxf * .vmsd) and in datastore2 (Windows7_1.vmdk and Windows7_2.vmdk)
.vmx file:
.encoding = "UTF-8"
config.version = "8"
virtualHW.version = "8"
pciBridge0.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
hpet0.present = "TRUE"
nvram = "Windows 7.nvram"
virtualHW.productCompatibility = "hosted"
powerType.powerOff = "soft"
powerType.powerOn = "hard"
powerType.suspend = "hard"
powerType.reset = "soft"
displayName = "Spiceworks & Cloudbacko"
extendedConfigFile = "Windows 7.vmxf"
floppy0.present = "TRUE"
scsi0.present = "TRUE"
scsi0.sharedBus = "none"
scsi0.virtualDev = "lsisas1068"
memsize = "3072"
scsi0:0.present = "TRUE"
scsi0:0.fileName = "Windows 7.vmdk"
scsi0:0.deviceType = "scsi-hardDisk"
ide1:0.present = "TRUE"
ide1:0.clientDevice = "TRUE"
ide1:0.deviceType = "atapi-cdrom"
ide1:0.startConnected = "FALSE"
floppy0.startConnected = "FALSE"
floppy0.fileName = ""
floppy0.clientDevice = "TRUE"
ethernet0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.networkName = "VM Network"
ethernet0.addressType = "generated"
guestOS = "windows7"
uuid.location = "56 4d d5 ab cd 99 38 02-2c 84 aa d6 b1 ae c4 20"
uuid.bios = "56 4d d5 ab cd 99 38 02-2c 84 aa d6 b1 ae c4 20"
vc.uuid = "52 2a f9 79 08 f8 f0 54-92 62 7b b5 96 eb 6f b3"
ide1:0.fileName = ""
ethernet0.generatedAddress = "00:0c:29:ae:c4:20"
svga.vramSize = "8388608"
vmci0.id = "-1313946592"
tools.syncTime = "FALSE"
cleanShutdown = "TRUE"
bios.forceSetupOnce = "FALSE"
replay.supported = "FALSE"
sched.swap.derivedName = "/vmfs/volumes/500d6348-94b39d94-ebaf-d4ae52b13633/Windows 7/Windows 7-da2816a0.vswp"
replay.filename = ""
scsi0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "160"
ethernet0.pciSlotNumber = "32"
vmci0.pciSlotNumber = "33"
scsi0.sasWWID = "50 05 05 6b cd 99 38 00"
ethernet0.generatedAddressOffset = "0"
tools.remindInstall = "TRUE"
hostCPUID.0 = "0000000b756e65476c65746e49656e69"
hostCPUID.1 = "000206c220200800029ee3ffbfebfbff"
hostCPUID.80000001 = "0000000000000000000000012c100800"
guestCPUID.0 = "0000000b756e65476c65746e49656e69"
guestCPUID.1 = "000206c200010800829822030febfbff"
guestCPUID.80000001 = "00000000000000000000000128100800"
userCPUID.0 = "0000000b756e65476c65746e49656e69"
userCPUID.1 = "000206c220200800029822030febfbff"
userCPUID.80000001 = "00000000000000000000000128100800"
evcCompatibilityMode = "FALSE"
vmotion.checkpointFBSize = "8388608"
checkpoint.vmState = ""
sched.scsi0:0.shares = "normal"
sched.scsi0:0.throughputCap = "off"
scsi0:1.present = "TRUE"
scsi0:1.fileName = "/vmfs/volumes/530afcdc-7a68e1e6-ce74-d4ae52b13631/Windows 7/Windows 7_2.vmdk"
scsi0:1.mode = "persistent"
scsi0:1.ctkEnabled = "FALSE"
scsi0:1.deviceType = "scsi-hardDisk"
scsi0:1.redo = ""
Do you have vcenter so you can do a storage vmotion? That would be the easiest way to move the VM, split or not.
No I don't have vCenter...
OKay, then you're going to have to do it the old fashioned way... using the VMKFSTOOLS command.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=900
You'll probably need to remove the VMDK from the VM (not delete it), move it, and then re-add it back to the VM manually.
That gives me something to read over the weekend then!
Thanks!
If you do not have vcenter, you can use VMKFSTOOLS.
Alternatively you can use move option from VI client (This is available from datastore browser). Please refer below 2 threads where I have posted step by step procedure to carry out file migration from one DS to other from VI client:
ESXi 5.5 - Move primary VMDK file only to different datastore?