dom0 seems to be getting a lot of updates at the moment (3x in the last
1-2 weeks?) ... are there any security holes we should know about?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails
> ***
> *** ERROR
> ***
> *** Cannot create chroot because the current filesystem is mounted as
> nodev. ***
> *** Build Qubes on a different
>
>
>
> Haven't used qubes windows tools at all, but the error output above
> seems to point at a mount options issue. It cannot create the chroot
> because the filesystem is mounted with `nodev`.
>
> As it says above, try `make remount`. Or manually with `mount -o
> remount,dev ` for
Hi,
Has anyone had any luck with cloning a crypted Qubes installation using
Clonezilla?
Even using DD the clone just won't boot
Thanks
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails
Hi!
I have a working Windows 10 (without qubes tools) VM with a 60GB root drive
that Windows partitioned like this:
500MB System-Partition
38GB C-Drive
473MB Repair-Partition
20GB unallocated
I would like to extend the C-Drive to include the 20GB free space but for that
I have to move the
didier.pelli...@gmail.com:
> Hi,
>
> Has anyone had any luck with cloning a crypted Qubes installation using
> Clonezilla?
>
> Even using DD the clone just won't boot
>
> Thanks
>
Should work if you are using legacy BIOS boot on both source &
destination. UEFI boot might need a command on the
Nevermind, my problem was trying to run `qvm-appmenus` from sudo.
Still unfortunate there's no --get-default-whitelist though.
On 6/15/20 6:48 PM, Emma Borhanian wrote:
Hi, I'm trying to programmatically configure the appmenus for a dispvm
template.
`qvm-appmenus --get-whitelist /
