Features | Documentation | Technical Resources | Knowledge Base
P2V 2.1.2 Release Notes
Check back frequently for additions
and updates to these release notes. Version 2.1.2 | 09/21/06 | Build 31118
Check back frequently for additions and updates to these release notes.
Version 2.1.2 | 09/21/06 | Build 31118
What's in the Release Notes
The release notes cover the following topics:
What's New in P2V Assistant 2.1.2
P2V Assistant 2.1.2 includes the following new support:
P2V Assistant 2.1.2 includes the following fixes and features:
What's New in P2V Assistant 2.1.1
The P2V Boot CD 2.1.1 includes several fixes to allow P2V cloning of a wider range of hardware. Specifically:
The P2V Assistant 2.1.1 includes several fixes as well:
What's New in P2V Assistant 2.1
P2V version 2.1 contains many new features, including:
The P2V Boot CD now automatically boots into a network-enabled, full-featured graphical desktop interface upon startup.
Based on the Linux Live CD distribution Knoppix 3.8.1, this release includes all the tools you'd expect to have on a full desktop operating system installation, including web browser support, graphical tools for configuring and setting up disks and network devices, and many other features.
The P2V setup process itself has been streamlined and many bugs have been fixed. The interface has been optimized for the most common case (transferring data from a server on a network using DHCP).
Note: For machines with 64 megabytes of RAM or less, the P2V Boot CD will remain in text console mode. If you wish to start the P2V Boot CD in text console mode, at the boot prompt, please enter:
to start the boot CD at run level 2 (console-only mode).
For more boot options to enable or disable specific hardware options, please see the Knoppix boot parameters document.
Note: The Hardware Support Customizer has been provided as an experimental tool, intended to assist customers whose hardware is not explicitly listed in the P2V Boot CD's hardware database.
To ensure the P2V Boot CD works reliably across hardware that isn't explicitly recognized by the hardware support database shipped with the product, this graphical tool allows you to add your own hardware to the list of recognized devices.
To start the Hardware Support Customizer, click on its icon in the graphical desktop interface's toolbar.
To find your unrecognized devices and add them to the
Hardware Support Customizer, check the most recent portion of the file /etc/bootcdlog.txt.
Open a terminal or press Ctrl-Alt-F2, and run:
Note down the vendor name and corresponding numeric PCI IDs for
your unrecognized device. For example, if your
Ethernet card was not recognized, check the corresponding two lines in bootcdlog.txt:
would tell me I had an AMD (vendor ID 1022) device with ID 2000.
To find the correct driver for this device, use your favorite search engine using the vendor name, ID, and device ID. Using the information in the example above you should be able to find the Linux pcnet32 driver, which is the correct driver for this device.
In the Hardware Customizer, select Add Device, enter the vendor and device details, as well as the name of the Linux driver to use for your device, and the P2V Boot CD will automatically re-scan your hardware and load the driver for your device.
While adding completely new drivers to the P2V Boot CD is not yet supported, by using the Hardware Support Customizer you can ensure even the latest revisions of your storage and network devices are correctly recognized by the corresponding Linux driver without having to wait for a new release of the P2V boot CD.
You can even save your customized hardware support list to external media (floppy, other hard drive partitions, or other device) and your customized list will be used on reboot.
From the Hardware Support Customizer, just click Export Hardware Support List and copy the exported file to your external media. Save the file with the filename pcitable in the top-level directory of your media. This allows system administrators running P2V on a large number of machines to use their own customized hardware support list.
Security Alerts for This Release
As of this writing, no security alerts have been identified specifically for P2V 2.1.
Please refer to KB 1107 for VMware product security alerts.
Check the VMware Knowledge Base for updates to the issues described in this document. To review all Knowledge Base articles related to P2V, search for the keyword "P2V".For any known issue that has a Knowledge Base article link, please use this path to access the article. Change the Knowledge Base number in the URL.
Pertinent Knowledge Base Articles
Boot CD Ethernet Driver Tool
One of the most commonly reported issues with the P2V Boot CD is trouble on specific network and Ethernet card combinations where media speed and duplex autonegotiation fails.
To address this issue, P2V 2.1 includes a new program, ethtool. This program unifies media speed and duplex settings across all Ethernet drivers in Linux 2.6.
Here's an example, running ethtool on the first
Ethernet device in the system, setting it to 100baseT speed and full duplex:
Note: sudo is a program shipped with the P2V Boot CD to run specified programs as the administrative user, "root". By default, programs executed in a terminal are started safely as a non-administrative user, but ethtool requires root access to run.
You can also set the speed to 10baseT, 1000baseT, and the duplex to half, among other options.
Run man ethtool from a terminal for a full explanation of ethtool's functionality and options. Note that not all functions in ethtool apply to all Ethernet cards.
Multiboot systems are those systems with multiple versions of Windows installed, either under Windows itself or through third party tools such as Linux LILO or V Communications System Commander.
This includes non-standard keyboards and mice.
RAM, Virtual Memory, Pagefile and all that stuff www.support.microsoft.com/default.aspx?scid=kb;en-us;555223&SD=tech
How To Move the Paging File in Windows XP www.support.microsoft.com/default.aspx?scid=kb;en-us;307886&sd=tech
This error message is displayed:
In the event of a clone and system reconfiguration together, error messages are displayed during the system reconfiguration phase:
System Reconfiguration Failed: Unable to locate system hive.
This is error is specific to the filename of the service pack only.
The error does not occur with Service Pack 5 or Service Pack 6.
Note: This does not change the encryption level of the Service Pack, only the name the P2V Assistant uses to apply it.
If the error is due to a machine specific system partition, perform the following:
To delete a partition using the P2V Assistant Boot CD:
Then make the changes to the boot.ini file on the cloned disk:
The cloned NT 4 disk should no longer give the NTDETECT failure error and can be booted in its own virtual machine.
VMware has tested this software on a wide array of systems with a variety of hardware configurations, but as there are combinations we have not yet encountered in our labs, please contact VMware Support if your storage and network devices are not recognized by the P2V Boot CD.
VMware is interested in continuing to add support for all our customers' configurations; based on customer feedback, VMware will attempt to support your hardware configurations in a future release.
For the most up-to-date list of hardware on which VMware has tested the P2V Boot CD, please see:
The devices listed in this section were recognized by the P2V 2.0 boot CD but are currently not supported by P2V 2.1. If you want to use P2V to create an image of these machines containing these devices, you must use the most recent P2V 2.0 boot CD.
Devices Not Supported by Linux 2.6 megaraid_mbox Driver
The following MegaRAID devices no longer have support from Dell and LSI Logic in the Linux 2.6 megaraid_mbox driver. See the file /etc/bootcdlog.txt to see if your MegaRAID device ID is listed in the table below:
Vendor Device ------ ------ 0x101e 0x9010 0x101e 0x9060 0x8086 0x1960
These devices are known by some of the following model names:
MegaRAID 428 Ultra RAID
Emulex Fibre Channel Devices
All Emulex Fibre Channel devices are currently unsupported in the P2V Boot CD release 2.1.
The Emulex LightPulse Fibre Channel driver (lpfc) was not introduced to the stable kernel until the recent 2.6.12 revision, and the P2V Boot CD is based on 2.6.11. We hope to restore support for these devices in a subsequent release.
Until that time, we recommend that customers with Emulex Fibre Channel devices continue to use the P2V 2.0.3 release.
Alternatively, you can move your data to your virtual machine by connecting your target virtual machine server directly to your Fibre Channel network. Refer to the KB article, KB 1885, for additional information.
The Application and the Boot CD
Please ensure that you have the P2V Assistant application downloaded and installed on a computer separate from the source machine which you plan to boot from the P2V Boot CD.
The P2V Assistant application (a Windows .exe file) and the P2V Boot CD (a bootable .iso CD-ROM image) are separate downloads, so please ensure you have both downloaded before starting the P2V process.
Please note that there are known incompatibilities when the P2V Assistant application is installed on the same computer as certain other VMware applications. The list of VMware applications that conflict with the P2V Assistant includes:
We recommend that you install the P2V Assistant application on a clean helper machine (either a virtual machine or a physical machine) as documented in the P2V Assistant User's Manual, available online at:
Upgrading from P2V Assistant Version 1.0 to Version 2.1.x
There is no upgrade path from P2V Assistant 1.0 to version 2.1.x. Both versions can be installed on your system simultaneously. P2V Assistant 2.1.x is installed through the P2V Assistant setup.exe utility. You do not need to uninstall P2V Assistant 1.0. You do not upgrade P2V Assistant from version 1.0 to version 2.0.
NOTE: The licensing information in the registry is shared between
the 1.x and 2.0 versions. This includes your system reconfiguration licenses.