https://bugzilla.novell.com/show_bug.cgi?id=790343 https://bugzilla.novell.com/show_bug.cgi?id=790343#c0 Summary: virt-manager permissions, one version runs without issue, another has a permissions issue Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Critical Priority: P5 - None Component: KVM AssignedTo: kvm-bugs@forge.provo.novell.com ReportedBy: tonysu@su-networking.com QAContact: jdouglas@suse.com Found By: --- Blocker: --- Created an attachment (id=513689) --> (http://bugzilla.novell.com/attachment.cgi?id=513689) History of New Packages Installed, then Removal and re-installation User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 First, and maybe unintentional I found that <two> versions of virt-manager can be running, likely suing the same virt-manager and virt-install packages! (see whole description) As described next, A default and possibly older version of virt-manager was initially installed with the functionality I wanted. I then proceeded to install additional KVM/QEMU/"req libvirt" packages which resulted in a different, slicker "Create Virtual Machines" wizard but results in undesirable restrictions. Reproducible: Always Steps to Reproduce: 1. Install default QEMU-KVM virtualization packages 2. Create a New VM using any method including Start > System > Virtualization > Create Virtual Machines for Xen and KVM 3. After initial "Create a Virtual Machine" if you're still running the default virt-manager you should see a screen asking whether you need to install an operating system or point to an existing disk image. If you do not see this, you are already running the "slicker interface" apparently running different underlying code. 4. Another double-check, if you are running the "default" virt-manager you should see tree options for NetWare, Other, RedHat, SUSE, Solaris, Ubuntu and Windows. If you do <not> see this, then you are already running the "slicker" virt-manager. Another check is that this "default" virt-manager will create virtual disks with a default size of 4GB whereas the "slicker" virt-manager will create disks with defaults much larger (eg 8.03 GB). With this "default" virt-manager, you can create VMs locating disks anywhere (I have not found any restriction). 5. After you are convinced you can create virtual machines with few restrictions, install new virtualization packages. I used QEMU, KVM and "requires libvirt" to find and install any packages related to virtualization kernels and management. I have included as an attachment to this bug related installation history. Note that I remember installing a Package that with a name starting with a capital "P" which I cannot now re-discover despite re-running YAST. 6. After installing the packages desribed, I found that re-running "Create Virtual Machines" invokes a slicker looking and possibly newer wizard process. 7. Attempt to create a new disk in a non-default location results in a permissions error "Unable to write..." - This is interesting since the assumption is that the "slicker" virt-manager is running with root permission, that might not be the case or is imposing some new requirement (Storage Group?). 8. Is possible to undo this virt-manager "upgrade" by doing what is described in the attachment to this bug, uninstalling and then re-installing virt-manager and virt-install. Actual Results: As described in "Steps to Reproduce" an undesirable upgrade to how virt-manager and virt-install occurred. But surprisingly simply uninstalling virt-manager and virt-install, then re-installing the likely same packages returned previous functionality. Note that this surprising different versions of virt-manager and virt-install means casts considerable uncertainty into all related bugs... Which code is actually being referred to in a bug report? Since intial bug submission only permits one attachment, I will attempt to upload an additional screenshot further identifying one version of virt-install. If not possible, then I will post elsewhere and link to it. I am ranking this Critical not because of the usual reasons but because if unresolved likely makes <all> bug reporting relating to virt-manager and virt-install and perhaps more likely un-actionable. But, pls don't overlook my personal bug issue which is the mixed-up permissions issue which likely has persisted for some time which prevents virtual disks (backing files) from being placed in a non-default location. I believe this exists cross-platform (Researching, have seen references to this default location issue mentioned in other distros). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.