On Monday, February 26, 2018 at 8:04:44 PM UTC+1, ThierryIT wrote:
> Hi,
>
> I would like to backup few of my VMs.
> I have mount my external usb (not using sys-usb) HDD.
> From the console where my HDD is attached/mounted, I have access through
> /mnt/removable to all my previous (3.2) backup
On Monday, February 26, 2018 at 8:04:44 PM UTC+1, ThierryIT wrote:
> Hi,
>
> I would like to backup few of my VMs.
> I have mount my external usb (not using sys-usb) HDD.
> From the console where my HDD is attached/mounted, I have access through
> /mnt/removable to all my previous (3.2) backup
Sorry wrong link at the bottom, here is the right one.
https://www.coreboot.org/Board_freedom_levels
--
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
On 02/26/2018 03:47 AM, Zbigniew Łukasiak wrote:
On Tue, Feb 6, 2018 at 2:01 PM, Utility Panel
wrote:
Meanwhile, the machines I'm currently replacing are both server workstations
with 96 gigs of EEC RAM. I'm looking to upgrade to something comparable, and
I'm
On Mon, Feb 26, 2018 at 6:53 AM, Utility Panel
wrote:
...
> So, I've decided to build with the KGPE-D16. Thus far, I've got the
> motherboard and two 6386SE CPUs with air coolers. I buy the other components
> when the pricing is favorable.
>
> Later, when I've got
On Monday, February 26, 2018 at 3:47:07 AM UTC-5, Zbigniew Łukasiak wrote:
> On Tue, Feb 6, 2018 at 2:01 PM, Utility Panel
> wrote:
>
> > Meanwhile, the machines I'm currently replacing are both server
> > workstations with 96 gigs of EEC RAM. I'm looking to upgrade
On Tue, Feb 6, 2018 at 2:01 PM, Utility Panel
wrote:
> Meanwhile, the machines I'm currently replacing are both server workstations
> with 96 gigs of EEC RAM. I'm looking to upgrade to something comparable, and
> I'm pretty certain at this point that I'll start
On Wed, February 7, 2018 12:16 am, taii...@gmx.com wrote:
> Forgot to add:
>
>
> It is a shame that qubes doesn't support POWER.
Meant to reply to this one earlier!
What would need to happen for Qubes to run on POWER? Does Xen support it?
--
You received this message because you are
On Thu, February 22, 2018 6:19 pm, 'Aaron Dough' via qubes-users wrote:
> Sorry for the avalanche of messages, I just had sys-net freeze on me even
> though the Ethernet controller was detached. As it turns out, the
> Wireless controller needs no-strict-reset=true too. Now it seems much
> more
On February 22, 2018 5:01 PM, Aaron Dough wrote:
>On February 22, 2018 1:57 PM, 'awokd' via qubes-users
>qubes-users@googlegroups.com wrote:
>
>>On Thu, February 22, 2018 1:49 pm, Aaron Dough wrote:
>>>Good to know. Since Tuxedo especially advertises it's native
>>>
On February 22, 2018 1:57 PM, 'awokd' via qubes-users
wrote:
>On Thu, February 22, 2018 1:49 pm, Aaron Dough wrote:
>
>>Good to know. Since Tuxedo especially advertises it's native
>> Linux-support, I think I'll ask their support directly regarding this
>> issue.
On Thu, February 22, 2018 1:49 pm, Aaron Dough wrote:
> Good to know. Since Tuxedo especially advertises it's native
> Linux-support, I think I'll ask their support directly regarding this
> issue. It may be far fetched, but if this is really solvable with updated
> firmware, it's worth a shot
Original Message
On February 22, 2018 1:28 PM, 'awokd' via qubes-users
wrote:
>On Thu, February 22, 2018 1:18 pm, 'Aaron Dough' via qubes-users wrote:
>>On February 22, 2018 1:06 PM, 'awokd' via qubes-users
>>qubes-users@googlegroups.com wrote:
On Thu, February 22, 2018 1:18 pm, 'Aaron Dough' via qubes-users wrote:
> On February 22, 2018 1:06 PM, 'awokd' via qubes-users
> wrote:
>> I'm wondering if sys-net and suspending will be more stable if you
>> attach everything on bus 3 to sys-net while leaving
On February 22, 2018 1:06 PM, 'awokd' via qubes-users
wrote:
>On Thu, February 22, 2018 12:52 pm, 'Aaron Dough' via qubes-users wrote:
>
>>Attaching 3:00.0 to sys-net also did not help, instead sys-net would not
>> start up any more ("Cannot execute
On Thu, February 22, 2018 12:52 pm, 'Aaron Dough' via qubes-users wrote:
> Attaching 3:00.0 to sys-net also did not help, instead sys-net would not
> start up any more ("Cannot execute qrexec-daemon").
>
> So I'm back to disabling ethernet altogether by not attaching 3:00.1 to
> sys-net. This is
On February 22, 2018 12:52 PM, Aaron Dough wrote:
>Hello again, my long overdue update on the matter, now with RC4:
>
>1. Installing Qubes 4.0 RC4 in UEFI-Mode works fine now :)
>
>2. No manual adjustment of GRUB needed any more :)
>
>3. Standby seems to work almost
Hello again, my long overdue update on the matter, now with RC4:
1. Installing Qubes 4.0 RC4 in UEFI-Mode works fine now :)
2. No manual adjustment of GRUB needed any more :)
3. Standby seems to work almost perfectly now. It does need about a minute to
kick in, and if I unlock my screen in this
Thought so. Wise decision IMO
--
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 post to this group, send email to
On Sunday, February 11, 2018 at 5:09:31 PM UTC+1,
cybe...@national.shitposting.agency wrote:
> @Yuraeitha
> actually i am experiencing this bug with qvm-backup-restore:
>
> https://groups.google.com/forum/#!topic/qubes-users/HZVBAqerLoI
>
> Is there a way to manually trigger a refresh of the
On Sunday, February 11, 2018 at 5:09:31 PM UTC+1,
cybe...@national.shitposting.agency wrote:
> @Yuraeitha
> actually i am experiencing this bug with qvm-backup-restore:
>
> https://groups.google.com/forum/#!topic/qubes-users/HZVBAqerLoI
>
> Is there a way to manually trigger a refresh of the
@Yuraeitha
actually i am experiencing this bug with qvm-backup-restore:
https://groups.google.com/forum/#!topic/qubes-users/HZVBAqerLoI
Is there a way to manually trigger a refresh of the drop-down menu of available
qubes? qvm-backup-restore does not reliably add qubes to the menu of available
@ cybe...@national.shitposting.agency
Glad it worked out for you:)
@Tom Zander
On Sunday, February 11, 2018 at 12:18:11 PM UTC+1, Tom Zander wrote:
> On Saturday, 10 February 2018 09:05:51 CET Yuraeitha wrote:
> > On Saturday, February 10, 2018 at 6:51:47 AM UTC+1,
>
On Saturday, 10 February 2018 09:05:51 CET Yuraeitha wrote:
> On Saturday, February 10, 2018 at 6:51:47 AM UTC+1,
cybe...@national.shitposting.agency wrote:
> > I have a usb drive attached to sys-usb, lets say its mounted at /mnt on
> > sys-usb and im trying to backup a vm named MyVm from dom0
thank you!
qvm-backup --help
didnt display too much information, so i was mostly guessing at usage, thank
you for your thorough answer
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails
On Saturday, February 10, 2018 at 6:51:47 AM UTC+1,
cybe...@national.shitposting.agency wrote:
> I have a usb drive attached to sys-usb, lets say its mounted at /mnt on
> sys-usb and im trying to backup a vm named MyVm
> from dom0 the command:
>
> sudo qvm-backup sys-usb:/mnt MyVm
>
> returns
On Saturday, February 10, 2018 at 6:51:47 AM UTC+1,
cybe...@national.shitposting.agency wrote:
> I have a usb drive attached to sys-usb, lets say its mounted at /mnt on
> sys-usb and im trying to backup a vm named MyVm
> from dom0 the command:
>
> sudo qvm-backup sys-usb:/mnt MyVm
>
> returns
On Saturday, February 10, 2018 at 6:51:47 AM UTC+1,
cybe...@national.shitposting.agency wrote:
> I have a usb drive attached to sys-usb, lets say its mounted at /mnt on
> sys-usb and im trying to backup a vm named MyVm
> from dom0 the command:
>
> sudo qvm-backup sys-usb:/mnt MyVm
>
> returns
Forgot to add:
It is a shame that qubes doesn't support POWER.
Due to the ceasing of manufacturing of the KGPE-D16 and D8 boards the
OpenPOWER9 TALOS 2 is soon the only reasonable brand new option for a
performance board with libre firmware/hardware.
It is of course possible to make a
5he nice thing going forward is most newer processors are coming with the iommu
etc where just 2 years ago it was at least 2x less choices. The real issue
these days is making sure the bios/efi software is supporting it to the
standard and not some half baked abortion of what it should be.
On Monday, February 5, 2018 at 10:34:34 AM UTC-5, Utility Panel wrote:
> I installed Qubes 4.0-rc4 on a machine with hardware that cannot support the
> following two features
>
> IOMMU/VT-d/AMD-Vi
> Interrupt Remapping
>
> The installation went fine. I simply continued installing after the
On Tue, February 6, 2018 11:35 am, 'awokd' via qubes-users wrote:
> [Re-titling this sub-thread]
> Anyone out there intimate with nft/iptables? My PR went through so the
> document is up for grabs again if you want it! (Or please give suggestions
> here and I can document it too.)
For anyone
[Re-titling this sub-thread]
On Tue, February 6, 2018 11:12 am, 'Tom Zander' via qubes-users wrote:
> On Tuesday, 6 February 2018 11:32:07 CET 'awokd' via qubes-users wrote:
>
>> I'm not getting past the first step of:
>>
>>
>> Verify you are cutting through the sys-net VM firewall by looking at
On Monday, 5 February 2018 12:21:51 CET Tim W wrote:
> I am currently going thru all the setup script qubes build template
> options to find what templates compile correctly and what ones have bugs.
> After that I am happy to write up a markdown page for how to compile and
> install the Qubes
On Monday, February 5, 2018 at 4:37:26 AM UTC-5, rob_66 wrote:
> On Sun, 4 Feb 2018 12:17:41 -0800 (PST)
> Yuraeitha wrote:
>
> > I think discussion is good and healthy, though I don't feel it's entirely
> > fair to paint it black
> > and white like this. I can agree on
On Monday, January 29, 2018 at 10:11:12 AM UTC+8, Qubed One wrote:
> Yuraeitha:
> > On Sunday, January 28, 2018 at 3:13:47 AM UTC+1, joeh...@gmail.com
> > wrote:
> >> I burned the ISO to USB stick then started to install Qubes but got
> >> the following:
> >>
> >> [0.093375] ACPI Error:
On Monday, January 29, 2018 at 10:11:12 AM UTC+8, Qubed One wrote:
> Yuraeitha:
> > On Sunday, January 28, 2018 at 3:13:47 AM UTC+1, joeh...@gmail.com
> > wrote:
> >> I burned the ISO to USB stick then started to install Qubes but got
> >> the following:
> >>
> >> [0.093375] ACPI Error:
Yuraeitha:
> On Sunday, January 28, 2018 at 3:13:47 AM UTC+1, joeh...@gmail.com
> wrote:
>> I burned the ISO to USB stick then started to install Qubes but got
>> the following:
>>
>> [0.093375] ACPI Error: [\SB_.PCIO.XHC_.RHUB.HS11] Namespace
>> lookup failure, AE_NOT_FOUND
On Sunday, January 28, 2018 at 3:13:47 AM UTC+1, joeh...@gmail.com wrote:
> I burned the ISO to USB stick then started to install Qubes but got the
> following:
>
> [0.093375] ACPI Error: [\SB_.PCIO.XHC_.RHUB.HS11] Namespace lookup
> failure, AE_NOT_FOUND (20170531/dswload-210)
> [
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, Jan 26, 2018 at 11:37:31PM -0600, Andrew David Wong wrote:
> On 2018-01-26 05:14, awokd wrote:
> > On Fri, January 26, 2018 3:36 am, Andrew David Wong wrote:
> >> On 2018-01-25 12:28, awokd wrote:
> >>> 1. Should I open an issue for tracking
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2018-01-26 05:14, awokd wrote:
> On Fri, January 26, 2018 3:36 am, Andrew David Wong wrote:
>> On 2018-01-25 12:28, awokd wrote:
>>> 1. Should I open an issue for tracking and move the discussion
>>> over there? Move to qubes-devel? Keep here?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2018-01-26 05:38, 'awokd' via qubes-users wrote:
> On Fri, January 26, 2018 9:22 am, Alex Dubois wrote:
>> On Friday, 26 January 2018 03:36:33 UTC, Andrew David Wong
>> wrote:
>
>> Happy to contribute. maybe we can have a direct conversation so
On Fri, January 26, 2018 9:22 am, Alex Dubois wrote:
> On Friday, 26 January 2018 03:36:33 UTC, Andrew David Wong wrote:
> Happy to contribute. maybe we can have a direct conversation so that we
> can discuss what is needed and where I feel comfortable...
Speaking only on my own behalf of
On Fri, January 26, 2018 3:36 am, Andrew David Wong wrote:
> On 2018-01-25 12:28, awokd wrote:
>> 1. Should I open an issue for tracking and move the discussion
>> over there? Move to qubes-devel? Keep here?
>
> Please open an issue in qubes-issues.
On Friday, 26 January 2018 03:36:33 UTC, Andrew David Wong wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2018-01-25 12:28, awokd wrote:
> > Resuming working my way through splitting up the documentation now
> > that the 3.2 vs. 3.3 question has been mostly settled. Some
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2018-01-25 12:28, awokd wrote:
> Resuming working my way through splitting up the documentation now
> that the 3.2 vs. 3.3 question has been mostly settled. Some
> general questions:
>
> 1. Should I open an issue for tracking and move the
On Sunday, January 21, 2018 at 9:15:49 PM UTC-5, pixel fairy wrote:
> qubes 4.0 rc3 fedora-26 template
>
> running the file manager from a menu will always start an appvm if its not
> running. but it wont always run the file manager. running terminal, or any
> other apps always works. running
On Monday, 22 January 2018 02:15:49 UTC, pixel fairy wrote:
> qubes 4.0 rc3 fedora-26 template
>
> running the file manager from a menu will always start an appvm if its not
> running. but it wont always run the file manager. running terminal, or any
> other apps always works. running nautilus
On Monday, January 8, 2018 at 8:56:58 PM UTC-5, Fabrizio Romano Genovese wrote:
> Well, I disabled intel speedstep in the bios and things seem to be better.
> Startup time now is around 1.20 mins (still better than 3mins), both in
> plugged and unplugged state (booting in plugged state was
Well, I disabled intel speedstep in the bios and things seem to be better.
Startup time now is around 1.20 mins (still better than 3mins), both in plugged
and unplugged state (booting in plugged state was around 45 secs before tho).
I'll use my PC for a bit more, trying another couple of
On Monday, January 8, 2018 at 1:27:45 PM UTC+1, Fabrizio Romano Genovese wrote:
> No, my PC is a Dell XPS13, not a Latitude. But I have some news:
>
> The booting problem is 100% dependent on being plugged or not. Precisely, I
> observed the following behaviors:
>
> Booting plugged: Everything
No, my PC is a Dell XPS13, not a Latitude. But I have some news:
The booting problem is 100% dependent on being plugged or not. Precisely, I
observed the following behaviors:
Booting plugged: Everything is normal, PC is fast. If I unplug it afterwards
nothing really happens and performance
So I managed to get past this bug by starting a fresh VM and using qvm-prefs
kernel parameter set to ''. This results in the VM at least recognizing the iso
and starting the windows installation process. Unfortunately it crashes at the
Windows logo. Looking around it does look like others are
fixed from enabling testing updates
--
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 post to this group, send email
On Tuesday, November 7, 2017 at 10:22:22 AM UTC, JPL wrote:
> I must have done something else because I got error messages when I tried to
> reset the firewall and sys-net VMs, so rather than spending any more time
> fiddling around I reinstalled and was more careful about the boxes I checked.
I must have done something else because I got error messages when I tried to
reset the firewall and sys-net VMs, so rather than spending any more time
fiddling around I reinstalled and was more careful about the boxes I checked.
While it's a good idea to have the option of seting update
JPL:
> I just installed RC2 for the first time, ticking the 'enable Tor' box
corresponding to the Whonix template. After booting and connecting to
WiFi I was surprised to note that the Whonix Gateway started with the
'connecting to Tor' dialog when I started the Fedora-25 template to
update it. So
On Thursday, 2 November 2017 09:25:30 UTC-4, cooloutac wrote:
> On Thursday, November 2, 2017 at 4:21:38 AM UTC-4, [799] wrote:
> > Hello,
> >
> > >> Did you make it permanently ?
> >
> > Yes of course :-) but thank you for the reminder, I edited in once in grub
> > for the first boot after
On Thursday, November 2, 2017 at 4:21:38 AM UTC-4, [799] wrote:
> Hello,
>
> >> Did you make it permanently ?
>
> Yes of course :-) but thank you for the reminder, I edited in once in grub
> for the first boot after installation and then applied it in the Grub
> configuration.
> Same results,
Hello,
>> Did you make it permanently ?
Yes of course :-) but thank you for the reminder, I edited in once in grub for
the first boot after installation and then applied it in the Grub configuration.
Same results, VMs won't start - it seems only the both sys network VMs work.
>> Dont give up
On Wednesday, 25 October 2017 13:26:51 UTC-4, [799] wrote:
> Hello,
>
> As at least one other Qubes user has the same problem, that VMs won't start,
> I'll add this as special topic.
>
> I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot
> the VMs.
> This includes
Hello,
I tried the suggestion to remove the iommu line from Grub and did so on the
first reboot after the installation.
Strangely this seems to work for sys-net and sys-firewall which boot up fine.
I also once been able to launch a disposable VM.
sys-usb and also other VMs which I've created
Hello,
>> Hi all sergio matta mention to remove the
>> iommu=no-igfx. this solve the problem and i
>> think it will solve 90% of you the issue . so
>> the credit is for you sergio . Thanks . R
I've reinstalled Qubes 4rc2 and removed the line "iommu=no-igfx" upon first
restart (after installing
Hey y'all, I have found some workarounds for getting VMs to boot. If you
change the virt_mode to pv instead of hvm, usually sys-usb and sys-firewall
will begin to boot regularly. I also increased the qrexec-timeout to 120
per someone's recommendation here, and that seemed to help sys-whonix boot
On Wed, November 1, 2017 00:25, '[799]' via qubes-users wrote:
> Or am I missing something and there is some action on the developer
> mailing list?
I was looking forward to trying out 4.0rc2 as well. Was a bit disappointed
to hit a roadblock, but I understand not all issues are going to be
Hello,
Honestly what is bothering me a bit, is that there seem to be lots of problems
with Qubes 4-rc2, which is ok, as it is a testing release - bit I'd like to see
more feedback from the Qubes Dev's, so that we can find out what is the Root
cause.
Isn't this how a test release should work?
Em terça-feira, 31 de outubro de 2017 11:10:22 UTC-2, Roy Bernat escreveu:
> On Tuesday, 31 October 2017 14:56:46 UTC+2, Roy Bernat wrote:
> > On Tuesday, 31 October 2017 14:52:10 UTC+2, Roy Bernat wrote:
> > > On Wednesday, 25 October 2017 20:26:51 UTC+3, [799] wrote:
> > > > Hello,
> > > >
I had this problem as well. However, the problem vanished when I adjusted the
qrexec_timeout setting to 120 via qvm-prefs for the desired VMs.
This kind of makes sense, since I'm doing my RC2 testing from a usb stick
(color me cautious).
--
You received this message because you are
On Wednesday, October 25, 2017 at 11:26:51 AM UTC-6, [799] wrote:
> Hello,
>
> As at least one other Qubes user has the same problem, that VMs won't start,
> I'll add this as special topic.
>
> I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot
> the VMs.
> This
Not working
Found that with debug it’s starting but then the appvm not...
--
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
On Tuesday, October 31, 2017 at 1:56:46 PM UTC+1, Roy Bernat wrote:
> On Tuesday, 31 October 2017 14:52:10 UTC+2, Roy Bernat wrote:
> > On Wednesday, 25 October 2017 20:26:51 UTC+3, [799] wrote:
> > > Hello,
> > >
> > > As at least one other Qubes user has the same problem, that VMs won't
> >
On Tuesday, 31 October 2017 14:56:46 UTC+2, Roy Bernat wrote:
> On Tuesday, 31 October 2017 14:52:10 UTC+2, Roy Bernat wrote:
> > On Wednesday, 25 October 2017 20:26:51 UTC+3, [799] wrote:
> > > Hello,
> > >
> > > As at least one other Qubes user has the same problem, that VMs won't
> > >
On Tuesday, 31 October 2017 14:52:10 UTC+2, Roy Bernat wrote:
> On Wednesday, 25 October 2017 20:26:51 UTC+3, [799] wrote:
> > Hello,
> >
> > As at least one other Qubes user has the same problem, that VMs won't
> > start, I'll add this as special topic.
> >
> > I've made a clean install of
On Wednesday, 25 October 2017 20:26:51 UTC+3, [799] wrote:
> Hello,
>
> As at least one other Qubes user has the same problem, that VMs won't start,
> I'll add this as special topic.
>
> I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot
> the VMs.
> This includes
On 10/31/17 05:21, RSS wrote:
I see I am not alone here.
Having the information on which laptops Qubes 4 "should" run or even
more where it is running (Dev Users?) would help. The HCL
https://www.qubes-os.org/hcl/ does not help me, as it has no
information if 4.x is ok for the X230.
It looks
I see I am not alone here.
> Having the information on which laptops Qubes 4 "should" run or even
> more where it is running (Dev Users?) would help. The HCL
> https://www.qubes-os.org/hcl/ does not help me, as it has no
> information if 4.x is ok for the X230.
It looks to me like a bigger
On 10/30/17 16:29, Roy Bernat wrote:
On Wednesday, 25 October 2017 13:26:51 UTC-4, [799] wrote:
Hello,
As at least one other Qubes user has the same problem, that VMs won't start,
I'll add this as special topic.
I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot the
Hello Rob,
>> So what is the solution ? Every reboot I am
>> struggle to Start the vm’s
As I haven't seen any good solution for this yet, I recommend going back to
Qubes 3.2 until 4.0 has been updated to fix this or until we know what is
causing the problems (hardware?).
[799]
--
You
And now the sys firewall don’t start anymore . Someone
Hel
--
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.
So what is the solution ? Every reboot I am struggle to
Start the vm’s
--
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
On Wednesday, October 25, 2017 at 10:26:51 AM UTC-7, [799] wrote:
> Hello,
>
> As at least one other Qubes user has the same problem, that VMs won't start,
> I'll add this as special topic.
>
> I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot
> the VMs.
> This
i think you are not alone having this problem why not post the problem here
https://github.com/QubesOS/qubes-issues/issues?utf8=%E2%9C%93=is%3Aopen%20no%3Amilestone%20
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this
On the move. Sorry if I'm terse.
On 26 Oct 2017, at 07:11, Sean Hunter wrote:
>
> One thing is that during the install it gave the attached message about ioMMU
> so perhaps something related to that has changed? I’m going to look at that
> next.
>
> It all worked on
On Wednesday, October 25, 2017 at 1:26:51 PM UTC-4, [799] wrote:
> Hello,
>
> As at least one other Qubes user has the same problem, that VMs won't start,
> I'll add this as special topic.
>
> I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot
> the VMs.
> This includes
can you see if this can help :
https://github.com/QubesOS/qubes-issues/issues/3133
--
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
>> I've made a clean install of Qubes 4-rc2
>> but ~70% of the time I can't boot the VMs
After 2h troubleshooting I deleted my whole setup and reinstalled, again
running into problems when trying to create new VMs.
... Ahrk. I. Hate. Linux. (From time to time).
Seriously, I burned now ~2h
On Wednesday, October 25, 2017 at 5:48:38 PM UTC, Yethal wrote:
> W dniu środa, 25 października 2017 19:26:51 UTC+2 użytkownik [799] napisał:
> > Hello,
> >
> > As at least one other Qubes user has the same problem, that VMs won't
> > start, I'll add this as special topic.
> >
> > I've made a
Hello,
>> Set pci strict reset on sys-net and sys-usb to
>> false and try again. If that doesn't help set
>> virt_mode to pv
qvm-prefs -s sys-usb pci_strictreset false
Results in:
qvm-prefs: error: no such property: 'pci_strictreset'
Has the setting be changed in Qubes 4? Same question has
W dniu środa, 25 października 2017 19:26:51 UTC+2 użytkownik [799] napisał:
> Hello,
>
> As at least one other Qubes user has the same problem, that VMs won't start,
> I'll add this as special topic.
>
> I've made a clean install of Qubes 4-rc2 but ~70% of the time I can't boot
> the VMs.
>
Am Montag, 16. Oktober 2017 20:17:02 UTC+2 schrieb Foppe de Haan:
> On Monday, October 16, 2017 at 8:07:37 PM UTC+2, plata...@gmail.com wrote:
> > Dear Qubes Team,
> >
> > in there the next delay or will the 4.0-rc2 be released in the next couple
> > of hours (today)?
> >
> > regards
> >
> >
Fedora works just fine for me as the template for sys-net in 4rc1 here.
As a first step what I would do is if sys-net can get online, set sys-net as
updatevm for dom0, apply all the dom0 updates, then open a terminal in whatever
you’re using as template for sys-net and apply all updates there
Il giorno domenica 22 ottobre 2017 16:29:14 UTC-4, yura...@gmail.com ha scritto:
> On Sunday, October 22, 2017 at 5:27:17 PM UTC, Francesco Rmp wrote:
> > Hello everyone,
> > i've just installed qubes 4.0 RC1 on my ryzen system ( i couldn't get the
> > 3.2 to install because of the kernel
On Sunday, October 22, 2017 at 5:27:17 PM UTC, Francesco Rmp wrote:
> Hello everyone,
> i've just installed qubes 4.0 RC1 on my ryzen system ( i couldn't get the 3.2
> to install because of the kernel compatibility).
>
> The installation went smooth and i can boot fine in the system, but i'm
>
Il giorno domenica 22 ottobre 2017 13:41:33 UTC-4, Foppe de Haan ha scritto:
> On Sunday, October 22, 2017 at 7:27:17 PM UTC+2, Francesco Rmp wrote:
> > Hello everyone,
> > i've just installed qubes 4.0 RC1 on my ryzen system ( i couldn't get the
> > 3.2 to install because of the kernel
On Sunday, October 22, 2017 at 7:27:17 PM UTC+2, Francesco Rmp wrote:
> Hello everyone,
> i've just installed qubes 4.0 RC1 on my ryzen system ( i couldn't get the 3.2
> to install because of the kernel compatibility).
>
> The installation went smooth and i can boot fine in the system, but i'm
Thanks for that, it works great.
Is there someplace where I can read docs specific to qubes 4.0?
--
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
On Monday, October 16, 2017 at 8:07:37 PM UTC+2, plata...@gmail.com wrote:
> Dear Qubes Team,
>
> in there the next delay or will the 4.0-rc2 be released in the next couple of
> hours (today)?
>
> regards
>
> gregor
Delayed one week. Reasons here:
Dear Qubes Team,
in there the next delay or will the 4.0-rc2 be released in the next couple of
hours (today)?
regards
gregor
--
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,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, Sep 14, 2017 at 05:13:27AM -0400, 'Aaron Dough' via qubes-users wrote:
> Original Message
>
> > Subject: [qubes-users] Re: Qubes 4.0 on Tuxedo BU1406
> > Local Time: September 13, 2017 11:53 PM
> >
> Original Message
> Subject: Re: [qubes-users] Re: Qubes 4.0 on Tuxedo BU1406
> Local Time: September 14, 2017 11:13 AM
> UTC Time: September 14, 2017 9:13 AM
> From: aaron_do...@protonmail.ch
> To: qubes-users@googlegroups.com <qubes-u
101 - 200 of 207 matches
Mail list logo