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 upReliable command execution in VM #86
Comments
marmarek
assigned
rootkovska
Mar 8, 2015
marmarek
added this to the Release 1 Beta 1 milestone
Mar 8, 2015
marmarek
added
enhancement
C: core
P: major
labels
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Modified by joanna on 15 Mar 2011 00:34 UTC |
marmarek
unassigned
rootkovska
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
Modified by joanna on 15 Mar 2011 00:38 UTC |
marmarek
added
P: critical
and removed
P: major
labels
Mar 8, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
marmarek
Mar 8, 2015
Member
Comment by rafal on 23 Mar 2011 15:53 UTC
Implemented.
TBD - improve performance. Probably the vchan buffer is the bottleneck.
|
Comment by rafal on 23 Mar 2011 15:53 UTC |
marmarek
closed this
Mar 8, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
marmarek commentedMar 8, 2015
Reported by rafal on 7 Mar 2011 11:10 UTC
Currently, dom0 can trigger command execution in VM via qubes-guid message. This has the following disadvantages:
a) requires running qubes-guid; some VMs, e.g. netvm, are started before X, so without qubes-guid
b) there is no stdin/stdout/stderr passing, and no info on exit code
Solve it via a dedicated qrexec-agent process in each VM.
Migrated-From: https://wiki.qubes-os.org/ticket/86