cannot connect to 'win7' qrexec agent for 300 seconds, giving up
16 views
Skip to first unread message
Franz
unread,
Dec 2, 2018, 3:55:12 PM12/2/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to qubes...@googlegroups.com
Suddenly win7 VM stopped starting on Qubes 3.2. Nothing changed except perhaps the last couple of dom0 updates.
The error message is:
cannot connect to 'win7' qrexec agent for 300 seconds, giving up
I tried debug mode, but it is just the same.
awokd
unread,
Dec 16, 2018, 3:43:48 PM12/16/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Franz, qubes...@googlegroups.com
Franz wrote on 12/2/18 8:54 PM:
I had this but it was because Win7 was trying to boot in recovery mode.
When you enable debug mode, watch the Win7 boot process in the console
to make sure it's not doing the same. If it is, tell it to start normally.
Franz
unread,
Dec 16, 2018, 8:59:36 PM12/16/18
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to awokd, qubes-users
thanks awokd, doing what you suggest, it hungs forever on the "Starting Windows" screen. also the dot on Qubes Manager remains yellow. But trying again it started showing the following:
"Xen pv network class needs to restart the system to complete installation. Press yes to restart now..."
So the issue seems to be that dom0 update installed some Xen change that interrupted normal Windows start.