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.
Comment 4Michael S. Tsirkin
2011-05-30 15:50:08 UTC
As far as I can make out, the host is out of memory here
so qemu kvm can't open a socket. It says guest but qemu-kvm
does not run on guest - I think it's a mistake and
the log triggers on host.
Can you confirm please?
Is the host really out of memory? Did you overcommit the host memory aggressively?
Looks like the host is receiving a (large) network packet and wants to allocate two contiguous pages of memory with the GFP_ATOMIC allocation flag, which is an allocation that cannot wait for memory to be defragmented.
Levente, does the warning message you get result in any problem for your KVM guests at all?
Judging from the backtrace, the likely result is just the loss of a network packet, which will no doubt be retransmitted and delivered later.
the truth is that i don''t know:-(
i've just found this message in the log just before we reboot the host since we've got problem with our pxe setup (but turn out that was completely different from this, and even from this server).
i just report this since imho it's not a 'normal' behavior...
Since the backtrace looks harmless (dropped packet) and you did not notice any malfunction, lets assume for now that nothing serious happened.
Having occasional packet loss is pretty much expected on modern computers, since networking is incredibly fast and memory cannot always be freed in time for the next packets.
Comment 10Andrea Arcangeli
2011-05-31 18:38:23 UTC