https://communities.vmware.com/thread/121798?start=0&tstart=0 Also, check to see there are no snapshots on the VMs you are attempting to migrate. 1 Habanero OP mxtj Aug 13, 2013 at 10:14 UTC See if you can ESX/ESXi 4.0 and later hosts do not require vMotion configuration n order to perform migration with Storage vMotion. To relocate a virtual machine's storage (including disks) 1 Determine the path to the virtual machine configuration file. 2 Run svmotion, for example: svmotion --url=https://myvc.mycorp.com/sdk --datacenter=DC1 --vm="[storage1] myvm/myvm.vmx:new_datastore" The example is You 50GB related file is what leads me to believe there is a snapshot (which is allowed in virtual compatibility mode) of the RDM volume. Source
Generally the problem will be caused by one of three things. 1. Join the community Back I agree Powerful tools you need, all for free. C:\>vifs.pl --server esx1.virtuallab.com --username root --password esxsvr40 -listds Content Listing --------------- Storage1 iSCSI_Shared C:\>vifs.pl --server esx2.virtuallab.com --username root --password esxsvr40 -listds Content Listing --------------- datastore1 iSCSI_Shared C:\>svmotion.pl --url=https://vcenter.virtuallab.com --datacenter="Virtual Lab" --vm Get 1:1 Help Now Advertise Here Enjoyed your answer?
By default, the virtual disk file has the same name as the VMX file but has a .vmdk extension. 3 (Optional) Use vifs to verify that you are using the correct This can be caused by another disk with the same VMDK file name being referenced by the VM. Thanks 0 Datil OP Sean Donnelly Aug 13, 2013 at 2:18 UTC Is your SAN Fibre or iSCSI? You'll need to enter either the WWN (Fibre) or IQN (iSCSI) of the LUN, which you can retrieve from your storage environment.
The svmotion command supports both interactive or noninteractive mode. Vmkernel Log And then the other way around. Can both esxi hosts see the storage so that vMotion can work properly? A migration with Storage vMotion invloves one access to the source datastore and one access to the destination datastore.
Demonstrates how to access the traditional view to begin managing your virtual mac… VMware Advertise Here 675 members asked questions and received personalized solutions in the past 7 days. Noninteractive Mode In noninteractive mode, the svmotion command uses the following syntax: svmotion [
Simply fill out this brief survey by 11:45 p.m. http://webinweb.net/unable-to/vmware-vmotion-unable-to-access-file.html You may get a better answer to your question by starting a new discussion. About Me I'm a System Engineer working with VMware & Oracle products. Got all working properly! Clone Virtual Machine Error Caused By File /vmfs/volumes/
That fails with the error - A general system error occurred: error while calling DiskLibWrapperLoader_IsDeltaDisk. The *Basic System Administration* manual discusses how to use svmotion. So if you dont want to go through the steps of committing the snapshots,etc, etc, one approach is to leave the disks as such and just clone the machine into a have a peek here Re: Vmotion error - "unable to access the virtual machine configuration: Unable to access File" NTurnbull Oct 1, 2009 7:21 AM (in response to BankTech) Is this vm on local storage?
Corrupt VMX file: There is a possibility that the VM's VMX file has corrupted. You can try to commit all snapshots prior to the migration (always a good idea). VMWare ESX - Creating a Windows XP VM and getting error: "Setup did not find any hard disk drives installed in your computer." Outlook Web Access (OWA) - How to fix Vmware Support I browse the datastore this VM is on, and find that there is a /hostname1_2.vmdk, but the file size on it is only .48k, obviously wrong.
I did find out with the issue was though when I attempted to do a storage motion with the VM. You must also make sure the mapping of that raw LUN is identicle on each ESX host involved in the vmotion. BankTech: vMotion requires the LUN the vm is sitting on to be shared (with the same ID) between the hosts. Check This Out Re: Vmotion error - "unable to access the virtual machine configuration: Unable to access File" acuster Jan 18, 2008 6:47 AM (in response to acuster) Update.It was actually a pretty simple
I am not very experienced at troubleshooting any deeper than the VC / GUI. I checked all the SAn settings for each LUN across all three of my ESX hosts and they are identical. Disk Naming Conflict: Two or more disks with the same VMDK name. Join Now When I try to migrate 2 servers on the same ESX host to another ESX host, I get the following messages when trying to move the server "File Server":
Good Luck 0 Message Author Comment by:Ailbe ID: 339052832010-10-14 I think the RDM issue is becoming a distraction. The command prompts you for the information necessary to complete the storage migration. You can use svmotion to initiate migrations for virtual machines running on either ESX or ESXi hosts. Like Show 0 Likes (0) Actions Go to original post Actions Remove from profile Feature on your profile More Like This Retrieving data ...
Specify this option to locate individual virtual disks to different datastores. Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We Join our community for more solutions or to ask questions. Don't know if that is also why I can't vmotion.
Thanks -lou Reply Subscribe RELATED TOPICS: BIOS Update Latitude E6510 A05 to A10 and Up Unable to Clone VCENTER VM Machine to another Host / Datastore vsphere 5.1 storage and Storage vMotion Requirements and Limitations Virtual machines with snapshots cannot be migrated using Storage vMotion. For virtual compatibility mode RDMs, you can migrate the mapping file or convert to thick-provisioned or thin-provisioned disks during migration as long as the destination is not a NFS datastore. That does at least explain why that happened. 0 LVL 28 Overall: Level 28 VMware 24 Storage 5 IT Administration 1 Message Accepted Solution by:bgoering bgoering earned 500 total points
I'm actually happy with it the way it is now, so I've deleted the original vm and just working off the clone with the datastore. Now what you need to do is work out what is actually locking this file and then (unsurprisingly) find a way to unlock it. I've never seen that happen before where a clone converts an RDM to .vmdk so even though it *seems* to be working, I am not sure it is right.