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.
Bug 607137 - window2003 and window2008 get incorrect mem
Summary: window2003 and window2008 get incorrect mem
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: qemu-kvm
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 580953
TreeView+ depends on / blocked
 
Reported: 2010-06-23 11:00 UTC by Suqin Huang
Modified: 2010-11-22 09:11 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-22 09:11:31 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Suqin Huang 2010-06-23 11:00:42 UTC 
Description of problem:
boot win2003 and win2008 with 2048M mem, guest only get 2047M, if boot with 4096M, will get 4095M

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.78.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1. boot guest

qemu-kvm -name 'vm1' -monitor tcp:0:6001,server,nowait -drive file=/win2003-64.qcow2,if=ide,cache=none,werror=stop,boot=on \
-net nic,vlan=0,model=rtl8139,macaddr=02:7E:61:38:f9:40 \
-net tap,vlan=0,script=/qemu-ifup-switch,downscript=no \
-m 4096 -smp 2 -soundhw ac97 -redir tcp:5000::22 -vnc :0 -usbdevice tablet -rtc-td-hack -cpu qemu64,+sse2 -no-kvm-pit-reinjection 



2. get meminfo
 systeminfo | find "Total Physical Memory"

3.
  
Actual results:
Memory size mismatch:
06:04:20 ERROR|     Assigned to VM: 4096
06:04:20 ERROR|     Reported by OS: 4095


Expected results:


Additional info:
xp, 08r2, win7 can get correct mem.
Comment 2 RHEL Program Management 2010-06-23 11:32:56 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 3 RHEL Program Management 2010-07-15 14:17:32 UTC 
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
Comment 5 Amit Shah 2010-11-10 11:30:37 UTC 
This looks like an issue with the guest OS.  Where do the ERROR lines you quoted come from?  Does this behaviour result in any loss of functionality or other bug in the guest operation?
Comment 6 Suqin Huang 2010-11-22 07:52:25 UTC 
run it with autotest script, get it from the test result.
the same result when issue: systeminfo | find "Total Physical Memory" cmd in guest.

doesn't result in loss  of functionality or other bug in the guest operation.
Comment 7 Amit Shah 2010-11-22 09:11:31 UTC 
In that case I'm fairly certain it's a bug in the guest and we can close this bug.
Note You need to log in before you can comment on or make changes to this bug.