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 804523 - Stable guest ABI fails on 6.3 host with -M 5.x.x
Summary: Stable guest ABI fails on 6.3 host with -M 5.x.x
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-19 07:22 UTC by Shaolong Hu
Modified: 2013-01-10 00:47 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 07:59:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Shaolong Hu 2012-03-19 07:22:32 UTC 
Description of problem:
------------------------
Run windows guest installed on 5.8 host with -M 5.x.x, windows needs re-activate.


Version-Release number of selected component (if applicable):
-------------------------------------------------------------
6.3 host: qemu-kvm-0.12.1.2-2.246.el6.x86_64
5.8 host: kvm-83-249.el5_8
guest: en_windows_7_ultimate_with_sp1_x64_dvd_618240.iso

How reproducible:
------------------
100%

Steps to Reproduce:
-------------------
1.5.8 host:
/usr/libexec/qemu-kvm -name vm1 -monitor unix:/tmp/monitor-humanmonitor,server,nowait -serial unix:/tmp/serial,server,nowait -drive file=win7-5.4.4,index=0,if=virtio,media=disk,cache=none,boot=on,format=qcow2 -net nic,vlan=0,model=virtio,macaddr=9a:7a:70:0b:81:2b -net tap,vlan=0,ifname=net0,script=/etc/qemu-ifup -m 4G -smp 4 -vnc :10 -rtc-td-hack -M rhel5.4.4 -boot dc -balloon virtio -no-kvm-pit-reinjection -usbdevice tablet -fda /usr/share/virtio-win/virtio-drivers-1.0.3-52454.vfd -cdrom en_windows_7_ultimate_with_sp1_x64_dvd_618240.iso -monitor stdio

2.6.3 host:
/usr/libexec/qemu-kvm -enable-kvm -M rhel5.4.4 -smp 4 -m 4G -name rhel6.3-64 -uuid 3f2ea5cd-3d29-48ff-aab2-23df1b6ae213 -drive file=win7-5.4.4,cache=none,if=none,rerror=stop,werror=stop,id=drive-virtio-disk0,format=qcow2 -device virtio-blk-pci,drive=drive-virtio-disk0,id=device-virtio-disk0 -netdev tap,script=/etc/qemu-ifup,id=netdev0,vhost=off -device virtio-net-pci,netdev=netdev0,id=device-net0 -boot order=cd -monitor stdio -usb -device usb-tablet,id=input0 -chardev socket,id=s1,path=/tmp/s1,server,nowait -device isa-serial,chardev=s1 -vnc :10 -monitor tcp::1234,server,nowait

  
Actual results:


Expected results:


Additional info:
Comment 2 Dor Laor 2012-03-21 07:59:37 UTC 
I have a doubt that someone is using rhel5 machine types on thel6 hosts. The
bios is different anyway and some of the devices.

Specifically, there is not virtio-serial device on rhel5 at all so it can't
expect to work. You can remove -M rhel5 from the rhel6 tests, at least until we get requests for that.

Another issue is the pci slots, you need to manually specify all of them to match the rhel5 slots. When you run w/ libvirt it does it automatically when -M rhel5 is added.
Note You need to log in before you can comment on or make changes to this bug.