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.
This reminds me strongly of a kernel bug we had in RHEL-6 Beta where Transparent Hugetables were corrupting the guest memory in very rare cases (which got triggered by rpm and bdb).
Are you running the latest 6.2 updates on the host and guest systems?
Thanks & regards, Phil
Comment 5Frantisek Reznicek
2012-02-28 16:28:45 UTC
I'm going to retest to see if it is still happening.
At the time of report guests were (getting) updated.
Virtualization host is not RHEL (F8 with custom virtualization:)
kvm-65-15.fc8.x86_64
libvirt-0.6.1-1.fc8.x86_64
libvirt-devel-0.6.1-1.fc8.x86_64
libvirt-python-0.6.1-1.fc8.x86_64
python-virtinst-0.400.3-3.fc9.noarch
qemu-0.9.1-6.fc8.x86_64
qemu-img-0.9.1-6.fc8.x86_64
virt-manager-0.7.0-8.fc8.x86_64
virt-manager-debuginfo-0.7.0-8.fc8.x86_64
virt-viewer-0.0.3-1.fc8.x86_64
Comment 6Frantisek Reznicek
2012-02-29 12:14:48 UTC
I reproduced the issue again on updated rhel6.2 guest (x86_64).
I'm not seeing this behavior with RHEL's virtualization (kvm-*83-239.el5 libvirt-*0.8.2-22.el5) I'm going to confirm by building them on f8.
Comment 7Frantisek Reznicek
2012-03-08 12:36:39 UTC
The issue is indeed caused by virtualization host kvm issues.
When switched to kvm-74 issue gone away which correlates with fact that this behavior was never detected on rhel6 guests virtualized on RHEL5.x virt. hosts.
Issue has no content.
-> CLOSED / NOT-A-BUG