Hide Forgot
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
Going to try and make this work for 6.2
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?
(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 :)
I didn't get to this yet, so unlikely for 6.2. Deferring to 6.3
Product Management has reviewed and declined this request. You may appeal this decision by reopening this request.