[virt-tools-list] bug report

Cole Robinson crobinso at redhat.com
Wed Jul 30 14:40:29 UTC 2014

On 07/30/2014 04:32 AM, Jeremy A. wrote:
> hello all, i am to lazy to go create an account to file a bug report so here
> it is:
> when using virt manager storage manager and you click on "new volume"
> if the running kernel is PaX hardened and the qemu-img binary  has not been
> already dehardened with paxctl, the virt-manager storage manager gui will
> create a ghost image, meaning it exists in tracking but not on disk since
> qemu-img failed to run because of PaX.
>  now this is not a hugh problem and easy to work around by simply using paxctl
> prior to running said scenario. but this is anoying for the image name you
> wanted to create is no longer useable since virt-manager thinks the file exists.
> basically there should be some error checking to make sure a virtual disk
> storage file is created before an entry is made into some XML db that tracks them.

Does virt-manager show a backtrace at all? When running qemu-img, how does it
fail: fail to even exec() it, or does some system call deep in qemu-img fail?

- Cole

More information about the virt-tools-list mailing list