Description of problem: Using virt-manager UI to create a paravirtual guest there are no available network devices under "Shared physical device" option. Only "Virtual network" option is possible. Version-Release number of selected component (if applicable): virt-manager-0.5.3-2.el5 How reproducible: 100% Steps to Reproduce: 1. Start virt-manager 2. Create new guest and navigate to network settings screen 3. Choose "Shared physical device" option Actual results: No devices present. Install can't continue Expected results: Device xenbr0 is present and can be chosen. Additional info: ifconfig output from the system eth0 Link encap:Ethernet HWaddr 00:1A:4B:0C:88:3B inet addr:10.12.5.42 Bcast:10.12.7.255 Mask:255.255.252.0 inet6 addr: fe80::21a:4bff:fe0c:883b/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4003 errors:0 dropped:0 overruns:0 frame:0 TX packets:2140 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:304077 (296.9 KiB) TX bytes:293840 (286.9 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:32 errors:0 dropped:0 overruns:0 frame:0 TX packets:32 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3624 (3.5 KiB) TX bytes:3624 (3.5 KiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:4159 errors:0 dropped:0 overruns:0 frame:0 TX packets:2152 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:329773 (322.0 KiB) TX bytes:303174 (296.0 KiB) Interrupt:17 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:2141 errors:0 dropped:0 overruns:0 frame:0 TX packets:4003 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:294002 (287.1 KiB) TX bytes:304077 (296.9 KiB) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:41 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:8894 (8.6 KiB) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:1446 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:89000 (86.9 KiB) TX bytes:0 (0.0 b)
Created attachment 297021 [details] screen dump of UI
Created attachment 297022 [details] screen dump from RHEL5.1 machine where this works ifconfig output from RHEL5.1 machine where this works. eth0 Link encap:Ethernet HWaddr 00:16:41:E4:1D:63 inet addr:10.34.32.137 Bcast:10.34.35.255 Mask:255.255.252.0 inet6 addr: fec0::f101:216:41ff:fee4:1d63/64 Scope:Site inet6 addr: fe80::216:41ff:fee4:1d63/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:51286 errors:0 dropped:0 overruns:0 frame:0 TX packets:27623 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22494169 (21.4 MiB) TX bytes:2958076 (2.8 MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:26814 errors:0 dropped:0 overruns:0 frame:0 TX packets:26814 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12032357 (11.4 MiB) TX bytes:12032357 (11.4 MiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:98576 errors:0 dropped:0 overruns:0 frame:0 TX packets:61198 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:85592144 (81.6 MiB) TX bytes:5543929 (5.2 MiB) Base address:0x3000 Memory:ee000000-ee020000 vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:27623 errors:0 dropped:0 overruns:0 frame:0 TX packets:51286 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2958076 (2.8 MiB) TX bytes:22494169 (21.4 MiB) vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:33538 errors:0 dropped:0 overruns:0 frame:0 TX packets:49961 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:1855904 (1.7 MiB) TX bytes:63262792 (60.3 MiB) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:6 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:468 (468.0 b) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fec0::f101:fcff:ffff:feff:ffff/64 Scope:Site inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:21591 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2139444 (2.0 MiB) TX bytes:0 (0.0 b)
Dan, is this a regression? What I can see from ifconfig dump is that xenbr0 doesn't have an address on the machine where that bug happens. Both machines are using DHPC.
Dan, I have the following in virt-manager.log right after the application starts even before doing anything else. [Thu, 06 Mar 2008 05:42:38 virt-manager 5692] ERROR (connection:156) Unable to connect to HAL to list network devices: '%s'dbus_bindings.DBusException A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "(unset)" member "QueryCapability" error name "(unset)" destination "org.freedesktop.Hal") Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 153, in detect_network_devices self._device_added(path) File "/usr/share/virt-manager/virtManager/connection.py", line 164, in _device_added if obj.QueryCapability("net"): File "/usr/lib64/python2.4/site-packages/dbus/proxies.py", line 25, in __call__ ret = self._proxy_method (*args, **keywords) File "/usr/lib64/python2.4/site-packages/dbus/proxies.py", line 102, in __call__ reply_message = self._connection.send_with_reply_and_block(message, timeout) File "dbus_bindings.pyx", line 455, in dbus_bindings.Connection.send_with_reply_and_block DBusException: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "(unset)" member "QueryCapability" error name "(unset)" destination "org.freedesktop.Hal") I have SELinux in permissive mode. Is that the root cause of the problem or it's another bug? Thanks.
This is a regression caused by the recent DBus security errata. We will need to z-stream this fix too :-(
This bugzilla has Keywords: Regression. Since no regressions are allowed between releases, it is also being proposed as a blocker for this release. Please resolve ASAP.
Upstream change to address this issue is http://hg.et.redhat.com/virt/applications/virt-manager--devel?cs=43d82ba67ffa Should be possible to backport this to 5.1.x and 5.2 virt-manager releases without any trouble.
Set dev ack.
set beta target
Fix from upstream is backported & built for 5.2 in $ brew latest-pkg dist-5E-qu-candidate virt-manager Build Tag Built by ---------------------------------------- -------------------- ---------------- virt-manager-0.5.3-3.el5 dist-5E-qu-candidate berrange
Requesting z-stream. BZ was already cloned by mistake. We will take care of duping it when the new bz is created...
*** Bug 436279 has been marked as a duplicate of this bug. ***
Is this the same as http://bugs.centos.org/view.php?id=2516 ?
Gianluca, I think so. That was caused by a HAL bug I believe.
The problem was caused by the recent DBus security errata which caused various DBus API calls to be rejected. We had to change the way we handled DBus in virt-manager
*** Bug 440482 has been marked as a duplicate of this bug. ***
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2008-0480.html