Bug 487278

Summary: Corrections in virtuaulization document.
Product: Red Hat Enterprise Linux 5 Reporter: Sadique Puthen <sputhenp>
Component: doc-Virtualization_GuideAssignee: Christopher Curran <ccurran>
Status: CLOSED CURRENTRELEASE QA Contact: Joshua Wulf <jwulf>
Severity: high Docs Contact:
Priority: high    
Version: 5.3CC: lcarlon
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-10-09 07:42:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sadique Puthen 2009-02-25 09:52:38 UTC
Description of problem:

The page http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Virtualization_Guide/chap-Virtualization-Virtualization_limitations.html

<snip>

Red Hat Virtualization limitations
Red Hat Enterprise Linux Virtualization has limits on the number of virtual devices available due to the virtualization software. Red Hat Enterprise Linux 5.2 limitations:

    *
      A maximum of four file-based virtual block devices. 

<snip>

This limit is only applicable for Fully Virtualized guests since it uses IDE emulation and not for para-virtualized guests.

For paravirtualized guests the limit was 16 in 5.2 which has been raised in 5.3. So the above statement should be mentioned to be specific to Fully virtualized guest.

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


How reproducible:


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


Expected results:


Additional info:

Comment 2 Christopher Curran 2009-09-23 08:02:16 UTC
Fixed in build 60. This limit is for other types as well. The expanded limitations section should be live in a few days.