https://bugzilla.novell.com/show_bug.cgi?id=398932
User tetsuichi.asaka@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=398932#c25
Tetsuichi Asaka
That output is indicative of libvirtd not running. Do you have libvirtd daemon running? I might have some problems in the 0.4.4 spec file since I took a stab at making the same spec file work for all products (SLES*, openSUSE*) and on arch's not supported by Xen.
Anyhow, I'll attach the patched 0.4.0 rpms for your testing pleasure.
I have installed the new RPMs. rpm -qa libvirt\* virt-manager libvirt-0.4.0-60 libvirt-python-0.4.0-60 virt-manager-0.5.3-21.1 On repetition in the logs I see, /var/log/messages Jul 7 15:01:56 server gconfd (root-12141): starting (version 2.22.0), pid 12141 user 'root' Jul 7 15:01:56 server gconfd (root-12141): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Jul 7 15:01:56 server gconfd (root-12141): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1 Jul 7 15:01:56 server gconfd (root-12141): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 Jul 7 15:01:56 server gconfd (root-12141): Resolved address "xml:readonly:/etc/gconf/gconf.xml.vendor" to a read-only configuration source at position 3 Jul 7 15:01:56 server gconfd (root-12141): Resolved address "xml:readonly:/etc/gconf/gconf.xml.schemas" to a read-only configuration source at position 4 /root/.virt-manager/virt-manager.log [Mon, 07 Jul 2008 15:01:54 virt-manager 12138] INFO (virt-manager:126) Application startup [Mon, 07 Jul 2008 15:01:55 virt-manager 12139] WARNING (keyring:31) No support for gnome-keyring [Mon, 07 Jul 2008 15:01:56 virt-manager 12139] DEBUG (engine:74) About to connect to uris ['xen:///'] [Mon, 07 Jul 2008 15:01:56 virt-manager 12139] DEBUG (manager:112) minimize_minutes set to 120 [Mon, 07 Jul 2008 15:01:56 virt-manager 12139] DEBUG (connection:311) Scheduling background open thread for xen:/// [Mon, 07 Jul 2008 15:01:56 virt-manager 12139] DEBUG (connection:318) Background thread is running [Mon, 07 Jul 2008 15:01:56 virt-manager 12139] DEBUG (connection:347) Background open thread complete, scheduling notify [Mon, 07 Jul 2008 15:01:56 virt-manager 12139] DEBUG (connection:356) Notifying open result [Mon, 07 Jul 2008 15:01:56 virt-manager 12139] WARNING (connection:487) Unable to list active networks [Mon, 07 Jul 2008 15:01:56 virt-manager 12139] WARNING (connection:491) Unable to list inactive networks [Mon, 07 Jul 2008 15:01:56 virt-manager 12139] DEBUG (manager:427) About to append vm: Domain-0 [Mon, 07 Jul 2008 15:01:56 virt-manager 12139] DEBUG (manager:417) VM Domain-0 started [Mon, 07 Jul 2008 15:01:57 virt-manager 12139] WARNING (connection:487) Unable to list active networks [Mon, 07 Jul 2008 15:01:57 virt-manager 12139] WARNING (connection:491) Unable to list inactive networks And so on repeatedley. For the libvirtd status I can check, I think correctly, service libvirtd status Checking status of libvirtd unused chkconfig --list | grep virt libvirtd 0:off 1:off 2:off 3:on 4:off 5:on 6:off So its not running. Is it required? I know from my reading that "libvirtd provides virbr0, an isolated netdev connected to external using forwarding+NAT" and since I will not use virbr0, but only several other bridge interfaces I will name, then I did think it is not required. It has never earlier been something required for me. -- 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.