Created attachment 556035 [details] vdsm log Description of problem: When user tries to use a floppy during Version-Release number of selected component (if applicable): libvirt-0.9.6-4.fc16.x86_64 qemu-kvm-0.15.1-3.fc16.x86_64 qemu-kvm-tools-0.15.1-3.fc16.x86_64 gpxe-roms-qemu-1.0.1-4.fc16.noarch qemu-img-0.15.1-3.fc16.x86_64 qemu-common-0.15.1-3.fc16.x86_64 qemu-system-x86-0.15.1-3.fc16.x86_64 ovirt-engine-config-3.0.0_0001-1.2.fc16.x86_64 ovirt-engine-log-collector-3.0.0_0001-1.2.fc16.x86_64 ovirt-engine-setup-3.0.0_0001-1.2.fc16.x86_64 ovirt-engine-iso-uploader-3.0.0_0001-1.2.fc16.x86_64 ovirt-engine-jboss-deps-3.0.0_0001-1.2.fc16.x86_64 ovirt-engine-notification-service-3.0.0_0001-1.2.fc16.x86_64 ovirt-engine-3.0.0_0001-1.2.fc16.x86_64 ovirt-engine-jbossas-1.2-2.fc16.x86_64 ovirt-engine-tools-common-3.0.0_0001-1.2.fc16.x86_64 ovirt-engine-restapi-3.0.0_0001-1.2.fc16.x86_64 ovirt-engine-backend-3.0.0_0001-1.2.fc16.x86_64 ovirt-engine-webadmin-portal-3.0.0_0001-1.2.fc16.x86_64 ovirt-engine-dbscripts-3.0.0_0001-1.2.fc16.x86_64 ovirt-engine-userportal-3.0.0_0001-1.2.fc16.x86_64 ovirt-engine-genericapi-3.0.0_0001-1.2.fc16.x86_64 How reproducible: 100 % from ovirt Steps to Reproduce: 1. In ovirt create an empty VM, add a disk to it 2. Start unattended installation (Run once + Floppy-unattended file + CD-ROM with windows) Actual results: Installation definitely isn't unattended, when trying to attach floppy to a VM with OS in it the floppy drive is not present in the vm Expected results: Floppy is parsed to VM and unattended installation/drivers load works Additional info: Attaching vdsm.log and log of the VM
Created attachment 556036 [details] Libvirtd.log Forgot also vdsm version. vdsm-4.9.3.1-0.fc16.x86_64
Created attachment 556037 [details] VM's log
Are you sure that the guest cannot see the floppy? Maybe the content of the floppy is bad, or the guest is buggy? qemu command line boasts -drive file=/rhev/data-center/81b64814-41a1-11e1-a3b8-fbb24d0ffbb1/f1621233-13f4-4c6b-99e3-86fbd4dbdad2/images/11111111-1111-1111-1111-111111111111/winXP-Pro-SP2-32-unattended.vfd,if=none,id=drive-fdc0-0-0,readonly=on,format=raw so I suspect this is not a Vdsm bug. What happens when you attach this floppy to a known-working Vm?
When I use this very same floppy in RHEV it works fine and the vm is installed with no attention needed.
Are you able to see the content of a floppy anywhere with oVirt? Can you see it when passed to libvirt directly (w/o vdsm)?
Jiri, can you spot anything wrong in the domxml or qemu cmdline?
I can't see the content in oVirt (neither in Win VM, nor in Windows VM) on the other hand I'm perfectly able to see it in RHEV. It is the same image on the same iso domain I share between RHEV and oVirt, so the difference is RHEV vs. oVirt.
WORKSFORME. I installed vdsm-4.9.3.1-0.fc16.x86_64, added vfd file to my iso domain and ran that vm with floppy using Run Once. The vm's xml contains the file as floppy device: <disk device="floppy" type="file"> <source file="/rhev/data-center/026a0bd0-5db0-4e34-8355-b91d9e7a5b8c/c37e94b2-b130-49b4-a7aa-b30e8a372878/images/11111111-1111-1111-1111-111111111111/win2k3.vfd"/> <target bus="fdc" dev="fda"/> </disk> In the guest (with RHEL os installed), I added the floppy module (modprobe floppy) and mounted the /dev/fd0 as vfat type, and I managed to access the floppy's files. The only small issue here is that the device was mapped as fd0 instead of fda.
Dan, I didn't spot anything wrong or suspicious anywhere in the XML or qemu command line. Rami, the "fda" from format dev attribute has very little in common with the device name you can see in a guest. So there is no issue there.
Closing as WORKSFORME - this behaviour is not reproducible on newest build of ovirt.