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: fail to boot and call trace when launch a rhel6.5 guest on rhel7 host with default virtual RAM size(Default is 128 MiB), if use 256 did not hit it. Maybe this is the gueset os limitation, but i think we could raise this default virtual RAM size value. Version-Release number of selected component (if applicable): host info: # uname -r && rpm -q qemu-kvm 3.10.0-121.el7.x86_64 qemu-kvm-1.5.3-60.el7.x86_64 guest info: 2.6.32-448.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.launch a rhel6.5 guest on rhel7 host with default virtual RAM size(Default is 128 MiB) # /usr/libexec/qemu-kvm -M pc -S -cpu SandyBridge -enable-kvm -smp 2,sockets=2,cores=1,threads=1 -no-kvm-pit-reinjection -usb -device usb-tablet,id=input0 -name sluo -uuid 990ea161-6b67-47b2-b803-19fb01d30d30 -rtc base=localtime,clock=host,driftfix=slew -device virtio-serial-pci,id=virtio-serial0,max_ports=16,vectors=0,bus=pci.0,addr=0x3 -drive file=/home/RHEL6.5-20131019.1_Server_x86_64.qcow2bk,if=none,id=drive-virtio-disk,format=qcow2,cache=none,aio=native,werror=stop,rerror=stop -device virtio-blk-pci,vectors=0,bus=pci.0,addr=0x4,scsi=off,drive=drive-virtio-disk,id=virtio-disk,bootindex=1 -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,id=virtio-net-pci0,mac=00:01:02:B6:40:21,bus=pci.0,addr=0x5 -device virtio-balloon-pci,id=ballooning,bus=pci.0,addr=0x6 -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0 -k en-us -boot menu=on -qmp tcp:0:4444,server,nowait -serial unix:/tmp/ttyS0,server,nowait -vnc :1 -spice disable-ticketing,port=5931 -vga qxl -monitor stdio 2. 3. Actual results: after step 1, guest fail to boot and call trace, I will attach the log later. ... Call Trace: [<ffffffff810d0ac1>] ? cpuset_print_task_mems_allowed+0x91/0xb0 [<ffffffff81123040>] ? dump_header+0x90/0x1b0 [<ffffffff812297bc>] ? security_real_capable_noaudit+0x3c/0x70 [<ffffffff811234c2>] ? oom_kill_process+0x82/0x2a0 [<ffffffff811233be>] ? select_bad_process+0x9e/0x120 [<ffffffff81123900>] ? out_of_memory+0x220/0x3c0 [<ffffffff8113021f>] ? __alloc_pages_nodemask+0x89f/0x8d0 [<ffffffff8116eb62>] ? kmem_getpages+0x62/0x170 [<ffffffff8116f77a>] ? fallback_alloc+0x1ba/0x270 [<ffffffff8116f1cf>] ? cache_grow+0x2cf/0x320 [<ffffffff8116f4f9>] ? ____cache_alloc_node+0x99/0x160 [<ffffffff8116fd67>] ? kmem_cache_alloc_trace+0x127/0x1b0 [<ffffffff8100bc2e>] ? invalidate_interrupt1+0xe/0x20 [<ffffffff812487a8>] ? cond_insertf+0x138/0x200 [<ffffffff8123eade>] ? avtab_read_item+0x15e/0x390 [<ffffffff81248670>] ? cond_insertf+0x0/0x200 [<ffffffff81248c31>] ? cond_read_av_list+0xb1/0xd0 [<ffffffff81248ee2>] ? cond_read_list+0x162/0x2a0 [<ffffffff81242ae6>] ? policydb_read+0x576/0x1080 [<ffffffff81172ba6>] ? kmem_cache_create+0x456/0x5a0 [<ffffffff8124684c>] ? security_load_policy+0x5c/0x410 [<ffffffff8117c007>] ? mem_cgroup_update_file_mapped+0x17/0x90 [<ffffffff81120127>] ? unlock_page+0x27/0x30 [<ffffffff8114abd9>] ? __do_fault+0x469/0x530 [<ffffffff8114ad97>] ? handle_pte_fault+0xf7/0xb00 [<ffffffff8116817a>] ? alloc_pages_current+0xaa/0x110 [<ffffffff8104f157>] ? pte_alloc_one+0x37/0x50 [<ffffffff8114b9ca>] ? handle_mm_fault+0x22a/0x300 [<ffffffff8104ac2c>] ? __do_page_fault+0x1ec/0x480 [<ffffffff8112d61e>] ? __get_free_pages+0xe/0x50 [<ffffffff81157bb9>] ? vmap_page_range_noflush+0x279/0x370 [<ffffffff81159750>] ? __vmalloc_area_node+0x100/0x190 [<ffffffff81531c6e>] ? do_page_fault+0x3e/0xa0 [<ffffffff8152f025>] ? page_fault+0x25/0x30 [<ffffffff8123a43b>] ? sel_write_load+0xdb/0x710 [<ffffffff8123530b>] ? selinux_file_permission+0xfb/0x150 [<ffffffff812281f6>] ? security_file_permission+0x16/0x20 [<ffffffff81189738>] ? vfs_write+0xb8/0x1a0 [<ffffffff8118a101>] ? sys_write+0x51/0x90 [<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b ... Expected results: It should no any harmful to our KVM if let it default virtual RAM size value. Additional info: qemu-kvm man help docs: ... -m megs Set virtual RAM size to megs megabytes. Default is 128 MiB. Optionally, a suffix of "M" or "G" can be used to signify a value in megabytes or gigabytes respectively.