Created a thin volume on a second hdd. Can use mount to attach it to dom0 and make a backup on it for example. mounted or unmounted, qvm-block can't see it. So, can't attach it to any other cube. Is that how it's supposed to be? -- You received this message because you are subscribed to the
We've also been trying for days to get a VPN to resolve on a brand new R4.0 install, to either one of 2 different VPN providers, using the iptables and cli scripts: https://www.qubes-os.org/doc/vpn/#set-up-a-proxyvm-as-a-vpn-gateway-using-iptables-and-cli-scripts I've also set it up before on a
> > Install per the instructions for Mr.Laprise's excellent > qubes-vpn-setup in an Template-based AppVM , don't miss any steps. > ELSE > > delete the AppVM and startover make sure openvpn is installed in > the Template chosen , make sure to enable proxy in the created AppVM > , and for services
Has anyone experienced this kind of problem with any of your apps: https://github.com/bisq-network/bisq/issues/2855 -- 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
Hello All, What is the general procedure in Qubes 4, if we can open the Luks, but then pool00 seems inaccessible with rdsosreport message: Check of pool qubes_dom0/pool00 failed (status:1). Manual repair required! Thank you for your time. Crypto Carabao Group --- #Plow_with_Carabao!
We have this same problem as here: https://github.com/trezor/trezord-go/issues/163#issuecomment-552288220 The trezor devs reopened the issue, but looks like they have more important problems to work. Is anyone using Trezor 1 with Qubes 4 successfully? What's the setup or at least