Created attachment 669529 [details] test F6 virtio driver problem Description of problem: fedora has a windows driver cd for KVM virtio,http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/virtio-win-0.1-49.iso build a floppy image virtio driver from the iso,prepare a windows 2003 guest setup. windows will load virtio driver correctly when i use kernel 3.5.xx .but if i use kernel 3.6.xx ,it's failed.windows cannot load virtio driver. windows will tell: "This disk cannot be read because it contains an unrecognized file system." kernel tested (have problems) kernel-3.6.10-2.fc17.x86_64 kernel-3.6.2-4.fc17x86_64 kernel-3.6.3-1.fc17.x86_64 kernel-3.6.10-4.fc18.x86_64 kernel tested (no problems) kernel-3.5.5-2.fc17.x86_64 kernel-3.3.4-5.fc17.x86_64 kernel-3.5.6-1.fc17.x86_64 driver cd tested virtio-win-0.1-49.iso (the lastest version when i post this message) virtio-win-0.1-30.iso it seems like something changed from kernel 3.5 to kernel 3.6. fedora 18 has same problems. Version-Release number of selected component (if applicable): problem under fedora 17 with kernel 3.6.xx fedora 18 with kernel 3.6.xx but fedora 17 with kernel 3.5.xx is fine,kernel 3.3.xx is fine also How reproducible: get virtio windows driver cd from http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/virtio-win-0.1-49.iso get some windows 2003 install cd image,for example ,we call it en_windows_server_2003_Enterprise.iso extract the attachment into some directory run script: ./build-f6.sh virtio-win-0.1-49.iso ,it will generate all windows setup floppy driver, w'll use virtio-WIN2003-x86.vfd or virtio-WIN2003-amd64.vfd then run script: ./f6test.sh virtio-WIN2003-x86.vfd en_windows_server_2003_Enterprise.iso , this script will report the vncport like "vnc port is :1" connect vnc port with vncviewer press F6 at windows setup when "Press F6 if you need to install a third party SCSI or RAID driver" Steps to Reproduce: 1. ./f6test.sh floppy iso 2. 3. Actual results: "This disk cannot be read because it contains an unrecognized file system." Expected results: Windows will find "Red Hat VirtIO"driver in floppy Additional info: if you update fedora 17 to latest updates and you want a 3.5.xx kernel,you can get it from http://koji.fedoraproject.org/koji/buildinfo?buildID=358712 .for example : you can get http://kojipkgs.fedoraproject.org//packages/kernel/3.5.6/1.fc17/x86_64/kernel-3.5.6-1.fc17.x86_64.rpm and http://kojipkgs.fedoraproject.org//packages/kernel/3.5.6/1.fc17/x86_64/kernel-modules-extra-3.5.6-1.fc17.x86_64.rpm and then rpm --force -ivh kernel*3.5.6*.rpm and then adjust grub boot default with grub2-set-default and then boot into 3.5.6-1 kernel and then run test again
*** Bug 890468 has been marked as a duplicate of this bug. ***
I have no idea what goes into producing the virtio-win stuff, but maybe it needs to be rebuilt against a 3.6 kernel. Assigning to Cole as he seems to own those files on alt.fedoraproject.org.
(In reply to comment #2) > I have no idea what goes into producing the virtio-win stuff, but maybe it > needs to be rebuilt against a 3.6 kernel. Assigning to Cole as he seems to > own those files on alt.fedoraproject.org. Pretty sure the virtio-win stuff is built on windows. I just pull the pre-built bits from an internal source and, stick them in an iso, and publish them. Vadim, Gal, any thoughts what might be going on here? (or someone else I should ping?)
(In reply to comment #3) > (In reply to comment #2) > > I have no idea what goes into producing the virtio-win stuff, but maybe it > > needs to be rebuilt against a 3.6 kernel. Assigning to Cole as he seems to > > own those files on alt.fedoraproject.org. > > Pretty sure the virtio-win stuff is built on windows. I just pull the > pre-built bits from an internal source and, stick them in an iso, and > publish them. > > Vadim, Gal, any thoughts what might be going on here? (or someone else I > should ping?) Hi Cole, I'm not familiar with build-f6.sh tool. Where it can be found? Any idea why we have two vfd files: virtio-WIN2003-x86.vfd and virtio-WIN2003-amd64.vfd? I would like to see them also. Best regards, Vadim.
wugong, can you provide more info about this? See comment #4
i have a attachment in bug report, https://bugzilla.redhat.com/attachment.cgi?id=669529 which contains 3 files build-f6.sh --- use this generate windows driver floppy image f6bug.xml --- the vm xml file f6test.sh --- replace some text in f6bug.xml and generate f6bug-real.xml and create the vm (In reply to comment #5) > wugong, can you provide more info about this? See comment #4
(In reply to comment #6) > i have a attachment in bug report, > https://bugzilla.redhat.com/attachment.cgi?id=669529 > which contains 3 files > build-f6.sh --- use this generate windows driver floppy image > f6bug.xml --- the vm xml file > f6test.sh --- replace some text in f6bug.xml and generate f6bug-real.xml > and create the vm > (In reply to comment #5) > > wugong, can you provide more info about this? See comment #4 Could you please upload vfd image? Vadim.
Created attachment 675643 [details] virtio f6 floppy for windows 2003
(In reply to comment #7) > (In reply to comment #6) > > i have a attachment in bug report, > > https://bugzilla.redhat.com/attachment.cgi?id=669529 > > which contains 3 files > > build-f6.sh --- use this generate windows driver floppy image > > f6bug.xml --- the vm xml file > > f6test.sh --- replace some text in f6bug.xml and generate f6bug-real.xml > > and create the vm > > (In reply to comment #5) > > > wugong, can you provide more info about this? See comment #4 > > Could you please upload vfd image? > Vadim. https://bugzilla.redhat.com/attachment.cgi?id=675643 Best regards, wugong
(In reply to comment #9) > (In reply to comment #7) > > (In reply to comment #6) > > > i have a attachment in bug report, > > > https://bugzilla.redhat.com/attachment.cgi?id=669529 > > > which contains 3 files > > > build-f6.sh --- use this generate windows driver floppy image > > > f6bug.xml --- the vm xml file > > > f6test.sh --- replace some text in f6bug.xml and generate f6bug-real.xml > > > and create the vm > > > (In reply to comment #5) > > > > wugong, can you provide more info about this? See comment #4 > > > > Could you please upload vfd image? > > Vadim. > > https://bugzilla.redhat.com/attachment.cgi?id=675643 > > Best regards, > wugong Thanks, Unfortunately it seems to be empty. Could you please check it? Best regards, Vadim.
Created attachment 676608 [details] virtio f6 floppy for windows 2003 updated
(In reply to comment #10) > (In reply to comment #9) > > (In reply to comment #7) > > > (In reply to comment #6) > > > > i have a attachment in bug report, > > > > https://bugzilla.redhat.com/attachment.cgi?id=669529 > > > > which contains 3 files > > > > build-f6.sh --- use this generate windows driver floppy image > > > > f6bug.xml --- the vm xml file > > > > f6test.sh --- replace some text in f6bug.xml and generate f6bug-real.xml > > > > and create the vm > > > > (In reply to comment #5) > > > > > wugong, can you provide more info about this? See comment #4 > > > > > > Could you please upload vfd image? > > > Vadim. > > > > https://bugzilla.redhat.com/attachment.cgi?id=675643 > > > > Best regards, > > wugong > > Thanks, > Unfortunately it seems to be empty. Could you please check it? > Best regards, > Vadim. sorry for this. i updated the attachment,and checked it. https://bugzilla.redhat.com/attachment.cgi?id=676608 Best regards, wugong
(In reply to comment #12) > https://bugzilla.redhat.com/attachment.cgi?id=676608 > Best regards, > wugong Thank you, floppy disk has a very strict layout. 32-bit code should be in i386 directory, 64-bit should go in amd64. Otherwise it won't work. Our floppy has the following structure: /mnt/ ├── amd64 │ ├── Win2003 │ │ ├── netkvm.cat │ │ ├── netkvm.inf │ │ ├── netkvm.sys │ │ ├── viostor.cat │ │ ├── viostor.inf │ │ └── viostor.sys │ ├── Win2008 │ │ ├── netkvm.cat │ │ ├── netkvmco.dll │ │ ├── netkvm.inf │ │ ├── netkvm.sys │ │ ├── readme.doc │ │ ├── viostor.cat │ │ ├── viostor.inf │ │ └── viostor.sys │ └── Win7 │ ├── qxl.cat │ ├── qxldd.dll │ ├── qxl.inf │ ├── qxl.sys │ ├── viostor.cat │ ├── viostor.inf │ └── viostor.sys ├── disk1 ├── i386 │ ├── Win2003 │ │ ├── netkvm.cat │ │ ├── netkvm.inf │ │ ├── netkvm.sys │ │ ├── viostor.cat │ │ ├── viostor.inf │ │ └── viostor.sys │ ├── Win2008 │ │ ├── netkvm.cat │ │ ├── netkvmco.dll │ │ ├── netkvm.inf │ │ ├── netkvm.sys │ │ ├── readme.doc │ │ ├── viostor.cat │ │ ├── viostor.inf │ │ └── viostor.sys │ ├── Win7 │ │ ├── qxl.cat │ │ ├── qxldd.dll │ │ ├── qxl.inf │ │ ├── qxl.sys │ │ ├── viostor.cat │ │ ├── viostor.inf │ │ └── viostor.sys │ └── WinXP │ ├── qxl.cat │ ├── qxldd.dll │ ├── qxl.inf │ ├── qxl.sys │ ├── viostor.cat │ ├── viostor.inf │ └── viostor.sys └── txtsetup.oem You can remove or mix-up qxl and netkvm, you can also create two separate images - one for i386, and another one for amd64, but you must keep viostor*, txtsetup.oem, and disk1 in the places, just were they are. Best regards, Vadim.
Created attachment 677621 [details] kernel 3.5 step1
Created attachment 677622 [details] kernel 3.5 step2
Created attachment 677623 [details] kernel 3.5 step3
Created attachment 677624 [details] kernel 3.6 step1
Created attachment 677625 [details] kernel 3.6 step2
Created attachment 677626 [details] kernel 3.6 step3
i think i put too many information in bug report,let's simplify it i use a empty floppy image this time (only has a fat file system,no files in it) so we can focus on the real problems screen capture under kernel-3.5.6-1.fc17.x86_64 (has no bug) step1 - https://bugzilla.redhat.com/attachment.cgi?id=677621 step2 - https://bugzilla.redhat.com/attachment.cgi?id=677622 step3 - https://bugzilla.redhat.com/attachment.cgi?id=677623 screen capture under kernel-3.6.11-1.fc17.x86_64 (has bug) step1 - https://bugzilla.redhat.com/attachment.cgi?id=677624 step2 - https://bugzilla.redhat.com/attachment.cgi?id=677625 step3 - https://bugzilla.redhat.com/attachment.cgi?id=677626 please look difference in step3: "the file xxx could not be found." vs "the disk cannot be read because it contains a unrecognized file system." i used same empty vfd image under test. so dont tell me "your floppy disk file system has problem!" (@_@) empty floppy build with follow commands: dd if=/dev/zero of=empty.vfd bs=1024 count=1440 mkfs.msdos empty.vfd Best regards, wugong
(In reply to comment #20) > i think i put too many information in bug report,let's simplify it > > i use a empty floppy image this time (only has a fat file system,no files in > it) > so we can focus on the real problems > > screen capture under kernel-3.5.6-1.fc17.x86_64 (has no bug) > step1 - https://bugzilla.redhat.com/attachment.cgi?id=677621 > step2 - https://bugzilla.redhat.com/attachment.cgi?id=677622 > step3 - https://bugzilla.redhat.com/attachment.cgi?id=677623 > > screen capture under kernel-3.6.11-1.fc17.x86_64 (has bug) > step1 - https://bugzilla.redhat.com/attachment.cgi?id=677624 > step2 - https://bugzilla.redhat.com/attachment.cgi?id=677625 > step3 - https://bugzilla.redhat.com/attachment.cgi?id=677626 > > please look difference in step3: > "the file xxx could not be found." vs "the disk cannot be read because it > contains a unrecognized file system." It only means that you didn't follow TxtSetup.oem file format. Just copy the same layout as I mentioned in #c13 and it will work. > > i used same empty vfd image under test. so dont tell me "your floppy disk > file system has problem!" (@_@) > At this point setup program doesn't care about FAT, it has too limited file system support to do anything except for simple read. But if it didn't find what it expected - it is an unrecognized file system. Best regards, Vadim. > empty floppy build with follow commands: > dd if=/dev/zero of=empty.vfd bs=1024 count=1440 > mkfs.msdos empty.vfd > > > Best regards, > wugong
Created attachment 677659 [details] new layout floppy driver
(In reply to comment #21) > (In reply to comment #20) > > i think i put too many information in bug report,let's simplify it > > > > i use a empty floppy image this time (only has a fat file system,no files in > > it) > > so we can focus on the real problems > > > > screen capture under kernel-3.5.6-1.fc17.x86_64 (has no bug) > > step1 - https://bugzilla.redhat.com/attachment.cgi?id=677621 > > step2 - https://bugzilla.redhat.com/attachment.cgi?id=677622 > > step3 - https://bugzilla.redhat.com/attachment.cgi?id=677623 > > > > screen capture under kernel-3.6.11-1.fc17.x86_64 (has bug) > > step1 - https://bugzilla.redhat.com/attachment.cgi?id=677624 > > step2 - https://bugzilla.redhat.com/attachment.cgi?id=677625 > > step3 - https://bugzilla.redhat.com/attachment.cgi?id=677626 > > > > please look difference in step3: > > "the file xxx could not be found." vs "the disk cannot be read because it > > contains a unrecognized file system." > > It only means that you didn't follow TxtSetup.oem file format. > Just copy the same layout as I mentioned in #c13 and it will work. i tried your layout ,it wont work for kernel 3.6.x ,but work for kernel 3.5.x. the same result these days.(see jpg files in attachments) the bug is : when you install a fc17 (kernel 3.3) ,start a windows guest with virsh. every floppy work fine, some day do a yum update,update kernel to kernel 3.5 every floppy also work fine! but another day ,yum update get a 3.6 kernel, the bug occur!!!! , reboot into old 3.5 kernel, work fine again. and unfortunatly，fc18 has same problem! if you dont believe me ,please try it yourself! i am sorry for my pool english，i cant explain the problem i short words. what i means: every thing work fine before update the kernel to 3.6.x, so i report the bug to kernel group. my floppy structure: . ├── amd64 │ └── Win2003 │ ├── viostor.cat │ ├── viostor.inf │ └── viostor.sys ├── disk1 └── txtsetup.oem ├── disk1 ├── i386 │ └── Win2003 │ ├── viostor.cat │ ├── viostor.inf │ └── viostor.sys └── txtsetup.oem my floppy: https://bugzilla.redhat.com/attachment.cgi?id=677659 Best regards, wugong > > > > > i used same empty vfd image under test. so dont tell me "your floppy disk > > file system has problem!" (@_@) > > > At this point setup program doesn't care about FAT, it has too limited file > system support to do anything except for simple read. But if it didn't find > what it expected - it is an unrecognized file system. > > Best regards, > Vadim. > > > empty floppy build with follow commands: > > dd if=/dev/zero of=empty.vfd bs=1024 count=1440 > > mkfs.msdos empty.vfd > > > > > > Best regards, > > wugong
(In reply to comment #23) > > i tried your layout ,it wont work for kernel 3.6.x ,but work for kernel > 3.5.x. > > the same result these days.(see jpg files in attachments) > > > the bug is : when you install a fc17 (kernel 3.3) ,start a windows guest > with virsh. every floppy work fine, > > some day do a yum update,update kernel to kernel 3.5 every floppy also work > fine! > > but another day ,yum update get a 3.6 kernel, the bug occur!!!! , reboot > into old 3.5 kernel, work fine again. > > and unfortunatly，fc18 has same problem! > > if you dont believe me ,please try it yourself! > what is the qemu version? thank you, Vadim.
(In reply to comment #24) > (In reply to comment #23) > > > > i tried your layout ,it wont work for kernel 3.6.x ,but work for kernel > > 3.5.x. > > > > the same result these days.(see jpg files in attachments) > > > > > > the bug is : when you install a fc17 (kernel 3.3) ,start a windows guest > > with virsh. every floppy work fine, > > > > some day do a yum update,update kernel to kernel 3.5 every floppy also work > > fine! > > > > but another day ,yum update get a 3.6 kernel, the bug occur!!!! , reboot > > into old 3.5 kernel, work fine again. > > > > and unfortunatly，fc18 has same problem! > > > > if you dont believe me ,please try it yourself! > > > > what is the qemu version? > thank you, > Vadim. qemu-kvm-1.0.1-2.fc17.x86_64 ipxe-roms-qemu-20120328-1.gitaac9718.fc17.noarch qemu-system-x86-1.0.1-2.fc17.x86_64 qemu-img-1.0.1-2.fc17.x86_64 qemu-common-1.0.1-2.fc17.x86_64
wugong, sorry this stalled out. can you still reproduce on kernel 3.8 which should be available as an f17 update?
I'm seeing the same error. It appears to be kvm specific, i.e. switching emulation from kvm to qemu avoids the unrecognized filesystem error.
(In reply to comment #27) > I'm seeing the same error. It appears to be kvm specific, i.e. switching > emulation from kvm to qemu avoids the unrecognized filesystem error. Michael, what kernel version are you using?
This bug has been dormant for a month. Michael Coulter, if you can still reproduce with an up to date F17, including rebooting into the latest kernel, please reopen and give us the kernel and qemu-system-x86 package versions.