[qubes-users] Error updating imported TemplateVM(from 3.2) on 4.0

Hi, When I manually launch update on imported template vm(clone of debian-8 template) I see errors like these: Err http://deb.qubes-os.org stretch Release.gpg Cannot initiate the connection to 10.137.255.254:8082 (10.137.255.254). - connect (101: Network is unreachable) One thing I noticed

Re: [qubes-users] Restoring 3.2 Standalone VM on Qubes 4.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/24/18 21:58, 'awokd' via qubes-users wrote: > On Tue, April 24, 2018 7:02 pm, donoban wrote: >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 >> >> >> Hi, >> >> >> I restored an standalone AppVM based on Fefodora 26. After trying >> to

Re: [qubes-users] Restoring 3.2 Standalone VM on Qubes 4.0

On Tue, April 24, 2018 7:02 pm, donoban wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > > Hi, > > > I restored an standalone AppVM based on Fefodora 26. After trying to > run I saw Qubes GUI didn't work but I could get a bash console from dom0 . > > > I removed qubes 3.2 repo, added

[qubes-users] Re: Setting up privateinternetaccess on qubes 3.2

oh sorry disregard , didn't realize you were referring to the github tasket vpn script ?? funny, I believe he actually designs it for debian > fedora :) still, I guess we're to assume you downloaded the PIA config files to the correct dir etc ?

[qubes-users] Restoring 3.2 Standalone VM on Qubes 4.0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I restored an standalone AppVM based on Fefodora 26. After trying to run I saw Qubes GUI didn't work but I could get a bash console from dom0 . I removed qubes 3.2 repo, added 4 and run 'dnf update'. It installed a lot of packages but now I

Re: [qubes-users] IMG sharing

Hello Drew, Drew White schrieb am Di., 24. Apr. 2018, 07:14: > Is it possible for every guest to share one virtual drive for cacheing and > auto mounting to same location for file transfers? > > i.e. One file always mounted to each guest and one reads while one writes. >

Re: [qubes-users] To use Windows 7 OEM as a Qubes VM; which hardware metadata is needed?

On Tue, 24 Apr 2018 18:28:19 +0200 Teqleez Motley wrote: >(Btw, I do of course have the license key, and I am NOT going to use that VM >online, so I do hopefully not need security updates or the like.) > > >Regards, >Teqleez > In that case, I would consider pulling

Re: [qubes-users] To use Windows 7 OEM as a Qubes VM; which hardware metadata is needed?

(Btw, I do of course have the license key, and I am NOT going to use that VM online, so I do hopefully not need security updates or the like.) Regards, Teqleez -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and

[qubes-users] To use Windows 7 OEM as a Qubes VM; which hardware metadata is needed?

Hi all, One of my old laptops have Windows 7, and I would like to use that license for a Qubes (H)VM. I have one question and one related concern: a) which metadata is needed for that OEM to continue believing that it is the master OS and running on the "same" hardware as initially set up

[qubes-users] Re: Created dvm appears as a normal AppVM instead of dvm

On Tuesday, April 24, 2018 at 5:54:11 AM UTC-4, qube...@tutanota.com wrote: > I created the new dvm: > > [user@dom0 ~]$ qvm-create --template debian-9 --label red deb-dvm-net > [user@dom0 ~]$ qvm-prefs deb-dvm-net template_for_dispvms True > [user@dom0 ~]$ qvm-features deb-dvm-net appmenus-dispvm

Re: [qubes-users] Created dvm appears as a normal AppVM instead of dvm

Sry, solved. Had to create an AppVM deb-dvm-net in advance through the Qube Manager. Than: [user@dom0 ~]$ qvm-prefs deb-dvm-net template_for_dispvms True [user@dom0 ~]$ qvm-features deb-dvm-net appmenus-dispvm 1 Now I can see the deb-dvm-net as a dvm in the Start menu as well. -- Securely

[qubes-users] Created dvm appears as a normal AppVM instead of dvm

I created the new dvm: [user@dom0 ~]$ qvm-create --template debian-9 --label red deb-dvm-net [user@dom0 ~]$ qvm-prefs deb-dvm-net template_for_dispvms True [user@dom0 ~]$ qvm-features deb-dvm-net appmenus-dispvm 1 The created deb-dvm-net is seen in the Qube Manager as a normal AppVM.  In the

Re: [qubes-users] IMG sharing

On 04/24/2018 09:01 AM, Drew White wrote: > On Tuesday, 24 April 2018 15:28:40 UTC+10, Ivan Mitev wrote: >> On 04/24/2018 08:14 AM, Drew White wrote: >>> Is it possible for every guest to share one virtual drive for cacheing and >>> auto mounting to same location for file transfers? >> >> It

Re: [qubes-users] IMG sharing

On Tuesday, 24 April 2018 15:28:40 UTC+10, Ivan Mitev wrote: > On 04/24/2018 08:14 AM, Drew White wrote: > > Is it possible for every guest to share one virtual drive for cacheing and > > auto mounting to same location for file transfers? > > It isn't possible unless you set up a clustered file