Description of problem: I wanted to install new linux virtual machine and as with VirtualBox wanted to keep virtual storage image in users home directory. virt-manager only offers to use my / partition and that is now acceptable because I use it only for Fedora and usually format it on every new release, and it is too small, only 10GB. Plenty of room for Fedora but not for additional virtual images. I have a large /home partition where I keep all my user files and also my virtual machines in VirtualBox. virt-manager doesn't support creating new storage image in /home partition, please change that. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 384832 [details] New VM
Created attachment 384833 [details] Locate or create storage volume
Created attachment 384834 [details] Add a Storage Volume
Grow your /var. According to FHS it's the correct place for variable runtime data and SELinux wouldn't allow libvirtd access your home anyway.
I don't wan't to store virtual images in /var but in /home as I do with VirtualBox and all other Virtualization apps. I have SELinux disabled and still pressing NEW IMAGE button doesn't present option to choose where to save virtual image file. please view this video: http://dl.dropbox.com/u/184632/virt-manager.ogg
or this link: http://www.youtube.com/watch?v=cqGOhZC_WXQ
Then you need to set up a new storage pool in /home. This is done before creating a new virtual machine. In virt-manager: Open the host details for 'localhost (qemu)' Click the 'storage' tab click the '+' on the bottom left side to add a pool You can add a storage pool to use with virtual machines in this way, and can create volumes in the new pool.
Thank you Justin for clarification, this helped a lot! This isn't for me as a new user of virt-manager and this functionality would be somehow more emphasized in UI of popup window when users try to add new storage image. I thought about these issues and posted two RFEs, please comment on them: https://bugzilla.redhat.com/show_bug.cgi?id=557103 https://bugzilla.redhat.com/show_bug.cgi?id=557107