Red Hat Bugzilla – Bug 596070
OS is not set accurately when exporting to RHEV
Last modified: 2010-11-09 08:22:01 EST
Description of problem:
When exporting to RHEV, in the output OVF /ovf:Envelop/Content/Section[@xsi:type='ovf:OperatingSystemSection_Type']/Description is always set to 'Unassigned'. This can apparently cause issues for Windows guests: clock will not be handled correctly and the RHEV agent CD will not be correctly presented to the guest.
Version-Release number of selected component (if applicable):
Fix posted: https://www.redhat.com/archives/libguestfs/2010-June/msg00064.html
The most effective end-to-end test for this is to export a guest to RHEV. After import to RHEV, select the guest under the 'Virtual Machines' tab and look at its meta information in the 'General' tab underneath the guest list. The 'Operating System' field should be correct.
Fixed in 0.6.0-4.el5
Created attachment 422779 [details]
log during conversion from LIBGUESTFS_TRACE=1
Unfortunately there's a bug in the error message here which is concealing the interesting information. At some point could you please edit line 862 of /usr/lib/perl5/vendor_perl/5.8.8/Sys/VirtV2V/Target/RHEV.pm, changing '_user_message' to 'user_message', then rerun this test. It should give you a warning message:
Unknown Windows version: X.Y
Can you please post that message to this bug.
This was caused by a simple typo. The fix is upstream.
(In reply to comment #7)
> This was caused by a simple typo. The fix is upstream.
Which version of virt-v2v supports to convert Windows?
There's no RHEL 5 build with this fix in it. The fix is in RHEL 6, though.
Created attachment 432308 [details]
Verified on virt-v2v-0.6.1-1.el5.
Now the 'Operating System' field is correcto for all guests, including RHEL and Windows after exporting to RHEV.
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.