Converter Log Analysis
Converter Log Analysis
Ajay Anthony
Note:
The above was derived at by reading through the log file using a Top to Bottom approach
of the vmware-converter.log file. Therefore this would be the sequence of events that
you can see occur in the converter log file when you move from the top of the log file and
scroll down to the bottom of the log file(where the error would be). This analysis was
done using log files from successful imports.
Converter Version and Build Number:
Log Excerpt:
Log Excerpt:
Log Excerpt:
Log Excerpt:
If
host = "10.16.112.2", implies the host being imported is a Remote Physical machine
host = "", implies this is the physical machine that is being imported.
If the source is a .sv2i image, the above lines would look like this
(sysimage.V2ISourceVMSpec) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
v2iFilePath = "C:\Documents and Settings\ajaya\Desktop\test.sv2i",
password = <unset>
}
If the source is a VM, the above lines would look like this
(sysimage.HostedSourceVMSpec) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
vmxFilePath = "C:\Virtual Machines\Servers\Terminus\Windows Server 2003
Standard Edition.vmx"
}
Number of Volumes and Active Volumes Information:
Log Excerpt:
This follows right after the Active volume information in the log.
Log Excerpt:
Log Excerpt:
Log Excerpt:
Log Excerpt:
'
App'1216 verbose] [importSource,461] (vim.vm.device.VirtualPCNet32) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
key = 1009,
deviceInfo = (vim.Description) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
label = "NIC2",
summary = "VMware Virtual Ethernet Adapter for VMnet1"
},
backing = (vim.vm.device.VirtualEthernetCard.LegacyNetworkBackingInfo) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
deviceName = ""
},
connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,
controllerKey = <unset>,
unitNumber = <unset>,
addressType = "manual",
macAddress = "00:50:56:C0:00:01",
wakeOnLanEnabled = <unset>
}
'
App'1216 verbose] [importSource,461] (vim.vm.device.VirtualPCNet32) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
key = 1010,
deviceInfo = (vim.Description) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
label = "NIC3",
summary = "VMware Virtual Ethernet Adapter for VMnet8"
},
backing = (vim.vm.device.VirtualEthernetCard.LegacyNetworkBackingInfo) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
deviceName = ""
},
connectable = (vim.vm.device.VirtualDevice.ConnectInfo) null,
controllerKey = <unset>,
unitNumber = <unset>,
addressType = "manual",
macAddress = "00:50:56:C0:00:08",
wakeOnLanEnabled = <unset>
}
'
App'1216 verbose] [importSource,464] 3 NICs found
The above snippet provides the number of NICs discovered by converter and their Mac
addresses.
Log Excerpt:
Shows the number of physical drives available and the amount of free space. Also
shows the volume (partition information) on these drives with their drive letters.
Log Excerpt:
disks = (sysimage.DiskInfo) [
(sysimage.DiskInfo) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
id = "disk={9ba2498e79b590fd75d62d8b65fa945c367c0fea}",
capacityInBytes = 160000000000,
deviceNumber = 0
},
(sysimage.DiskInfo) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
id = "disk={5c822bdfe4346fded26a0a0854198ded817c6666}",
capacityInBytes = 750156374016,
deviceNumber = 1
}
],
volumes = (sysimage.VolumeInfo) [
(sysimage.VolumeInfo) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
id = "attVol={computer={2202622998d91b89190c31c8980df6baba3cfd5d},1}",
driveLetter = "d:",
capacityInBytes = 750145503744,
spaceUsedInBytes = 185891017216,
systemVolume = false,
activeVolume = false,
filesystemUnderstood = true,
diskDeviceNumber = 1
},
(sysimage.VolumeInfo) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
id = "attVol={computer={2202622998d91b89190c31c8980df6baba3cfd5d},2}",
driveLetter = "c:",
capacityInBytes = 39843224064,
spaceUsedInBytes = 28783663616,
systemVolume = true,
activeVolume = true,
filesystemUnderstood = true,
diskDeviceNumber = 0
}
For example, from the above snippet, this is the info that we can derive at.
• 2 physical hard drives; one with a capacity of 160 GB and the other with
capacity about 700 GB.
• Two partitions. One Partition (d:)on the 700 GB Hard Drive (
diskDeviceNumber = 1) with a supported file system (filesystemUnderstood =
true,) using the complete capacity with used space of about 174 GB. The
lines
systemVolume = false,
activeVolume = false, show that there is no OS installed on this partition.
• C: is from the 160 GB harddrive and has about 40 GB of space with free space
of about 10 GB. Also, this is the partition with the OS.
• Another thing that you can deduce is that the rest of 160 GB hard drive is
either unallocated or a partition that Converter does not understand.
Target Machine Info
Log Excerpt:
Target VM specification:
Log Excerpt:
'
App'724 verbose] [vmImporter,191] params:
(sysimage.ImportParams) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
targetProductVersion = "PRODUCT_MANAGED",
diskType = "VMFS",
preallocateDisks = false,
clonePagefile = false,
nicMapping = (string) [],
volumesToClone = (sysimage.VolumeCloneInfo) [
(sysimage.VolumeCloneInfo) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
volumeId =
"virtVol={computer={8061a3b8ea86a9d75451874a952f45d7ec6f0d1},0}",
bResize = true,
newCapacityInBytes = 10737418240
},
(sysimage.VolumeCloneInfo) {
dynamicType = <unset>,
dynamicProperty = (vmodl.DynamicProperty) [],
volumeId =
"virtVol={computer={8061a3b8ea86a9d75451874a952f45d7ec6f0d1},1}",
bResize = true,
newCapacityInBytes = 524288000
}
The above log snippet shows that the target is going to a VMFS partition on a ESX server
managed by a VC machine. The destination VM is configured with 2 partitions, a 10 GB
partition and a .5 GB partition. The line “ bResize = true” implies that they the option to
shrink the disk was chosen while selecting disks. Which would then imply that the
process of cloning would be File Level Cloning and not Block Level Cloning.
This is when the process of creating the VM on the destination and the cloning of the
volumes begin.
Log Excerpt:
The datastore information is given along with IP information and port number.
Log Excerpt:
From the above log snippet, it can be seen that there are 2 partitions for the destination
VM and its sizes are also shown.
Log Excerpt:
The above log snippet is seen if Converter sees two volumes and the user selects just one.
Log Excerpt:
The target VM was created at the destination at the shown File path.
The below log file snippet shows reconfiguration parameters since there were no OS
found. In general, when there is an OS, the log does not show up.
Log Excerpt: