On 08/15/2011 10:07 AM, Guido Günther wrote: > On Mon, Aug 15, 2011 at 09:12:15PM +0800, j20110...@js.id.au wrote: >> It happens I have rebooted, and the problem wrt that particular disk image >> now does not occur. >> >> The file did, in fact, exist; I've changed the way I pass data to my new >> guests and now do not use a floppy >> image, so I used to commands I already showed you in order to recreate the >> problem. >> >> Previously, I expanded the allocated size of the file using a dd command >> similar to this: >> dd if=/dev/zero of=/var/lib/libvirt/images/fd1440a.img seek=1 bs=2G count=0 >> and the problem went away. Since that it now does not go away that way, I >> expect I must have done something >> else as well, lile restart libvirtd. >> >> Since the message, "ValueError: Size must be specified for non existent >> volume path '/var/lib/libvirt/images/fd1440a.img'" >> is clearly misleading because the ls command (which is the obvious way to >> check) reveals the file does exist. > > This sounds like you've not refreshed the storage pool after adding the > image? I leave the bug open for now since the error message is > misleading indeed. > -- Guido >
What virtinst version is this? Current release should refresh the storage pool if it doesn't find the referenced basename. - Cole >> >> I suggest that libvirtd (or whatever is the offending code) be changed to >> ask the filesystem whether the file exists >> (stat() and/or access()) and that the error reporting be improved to more >> accurately reflect the actual problem. >> >> Thanks for your time. >> >> >> -- >> John Summerfield >> >> >> >> >> >> _______________________________________________ >> Pkg-libvirt-maintainers mailing list >> pkg-libvirt-maintain...@lists.alioth.debian.org >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-libvirt-maintainers >> > > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org