Description of problem: Qemu does not work correctly when used with networked disk over the NBD protocol (with qemu-nbd). Qemu dies with "could not open disk image", and qemu-nbd exits immediately after even when started with --shared=2. Version-Release number of selected component (if applicable): qemu-0.10.4-4.fc11.x86_64 How reproducible: 100 % Steps to Reproduce: 1. setenforce 0 # Just to be sure that SELinux is not involved 2. qemu-img create -f qcow2 /tmp/hda.qcow2 20G 3. qemu-nbd -v -k /tmp/hda.sock -e 2 /tmp/hda.qcow2 4. (in a different shell) qemu-kvm -drive file=nbd:unix:/tmp/hda.sock,if=virtio,boot=on -m 1024 -k en-us -vnc :1 Actual results: Qemu dies with "qemu: could not open disk image nbd:unix:/tmp/hda.sock", and qemu-img exits with code 0. Expected results: Qemu should be able to use the NBD disk. Additional info: Tested on x86_64 OS only. The problem still exists when using NBD over TCP instead of UNIX sockets.
Seems to work fine with if=ide on it's own, and fails with if=ide,boot=on - looks like an extboot problem
Actually, no. If I do: $> qemu-nbd -k /tmp/foo -v -e 2 foo.img in one shell and in another: $> qemu-kvm -drive file=nbd:unix:/tmp/foo,if=virtio,boot=on it works fine; however, when I quite qemu-kvm, qemu-nbd dies with: nbd.c:nbd_receive_request():L465: read failed and if I try to start qemu-kvm without re-starting qemu-nbd, I get: $> qemu-kvm -drive file=nbd:unix:/tmp/foo,if=virtio,boot=on qemu: could not open disk image nbd:unix:/tmp/foo Is that what you're seeing too, Jan?
Yes, I am seeing the same behaviour as described in comment #2.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
The problem still exists in F12: qemu-common-0.11.0-13.fc12.x86_64 qemu-system-x86-0.11.0-13.fc12.x86_64
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.