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 828175 - Docs QE Review: Chapter 6. Virtualization
Summary: Docs QE Review: Chapter 6. Virtualization
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Technical_Notes
Version: 6.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Martin Prpič
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: 854093
TreeView+ depends on / blocked
 
Reported: 2012-06-04 12:16 UTC by Miya Chen
Modified: 2015-09-28 02:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 854093 (view as bug list)
Environment:
Last Closed: 2013-01-22 14:13:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Miya Chen 2012-06-04 12:16:00 UTC 
Description of problem:
1. The maximum supported memory in a KVM guest increased from 512 GB to 4 TB. 

--->From the following bug, it should be 2TB
Bug 769041 - Increase Guest RAM limit to 2TB

2. KVM in Red Hat Enterprise Linux 6.3 improved the access to qcow2 disk images (qcow2  is the default format) by making it more asynchronous, thus avoiding vCPU stalls and enhancing the overall performance during disk I/O. 

--->qcow2 is not the default format, this sentence should be removed.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 2 Martin Prpič 2012-06-04 12:31:23 UTC 
(In reply to comment #0)

I'm guessing this is filed against the Release Notes?

> Description of problem:
> 1. The maximum supported memory in a KVM guest increased from 512 GB to 4
> TB. 

Snip from the Release Notes:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/6.3_Release_Notes/index.html

"The maximum supported memory in a KVM guest increased from 512 GB to 2 TB."

No mention of 4 TB.

> 
> --->From the following bug, it should be 2TB
> Bug 769041 - Increase Guest RAM limit to 2TB
> 
> 2. KVM in Red Hat Enterprise Linux 6.3 improved the access to qcow2 disk
> images (qcow2  is the default format) by making it more asynchronous, thus
> avoiding vCPU stalls and enhancing the overall performance during disk I/O. 
> 
> --->qcow2 is not the default format, this sentence should be removed.

Do you have any info on this? The Technical Notes field in Bug 783950 has been edited by multiple engineers and not one of them removed that line.

Thanks,
Martin
Comment 3 Miya Chen 2012-06-05 05:07:06 UTC 
> Snip from the Release Notes:
> 
> http://documentation-stage.bne.redhat.com/docs/en-US/
> Red_Hat_Enterprise_Linux/6/html-single/6.3_Release_Notes/index.html
> 
> "The maximum supported memory in a KVM guest increased from 512 GB to 2 TB."
> 
> No mention of 4 TB.

Sorry, Martin, I think i am reviewing a wrong link:
http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/6.3_Release_Notes/virtualization.html#kvm

Please ignore this bug if the above docs needs no change.

> > 
> > 2. KVM in Red Hat Enterprise Linux 6.3 improved the access to qcow2 disk
> > images (qcow2  is the default format) by making it more asynchronous, thus
> > avoiding vCPU stalls and enhancing the overall performance during disk I/O. 
> > 
> > --->qcow2 is not the default format, this sentence should be removed.
> 
> Do you have any info on this? The Technical Notes field in Bug 783950 has
> been edited by multiple engineers and not one of them removed that line.
> 

Let's involve the bug assignee Kevin to help confirm this.

Hi Kevin, can you please help confirm why there is "qcow2  is the default format" in the technical note? AFAIK, qcow2 is not the default, thanks.
Comment 4 Kevin Wolf 2012-06-05 08:19:58 UTC 
I guess it depends. If you use qemu-kvm directly, then raw is generally the default format (expect for things like live snapshots where the features of qcow2 are a requirement). However, I seem to remember that at least at some point qcow2 was the default format in libvirt/virt-manager (not sure which one is responsible) indeed, and I'm not aware of a change. Daniel should know the details.

Or you can just drop the sentence and don't say anything about default formats, that's safe in any case.
Note You need to log in before you can comment on or make changes to this bug.