Hi Han,
Han Pilmeyer wrote:
Where would you like me to report back? Here or on the list?
list, cc'ed
What I'm mainly concerned about is losing accenot sure it's thess to
the mouse. If that happens, I can not easily fix the guest image.
can you send the logs from this scenario? you can always shutdown using
keyboard;)
On my test guest it worked after restarting the service with the new
executables (but it worked before as well) and also on the 2nd reboot.
ok
On the 1st reboot I had one of my other issues, namely that the
vdagent doesn't start.
this seems to be virtio-serial issue. what are the versions of the
driver and qemu?
That could seems to have changed as there now appear to be retries
every 3 seconds for a bit of time. Below is the log of that:
not sure it's the right behavior, or it's a leftover. i'll consider
removing the retries.
2580::INFO::2012-11-29 17:34:43,610::log_version::0.5.1.0
2580::INFO::2012-11-29
17:34:43,610::DesktopLayout::consistent_displays::#qxls 1 #others 0
2580::INFO::2012-11-29
17:34:43,610::VDAgent::send_announce_capabilities::Sending capabilities:
2580::INFO::2012-11-29
17:34:43,610::VDAgent::send_announce_capabilities::37
2580::INFO::2012-11-29 17:34:43,610::VDAgent::run::Connected to server
2580::INFO::2012-11-29
17:34:43,610::VDAgent::input_desktop_message_loop::Desktop: Winlogon
2580::INFO::2012-11-29
17:34:43,610::VDAgent::handle_announce_capabilities::Got capabilities (1)
2580::INFO::2012-11-29
17:34:43,610::VDAgent::handle_announce_capabilities::77
2580::INFO::2012-11-29
17:34:43,610::VDAgent::send_announce_capabilities::Sending capabilities:
2580::INFO::2012-11-29
17:34:43,610::VDAgent::send_announce_capabilities::37
2580::INFO::2012-11-29
17:34:43,610::VDAgent::handle_announce_capabilities::Got capabilities (1)
2580::INFO::2012-11-29
17:34:43,610::VDAgent::handle_announce_capabilities::77
2580::INFO::2012-11-29 17:34:43,610::DisplaySetting::set::setting
display options
2580::INFO::2012-11-29
17:34:43,610::DisplaySetting::get_user_process_id::explorer.exe not found
2580::INFO::2012-11-29
17:34:43,610::DisplaySetting::reload_from_registry::get_user_process_id
failed
792::INFO::2012-11-29 17:35:35,725::VDAgent::run::***Agent started in
session 1***
792::INFO::2012-11-29 17:35:35,725::log_version::0.5.1.0
792::INFO::2012-11-29
17:35:35,725::DesktopLayout::consistent_displays::#qxls 1 #others 0
792::INFO::2012-11-29 17:35:35,725::VDAgent::init_vio_serial::Failed
opening \\.\Global\com.redhat.spice.0, error 2
1188::INFO::2012-11-29 17:35:37,914::VDAgent::run::***Agent started in
session 1***
1188::INFO::2012-11-29 17:35:37,915::log_version::0.5.1.0
1188::INFO::2012-11-29
17:35:37,916::DesktopLayout::consistent_displays::#qxls 1 #others 0
1188::INFO::2012-11-29 17:35:37,916::VDAgent::init_vio_serial::Failed
opening \\.\Global\com.redhat.spice.0, error 2
1660::INFO::2012-11-29 17:35:40,937::VDAgent::run::***Agent started in
session 1***
1660::INFO::2012-11-29 17:35:40,937::log_version::0.5.1.0
1660::INFO::2012-11-29
17:35:40,937::DesktopLayout::consistent_displays::#qxls 1 #others 0
1660::INFO::2012-11-29 17:35:40,937::VDAgent::init_vio_serial::Failed
opening \\.\Global\com.redhat.spice.0, error 2
1956::INFO::2012-11-29 17:35:44,030::VDAgent::run::***Agent started in
session 1*** not sure the
1956::INFO::2012-11-29 17:35:44,030::log_version::0.5.1.0
1956::INFO::2012-11-29
17:35:44,030::DesktopLayout::consistent_displays::#qxls 1 #others 0
1956::INFO::2012-11-29 17:35:44,030::VDAgent::init_vio_serial::Failed
opening \\.\Global\com.redhat.spice.0, error 2
2152::INFO::2012-11-29 17:35:47,056::VDAgent::run::***Agent started in
session 1***
2152::INFO::2012-11-29 17:35:48,694::log_version::0.5.1.0
2152::INFO::2012-11-29
17:35:48,694::DesktopLayout::consistent_displays::#qxls 1 #others 0
2152::INFO::2012-11-29 17:35:48,694::VDAgent::init_vio_serial::Failed
opening \\.\Global\com.redhat.spice.0, error 2
2332::INFO::2012-11-29 17:35:51,830::VDAgent::run::***Agent started in
session 1***
On 29/11/2012 17:27, Arnon Gilboa wrote:
Han Pilmeyer wrote:
Arnon,
Just a quick question before I do something stupid. I just tried
placing the exe's in the proper location and restarting the service.
It didn't work.
update should be done after stopping g the service (verify that
vdservice & vdagent are not running), then start it.
if it doesn't help, try to restart your vm. anyway please send the
relevant lines of both vdagent & vdservice logs.
There were some different messages in the log (compared to previous
logs), but my feeling was that the cut/paste was completely ignored.
I was tempted to reboot to make sure, but I noticed that my mouse
didn't work when I stopped the service. This would make my guest
virtually useless.
Is there a proper/safe way to test this? I'm going to retry with a
test guest now.
Cheers,
Han
_______________________________________________
Spice-devel mailing list
Spice-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
