Description of problem:
after import the windows guest to rhevm, boot the vm guest first time without the rhev-tools iso file available, then shutdown the machine, and try the second time with the rhev-tools iso file available, you could find the rhev-tools is attached to the cdrom,
but won't install the driver anyway, try to install the driver, after reboot, we got BSOD,
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1,import the windows guest to rhev,
2,start the guest without the iso files available,
3,shutdown the guest,
3,upload the iso files to the iso domain, and make sure the iso domain is attach to the relate data domain,
4,boot the guest again,
5,already attach the guest, but won't install,
6,manually install the driver,
7,after reboot, got BSOD
can't install the driver automatically,
install the driver automatically, and won't get any BSOD
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
Verified with virt-v2v-0.7.1-4.el5.
The new v2v mechanism will try to install virtio driver via copying drivers into corresponding dir instead of CDUpgrader's help. So this issue has been resolved automatically after mechanism update.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.