Paul Walsh
asked on
Vmware 6.5 Existing hard disk (vmdk)
Hi,
I am in the process of cold moving a number of vm's from our old 5.5 platform to our new 6.5. Our storage server comprises of two disks, boot and storage. The storage disk is 2.7tb and is a separate virtual disk on a separate datastore, thin provisioned. When I register the vm on the new 6.5 host the storage disk doesn't get recognised correctly and has an alert icon next to it. The capacity on the disk is listed as zero, and I cannot increase the capacity as the option is greyed out. In the maximum size option it states: N/A Maximum virtual disk size will not be validated if datastore cluster is selected as storage. In the disk name section it identifies the file location in the following format []/vmfs/volume no xxx.vmdk
If I add the disk as an existing disk all seems fine apart from the fact the maximum disk size is listed as only 67gb (The actual disk size of 2.7tb is picked up) and I cannot change it. The disk file location is listed as expected: datastore name\disk name.vmdk.
Any clues as to why the second disk settings are not picked up correctly? Will the storage disk work/ be safe to use if I dd it as an exisiting disk with the above settings?
Cheers,
Paul
I am in the process of cold moving a number of vm's from our old 5.5 platform to our new 6.5. Our storage server comprises of two disks, boot and storage. The storage disk is 2.7tb and is a separate virtual disk on a separate datastore, thin provisioned. When I register the vm on the new 6.5 host the storage disk doesn't get recognised correctly and has an alert icon next to it. The capacity on the disk is listed as zero, and I cannot increase the capacity as the option is greyed out. In the maximum size option it states: N/A Maximum virtual disk size will not be validated if datastore cluster is selected as storage. In the disk name section it identifies the file location in the following format []/vmfs/volume no xxx.vmdk
If I add the disk as an existing disk all seems fine apart from the fact the maximum disk size is listed as only 67gb (The actual disk size of 2.7tb is picked up) and I cannot change it. The disk file location is listed as expected: datastore name\disk name.vmdk.
Any clues as to why the second disk settings are not picked up correctly? Will the storage disk work/ be safe to use if I dd it as an exisiting disk with the above settings?
Cheers,
Paul
ASKER
Hi,
The process I have been using has been - power off vm on old 5.5 host. Navigate to datastore where the virtual machine lives on 6.5, right click vmx file and register. Edit the settings of the newly registered vm (video graphics and nic vlan). Power on the the vm (answering the copied or moved question with copied). Check all services etc are running on the vm. When happy remove the vm from inventory on the old 5.5 vcenter. This has worked for all the other servers. Is this the incorrect method / if so how should I be doing this?
Cheers,
Paul
The process I have been using has been - power off vm on old 5.5 host. Navigate to datastore where the virtual machine lives on 6.5, right click vmx file and register. Edit the settings of the newly registered vm (video graphics and nic vlan). Power on the the vm (answering the copied or moved question with copied). Check all services etc are running on the vm. When happy remove the vm from inventory on the old 5.5 vcenter. This has worked for all the other servers. Is this the incorrect method / if so how should I be doing this?
Cheers,
Paul
So the VM never changes location on the datastore ?
it's just a remove and add to another inventory ?
and the 6.5 host can see all the datastores, that the 5.5 host can see ?
it's just a remove and add to another inventory ?
and the 6.5 host can see all the datastores, that the 5.5 host can see ?
ASKER
Hi,
Yes the datastore never changes, the 6.5 can see all of the datatstores the 5.5 can see. Interestingly if I add it as an extra existing disk it sees it fine, but the maximum size is only 67gb (it is a 2.7tb thin provisioned disk).
Cheers,
Paul
Yes the datastore never changes, the 6.5 can see all of the datatstores the 5.5 can see. Interestingly if I add it as an extra existing disk it sees it fine, but the maximum size is only 67gb (it is a 2.7tb thin provisioned disk).
Cheers,
Paul
Something is very odd here.
I think I would use VMware Converter, and create a V2V.
or Export/Import.
I think I would use VMware Converter, and create a V2V.
or Export/Import.
ASKER
Hi,
Can you have two vms connected to the same hard disk? If possible id like to attach the second hard disk to a brand new server and test that it will work / see if I still get the strange maximum size issue.
Cheers,
paul
Can you have two vms connected to the same hard disk? If possible id like to attach the second hard disk to a brand new server and test that it will work / see if I still get the strange maximum size issue.
Cheers,
paul
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Something is not correct if the disk is not being recognised.
please explain how this is being done.