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.
Description of problem:
qemu/kvm deep sleep state (c3) seems to be causing guest virtio-blk
softlockups, as follows :
kernel: BUG: soft lockup - CPU#1 stuck for 16s! [swapper:0]
kernel:
kernel: Pid: 0, comm: swapper
kernel: EIP: 0060:[<c0403be1>] CPU: 1
kernel: EIP is at default_idle+0x31/0x59
kernel: EFLAGS: 00000246 Not tainted (2.6.18-194.el5 #1)
kernel: EAX: 00000000 EBX: 00000001 ECX: c0403bb0 EDX: f7d4a000
kernel: ESI: 000084f4 EDI: 00000000 EBP: 00000000 DS: 007b ES: 007b
kernel: CR0: 8005003b CR2: bfec2ee4 CR3: 01bb3000 CR4: 00000690
kernel: [<c0403ca8>] cpu_idle+0x9f/0xb9
kernel: =======================
This may be related to BZ 609286, except that BZ deals with s-states
(suspend). Either way, the upstream work mentioned in BZ 609286 is
probably relevant.
Workarounds: set processor.max_cstate=1 on the KVM host, or boot with
the tickless feature turned off (nohz=off).
Version-Release number of selected component (if applicable):
Host: RHEL6.0 GA with qemu-kvm-0.12.1.2-2.113.el6.x86_64
Guest: RHEL5.5 GA, kernel version: 2.6.18-194.EL5
How reproducible:
only sometimes - 10% only
Steps to Reproduce: (paste from support case)
- Host
1. Install RHEL6
2. Boot RHEL6
3. Start to Virtual Machine Manager, and add to guest.
4. Install RHEL5.5 as guest OS.
- Guest
1. Shutdown RHEL5.5
2. Display details of virtual hardware on KVM menu
3. Puch "Add Hardware" button
4. Select "Storage" as hardware type, and set new storage device about 10GB
* Change to "none" from "default" on cashmode
5. Display Graphical console
6. Reboot RHEL5.5
7. Mount the storage device set in 4. and optional directory
(ex) # mount /dev/hda1 /b
8. Make file with dd command as follows
(ex) # dd if=/dev/zero of=/b/f000/file bs=2048b count=8192
9. After read file made in 8. with dd command,
measure read time with time command as follows,
and repeat from 10 to 15 times this operation
(ex) # time -p sh -c 'dd if=/b/f000 of=/dev/null bs=2048b count=8192& wait'
Actual results:
Softlockup occurs on the guest when the reading file, guest hangs
Expected results:
No softlockup
Additional info:
So does guest hangs (as in totally dead, not responding any more...), or just softlockup message is displayed and guest continues running? Also host HW information is missing.
Soft lockupus are not bugs in virtual environment. Closing as NOTABUG since I do not get response from bug reporter. Please reopen If guest hangs completely.
Description of problem: qemu/kvm deep sleep state (c3) seems to be causing guest virtio-blk softlockups, as follows : kernel: BUG: soft lockup - CPU#1 stuck for 16s! [swapper:0] kernel: kernel: Pid: 0, comm: swapper kernel: EIP: 0060:[<c0403be1>] CPU: 1 kernel: EIP is at default_idle+0x31/0x59 kernel: EFLAGS: 00000246 Not tainted (2.6.18-194.el5 #1) kernel: EAX: 00000000 EBX: 00000001 ECX: c0403bb0 EDX: f7d4a000 kernel: ESI: 000084f4 EDI: 00000000 EBP: 00000000 DS: 007b ES: 007b kernel: CR0: 8005003b CR2: bfec2ee4 CR3: 01bb3000 CR4: 00000690 kernel: [<c0403ca8>] cpu_idle+0x9f/0xb9 kernel: ======================= This may be related to BZ 609286, except that BZ deals with s-states (suspend). Either way, the upstream work mentioned in BZ 609286 is probably relevant. Workarounds: set processor.max_cstate=1 on the KVM host, or boot with the tickless feature turned off (nohz=off). Version-Release number of selected component (if applicable): Host: RHEL6.0 GA with qemu-kvm-0.12.1.2-2.113.el6.x86_64 Guest: RHEL5.5 GA, kernel version: 2.6.18-194.EL5 How reproducible: only sometimes - 10% only Steps to Reproduce: (paste from support case) - Host 1. Install RHEL6 2. Boot RHEL6 3. Start to Virtual Machine Manager, and add to guest. 4. Install RHEL5.5 as guest OS. - Guest 1. Shutdown RHEL5.5 2. Display details of virtual hardware on KVM menu 3. Puch "Add Hardware" button 4. Select "Storage" as hardware type, and set new storage device about 10GB * Change to "none" from "default" on cashmode 5. Display Graphical console 6. Reboot RHEL5.5 7. Mount the storage device set in 4. and optional directory (ex) # mount /dev/hda1 /b 8. Make file with dd command as follows (ex) # dd if=/dev/zero of=/b/f000/file bs=2048b count=8192 9. After read file made in 8. with dd command, measure read time with time command as follows, and repeat from 10 to 15 times this operation (ex) # time -p sh -c 'dd if=/b/f000 of=/dev/null bs=2048b count=8192& wait' Actual results: Softlockup occurs on the guest when the reading file, guest hangs Expected results: No softlockup Additional info: