From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerry Reno Subject: Re: After upgrading from F7 kvm-65-15 to F10 kvm-74-10 Date: Sun, 29 Mar 2009 23:08:16 -0400 Message-ID: <49D037A0.3030804@verizon.net> References: <49CF9EBB.3070404@verizon.net> <49CFEC54.60507@verizon.net> <49D01DCE.9010401@verizon.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: kvm@vger.kernel.org Return-path: Received: from vms173009pub.verizon.net ([206.46.173.9]:53440 "EHLO vms173009pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753486AbZC3DI3 (ORCPT ); Sun, 29 Mar 2009 23:08:29 -0400 Received: from [192.168.2.100] ([72.91.189.24]) by vms173009.mailsrvcs.net (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008; 32bit)) with ESMTPA id <0KHA0054DU1S843X@vms173009.mailsrvcs.net> for kvm@vger.kernel.org; Sun, 29 Mar 2009 22:08:17 -0500 (CDT) In-reply-to: <49D01DCE.9010401@verizon.net> Sender: kvm-owner@vger.kernel.org List-ID: Gerry Reno wrote: > > So the only problem I'm very concerned about at the moment is the VM > that was at the point of first reboot after the successful completion > of an F9 install. Any suggestions as to how to get that VM running? > > In the virtmanager log we see this when we try to start this VM: [Sun, 29 Mar 2009 22:37:27 virt-manager 5707] DEBUG (manager:427) VM MX_2 started [Sun, 29 Mar 2009 22:37:27 virt-manager 5707] DEBUG (details:1042) Got timed retry [Sun, 29 Mar 2009 22:37:27 virt-manager 5707] DEBUG (details:1094) Trying console login [Sun, 29 Mar 2009 22:37:27 virt-manager 5707] DEBUG (details:1108) Graphics console configured at vnc://127.0.0.1:5901 [Sun, 29 Mar 2009 22:37:27 virt-manager 5707] DEBUG (details:1121) Starting connect process for 127.0.0.1 5901 [Sun, 29 Mar 2009 22:37:27 virt-manager 5707] DEBUG (details:1020) VNC initialized [Sun, 29 Mar 2009 22:37:30 virt-manager 5707] DEBUG (details:1006) VNC disconnected [Sun, 29 Mar 2009 22:37:30 virt-manager 5707] WARNING (details:1032) Retrying connection in 125 ms [Sun, 29 Mar 2009 22:37:30 virt-manager 5707] ERROR (proxies:400) Introspect error on :1.5:/org/freedesktop/Hal/devices/net_06_d3_60_e9_70_0f: dbus.exceptions.DBusException: org.freedesktop.Hal.NoSuchDevice: No device with id /org/freedesktop/Hal/devices/net_06_d3_60_e9_70_0f [Sun, 29 Mar 2009 22:37:30 virt-manager 5707] DEBUG (proxies:403) Executing introspect queue due to error [Sun, 29 Mar 2009 22:37:30 virt-manager 5707] ERROR (connection:218) Exception in handler for D-Bus signal: Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 214, in maybe_handle_message self._handler(*args, **kwargs) File "/usr/share/virt-manager/virtManager/connection.py", line 278, in _net_phys_device_removed if objif.QueryCapability("net"): File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 68, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 140, in __call__ **keywords) File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 630, in call_blocking message, timeout) What does this mean? Regards, Gerry