Bug 695275

Description of problem:

Chpater 23
http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization/convert-windows-guest.html
23.4.2. Configuration changes for Windows virtualized guests
Windows virtualized guest images are converted as follows:

   1.virt-v2v installs virtio block drivers.
   2.virt-v2v installs the CDUpgrader utility.
   3.virt-v2v makes registry changes to include the virtio block drivers in the CriticalDeviceDatabase section of the registry, and ensure the CDUpgrader service is started at the next boot.

Now,the steps should be updated like this:

   1.virt-v2v installs virtio block drivers.
   2.virt-v2v installs the CDUpgrader utility.
   3.virt-v2v copies virtio block and network drivers to %SystemRoot%\Drivers\VirtIO. The virtio-win package does not include network drivers for Windows 7 and Windows XP. For those operating systems, the rtl8139 network drivers are used. rtl8139 support must be already available in the guest.
   4.virt-v2v adds %SystemRoot%\Drivers\VirtIO to DevicePath, meaning this directory is automatically searched for drivers when a new device is detected.
   5.virt-v2v makes registry changes to include the virtio block drivers in the CriticalDeviceDatabase section of the registry, and ensure the CDUpgrader service is started at the next boot.

As the windows conversion can copy drivers from virtio-win to guest directly,so attach Guest Tools CD is not required,it is recommend.Document should point out this.Refer to bug https://bugzilla.redhat.com/show_bug.cgi?id=694773

Additional info:
Set Priority/Severity to high/high and raise the blocker flag, as it's better
to fix this doc bug in rhel-6.1.0.