Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Support for multiple DispVMs #866

Closed
marmarek opened this issue Mar 8, 2015 · 5 comments
Closed

Support for multiple DispVMs #866

marmarek opened this issue Mar 8, 2015 · 5 comments
Labels
C: core P: major Priority: major. Between "default" and "critical" in severity. release notes This issue should be mentioned in the release notes. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Milestone
Release 4.0

Comments

@marmarek
Copy link
Member

marmarek commented Mar 8, 2015

Reported by joanna on 2 Jun 2014 12:46 UTC
See:

https://groups.google.com/forum/#!topic/qubes-devel/uQJL7I70GQs

Migrated-From: https://wiki.qubes-os.org/ticket/866
@marmarek marmarek added this to the Release 3 milestone Mar 8, 2015
@marmarek marmarek added T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality. C: core P: major Priority: major. Between "default" and "critical" in severity. labels Mar 8, 2015
@marmarek marmarek modified the milestones: Release 4.0, Release 3.0 May 13, 2015
@marmarek marmarek mentioned this issue Oct 8, 2015
Open
@marmarek marmarek mentioned this issue Feb 28, 2016
Closed
3 tasks
@mfc mfc mentioned this issue Mar 17, 2016
Closed
@marmarek marmarek mentioned this issue Mar 29, 2016
Closed
@marmarek marmarek added the release notes This issue should be mentioned in the release notes. label May 20, 2016
@marmarek
Copy link
Member Author

In principle it will be possible to start an AppVM in "disposable" mode - which means changes to its private image (in addition to root image as in normal AppVM) will be discarded after VM shutdown. Technically any AppVM can be used for that, but practically it makes sense to have dedicated "DispVM template" AppVMs (as currently fedora-xx-dvm).

More discussion here:
https://groups.google.com/d/msgid/qubes-devel/20160517124118.GK25975%40mail-itl

marmarek added a commit to marmarek/old-qubes-core-admin that referenced this issue May 20, 2016
@marmarek
qubes/storage: allow snapshots of snapshots
4f91a1f 
It may make sense to create 'snapshot' volume out of already 'snapshot',
not only 'origin'. In pracice it will exactly the same as 'snapshot
connected directly to 'origin'.

QubesOS/qubes-issues#866
marmarek added a commit to marmarek/old-qubes-core-admin that referenced this issue May 20, 2016
@marmarek
qubes/vm: Implement Disposable VM
24d7329 
Implement DispVM as a VM based on AppVM.

QubesOS/qubes-issues#866
@marmarek
Copy link
Member Author

@woju where should be a code to make use of the DispVM? It would:

  1. Create new DispVM
  2. Start it
  3. Call a service
  4. Cleanup when service finished

IOW equivalent of /usr/lib/qubes/qfile-daemon-dvm tool.
The main usage would be when someone call an RPC service with $dispvm:sth target, but sometimes it is also useful to start new DispVM manually (from dom0 menu for example).

Should it be new qvm-start-dispvm tool? Option to some existing one (qvm-run?)? Function somewhere in the core (where?), connected to existing or a new tool?

marmarek added a commit to marmarek/old-qubes-core-admin that referenced this issue May 20, 2016
@marmarek
qubes/vm: Implement Disposable VM
eb49eb9 
Implement DispVM as a VM based on AppVM.

QubesOS/qubes-issues#866
@woju
Copy link
Member

woju commented May 21, 2016

Some function in core, preferably a method of AppVM class
(get_dispvm()?). And CLI tool also. If you have to run a service there,
that would probably be qvm-run.

pozdrawiam / best regards .-.
Wojtek Porczyk .-^' '^-.
Invisible Things Lab |'-.-^-.-'|
| | | |
I do not fear computers, | '-.-' |
I fear lack of them. '-._ : ,-'
-- Isaac Asimov `^-^-_>

@marmarek
Copy link
Member Author

So vm.get_dispvm() would return DispVM based on this VM? Already running?
Generally I'm not so sure whether it should be in any *VM class, as it create new VM instance. And even worse - may need to reload qubes.xml to cleanup it later. Slightly more detailed content of this function:

  1. Create new DispVM (create object, add to app.domains)
  2. dispvm.create_on_disk()
  3. app.save()
  4. dispvm.start()
  5. dispvm.run_service(..., wait=True) (or something)
  6. Possibly reload qubes.xml if changed in the meantime
  7. dispvm.force_shutdown()
  8. dispvm.remove_from_disk()
  9. del app.domains[dispvm]
  10. app.save()

woju pushed a commit to woju/qubes-core-admin that referenced this issue Jun 2, 2016
@marmarek @woju
qubes/storage: allow snapshots of snapshots
54c7076 
It may make sense to create 'snapshot' volume out of already 'snapshot',
not only 'origin'. In pracice it will exactly the same as 'snapshot
connected directly to 'origin'.

QubesOS/qubes-issues#866
woju pushed a commit to woju/qubes-core-admin that referenced this issue Jun 2, 2016
@marmarek @woju
qubes/vm: Implement Disposable VM
c965024 
Implement DispVM as a VM based on AppVM.

QubesOS/qubes-issues#866
woju added a commit to woju/qubes-core-admin that referenced this issue Jun 2, 2016
@woju
qubes/vm/qubesvm: return self from methods modifying state
476b681 
This is helpful when writing oneliners.

QubesOS/qubes-issues#866
woju added a commit to woju/qubes-core-admin that referenced this issue Jun 2, 2016
@woju
qubes/vm/qubesvm: allow looking up by UUID
a719e0d 
Also, allow lookup using VM from other app.

QubesOS/qubes-issues#866
andrewdavidwong added a commit that referenced this issue Jun 3, 2016
@andrewdavidwong
Untrack #866 (completed)
9c21c74
@marmarek marmarek mentioned this issue Jun 16, 2016
Closed
@marmarek marmarek mentioned this issue Dec 6, 2016
Closed
@marmarek marmarek mentioned this issue Jan 8, 2017
Closed
@andrewdavidwong
Copy link
Member

Workaround provided by by @unman:
https://groups.google.com/d/msg/qubes-users/2uN9ybLTqHQ/XMy6d5UkDwAJ

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: core P: major Priority: major. Between "default" and "critical" in severity. release notes This issue should be mentioned in the release notes. T: enhancement Type: enhancement. A new feature that does not yet exist or improvement of existing functionality.
Projects
None yet
Milestone
Release 4.0
Development

No branches or pull requests
3 participants
@marmarek @woju @andrewdavidwong