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 605164 - RHEL-4.8 32 image could not boot up with latest kernel.
Summary: RHEL-4.8 32 image could not boot up with latest kernel.
Keywords:
Status: CLOSED DUPLICATE of bug 606643
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-17 10:44 UTC by YangFeng
Modified: 2015-04-20 00:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-23 10:41:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
kvmtarce log (7.78 MB, text/plain)
2010-06-17 10:49 UTC, YangFeng 		no flags Details
View All

Description YangFeng 2010-06-17 10:44:01 UTC 
Description of problem:
RHEL-4.8 32 image could not boot up after update kernel to latest.

Version-Release number of selected component (if applicable):
Host kernel:
2.6.32-33.el6.x86_64
qemu-kvm version:
qemu-kvm-0.12.1.2-2.73.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Start a RHEL-4.8 32 guest os.
'qemu-kvm -name 'vm1' -monitor tcp:0:6001,server,nowait -drive file=RHEL-4.8-32-2.qcow2,if=ide,cache=none,boot=on,aio=native -net nic,vlan=0,model=e1000,macaddr=02:8F:50:B4:3c:42 -net tap,vlan=0,ifname=e1000_0_6001,script=/etc/qemu-ifup-switch,downscript=no,vhost=on -m 2048 -smp 2 -soundhw ac97 -redir tcp:5000::22 -vnc :0 -usbdevice tablet -rtc-td-hack -cpu qemu64,+sse2 -no-kvm-pit-reinjection -serial unix:/tmp/serial-20100613-180943-9cCi,server,nowait
'
2. Update RHEL-4.8 kernel to latest.
'rpm -ivhf http://download.devel.redhat.com/brewroot/packages/kernel/2.6.9/89.28.EL/i686/kernel-smp-2.6.9-89.28.EL.i686.rpm'
3. Reboot RHEL-4.8 32 guest os.
  
Actual results:
RHEL-4.8 32 guest could not boot up successfully. It stop at probing PCI hardware.

Expected results:
RHEL-4.8 32 guest boot up successfully. 

Additional info:
Original kernel in RHEL-4.8 32 image(uname -a):
Linux virtlab-66-84-137.englab.nay.redhat.com 2.6.9-89.EL #1 Mon Apr 20 10:22:29 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux

Information got from serial port:
ENABLING IO-APIC IRQs

..TIMER: vector=0x31 pin1=2 pin2=-1

checking TSC synchronization across 2 CPUs: 

CPU#0 had -1393445 usecs TSC skew, fixed it up.

CPU#1 had 0 usecs TSC skew, fixed it up.

Brought up 2 CPUs

zapping low mappings.

checking if image is initramfs... it is

Freeing initrd memory: 1560k freed

NET: Registered protocol family 16

PCI: PCI BIOS revision 2.10 entry at 0xffe77, last bus=0

PCI: Using configuration type 1

mtrr: v2.0 (20020519)

mtrr: your CPUs had inconsistent variable MTRR settings

mtrr: your CPUs had inconsistent MTRRdefType settings

mtrr: probably your BIOS does not setup all CPUs.

mtrr: corrected configuration.

ACPI: Subsystem revision 20040816

ACPI: Interpreter enabled

ACPI: Using IOAPIC for interrupt routing

ACPI: PCI Root Bridge [PCI0] (00:00)

PCI: Probing PCI hardware (bus 00)
Comment 2 YangFeng 2010-06-17 10:49:22 UTC 
Created attachment 424757 [details]
kvmtarce log
Comment 3 RHEL Program Management 2010-06-17 10:53:14 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 4 YangFeng 2010-06-21 09:52:49 UTC 
Also meet this bug on kvm-83-164.el5_5.12.
Comment 5 Juan Quintela 2010-06-23 10:41:53 UTC 

*** This bug has been marked as a duplicate of bug 606643 ***
Note You need to log in before you can comment on or make changes to this bug.