Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upqubes manager throws an exception when quickly restarting an AppVM #315
Comments
marmarek
assigned
rootkovska
Mar 8, 2015
marmarek
added this to the Release 1 Beta 2 milestone
Mar 8, 2015
marmarek
added
bug
C: qubes-manager
P: minor
labels
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Modified by joanna on 1 Aug 2011 19:09 UTC |
marmarek
modified the milestones:
Release 1 Beta 3,
Release 1 Beta 2
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Modified by joanna on 10 Sep 2011 08:17 UTC |
marmarek
modified the milestones:
Release 1 Beta 2,
Release 1 Beta 3
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Mar 8, 2015
Member
Comment by joanna on 14 Sep 2011 18:14 UTC
Seems like the problem is in this code:
if not vm.is_running() or vm.get_start_time() >= datetime.utcnow() - timedelta(0,vm_shutdown_timeout/1000):
specifically, if a VM has been 'running' at the time of the first condition check (not vm.is_running), but later became '!running' and so the vm.get_start_time() returns something that is not of type datatime.
|
Comment by joanna on 14 Sep 2011 18:14 UTC if not vm.is_running() or vm.get_start_time() >= datetime.utcnow() - timedelta(0,vm_shutdown_timeout/1000): specifically, if a VM has been 'running' at the time of the first condition check (not vm.is_running), but later became '!running' and so the vm.get_start_time() returns something that is not of type datatime. |
marmarek commentedMar 8, 2015
Reported by joanna on 28 Jul 2011 19:06 UTC
When I shutdown, and the quickly start again the same VM, the manager usually shows this eception:
After I dismiss the message window, it continues to work fine though.
Migrated-From: https://wiki.qubes-os.org/ticket/315