/qubes-issues

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.

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

Move 'volatile.img' structure creation to the VM (initramfs) #1308

Closed
marmarek opened this Issue Oct 9, 2015 · 0 comments

Comments

Assignees
No one assigned
Labels
Projects
None yet
Milestone
  Release 3.1
1 participant
@marmarek
@marmarek
Member

marmarek commented Oct 9, 2015

It really shouldn't be dom0 (or storage domain) which create this structure, it is mostly VM specific.
This would greatly simplify things:

@marmarek marmarek added enhancement C: core P: major labels Oct 9, 2015

@marmarek marmarek added this to the Release 3.1 milestone Oct 9, 2015

@marmarek marmarek referenced this issue Oct 12, 2015

Open

DispVMs: support for in-RAM execution only (for anti-forensics) #904

marmarek added a commit to QubesOS/qubes-linux-utils that referenced this issue Oct 30, 2015

@marmarek
dracut: initialize volatile.img partitions 
Do not rely on dom0 initializing that device. Actually volatile.img
content should be none of dom0 business.

QubesOS/qubes-issues#1308
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
a30d583

@marmarek marmarek closed this in QubesOS/qubes-core-admin@de275cc Nov 25, 2015

marmarek added a commit to QubesOS/qubes-linux-utils that referenced this issue Nov 25, 2015

@marmarek
initramfs: initialize volatile.img partition table also in TemplateVM 
While there is no additional snapshot device, swap partition is still
used.

Fixes QubesOS/qubes-issues#1308
Verified
This commit was signed with a verified signature.
@marmarek marmarek Marek Marczykowski-Górecki
GPG key ID: 063938BA42CFA724 Learn about signing commits
a23030e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment