[qubes-users] A lot of dom0 updates recently
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 from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20200617045326.GA5613%40danwin1210.me.
Re: [qubes-users] issue with building Qubes Windows Tools
> *** > *** ERROR > *** > *** Cannot create chroot because the current filesystem is mounted as > nodev. *** > *** Build Qubes on a different filesystem, or run 'make remount' to > remount *** > *** with dev option. > *** > *** > *** 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 example, if you are working in your home directory in an AppVM, the command would be `mount -o remount,dev /rw`. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/17f3899b-80d0-b3dc-dd32-31a18501eb8c%40undef.tools.
Re: [qubes-users] issue with building Qubes Windows Tools
> > > > 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 example, if you are working in your home > directory in an AppVM, the command would be `mount -o remount,dev /rw`. > > # make remount ./scripts/find-mount-point: line 8: findmnt: command not found + sudo mount '' -o dev,remount ./scripts/remount: line 10: sudo: command not found make: *** [Makefile:452: remount] Error 127 I'm trying it in MSYS2 in Windows 7. If I try to manually remount It returns "mount: invalid option - 'remount'". -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/29b8b66a-4c62-4c95-88d6-918f5b6427c1o%40googlegroups.com.
[qubes-users] Qubes OS and clonezilla
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 from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ea043ea1-ad96-4593-9a04-0835bc48cb32o%40googlegroups.com.
[qubes-users] Changing Partitions of a Windows 10 Qube
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 Repair-Partition to the end of the drive and make the unallocated space become adjacent to the C-drive partition. Windows won’t allow me to move this partition out of the way and Google brings up information, that it can safely be moved but one needs to use a boot disk with a third party tool to get the moving done while Windows is not running. Well... this being Qubes I thought I can use a disp vm, hook up the root image of the Windows VM to it and use gparted to do the work. To be sure I don’t destroy my Windows VM in the process I was cloning the VM first and then working on the clone. So here is what I have done: In dom0: qvm-clone windows10 windows10-c ls -l /dev/mapper | grep windows10 (that showed /dev/mapper/qubes_dom0-vm—windows10–c—root to be a link to /dev/dm-18 and ...windows10–c—root—1592406155–back to be a link to /dev/dm-7) Naiv as I am, I did (again in dom0) losetup -P -f /dev/dm-18 Which gave me /dev/loop2 which I then attached to a disp VM as /dev/xvdi via the Qubes Devices widget. In the disp VM I ran gparted and moved the repair partition to the end and extended the C-Drive partition right the way as well. That all worked fine and after detaching the volume and removing the /dev/loop2 back in dom0 m, fdisk -l /dev/dm-18 showed the changed partition table exactly the way I wanted it. But when I boot the cloned windows10-c VM of which I presumably just changed the partitions and go into the disk manager of Windows 10, it presents me with the old, unchanged partitioning listed all the way at the top of this message. Nothing had changed at all. So obviously I am missing some important part here, but I have no clue as to what that might be. Can anybody enlighten me, please? I have tried Google and the Qubes documentation quite extensively and if there is any further information available there, I proved to be unworthy of finding it... Regards, Frank -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5791-1592407611-233091%40sneakemail.com.
Re: [qubes-users] Qubes OS and clonezilla
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 destination system to add the new boot source, something like efibootmgr. -- - don't top post Mailing list etiquette: - trim quoted reply to only relevant portions - when possible, copy and paste text instead of screenshots -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a800e8c9-90ac-4a6a-1905-770b7368%40danwin1210.me.
[qubes-users] Re: Programmatically configuring appmenus for dispvm templates
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 / --set-whitelist / --set-default-whitelist` seems out-of-sync with what I configure in Qube Manager, and neither --set-whitelist or --set-default-whitelist work for dispvm templates. I'm also confused why there's no `--get-default-whitelist`. I considered just manually copying over the .desktop files, but the `apps.templates` directory is empty and doesn't populate when I run `qvm-sync-appmenus`. Are they put somewhere else? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d23575a9-4ac8-99ee-c70a-c68f7f1fa23d%40gmail.com.
