[libvirt-users] 答复: What is the difference between running "virt-manager" and "sudo virt-manager"?

重启服务器后，root下virt-manager能执行了，我看你的帐号还不行。 发件人: Allen Qiu [mailto:my1stbox@163.com] 发送时间: 2014年10月27日 16:31 收件人: libvirt-users(a)redhat.com 抄送: 王成武; 'Bin Liu'; zoubinbin100(a)163.com 主题: What is the difference between running "virt-manager" and "sudo virt-manager"? Hi all, What is the difference between starting virt-manager by "virt-manager" and by "sudo virt-manager"? It seems that there are two copy of virt-manager running in the background. When I run "virt-manager", I got a error of "Unable to open a connection to the libvirt management daemon. Libvirt URI is: qemu:///system Verify that: - The 'libvirtd' daemon has been started". Whereas when I run "sudo virt-manager", I got a error of "Error starting Virtual Machine Manager: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See <http://projects.gnome.org/gconf/> http://projects.gnome.org/gconf/ for information." How should I deal with the two issues respectively? Is there any drawback by simply running "virt-manager"? Regards, Allen 2014-10-27 _____ Allen Qiu