RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 614377 - Windows 7 requires re-activation when migrated from RHEL5 to RHEL6
Summary: Windows 7 requires re-activation when migrated from RHEL5 to RHEL6
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-14 10:20 UTC by Jes Sorensen
Modified: 2013-01-09 22:52 UTC (History)
8 users (show)

Fixed In Version: qemu-kvm-0.12.1.2-2.97.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 615057 (view as bug list)
Environment:
Last Closed: 2010-11-10 21:26:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jes Sorensen 2010-07-14 10:20:48 UTC 
Description of problem:
Windows 7 requires re-activation when migrated from RHEL5 to RHEL6
due to change in SMBIOS data. 

Version-Release number of selected component (if applicable):


How reproducible:
Every time

Steps to Reproduce:
1. Install Windows 7 under RHEL5.5
2. Boot image under RHEL6 with -M rhel5.5.0 (or without -M)
3. Windows 7 then requires re-activation
  
Actual results:


Expected results:


Additional info:
Comment 2 Jes Sorensen 2010-07-14 10:48:00 UTC 
Looks like this is fixable directly in qemu-kvm, without having to
make modifications to seabios, so changing component.
Comment 6 Jes Sorensen 2010-07-14 20:48:53 UTC 
According to the discussion I had today with danpb, libvirt will set
-M per default, so yes.

Dan, can you please confirm?

Thanks,
Jes
Comment 7 Daniel Berrangé 2010-07-15 09:36:47 UTC 
The -M argument corresponds to the 'machine' attribute in libvirt XML

 <domain type='kvm'>
  <name>foo</name>
  ....
  <os>
    <type arch='i686' machine='pc-0.11'>hvm</type>
  </os>
  ...
 </domain>

If omitted, libvirt will pick a default machine type at time the guest is initially defined. On RHEL6 this will be the QEMU default machine type. On RHEL5 this is hardcoded as 'rhel-5.4.0'
Comment 9 Jes Sorensen 2010-07-23 07:50:14 UTC 
Tested .97 here with a pre-installed win7 x64 image from RHEL6 and the image
stays activated as expected. Looks good to me.
Comment 10 Mike Cao 2010-07-23 11:04:53 UTC 
Verified both for win7 32bit and win7 64 bit in qemu-kvm-0.12.1.2-2.97.el6.x86_64 ,Reproduced in qemu-kvm-0.12.1.2-2.96.el6.x86_64

Repeat the steps in comment #0,(note -M is a must in RHEL6 host)

Actual Results:

Windows 7 does NOT require re-activation.

The issue has already been fixed.
Comment 12 Mike Cao 2010-07-29 01:26:24 UTC 
According to the comment #9 and comment #10, change issue's status to Verified.
Comment 13 releng-rhel@redhat.com 2010-11-10 21:26:33 UTC 
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Note You need to log in before you can comment on or make changes to this bug.