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 upOpening a DispVM when the TemplateVM is running forces savefile regeneration #754
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Modified by joanna on 26 Nov 2013 13:32 UTC |
marmarek
added this to the Release 2 Beta 3 milestone
Mar 8, 2015
marmarek
added
bug
C: core
P: major
labels
Mar 8, 2015
marmarek
removed this from the Release 2 Beta 3 milestone
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Modified by joanna on 26 Nov 2013 17:47 UTC |
marmarek
added this to the Release 2 Beta 3 milestone
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Modified by joanna on 8 Dec 2013 16:34 UTC |
marmarek
removed this from the Release 2 Beta 3 milestone
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Comment by marmarek on 11 Mar 2014 13:18 UTC |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Mar 8, 2015
Member
Comment by joanna on 24 Mar 2014 11:34 UTC
Ok, I cannot really reproduce the deadlock, however I have the following observation (tested on all the latest packets from current-testing):
When I keep the template running (on which my dispvm is based), then each time I start a dispvm it gets its savefile regenerated. I think this is not correct -- it should get its savefile regenerated only after the template is shutdown.
|
Comment by joanna on 24 Mar 2014 11:34 UTC When I keep the template running (on which my dispvm is based), then each time I start a dispvm it gets its savefile regenerated. I think this is not correct -- it should get its savefile regenerated only after the template is shutdown. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
Modified by joanna on 24 Mar 2014 11:49 UTC |
marmarek
added
P: minor
and removed
P: major
labels
Mar 8, 2015
marmarek
changed the title from
Opening a DispVM when the TemplateVM is running causes a deadlock
to
Opening a DispVM when the TemplateVM is running forces savefile regeneration
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Mar 8, 2015
Member
Comment by marmarek on 24 Mar 2014 12:00 UTC
Checking timestamp of actual root image (provided as device-mapper snapshot) while the template is running isn't straightforward... but surely doable.
Anyway template isn't running for the most of the time.
|
Comment by marmarek on 24 Mar 2014 12:00 UTC |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Mar 8, 2015
Member
Comment by marmarek on 28 Mar 2014 06:01 UTC
Added warning:
http://git.qubes-os.org/?p=marmarek/core-admin.git;a=commit;h=8be54ab174542cc6e28f549f25fee431ff90b116
|
Comment by marmarek on 28 Mar 2014 06:01 UTC |
marmarek commentedMar 8, 2015
Reported by joanna on 16 Nov 2013 12:48 UTC
... which later requites Qubes restart to get rid of, as e.g. qvm-* tools work no longer, waiting on the lock.
To reproduce:
Migrated-From: https://wiki.qubes-os.org/ticket/754