From: Gerry Reno <greno@verizon.net>
To: kvm@vger.kernel.org
Subject: Re: After upgrading from F7 kvm-65-15 to F10 kvm-74-10
Date: Sun, 29 Mar 2009 23:08:16 -0400 [thread overview]
Message-ID: <49D037A0.3030804@verizon.net> (raw)
In-Reply-To: <49D01DCE.9010401@verizon.net>
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
next prev parent reply other threads:[~2009-03-30 3:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 16:15 After upgrading from F7 kvm-65-15 to F10 kvm-74-10 Gerry Reno
2009-03-29 21:47 ` Gerry Reno
2009-03-30 1:18 ` Gerry Reno
2009-03-30 3:08 ` Gerry Reno [this message]
2009-03-29 22:00 ` Ross McKay
2009-03-29 23:56 ` Gerry Reno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49D037A0.3030804@verizon.net \
--to=greno@verizon.net \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox