sure whether that
> is relevant though.
Both seem unhappy with your video card. What's in that laptop? Please post
Debian's boot log (redact hardware serial numbers & MAC addresses), and
Qubes' xl dmesg log if you can get it.
--
You received this message because you are subscribed to the G
On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote:
> Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev a...@it-minds.dk:
>
>> Den fredag den 19. januar 2018 kl. 14.08.21 UTC+1 skrev Tom Zander:
>>
>>> On Friday, 19 January 2018 11:48:56 CET aaq via qube
Hello,
I want to use fedora-26-minimal based sys-vms and followed the documentation
(https://www.qubes-os.org/doc/templates/fedora-minimal )
I have updated the default fedora-26-minimal template and installed all
packages mentioned in the docs (Qubes 4.0 part of the above documentation link
On Fri, January 19, 2018 2:33 pm, aaq via qubes-users wrote:
> Den fredag den 19. januar 2018 kl. 15.28.27 UTC+1 skrev awokd:
>
>> On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote:
>>
>>> Den fredag den 19. januar 2018 kl. 14.44.26 UTC+1 skrev
>>>
Den fredag den 19. januar 2018 kl. 15.44.35 UTC+1 skrev awokd:
> On Fri, January 19, 2018 2:33 pm, aaq via qubes-users wrote:
> > Den fredag den 19. januar 2018 kl. 15.28.27 UTC+1 skrev awokd:
> >
> >> On Fri, January 19, 2018 1:48 pm, aaq via qubes-users wrote:
>
Den fredag den 19. januar 2018 kl. 15.48.08 UTC+1 skrev a...@it-minds.dk:
> Den fredag den 19. januar 2018 kl. 15.44.35 UTC+1 skrev awokd:
> > On Fri, January 19, 2018 2:33 pm, aaq via qubes-users wrote:
> > > Den fredag den 19. januar 2018 kl. 15.28.27 UTC+1 skrev awokd:
&
On Fri, January 19, 2018 2:53 pm, aaq via qubes-users wrote:
>
> I set the maxmem to 1 (cannot set it to 0) and initial mem to 800.
> sys-net starts now.
Good! In theory it should work too if you leave maxmem at 4000.
> I am updating my system now, hopefully this will disappea
only sys-firewall and sys-net
running:
Test on my Lenovo x230
Intel Core i5-3320M @ 2.60Ghz
16 GB RAM
500 GB SanDisk SSD
Qubes 4.0rc3
Coreboot'able
startup/boot till xterm window = 17sec (normal AppVM)
startup/boot till xterm window = 21sec (Disposable AppVM)
Test on my Lenovo W540
Intel Core
ble to get Network Manager running and instead of using the default
"fat" fedora-templates, I am now running the sys-VMs with fedora-26-minimal
templates.
I was always wondering why Qubes doesn't come with a dedicated sys-template, so
that the sys VMs (sys-net | sys-firewall | sys-usb)
ure out how to get to a command line
> window for dom0. Can someone please tell me, or point to documentation
> which explains? I've done several web searches without finding an answer.
Click the Q button, then Terminal Emulator.
Recommend not trying to upgrade though, rather you "sudo qub
::ShiftAltTab
3) run Autohotkey with the above configuration
I am now able to switch windows back & forward using Alt + Q and Alt + W, which
is good enough.
[799]
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe fro
> I tried to remove the default DVM, but it didn't > work. What do I need to
> do, to get rid of the
> old (Fedora 25 based) DVM which comes with > the default Qubes 4rc3
> isntallation ?
After some trial and error I found out what was causing the problem, deleting
the def
Qubes 4 RC3
So, I updated using current testing yesterday, and there was an update to qubes
core dom0 and other changes..
Network worked fine before I shutdown my machine, but now when I try to start
sys-net I get an error saying "Not enough memory to start domain 'sys-net'"
I
Den fredag den 19. januar 2018 kl. 16.39.31 UTC+1 skrev Marek
Marczykowski-Górecki:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Fri, Jan 19, 2018 at 06:53:55AM -0800, aaq via qubes-users wrote:
> > Den fredag den 19. januar 2018 kl. 15.48.08 UTC+1 skre
y used VMs are hidden and shown only clicking a button. To
> > do that, there should be a flag to differentiate the visibility of VMs.
>
> I made a start with this based on my own usage; See the attached
> screenshots.
> Going from screenshot1 (showing all my qubes) to 5 by removin
pixel fairy wrote:
>> qubes 4.0rc3 Id like to make custom
>> launchers for two purposes [...]
Hello pixel fairy,
My suggestion is: don't spend time playing around tweaking custom . desktop
files.
I have installed menulibre in dom0 and I am now able to tweak my menu through a
com
On Mon, January 22, 2018 4:54 pm, Brian LoBue wrote:
> Error starting VM work: VM root image doesn't exist
> /var/lib/qubes/vm-templates/fedora-23/root.img
> Is there a way to reinstall fedora-23 and get sys-net and my app vms to
> work again?
I'm not aware of a way to re
On Mon, January 22, 2018 5:17 pm, jerr...@disroot.org wrote:
> what is the command to install whonix-ws and anon-whonix? the full
> specific command
"sudo qubes-dom0-update qubes-template-whonix-ws" for the ws template. Not
sure there's a documented process for creating anon-
a quality
See
CONFIG_DRM_I915_ALPHA_SUPPORT
or i915.alpha_support module
parameter
to enable support in this
kernel version, or check for
kernel updates.
This is enabled by default on Qubes 4.0, but I'm not sure if that's the
case for 3.2. That could be
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.
https://github.com/QubesO
so thanks to those contributors as well!
--
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 thi
Den torsdag den 25. januar 2018 kl. 20.17.48 UTC+1 skrev Kevin Martinsen:
> i3 has been working fine for me.
>
> Did you follow the installation instructions on
> https://www.qubes-os.org/doc/i3/? Specifically:
> $ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
rage you to switch completely to Linux!
> I can't see any windows-tools in the repository in Qubes 4, was it
> integrated into Qubes from the beginning, done in a different way, or
> maybe its not been done yet?
There might be a GSoC suggestion to update them but like you found, I
don't think they hav
ed
> in some way.
Add iommu=debug loglvl=all to your Xen boot options, then display the
results with xl dmesg.
--
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
to.
>
>
> First of all I have all the respect in the world for the entire Qubes team,
> and I sincerely believe that you are making the world a better place.
>
>
> The machine: ThinkPad X270 (full specs:
> https://www.uk.insight.com/en-gb/productinfo/portatili-
nd I simply can't understand half of the issues, and the other
> > half I can't seem to find a solution to.
> >
> >
> > First of all I have all the respect in the world for the entire Qubes team,
> > and I sincerely believe that you are making the world a bet
On Sun, January 14, 2018 7:07 pm, 'Emil Novik' via qubes-users wrote:
> I did, no idea why HVM still doesn't work.
>
>
> ---
> Emil Novik
>
>
> Original Message
> On Jan 14, 2018, 19:48, taii...@gmx.com wrote:
>
>
>> On 01/14/2018 06:05
On Fri, January 12, 2018 8:23 am, Wim Vervoorn wrote:
> Hello,
>
>
> Thanks. I tried this. Now I am running into problems with the PCI devices
> I am using. Qubes can't reset those. For some reason they are not
> exposing the FLR capability. I am trying to find out why bec
Den fredag den 12. januar 2018 kl. 12.38.20 UTC+1 skrev awokd:
> On Fri, January 12, 2018 10:12 am, aaq via qubes-users wrote:
>
> > 6) Resizing a urxvt window in my debian unstable to a certain dimension
> > (or fullscreen hotkey) crashes the terminal. If I have another window
On Fri, January 12, 2018 12:28 pm, aaq via qubes-users wrote:
> Den fredag den 12. januar 2018 kl. 12.38.20 UTC+1 skrev awokd:
>
>> On Fri, January 12, 2018 10:12 am, aaq via qubes-users wrote:
>>
>>
>>> 6) Resizing a urxvt window in my debian unstable to a cer
On Fri, January 12, 2018 4:20 am, Andrew David Wong wrote:
> It shouldn't require much effort. In most cases, all you have to add
> is `## Qubes 3.2` above the existing documentation, shift the rest of the
> headers down one by adding a `#` in front of each one, then add `## Qubes
>
all. That's a huge speed
> improvement over sys-whonix.
>
> Now I'm wondering if my failure to set firewall rules was the reason I
> couldn't use your earlier IPtables examples. I might revisit that, but for
> now this solution allows me to use Qubes somewhat normally behind this
> corporate
On Fri, January 12, 2018 10:12 am, aaq via qubes-users wrote:
> 6) Resizing a urxvt window in my debian unstable to a certain dimension
> (or fullscreen hotkey) crashes the terminal. If I have another window
> running the VM, and that window already 'broke' the dimensions in
&
On Fri, January 12, 2018 6:48 am, ThierryIT wrote:
> Hello,
>
>
> I have a laptop with two internal Hard Drives.
> One HD with Windows 7 the second Hard Drive with Qubes on it.
> Is it possible to run Windows 7 from a VM's Qubes instead of building a
> Win dows's VM ?
You mi
e 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 qubes-users@googlegroups.com.
To view this discussion on the
quot;ucode=scan" addition to the bootloader; yes,
you'd enter those from dom0.
> As a side-note, spectre does compromise the entire qubes architecture. I
> know, nobody was thinking about these things, so no shame in that. But
> one of the main premises in qubes is that VMs are isolated
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 discussion over there?
Move to qubes-devel? Keep here?
2. The command line tools in particular
On Thu, January 25, 2018 10:51 pm, yreb...@riseup.net wrote:
> *by this if I ran sudo qubes-dom0-update
> --enablerepo=qubes-dom0-security-testing*once, I take it , that
> I am still on the Stable Track "repo" so somehow magically I
> have the current
3)
> after doing the 1x securitytesting repo update, how do I check which Xen
> package is now installed?
In dom0, "dnf list installed".
> and/or how do I bring up the GUI
> update manager when it doesn't actually need to update it doesn't persist
No GUI, but in dom0 y
On Wed, January 24, 2018 7:42 pm, Krišjānis Gross wrote:
> On Tuesday, 23 January 2018 19:36:00 UTC+2, Krišjānis Gross wrote:
>> -> Verifying signatures...
>> Filename:
>> /home/krish/qubes-builder/cache/fc25/base_rpms/acl-2.2.52-13.fc25.x86_6
>> 4.rpm is not signe
t;. Review and redact any sensitive
information (serial numbers, usernames, etc.) then reply here with it
attached.
--
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, sen
ree up space. It's pretty easy to end up with a non-booting system if
there are other OSes on the same drive, so use caution if that's the case
(don't think it is in yours).
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To uns
(from fedora to debian template) if I need to do
>> it ?
>>
>> Thx
Look in VM Settings for sys-usb.
--
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
u 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 qubes-users@googlegroups.com.
On Thu, January 25, 2018 9:10 am, darkla...@gmail.com wrote:
> Hi,
> as per title, when trying to install on a laptop (with new partitions
> automatically created by the installer) I get this error. I've seen
> another person with the same problem but he was upgrading qubes, q
to do somethings
like qvm-run firefox, my CPU responds.
Just a peculiar issue, but makes i3 unusable for me nonetheless..
Any feedback appreciated :)
Cheers!
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from
Den torsdag den 25. januar 2018 kl. 14.40.14 UTC+1 skrev WolfSkin:
> On Thursday, 25 January 2018 13:36:18 UTC, WolfSkin wrote:
> > Basically my issue is that I am getting a kernel panic when I try
> > installing qubes-os on my laptop both in UEFI and legacy mode.
> >
> From Dom0 I am able to have access to all my Window 7 files.
>
>
> Any ideas ?
>
>
> Thx
>
>
> Le vendredi 12 janvier 2018 13:59:56 UTC+2, awokd a écrit :
>
>> On Fri, January 12, 2018 6:48 am, ThierryIT wrote:
>>
>>> Hello,
>>>
>>
On Thu, January 11, 2018 9:03 pm, pa...@kc.pl wrote:
> On Thursday, 11 January 2018 21:58:32 UTC+1, awokd wrote:
>
>
>> You can run qvm-backup from the command line. I thought there was a way
>> to start the GUI one too but am not finding it.
>
> I have no qvm* command
Thats ofcourse an option to, all ideas and input are welcome.
Also cooloutac, believe me, I will make sure to put some big warning at the
beginning to advise against this, and inform them of the dangers.
--
You received this message because you are subscribed to the Google Groups
"qubes-
On Thu, January 11, 2018 8:49 pm, Pawel G wrote:
> On Thursday, 11 January 2018 21:12:22 UTC+1, awokd wrote:
>
>
>> If you back up the VMs first, you can reinstall then restore the VMs.
>> In
>> 3.2, go to Qubes VM Manager, then System menu, and choose Ba
On Thu, January 11, 2018 7:37 pm, Pawel G wrote:
> I upgraded dom0 (following "Installing and using Windows-based AppVMs"
> doc):
>
>
> sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing
> qubes-windows-tools
>
> and not long after that I upgraded
Andrew David Wong wrote:
> Specifically, it will not duplicate functionality
> that is already provided by the new 4.0
> widgets. Specific examples include attaching
> and detaching block devices, attaching and
> detaching the microphone, and VM CPU
> usage.
Great news that
> Thx
>>>
>>>
>>>
>>> Le vendredi 12 janvier 2018 13:59:56 UTC+2, awokd a écrit :
>>>
>>>
>>>> On Fri, January 12, 2018 6:48 am, ThierryIT wrote:
>>>>
>>>>
>>>>> Hello,
>>>>>
&
Great! Would you consider including instructions on how to multiboot
between Qubes OS 3.2 (main system) and Qubes OS 4 (test/future system)?
I'd love to test and play with 4RCx but need to have a stable
environment for work (3.2).
I can see where your coming from, but I dont know if it would
On Tue, January 30, 2018 1:23 pm, pascal.mignot.u...@gmail.com wrote:
> I've tried to install Qubes v4.0-RC3 on an HP ProBook 650 laptop.
>
>
> The installation interface prevent me to proceed, saying that my hardware
> is not compatible with Qubes v4.0.
> So my question i
On Tue, January 30, 2018 5:14 am, freddycribb...@gmail.com wrote:
> I have installed Qubes OS 3.2 to a secondary SSD in an attempt at
> The UEFI entry is successfully created by the installer, but upon
Dual booting Qubes isn't really recommended. Better to have a separate
physical m
On Mon, January 29, 2018 10:53 pm, ludwig jaffe wrote:
> Yes, I want to repair my qubes-vm-manager.
Did you In Qubes Manager, go to the View menu and click Show/Hide Inactive
VMs?
> made a back-up and I want to modify config files by hand so the tools do
> what they should do. So I n
On Mon, January 29, 2018 10:25 pm, ludwig jaffe wrote:
> On Monday, January 29, 2018 at 9:14:38 AM UTC-5, Yuraeitha wrote:
>
>> On Monday, January 29, 2018 at 1:06:13 PM UTC+1, ludwig jaffe wrote:
>>> The Qubes-VM-Manager only shows running VMs and not all the VMs that
&g
On Thu, February 1, 2018 8:58 am, ThierryIT wrote:
> If I did understood well, when using Qubes 4.0r3, there is no sys-usb ...
If you chose not to set one up on install there wouldn't be, but usually
you should unless using a usb keyboard maybe. You can still add one now;
check the d
On Thu, February 1, 2018 10:21 am, Willem D wrote:
> I found the report on Github:
> https://github.com/QubesOS/qubes-issues/issues/2838 which describes the
> same issue as I have. I would like to debug the problem, but I require
> assistance with that.
To workaround the proble
On Thu, February 1, 2018 6:47 am, evo wrote:
> Hi all!
>
>
> I have sometimes big problem with Qubes 3.2.
> Just now, by writing an email... suddenly my laptop rebooted. Without
> any errors. Blackscreen and reboot.
>
> This was the second time, but after rather large
On Thu, February 1, 2018 9:54 am, pixel fairy wrote:
> noscript, the firefox extention, pops up the following about the qubes
> site,
>
> NoScript detected a potential Cross-Site Scripting attack
>
>
> from [...] to https://www.qubes-os.org.
>
> Suspicious data:
&g
On Fri, February 2, 2018 6:03 am, ThierryIT wrote:
>
> I have installed "qubes-usb-proxy" on my StandaloneVM.
> -> qvm-usb l : sys-usb:4-2 Yubico_Yubikey_4_U2F+CCID
>
>
> -> qvm-device usb attach vm-name sys-usb:4-2 : Device attach failed: No
> device in
On Fri, February 2, 2018 9:24 am, yreb...@riseup.net wrote:
> so, I created an win7 HVM ; and I think installed windows tools, but when
> I read through the qubes docs, the instructions seem to be
> circular.
> I guess the benefit of the AppVM over the HVM is Qubes integratio
ure "Reconnecting VMs after a NetVM reboot" on
https://www.qubes-os.org/doc/firewall/ to reconnect it. Have not
thoroughly tested.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receivin
.2'
You need to use "4-2", not "4.2".
>> And it is not possible for me to un-attached the key through this
>> widget ...
I noticed that too. Might be
https://github.com/QubesOS/qubes-issues/issues/3215.
--
You received this message because you are subscribed to the Google Groups
&q
On Sat, January 27, 2018 11:46 am, code9n wrote:
> Running the WhonixCheck from the default anon-whonix app vm in the Qubes
> manager list; the fail warning basically says:
>
> SocksPort test [fails]. ... (curl exit code: [7] - [failed to connect to
> host])
>
> The browser
On Sat, January 27, 2018 3:00 pm, beso wrote:
> On Saturday, January 27, 2018 at 4:33:47 PM UTC+2, awokd wrote:
>
>> On Sat, January 27, 2018 2:20 pm, beso wrote:
>>
>>
>>>> On Sat, January 27, 2018 6:31 am, beso wrote:
>>>>
>>>>
>
On Sat, January 27, 2018 2:20 pm, beso wrote:
>> On Sat, January 27, 2018 6:31 am, beso wrote:
>>
>>> ERROR: Device attach failed: /usr/lib/qubes/usb-import: 37: [:
>>> Illegal
>>> number: stash: printf: I/O error.
>>> How to solve this pr
Hello,
ThierryIT wrote:
> Hi, Not possible anymore to hide "un-running
> VMs" ?
Ist Qubes Manager already available in 4rc3?
I haven't read anything and thought that it will come with Qubes 4rc4.
[799]
--
You received this message because you are subscribed to the Google Grou
> Now I can not connect the dom0 to a nic.
> Is there a trick to do it?
> booting a rescue linux from a stick would be a way but I first want to try
> using qubes-os and changing a thing in the configs.
4.0? I think the "Qubes way" would be to boot from your install media,
pick Rescue mo
workarounds, fixes: https://github.com/QubesOS/qubes-issues/issues/3486
--
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...@google
I would ask on the Whonix Forum. https://forums.whonix.org/
--
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.co
cause 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 qubes-users@googlegroups.com.
To view this discussion on t
On Sun, January 28, 2018 2:13 am, joeh9...@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) [
On Sun, January 28, 2018 7:46 am, ThierryIT wrote:
>
> I am a bit lost with Qubes 4.0 RC3 ...
> Before moving to 4.0, I have done my VM's backup.
> How to restore them to Qubes 4.0 ?
Please check out https://www.qubes-os.org/doc/upgrade-to-r4.0/. Let me
know if you have any question
On Sun, January 28, 2018 1:58 pm, ThierryIT wrote:
> Hi,
>
>
> I have installed Qubes 4 without any problem.
> I have done the dom0 upgrade.
> I am able to start the system.
>
>
> But I do not have any "Qubes Manager" ...
That might be only available in the
k. What does
"qvm-usb attach vm_name sys-usb:4-2" do?
If it's the same error, did you install qubes-usb-proxy in your templates?
See https://www.qubes-os.org/doc/usb/.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscrib
o is update your whonix-gw and whonix-ws templates as usual.
--
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
On Tue, January 30, 2018 1:51 am, awokd wrote:
> On Tue, January 30, 2018 12:05 am, 'Tom Zander' via qubes-users wrote:
>
>> Is this a known issue?
>>
>>
>>
>> I can start a VM using qvm-start, but when I use qvm-run nothing
>> happens, it hangs forever
On Wed, January 31, 2018 2:39 pm, jaya...@gmail.com wrote:
> What do you mean it is easy to do? Where do you get a compatible wireless
> card, that is definitely supported by Qubes anyway?
>
> I somehow imagined that getting appropriate driver should be simpler :/
It's not necessar
On Sun, February 4, 2018 7:16 am, ThierryIT wrote:
>
> I have check it, but when doing a "dnf list installed "qubes-*" on my
> sys-usb, I can see that qubes-usb-proxy is installed:
> qubes-usb-proxy.noarch 1.0.12-1.fc26 @qubes-vm-r3.2-current Shouldn't
>
On Sun, February 4, 2018 4:00 pm, Yuraeitha wrote:
> On Sunday, February 4, 2018 at 1:10:59 PM UTC+1, Nuno Branco wrote:
> Reply to #3
In addition to what Yuraeitha wrote, check
https://github.com/QubesOS/qubes-issues/issues/3470.
> Reply to #4
qvm-prefs vmname kernel ""
On Sun, February 4, 2018 7:14 pm, 'Tom Zander' via qubes-users wrote:
> The biggest issue i ran into is that Qubes4 is just too immature to
> actually use for more than browsing and email. It was too painful for my
> desktop full-time work machine. I tried for 2 months, my signific
On Sun, February 4, 2018 4:55 pm, Demi Obenour wrote:
>
>
> On 02/04/18 14:15, donoban wrote:
>
>> On 02/04/2018 08:05 PM, demioben...@gmail.com wrote:
>>
>>> My FirewallVM doesn’t seem to be running the Firewall service. How
>>> can I set that up?
>
On Mon, February 5, 2018 4:37 pm, 'Guillaume Bertin' via qubes-users wrote:
> Hi,
>
>
> I don't manage installing hdparm in dom0. No package...
>
>
> Have I missed something? Should harddisk management be done outside of
> dom0?
Usually, for security reasons you should a
On Tue, January 30, 2018 12:05 am, 'Tom Zander' via qubes-users wrote:
> Is this a known issue?
>
>
> I can start a VM using qvm-start, but when I use qvm-run nothing happens,
> it hangs forever. Even commands that don't need a X server. For any qube of
> the various OSs I r
h mode ??
>
>
> What is the pvh mode ?
That's one of the new remediations for Spectre/Meltdown. In order to
attach a PCI device, you have to switch your NetVM back to HVM mode. You
can do that in VM Settings GUI or dom0 command with qvm-prefs.
--
You received this message because you are
Hello Rumsey,
>> I can now send email using emacs/mu4e
>> and Qubes split gpg
I am also interested in this setup. Can you give me some more information what
needs to be done to start from a plain installation?
Something like a copy of the relevant configuration files (s
soon as I can fit it into my work stream. Others already have
and are (happily) running it daily.
--
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 Sat, February 3, 2018 1:37 pm, Shashank wrote:
> Hi I’ve been trying to install qubes 4.0 rc4 in my dell xps15
> But I am not able to get the installation done.
> and the message below goes on repeating Watchdog: BUG: soft lockup - cpu
> stuck for 22s[xorg:1325]
Is it trying t
On Sat, February 3, 2018 2:29 pm, Shashank wrote:
> Here is the full error:
> Starting Installer, one moment
> Anaconda 25.28.9-10 for Qubes R4.0-rc4 started.
> *Installation log files are stored in /temp during the installation
> *shell is available on TTY2
> *If the grap
On Mon, February 5, 2018 5:22 pm, donoban wrote:
>
> On 02/05/2018 06:21 PM, donoban wrote:
>
>> On 02/05/2018 05:37 PM, 'Guillaume Bertin' via qubes-users wrote:
>>
>>> I don't manage installing hdparm in dom0. No package...
>
> Sorry I mean 'sudo qubes-dom
On Mon, February 5, 2018 5:57 pm, 'Tom Zander' via qubes-users wrote:
> On Monday, 5 February 2018 08:00:35 CET 'awokd' via qubes-users wrote:
>
> Release candidates are, like the word describes, not made unless the
> developers are thinking that its ready to release but needs more
On Mon, February 5, 2018 5:43 pm, donoban wrote:
> On 02/05/2018 06:38 PM, 'awokd' via qubes-users wrote:
>
>> On Mon, February 5, 2018 5:22 pm, donoban wrote:
>>> Sorry I mean 'sudo qubes-dom0-update hdparm'
Sure enough, I tried the above on both versions an
e reading and interested) are any good
at C++? Would be nice to get that Coreboot patch re-activated and working
properly. I can usually hack my way around code but that AGESA code base
is beyond my skill-set.
--
You received this message because you are subscribed to the Google Groups
"qube
On Fri, February 9, 2018 10:25 am, Alex Dubois wrote:
> On Friday, 9 February 2018 08:35:17 UTC, awokd wrote:
>
>> On Fri, February 9, 2018 8:25 am, Alex Dubois wrote:
>> Try
>> qvm-prefs win7 kernel ""
>
> @awokd, I've created a pull request to update th
On Fri, February 9, 2018 8:11 am, Johannes Graumann wrote:
> and fail to understand/find where that particular property is set,
> respectively may be changed ...
Check qubes-prefs too.
--
You received this message because you are subscribed to the Google Groups
"qubes-u
On Fri, February 9, 2018 8:25 am, Alex Dubois wrote:
Try
qvm-prefs win7 kernel ""
--
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
801 - 900 of 4380 matches
Mail list logo