Bug 961612
Summary: | there is no -redhat-disable-KSM introduction in man page | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Sibiao Luo <sluo> |
Component: | qemu-kvm | Assignee: | Andrea Arcangeli <aarcange> |
Status: | CLOSED NOTABUG | QA Contact: | Yumei Huang <yuhuang> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 7.0 | CC: | aarcange, chayang, hhuang, jinzhao, juzhang, knoel, qzhang, virt-maint, xfu, yuhuang |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-12-06 13:21:30 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sibiao Luo
2013-05-10 05:24:48 UTC
In RHEL7 the --redhat-disable-KSM command line doesn't exist because it was obsoleted, it wasn't just the entry missing in the manpage. Instead there is a mem-merge command line given to the machine type that you should find in the documentation too: -machine mem=merge=on|off mem-merge=on|off Enables or disables memory merge support. This feature, when upported by the host, de- duplicates identical memory pages among VMs instances (enabled by default). So the manager software should start the VM with -machine mem-merge=off if the host is a RHEL7 and it wants to disable KSM. Unfortunately specifying the KSM on or off option as part of the machine type doesn't make sense because KSM on or off cannot affect live migration and is totally invisible to the guest and independent of the actual machine topology lawyout emulated hardware or anything related to the machine type. But this is the upstream API so we need to live with it and embed this to the machine type. I learnt about this mistake once it was already committed upstream so it's not worth fixing now. |