Bug 702269

Summary: RFE: set up Win guest to use virtio devices if virtio-win package is installed
Product: Red Hat Enterprise Linux 6 Reporter: David Jaša <djasa>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 6.2CC: bsarathy, dallan, dyuan, jwu, mzhan, rwu
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-09 16:45:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 756082    

Description David Jaša 2011-05-05 08:48:06 UTC
Description of problem:
If one installs package virtio-win on hypervisor, he/she probably wants to use virtio devices in Windows guests and attach floppy with drivers during installation time.

Version-Release number of selected component (if applicable):
virt-manager-0.8.6-4.el6.noarch
virtio-win-1.1.16-1.el6.noarch

How reproducible:
always

Steps to Reproduce:
1. install virtio-win package
2. create a new machine with OS type set to any flavour of Windows
3. run installation
  
Actual results:
network device is set to Realtek 8139 and disk is set to IDE disk

Expected results:
* both network and disk devices should be set to Virtio type
* floppy with drivers is attached (readonly) during installation

Additional info:
path to floppy is: /usr/share/virtio-win/virtio-win.vfd
When OS type is set to Linux/RHEL6, devices are set to Virtio type

Comment 4 Cole Robinson 2011-06-10 22:29:10 UTC
Going to try and make this work for 6.2

Comment 5 Cole Robinson 2011-07-23 00:47:02 UTC
Okay, there are two pieces here I think.

1) If the user is installing a windows VM, and the virtio-win package is not installed, we ask the user if they want to install it (with a checkbox for don't ask me again). then we call out to packagekit and try to fetch it. this requires virtio-win being in the typical rhel repos, is that true? can't say I've ever actually used it. we'll have to skip this step for remote vm installs

2) if the user is installing a windows VM, and virt-manager sees /usr/share/virtio-win/virtio-win.vfd, setup the VM to install with virtio. we can probably make this work in the remote case. not sure if svirt or libvirt permissioning is gonna make things funky here though.

getting part 2 should be doable for 6.2, we'll see about part 1. any one have any more info about virtio-win packaging?

Comment 6 Perry Myers 2011-07-25 13:34:15 UTC
(In reply to comment #5)
> Okay, there are two pieces here I think.
> 
> 1) If the user is installing a windows VM, and the virtio-win package is not
> installed, we ask the user if they want to install it (with a checkbox for
> don't ask me again). then we call out to packagekit and try to fetch it. this
> requires virtio-win being in the typical rhel repos, is that true? can't say
> I've ever actually used it. we'll have to skip this step for remote vm installs

virtio-win is in the RHEL supplementary repos.  I'm not sure if these are configured/activated by default.  In any case, just do a simple yum install 'virtio-win'... If the repo is configured it'll install, if not, it's up to the user to properly configure yum :)

Comment 7 Cole Robinson 2011-09-27 15:34:19 UTC
I didn't get to this yet, so unlikely for 6.2. Deferring to 6.3

Comment 11 RHEL Program Management 2011-12-09 16:45:19 UTC
Product Management has reviewed and declined this request.  You may appeal this
decision by reopening this request.