Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1545849

Summary: no floppy in RunOnce flow
Product: [oVirt] ovirt-engine Reporter: Michal Skrivanek <michal.skrivanek>
Component: BLL.VirtAssignee: Arik <ahadas>
Status: CLOSED CURRENTRELEASE QA Contact: meital avital <mavital>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.1CC: ahadas, bugs, rik.theys
Target Milestone: ovirt-4.2.2Keywords: Regression
Target Release: ---Flags: rule-engine: ovirt-4.2+
rule-engine: blocker+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-29 11:00:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine log during bootup of VM with floppy attached
none
vdsm logs on the host none

Description Michal Skrivanek 2018-02-15 17:17:03 UTC 
from http://lists.ovirt.org/pipermail/users/2018-February/086699.html

----

I am trying to install Windows 10 on Ovirt 4.2

I pushed the virtio-win iso and vfd files to my ISO domain.   I created the VM and loaded the CD rom with the windows install ISO and in the "run once" settings I chose the virtio-win selection as a floppy.  However when entering windows setup, there is no drive to install to, and no floppy shows up in the usual place to install the drivers. 

the installation did succeed when selecting "IDE" as the target disk instead of the virtio or virtio-SCSI options.

Is there any way to install the drivers after the fact and then change the disk mode from IDE to virtio?

Is the method on this page https://www.ovirt.org/documentation/how-to/virtual-machines/create-a-windows-7-virtual-machine/ 
still relevant?  Looks like they suggest swapping the CD disk once the windows setup has begun.
Comment 1 Rik Theys 2018-02-19 09:08:15 UTC 
Hi,

We are experiencing the same bug. When a floppy is added to the 'run-once' of a VM, it is not attached to the VM.

I will add some logs of an attempt to run-once boot a new Server 2016 VM with the DVD attached and the floppy with the virtio drivers.

Regards,

Rik
Comment 2 Rik Theys 2018-02-19 09:10:26 UTC 
Created attachment 1397759 [details]
engine log during bootup of VM with floppy attached

The VM being started is 'test-voor-marc' with the server 2016 DVD attached and a virtio floppy. The floppy does not show up inside the VM. It is also not visible in the generated libvirt XML file for the VM.
Comment 3 Rik Theys 2018-02-19 09:12:31 UTC 
Created attachment 1397761 [details]
vdsm logs on the host

There are the vdsm and supervdsm logs on the host during bootup of the VM.
Comment 4 Red Hat Bugzilla Rules Engine 2018-02-21 11:41:12 UTC 
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
Comment 5 meital avital 2018-03-06 14:20:50 UTC 
Verified on version: 4.2.2.2-0.1.el7

Steps:
1) run-once a VM1 with floppy 
2) checked : 
2.1) virsh -r list
2.2) virsh -r dumpxml <VM1 num>

 <disk type='file' device='floppy'>                                                                                                                                                                               
      <driver name='qemu' type='raw'/>                                                                                                                                                                               
      <source file='/rhev/data-center/mnt/mantis-nfs-lif1.lab.eng.tlv2.redhat.com:_iso__domain/d31037e5-0d45-4306-975b-73eea845ae86/images/11111111-1111-1111-1111-111111111111/1.vfd' startupPolicy='optional'/>    
      <backingStore/>                                                                                                                                                                                                
      <target dev='fda' bus='fdc'/>                                                                                                                                                                                  
      <readonly/>                                                                                                                                                                                                    
      <alias name='fdc0-0-0'/>                                                                                                                                                                                       
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>                                                                                                                                             
    </disk>
Comment 6 Sandro Bonazzola 2018-03-29 11:00:34 UTC 
This bugzilla is included in oVirt 4.2.2 release, published on March 28th 2018.

Since the problem described in this bug report should be
resolved in oVirt 4.2.2 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.