Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 425020[details]
Screendump of BSOD
Description of problem:
Installing XP under RHEL55, activating it, rebooting the host into RHEL6 and trying to boot the XP guest results in a BSOD. It comes up, tries to install the genuine validation tool or something, then explodes in the BSOD.
Version-Release number of selected component (if applicable):
1.1.5
How reproducible:
Every time
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Installed under RHEL55 like this:
/usr/libexec/qemu-kvm -m 2G -smp 2 -drive file=/var/lib/libvirt/images/xp3.img,if=virtio,cache=off,boot=on -net nic,model=virtio,vlan=1,macaddr=02:00:40:3F:20:10 -net tap,vlan=1,script=/etc/kvm-ifup.sh -boot dc -uuid 17544ecc-d3a1-4d3c-a386-12daf50015f1 -usbdevice tablet -no-hpet -rtc-td-hack -no-kvm-pit-reinjection -monitor stdio -balloon none -startdate now -name xp-test -fda /home/jes/virtio-win-1.1.5-0.vfd -cdrom /home/isos/en_windows_xp_professional_with_service_pack_3_x86_cd_x14-80428.iso -vnc 127.0.0.1:0
Rebooted under RHEL6 like this:
/usr/libexec/qemu-kvm -m 2G -smp 2 -drive file=/var/lib/libvirt/images/xp3.img,if=virtio,cache=off,boot=on -net nic,model=virtio,vlan=1,macaddr=02:00:40:3F:20:10 -net tap,vlan=1,script=/etc/kvm-ifup.sh -boot c -uuid 17544ecc-d3a1-4d3c-a386-12daf50015f1 -rtc-td-hack -no-kvm-pit-reinjection -monitor stdio -balloon none -startdate now -name xp-test -cdrom /home/isos/en_windows_xp_professional_with_service_pack_3_x86_cd_x14-80428.iso -vnc 127.0.0.1:0
QEMU 0.12.1 monitor - type 'help' for more information
(qemu) virtio_ioport_write: unexpected address 0x13 value 0x1
Note the strange virtio_ioport_write message.
Comment 2RHEL Program Management
2010-06-18 07:14:56 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release. Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release. This request is not yet committed for
inclusion.
Comment 3Yvugenfi@redhat.com
2010-06-19 09:14:51 UTC
If possible please extract memory dump from the guest (boot it again in RHEL5.5).
Memory dumps should be in c:\windows\memory.dmp or c:\windows\minidumps
(better configure OS to generate kernel memory dumps before the crash).
I will try to see if I can extract the info.
I just tried rebooting under RHEL55 but no it claims that autochk doesn't exist, then reboots and tries again, then fails again ....
I will try and reinstall it and see if I can reproduce it and pull it out.
Jes
Created attachment 425020 [details] Screendump of BSOD Description of problem: Installing XP under RHEL55, activating it, rebooting the host into RHEL6 and trying to boot the XP guest results in a BSOD. It comes up, tries to install the genuine validation tool or something, then explodes in the BSOD. Version-Release number of selected component (if applicable): 1.1.5 How reproducible: Every time Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: Installed under RHEL55 like this: /usr/libexec/qemu-kvm -m 2G -smp 2 -drive file=/var/lib/libvirt/images/xp3.img,if=virtio,cache=off,boot=on -net nic,model=virtio,vlan=1,macaddr=02:00:40:3F:20:10 -net tap,vlan=1,script=/etc/kvm-ifup.sh -boot dc -uuid 17544ecc-d3a1-4d3c-a386-12daf50015f1 -usbdevice tablet -no-hpet -rtc-td-hack -no-kvm-pit-reinjection -monitor stdio -balloon none -startdate now -name xp-test -fda /home/jes/virtio-win-1.1.5-0.vfd -cdrom /home/isos/en_windows_xp_professional_with_service_pack_3_x86_cd_x14-80428.iso -vnc 127.0.0.1:0 Rebooted under RHEL6 like this: /usr/libexec/qemu-kvm -m 2G -smp 2 -drive file=/var/lib/libvirt/images/xp3.img,if=virtio,cache=off,boot=on -net nic,model=virtio,vlan=1,macaddr=02:00:40:3F:20:10 -net tap,vlan=1,script=/etc/kvm-ifup.sh -boot c -uuid 17544ecc-d3a1-4d3c-a386-12daf50015f1 -rtc-td-hack -no-kvm-pit-reinjection -monitor stdio -balloon none -startdate now -name xp-test -cdrom /home/isos/en_windows_xp_professional_with_service_pack_3_x86_cd_x14-80428.iso -vnc 127.0.0.1:0 QEMU 0.12.1 monitor - type 'help' for more information (qemu) virtio_ioport_write: unexpected address 0x13 value 0x1 Note the strange virtio_ioport_write message.