My disk has enough free space. When I used VB 6.1.18 with LisLogic SAS live mode on the host worked well and I was able to start whonix VB with a live mode on the host. But now when live mode is on on the host I got this error - VERR_DISK_FULL
Also now is impossible to switch AHCI VB to read only.
Never mind VB issued version 6.1.22 with fixed LsiLogic SAS problem.
Thanks for reporting the bug, Though im getting different error message:(Debian host)
and debian didnt yet upgraded vbox in sid yet to .22:
As noticed in above forum thread, /boot
isn’t write protected. Any idea how /boot
could also be covered?
grub-live ported to dracut would be great!
Debian feature request
Boot existing Host Operating System or VM into Live Mode (grub-live)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991276
When this becomes available will it be used in very much the same way one would use tails? Burn onto usb or dvdr then use it as an OS like tails?
This feature is already available. See links to wiki (edit) in initial post in this forum thread.
Thanks for getting back. But isn’t there something still in development where we would be able to boot a usb stick or DVD and it will take us straight into the whonix environment? Whonix live ISO or something…Without using any virtual machine? If so is it ready for end users yet? Thanks again for response
You can combine
with
That’s the most you can get for now.
Future:
No ETA.
Cool… well I’d happily donate towards it I think it’s a great idea and am in full support of it. Unfortunately though with my lack of technical knowledge I can’t be of much help in that area
Added to Combine Kicksecure ™ Live VMs with Read-only Mode for Virtual Hard Drives chapter VirtualBox in Kicksecure wiki just now:
On Debian bookworm based Kicksecure ™
17
(and above) / Newer VirtualBox versions:
- VirtualBox might no longer support
VBoxInternal/Devices/lsilogicsas/0/LUN#0/AttachedDriver/Config/ReadOnly
. Settings set thorughVBoxManage setextradata
are not officially supported and might be gone at some time such as now.- VirtualBox documentation chapter Special Image Write Modes
mentions
immutable images
but this might not be as good asread-only images
.
Above two issues are not easy to fix.
Help welcome!
Link to source code: