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 1094855 - it took too long time to boot when starting guest windows 2003 with 512G memory
Summary: it took too long time to boot when starting guest windows 2003 with 512G memory
Keywords:
Status: CLOSED DUPLICATE of bug 996259
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Marcelo Tosatti
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On: 740221
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-06 15:37 UTC by Ademar Reis
Modified: 2014-05-24 20:40 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 740221
Environment:
Last Closed: 2014-05-24 20:38:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 1 Ronen Hod 2014-05-07 11:26:13 UTC
Some comments:
1. Win2003 by itself is not interesting. There are other O/Ss mentioned in this BZ.
2. I would try it with "swapoff -a" to make sure that is it not a matter of swapping (on the host).
3. It might also be related to proper NUMA mapping of the guest to the physical memory.

Comment 6 Marcelo Tosatti 2014-05-24 20:38:17 UTC
1) No NUMA binding:
first boot: 9 minutes

2) guest NUMA matching host NUMA, with proper mbind:
first boot: 3min 30secs
system reboot: 2 minutes

3) 2)+VCPU PINNING:
first boot: 2m40s
system reboot:  1m20s

Since its likely that such huge guests should have NUMA information 
exposed to guests, and with static NUMA binding, marking this bug 
as duplicate of 996259.

Test 2 was performed with multi-node NUMA binding feature.

*** This bug has been marked as a duplicate of bug 996259 ***


Note You need to log in before you can comment on or make changes to this bug.