Bug 975634

Summary: [Docs] [Admin] virtio-scsi installer for 2008/2012/2003
Product: Red Hat Enterprise Virtualization Manager Reporter: Tim Hildred <thildred>
Component: DocumentationAssignee: Tim Hildred <thildred>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: acathrow, alyoung, gklein, lveyde, thildred, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: integration
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 967607 Environment:
Last Closed: 2014-04-07 03:09:34 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:
Bug Depends On: 967607    
Bug Blocks:    

Comment 1 Tim Hildred 2013-07-15 04:30:25 UTC
Hello Lev,

I'm trying to make sure the documentation captures this feature. 

Could you please help me understand:

1) How does the user experience this feature? Is this a new driver installed of guest tools iso after install? Floppy during install? Other way?

2) How to add an entry for virtio-scsi in "Table 15.3. Red Hat Enterprise Virtualization Guest Drivers". Does this driver provide similar functionality for virtio-block?

3) In what circumstances would a user choose this device driver over other ones?

Thank you for your help Lev.

Comment 2 Lev Veyde 2013-07-15 08:45:18 UTC
(In reply to Tim Hildred from comment #1)
> Hello Lev,
> 
> I'm trying to make sure the documentation captures this feature. 
> 
> Could you please help me understand:
> 
> 1) How does the user experience this feature? Is this a new driver installed
> of guest tools iso after install? Floppy during install? Other way?
> 
> 2) How to add an entry for virtio-scsi in "Table 15.3. Red Hat Enterprise
> Virtualization Guest Drivers". Does this driver provide similar
> functionality for virtio-block?
> 
> 3) In what circumstances would a user choose this device driver over other
> ones?
> 
> Thank you for your help Lev.

Hi Tim,

1) Since it's a storage driver it included on both the floppy image (otherwise the user won't have an option to originally install the OS on the Virtio-SCSI device) and in the Windows Guest Tools (allowing him to add additional Virtio-SCSI devices).

2) I'm not sure to what document/table you are referring to. Can you please provide me with a link?

3) A lot of useful information about the new Virtio-SCSI driver is available at http://www.ovirt.org/Features/Virtio-SCSI .

Generally the main advantage is for the customers that need to add hundreds of block devices (disks) to the OS, as with Virtio-Block they are limited to about 30, but there are more advantages that may cause some clients to prefer using Virtio-SCSI over Virtio-Block (i.e. if they plan to export the VMs later on to another (other vendor) Virtualization env.) as the device naming is more standard) etc.

Thanks in advance,
Lev Veyde.

Comment 5 Tim Hildred 2013-07-25 07:38:52 UTC
Related to:
https://bugzilla.redhat.com/show_bug.cgi?id=921114

Comment 7 Tim Hildred 2013-10-04 09:10:48 UTC
The way I've resolved this bug is:

Updated: Red Hat Enterprise Virtualization Guest Drivers and Guest Agents
"Paravirtualized iSCSI HDD driver offers similar functionality to the virtio-block device, with some additional enhancements. In particular, this driver supports adding hundreds of devices, and names devices using the standard SCSI device naming scheme."

And added: Installing Windows on VirtIO-optimized Hardware