[Bug 658610] Re: Check whether images have write permissions
I think what it means that, if the file permission for the disk image in host OS is read only for the user running qemu, then it is not saying that clearly. May be qemu should just exit as soon as it sees that image is read only. I am not sure if in some kind of mode it is possible to run a VM without the need of writing anything on the image. If that is the case then probably it should give an option or default to run in that mode under such circumstances. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/658610 Title: Check whether images have write permissions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 418112] Re: qemu-img should give reasons for failing
** Description changed: Binary package hint: qemu - $ kvm-img create -f qcow2 disks/t.img 4000M - Formatting 'disks/t.img', fmt=qcow2, size=4096000 kB - qemu-img: Error while formatting + $ kvm-img create -f qcow2 disks/t.img 4000M + Formatting 'disks/t.img', fmt=qcow2, size=4096000 kB + qemu-img: Error while formatting strace shows that the real error was Permission denied. It should say so, using strerror. ProblemType: Bug Architecture: i386 Date: Mon Aug 24 13:31:45 2009 DistroRelease: Ubuntu 9.10 Package: qemu 0.10.6-1ubuntu1 ProcEnviron: - LANGUAGE=en_GB.UTF-8 - LC_COLLATE=C - PATH=(custom, user) - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_GB.UTF-8 + LC_COLLATE=C + PATH=(custom, user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-5.24-generic SourcePackage: qemu Uname: Linux 2.6.31-5-generic i686 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/418112 Title: qemu-img should give reasons for failing -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 658610] Re: Check whether images have write permissions
I think what it means that, if the file permission for the disk image in host OS is read only for the user running qemu, then it is not saying that clearly. May be qemu should just exit as soon as it sees that image is read only. I am not sure if in some kind of mode it is possible to run a VM without the need of writing anything on the image. If that is the case then probably it should give an option or default to run in that mode under such circumstances. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/658610 Title: Check whether images have write permissions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 418112] Re: qemu-img should give reasons for failing
** Description changed: Binary package hint: qemu - $ kvm-img create -f qcow2 disks/t.img 4000M - Formatting 'disks/t.img', fmt=qcow2, size=4096000 kB - qemu-img: Error while formatting + $ kvm-img create -f qcow2 disks/t.img 4000M + Formatting 'disks/t.img', fmt=qcow2, size=4096000 kB + qemu-img: Error while formatting strace shows that the real error was Permission denied. It should say so, using strerror. ProblemType: Bug Architecture: i386 Date: Mon Aug 24 13:31:45 2009 DistroRelease: Ubuntu 9.10 Package: qemu 0.10.6-1ubuntu1 ProcEnviron: - LANGUAGE=en_GB.UTF-8 - LC_COLLATE=C - PATH=(custom, user) - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_GB.UTF-8 + LC_COLLATE=C + PATH=(custom, user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-5.24-generic SourcePackage: qemu Uname: Linux 2.6.31-5-generic i686 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/418112 Title: qemu-img should give reasons for failing -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
