Important! This is an automatic machine translated page. If you can read english, you should Click Here to read the original English version of the article.

Moving a Linked Clone's Base Virtual Machine in VMware Moving Saistīts Clone's Base Virtual Machine VMware

If you are using the linked clone feature in VMware (and you should be), then you might be annoyed that you can't move the base virtual machine around without breaking all of the linked clones. Ja jūs izmantojat saistīti klona iezīme VMware (un jums vajadzētu būt), tad Jums varētu būt kaitina, ka jūs nevar pārvietot bāze virtuālā mašīna ap nesalaužot visas saistītās klonu.

The error you'll get will be similar to this: ” cannot open the disk D:\Ubuntu\Ubuntu.vmdk or one of the snapshot disks it depends on. Kļūda jūs saņemsiet būs līdzīgi šim: "Nevar atvērt diska D: \ Ubuntu \ Ubuntu.vmdk vai viens no momentuzņēmums diskiem tas ir atkarīgs. Reason: failed to lock the file.” Reason: failed to lock file. "

To fix this problem, open up the *.vmx file in your linked clone's directory, and find the following line: Lai atrisinātu šo problēmu, atvērt *. vmx failu saistīts klons direktorijā un atrodiet šādu rindu:

fileSearchPath = “.;D:\VMware\UbuntuBaseVM” fileSearchPath = "., D: \ VMware \ UbuntuBaseVM"

The path there will reflect the old location of the linked clone's base machine. Ceļš būs jāatspoguļo veco vietu, kas saistīti klona's bāze mašīna. Just update it to the new directory, and you are once again in business. Just to atjaunina, lai jaunu direktoriju, un jūs atkal biznesā.

This article was originally written on 01/2/07 Tagged with: Šis pants tika sākotnēji rakstīts uz 01/2/07 tagged with: VMware VMware

Daily Email Updates Daily Email Updates

You can get our how-to articles in your inbox each day for free. Jūs varat saņemt mūsu how-to rakstus savā pastkastītē katru dienu par brīvu. Just enter your name and email below: Vienkārši ievadiet jūsu vārdu un e-pasta zemāk:


Name: Vārds:
Email: E-pasts:

Comments (2) Komentāri (2)

  1. Louie Louie

    I moved the (machineName).vmdk.lck to the parent directory and was able to load successfully. Es pārcēlos (machineName). Vmdk.lck lai Parent Directory un varēja ielādēt veiksmīgi. I think you can just delete the (machineName).vmdk.lck completely Es domāju, ka jūs varat vienkārši izdzēst (machineName). Vmdk.lck pilnīgi

  2. ChrisA ChrisA

    perfect solution, thanks for the help. ideāls risinājums, paldies par palīdzību.


Our Friends Our Friends
Getting Started Getting Started


About How-To Geek Par How-To Geek
What Is That Process? Kas ir šis process?
svchost.exe svchost.exe
jusched.exe jusched.exe
dwm.exe dwm.exe
ctfmon.exe ctfmon.exe
wmpnetwk.exe wmpnetwk.exe
mDNSResponder.exe mDNSResponder.exe
wmpnscfg.exe wmpnscfg.exe
rundll32.exe rundll32.exe
wfcrun32.exe wfcrun32.exe
Ipoint.exe Ipoint.exe
Itype.exe Itype.exe
Wfica32.exe Wfica32.exe
Mobsync.exe Mobsync.exe
conhost.exe conhost.exe
Dpupdchk.exe Dpupdchk.exe Adobe_Updater.exe Adobe_Updater.exe

Copyright © 2006-2009 HowToGeek.com. Copyright © 2006-2009 HowToGeek.com. All Rights Reserved. All Rights Reserved.