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:
The value of command line parameter ram_size or vram_size fail to be changed, which are in the normal range both of them.
Version-Release number of selected component (if applicable):
host info:
# uname -r && rpm -q qemu-kvm
2.6.32-221.el6.x86_64
qemu-kvm-0.12.1.2-2.213.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. boot the guest with the value of command line parameter ram_size and vram_size which are in the normal range both of them.
eg: # /usr/libexec/qemu-kvm -M rhel6.2.0 -enable-kvm -m 2048 -smp 2,sockets=1,cores=2,threads=1 -name rhel6.2-64 -uuid f1606ee0-2c5e-4dc5-9de1-455e5e451d1c -boot menu=on -drive file=/root/rhel6.2-64.qcow2,if=none,id=drive-ide-0-0,media=disk,format=qcow2,cache=none,werror=stop,rerror=stop -device ide-drive,drive=drive-ide-0-0,id=ide0-0-0 -netdev tap,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=22:1a:4a:42:1b:37 -usb -device usb-tablet,id=input1 -monitor stdio -balloon none -spice disable-ticketing,port=5912 -vga qxl -global qxl-vga.ram_size=43433355
2. check the value of ram_size or vram_size with info qtree in the qemu monitor.
Actual results:
...
dev: qxl-vga, id ""
dev-prop: ram_size = 67108864
...
Expected results:
the value of ram_size or vram_size can be changed successfully.
Additional info:
This is by design - the values are set to the smallest next power of two, so if you give a value between 2^n+1..2^n you get 2^n, in this case 2**25<43433355<=2**26 => 67108864
Alon