I think I found why some subroutines are not called. In our environment we don't use Repository Path (under VM Host profile) and it looks like those subs only called when the setting is configured. Ie. libvirt.pm:find_repository_image_file_paths() sub excludes .vmdk and returns proper -flat.vmdk file. KVM.pm::update_windows_image() is also called on a condition when Repository Path is present in a VM profile.
What does Repository Path do and how is it different from Base Images (Virtual Disk Path)? I use Virtual Disk Path (Base Images) and VM Working Directory Path for linked clones. Both paths are on a shared NFS storage where all VM hosts have access. Thank you, -- Dmitri Chebotarov Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging 223 Aquia Building, Ffx, MSN: 1B5 Phone: (703) 993-6175 Fax: (703) 993-3404 On Friday, March 8, 2013 at 13:06 , Andy Kurth wrote: > > > On 3/8/2013 12:53 PM, Dmitri Chebotarov wrote: > > I'm still working on details and testing, but at this point VCL loads > > VMware images on KVM hosts. > > I needed to make some changes to Windows XP image to load it on KVM - this > > link has details -> > > http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Prepare_the_Windows_operating_system_2. > > I did first two steps (remove vmware-tools & Enable IDE) on the VMware > > image and it loads on KVM just fine and everything appears working OK. > > > > The KVM.pm::update_windows_image should be doing this automatically. It > edits the registry of the offline Windows image to disable the VMware > Tools services and add the IDE disk entries. Please check if the > subroutine is working correctly in your environment. > > Thanks, > Andy
