Ian Pilcher <[email protected]> writes: > On 01/02/2012 03:43 AM, Markus Armbruster wrote: >> What is your exact qemu-kvm command line? Fish it out of libvirt's >> GUEST.log. > > It's long. ;-) It does, however, include the following:
It's always long :) > -drive file=/mnt/scratch/software/virt- > drivers/virtio-win-1.1.16.vfd,if=none,id=drive-fdc0-0-0,format=raw > -global isa-fdc.driveA=drive-fdc0 > -0-0 -global isa-fdc.bootindexA=3 > >> $ virsh qemu-monitor-command --hmp GUEST 'info qtree' >> >> What do you get? > > dev: isa-fdc, id "" > dev-prop: driveA = drive-fdc0-0-0 > dev-prop: driveB = <null> > dev-prop: bootindexA = 3 > dev-prop: bootindexB = -1 > isa irq 6 Looks good. >> If you have a drive, look it up in output of: >> >> $ virsh qemu-monitor-command --hmp GUEST 'info block' > > drive-fdc0-0-0: removable=1 locked=0 > file=/mnt/scratch/software/virt-drivers/virtio-win-1.1.16.vfd ro=0 > drv=raw encrypted=0 Looks good, too. > Within the guest, Device Manager shows a "Standard floppy disk > controller", but it does not show an attached drive. > > I haven't found anything in any of the log files that indicates a > problem. Weird and annoying. Fedora 16, you said. Could be this one: https://bugzilla.redhat.com/show_bug.cgi?id=753863 Comment#2 promises the fix "will make the next update". Justin, got an ETA? _______________________________________________ virt mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/virt
