seshu wrote on 12/16/18 5:01 PM:
Hi, I'm a Qubes newbie but coming along really well. I'm using 4.0.1 rc-1.
I had a question about what the process is to add new storage drives (ssd or
hdd). Looking through the documentation I can see there are several docs that
help but raised other
dimi wrote on 12/17/18 7:03 AM:
On Sunday, December 16, 2018 at 11:32:57 PM UTC+2, awokd wrote:
dimi wrote on 12/13/18 2:10 PM:
Having fun with qubes r4 but can't help myself with this problem.
sudo lvs, shows me a bunch of deleted VM's that 'seem' to eat up my disk space.
1) Mostly used
'Udjat' via qubes-users wrote on 12/6/18 2:22 PM:
Hi, Folk's,
the boot process in Release 3.2 crashes always during VM sys-usb start up.
The error message : ... Illegal opcode ...
Exists a way to disable the start of sys-usb for the boot ?
For example are there some kernel parameters
haaber wrote on 12/12/18 1:02 PM:
This happens when I connect my mobile via usb. I have qubes-input-proxy
installed on sys-usb and untreusted (say), and I can mount other usb
devices (my backup HD for example). Did you encouter this problem
already? Thank you for hints. Bernhard
Yes, some
by the sys-net VM
froze Qubes. Thereafter, Qubes would always freeze on startup before I could
login. I had to recover the install by booting from a USB key, mounting the
disk and editing qubes.xml to remove the offending device.
Has anyone experienced a similar issue or has, on the contrary
help/guidance?
at the moment - to my understanding, the method of notifying qubes about vms on a drive is
via qubes.xml - so i'm manually copying the .. sections once
i've connected the drive. extra fun is then each computer has different vm-ids so i'm
having to manually craft the id to suit/fit
dimi wrote on 12/13/18 2:10 PM:
Having fun with qubes r4 but can't help myself with this problem.
sudo lvs, shows me a bunch of deleted VM's that 'seem' to eat up my disk space.
1) Mostly used Qubes Manager to delete them. How do you delete appVM's /
TemplateVM's the right way so
Franz wrote on 12/2/18 8:54 PM:
Suddenly win7 VM stopped starting on Qubes 3.2. Nothing changed except
perhaps the last couple of dom0 updates.
The error message is:
cannot connect to 'win7' qrexec agent for 300 seconds, giving up
I tried debug mode, but it is just the same.
I had
to reboot the whole machine.
I think I saw this a few times on 3.2 and closing and reopening Qubes
Manager worked around it. Don't remember it on 4.0, but try the same.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from
mike wrote on 12/7/18 4:04 PM:
Hi All,
I extended my Qubes partition, but don't know how to extend the LVM pool.
I.e. extended the actual partition, LUKS, LVM PV, LVM VG.
Now, my qubes_dom0 VG is of the new extended size.
How can I make Qubes use the whole VG?
Maybe I'm missing something
taii...@gmx.com wrote on 12/6/18 5:01 PM:
On 12/05/2018 06:19 PM, '我' via qubes-users wrote:
Hello.
When reading this list I thought G505s A10 is the best laptop for Qubes.
So I'd like to purchase it, but I am wondering how many memory to put in.
Could you give me some advice?
2x8GB DDR3
onfigure AEM without success. However, I've never seen this output
earlier.
Thanks in advance for your kind attention.
--
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
is not an
option for them.
Short answer:
Qubes OS is not an option for them.
The risk part would come only after this feature exists in practice ;)
Search back for the details.
What Zrubi said, really. Not a practical solution at this point. If at
some point it works better, it seems to me too
seshu:
I'm trying to build an Ubuntu templateVM using Qubes Builder. I'm running
4.0.1rc2
When, I ran the 'setup' command I got the following error message:
[user@qubes-builder qubes-builder]$ sudo bash setup
setup: line 16: from: command not found
setup: line 34: syntax error near unexpected
***
>
> Any help appreciated.
> Thank you!
I could not resolve the issue with the answers in this thread, but fedora
mailinglist did help me resolve the issue. The solution provided is provided
here:
https://www.spinics.net/linux/fedora/fedora-users/msg488308.h
tirsdag den 4. december 2018 kl. 23.46.32 UTC+1 skrev Ranguvar:
> On Tue, Dec 4, 2018 at 5:41 PM wrote:
> Hey all!
>
>
>
> Using Qubes 4.0.1-rc1, been updating with qubes-dom0-update --releasever=4.0
>
>
>
> I installed @kde-desktop-qub
onsdag den 5. december 2018 kl. 15.45.33 UTC+1 skrev Ranguvar:
> On Wed, Dec 5, 2018 at 3:56 AM aaq via qubes-users
> wrote:
> tirsdag den 4. december 2018 kl. 23.46.32 UTC+1 skrev Ranguvar:
>
> > On Tue, Dec 4, 2018 at 5:41 PM wrote:
>
> > Hey all!
>
> >
Hello.
When reading this list I thought G505s A10 is the best laptop for Qubes.
So I'd like to purchase it, but I am wondering how many memory to put in.
Could you give me some advice?
--
You received this message because you are subscribed to the Google Groups
"qubes-users&q
ciao
--
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 qubes-users@google
menue loaded on both cards and i could choose the
language, but afterwards i got the message "This hardware lacks features
required by Qubes OS. Missing features: HAP/SLAT/EPT/RVI. Without these
features, Qubes OS will not function normally. " When i reboot the system i
got a [dom0] Err
a terrible time at even getting Jack Audio off of the floor.
System: Base Qubes 4.0 installation, Fedora 28 template, Thinkpad T480 w/32Gb
RAM.
Expected results: Pressing "Start" on the QJackCtl GUI starts the server, per
the online manuals and Fedora's Musician documentation.
Actu
6:54 AM, Ivan Mitev wrote:
> Hi Fabio,
>
> On 11/27/18 2:33 AM, 'Fabio' via qubes-users wrote:
>
> > Thanks for the reply Ivan.
> > I was able to mount `dom0:/dev/qubes_dom0/vm-...-private vmname`
> > successfully, however when trying to mount
> > `dom0:/d
arly shows that it is.
In fact rpm says that the older kernel 4.14.74-1 is *not* installed. If
so, then how is this template even running? I'm using it daily!
I know dnf can block a package from upgrading, but that is clearly not
what is happening here. The packages do update but apparently Qube
wrote:
Awesome, thanks for the response. This worked!
Thanks again!
On Tue, Nov 20, 2018, 11:51 PM 799 wrote:
Hello Pieter,
Am Di., 20. Nov. 2018, 20:20 hat pieter lems
geschrieben:
[...]
I was wondering how i can make it so that when qubes is starting i see
the boot information (the output
Gottfried F. Zojer wrote on 11/18/18 12:18 AM:
Hello to everyone,
Myself I am new to Qubes after reading about it in Linux-Magazine December
2018 edition
Just curios if somebody is using it on a AMD Ryzen system
Try to evaluate it if it can be used for memory forensics and in
combination
Koma Kurt wrote on 11/20/18 7:23 PM:
Hi there, they told me to send my question to this mailing list ..hope you can
help me guys;-)
Hi there im new to Qubes OS and i want to install it on external ssd...
rEFInd 0.11.4 is already installed and macOS is updated to macOS 10.14 Mojave.
Wanna
'qubesusermarco' via qubes-users wrote on 11/21/18 4:47 PM:
I have a Windows-7-VM assigned as some LinuxVM's netVM. And I get the error
below after some timeout when I try to start the appvm:
ERROR: Start failed: internal error: libxenlight failed to create new domain
'appVM_name'. See /var
. "sudo xl console "
might be what you're after.
--
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
those
manually before booting from the ISO.
Desktop PC. No TPM installed.
--
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
or I'm missing
something?
--
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 emai
mandag den 19. november 2018 kl. 16.55.42 UTC+1 skrev 22...@tutamail.com:
> I recreated a new Appvm for my templates to use for updates. I currently use
> sys-whonix...the new template is sys-whonix-New.
>
>
> How would I do this?
Hey there!
I am not currently on my Qubes box,
message when trying to mount any
`--root` suffixed volume nested under `/dev/qubes_dom0`.
To confirm, I am running Qubes v4.0.
Any reason why the `--root` volumes in particular aren't mounting? Those are
where `/etc/fstab` would be located, right?
Thanks again for your help!
Fabio
e-to-incorrect-fstab
Hello!
Please this issue:
https://groups.google.com/forum/#!topic/qubes-users/rWRNIt0NOc4
Hope this helps :)
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails
YOUR_FAULTY_TEMPLATE
Related issue:
https://unix.stackexchange.com/questions/44027/how-to-fix-boot-failure-due-to-incorrect-fstab
--
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
. And Tor doesn't support UDP.
>
> https://www.whonix.org/wiki/Tor#UDP
Ping is ICMP, not UDP.
https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from thi
søndag den 18. november 2018 kl. 17.00.19 UTC+1 skrev Campbell:
> On install I chose UK English with US Keyboard. For some reason upon
> installation Qubes set my laptop keyboard to UK, even though I chose US
> keyboard during installation.
>
> My guess is that when Qubes set
tures import cancelledError
ImportError: No module named concurrent.futures
...
A little back ground on my Qubes...I started using Qubes out of an immediate
need for security and have been backing in to how to use it over the last few
years. I consider myself pretty good but I am still missing what ap
probably be the easiest fix, but you are
bypassing Qubes' networking security.
Otherwise, you're on the right track with the Qubes firewall document
you referenced. You could write rules so the source permits an entire
subnet, not just a single IP. Iptables/NFT rules aren't very
straight-forward
remresalexan...@gmail.com wrote on 1/8/19 5:35 PM:
No Vm is starting, onboard NIC doesnt works and the Startup says failed to load
Kernel Modules
Im booting from Legacy mode
You can see your libxl-driver.log by going to Qubes menu/Terminal
Emulator (dom0) and then typing "sudo cat
/va
to create a
Standalone VM and install everything in there, instead of templates &
AppVMs.
--
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+unsu
seshu wrote on 1/7/19 10:38 PM:
I think I screwed something up :) as I was trying to reinstall the
xorg-x11-nouveau driver.
When I rebooted, the qubes manager doesn't work, my usb mouse doesn't work and
when I try to reinstall packages with qubes-dom0-update I get an error message
saying
troduced via a
dom0 update.
Maybe opening "Qubes Global Settings" and clicking on "Disable checking for
updates for all Qubes" might be a temporary fix?
- O
22rip, where did you see that Update icon always used sys-net? Doesn't
seem like it should, if your other settings point
.
There is multiple addresses that are being listed in ifconfig on sys-whonix,
and windows. Also the qubes settings lists another set of addresses.
Could I addressing the IPv4 wrong? My knowledge is limited sorry hopefully
someone could point me the right direction.
Check the Networking section of your anon
me a "nothing to
do" with out ever starting sys-whonix (I don't start this VM with start-ups of Qubes)
2) I played with the sun icon again after the Dom0 update today and noticed that it just clocked
after starting sys-whonix. When I update using the Qubes Manager I start my sys-whonix manua
unman wrote on 1/7/19 11:31 PM:
On Tue, Jan 08, 2019 at 12:03:46AM +0100, Achim Patzner wrote:
Hi!
Would someone please update https://www.qubes-os.org/doc/bind-dirs/ and
add that in 4.0 and on /usr/lib/qubes/bind-dirs.sh has moved to
/usr/lib/qubes/init?
Achim
It is, of course, still
insight!
--
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 qubes-users@google
cyber.citi...@tutanota.com:
Hello everyone,
I'd like to install Qubes 4.0.1 on a g505s, but the installation routine is
telling me that IOMMU/Vt-d/AMD-Vi, and Interrupt Remapping are not available.
I've tried every possible combination of BIOS settings I can imagine (such as
enabling SVM
lctl after plugging one in?
--
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
Max
--
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 qubes-users@google
gone wrote on 1/12/19 5:03 PM:
On 1/12/19 1:44 AM, 'awokd' via qubes-users wrote:
gone wrote on 1/11/19 9:01 PM:
Hello,
I've tried to use different USB to Ethernet adapters with QubesOS but
without success. Is there a chance to make them usable?
I've seen some have been successful. Where
] ? do_early_param+0x16e/0x16e
[3.682851] kernel_init_freeable+0x2e8/0x32d
[3.683270] ? rest_init+0xb0/0xb0
[3.683685] kernel_init+0xa/0x101
[3.684101] ret_from_fork+0x35/0x40
[3.684536] Kernel Offset: disabled.
So, I booted into recovery mode prompt from a USB key (Troubleshooting and
Rescue a Qubes system
mode prompt from a USB key (Troubleshooting and
Rescue a Qubes system (read-write choice).
It seems that I can’t boot an older kernel version.
# ls /boot
initramfs-vmlinuz-4.14.74-1.pvops.qubes.x86_64
#
I don't really know what to do to fix it.
Your help will be greatly appreciated!
Thank you
Patrick wrote on 1/12/19 7:22 PM:
Hi, on my laptop qubes this doesn't show any usb devices, and an external
keyboard using USB doesn't work. What can I check and do? I compare my settings
to my other machine running 4.0 and they look the same, and do see USB.
One difference - I do not see
i or lspci
will list devices you can assign. Read further in there how to determine
to which one your keyboard's connected.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails fr
the error "failed to
install boot loader. To you want to continue? It will not be bootable..." or something to that effect.
I indicated "yes" just to see what would happen, and it completed.
On reboot, neither Qubes nor KDE neon would come up, no grub menu came up, and
no
device I could find. It
generated a different GUI error during the Post installation qubes
configuration screen, with everything disabled and disconnected:
['/usr/bin/qvm-start', 'sys-firewall'] failed:
stdout: ""
stderr: "PCI device dom0:00_14.3 does not exist"
Once logged i
Hello everybody!
Set up qubes on external hard drive to boot upon launch. Downloaded latest
version from [https://www.qubes-os.org](https://www.qubes-os.org/)
Installer loads fine, proceeds with install, but then I get these errors:
[ 215.94. ] dracut-initqueue[649]: Warning: dracut
799 wrote on 1/13/19 7:11 PM:
Hello,
after I had some problems rebuilding my fedora-28 based templates with
fedora-29, I re-installed the template using:
sudo qubes-dom0-update --action=reinstall qubes-fedora-29-minimal
while the installation worked and I can start and qvm-shutdown the new
hat
device is :00:14.0. Then in sys-net's Qube Settings/Devices tab, use
the "Configure strict reset" button to disable the requirement for that
device.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe f
the initial setup, partitions the drive, etc and
reboots. After first reboot, when selecting which qubes to configure, the
system starts to configure all the Qubes.
It is upon completion of this step, just before the system switches to the
login screen, that the error message pops up:
/usr/bin
ultimatev...@gmail.com:
Qubes OS version:
R4.0
Affected component(s):
Intel Wireless N 1000
Steps to reproduce the behavior:
I installed QubesOS R4.0 and made it to the installation configuration page
(where the system finishes installing, reboots, and then you are prompted with
the config
On Wed, September 12, 2018 8:39 pm, Chris Laprise wrote:
> Another alternative would be to configure a single sys-net with either
> dispVM or Qubes-VM-hardening so that neither passwords nor malware would be
> retained when sys-net is restarted.
Was going to suggest a dispVM as well,
, September 15, 2018 5:17 PM, wrote:
> On Saturday, September 15, 2018 at 8:32:23 AM UTC-7, casiu wrote:
>
> > Sent with ProtonMail Secure Email.
> > ‐‐‐ Original Message ‐‐‐
> > On Saturday, September 15, 2018 10:30 AM, qubes-...@tutanota.com wrote:
>
posts/purism-librem-laptops-completely-disable-intel-management-engine/
>
> Talking about alternatives: how the Qubes 4.0 stand with RYF certified X200?
> Like for example this one:https://tehnoetic.com/laptops/tet-x200s
> https://tehnoetic.com/laptops/tet-x200s and others li
On Sat, September 15, 2018 10:30 am, qubes-...@tutanota.com wrote:
> Hi, during my email conversation with the Todd Weaver in the
> pre-IME-disabled time, he told me they will fully disable the IME and AMT
> within next week. After about a week they announced they did just that.
> Ar
On Sat, September 15, 2018 3:21 am, Wolf moon wrote:
> Hi guys New to Qubes ( which is an amazing feat of cyber security
> engineering ) all working fine and learning my way around it.
>
> My only issue is logging into my vpn service.
>
>
> I have followed the Qubes instructio
On Sat, September 15, 2018 5:18 pm, Djon Snow wrote:
> The time in the cube 4.0 rushes for 10 minutes. What is the reason for
> this?
Your hardware clock might be off. Check/set with "sudo hwclock" in dom0.
--
You received this message because you are subscribed to the Googl
On Sat, September 15, 2018 6:28 pm, qubenix wrote:
> Hello all.
>
>
> I'm attempting to build a custom Qubes with one patch added to Xen. Is
> it enough to simply add the patch with the others in
> qubes-builder/qubes-src/vmm-xen/, add a line for it in
> qubes-builder/qubes-sr
Heya mate are you still selling stickers? I'd love to buy one.
--
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
u can see where the Qubes OS daemon fails. It is immediately preceded
> by the 1d.2 pci device worker failing, suggesting that something about
> this failure is causing the daemon from starting (which occurs below the
> blank line I added to the log). 1d.2 is a PCI Bridge, Intel Corp Devi
On Fri, September 14, 2018 3:36 am, Stuart Perkins wrote:
> I deleted the whonix vms and went to install whonix-14 and it won't work.
> The salt command continues to say that the community repo is unknown.
> What am I missing?
Did you "Sometimes the Qubes Community Templates reposi
ock. It gets quite difficult to
>>> find windows after a bunch have been opened without icons to clue me
>>> in. Not sure what's causing this problem because evidently the
>>> .desktop files work fine for the launcher and Whiskers.
>>>
>>>
>&
qubes-...@tutanota.com:
> hi, after the last update of the whonix-ws-14 template with recommended
> apt-get autoremove, the template got broken.
> - Most of the apps disappeared
> - torbrowser doesnt connect to net
> - template itself cant be updated.
>
> user@host:~
taii...@gmx.com:
> On 09/16/2018 02:51 AM, 'awokd' via qubes-users wrote:
>> At present, RYF has not certified any laptops with hardware capable of
>> running Qubes 4.0, but there are a couple older AMDs that can. A scale of
>> hardware openness/owner control fro
qubes-...@tutanota.com:
> Looks like it is a bit of a blind way. To use the reasonably secure OS
> without possibility to use it on the reasonably secure HW, is an issue which
> needs to be addressed a bit. I originally guessed that Qubes would run on the
> RYF devices well, an
tab. If it still doesn't work, see
https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues.
--
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
t
Wolf moon:
> Guys I was told the fedora 26 that came with my latest version of qubes 4.0
> is out of date so after a google search I found kushal das's page telling me
> to open up dom 0 and enter sudo qubes-dom0-update qubes-template-fedora-28
>
> https://kushaldas.in/posts/fed
Hi there,
I have started using qubes 4.0 only recently and I ran into an issue I can't
seem to find a solution for.
I need to setup a PenTest Lab and I have already installed Kali and Win7 with
no issues. However, I am unable to install WinXP and I get the following error:
I tried 2 different
how to enable debug mode, and I don't see anything in
>>>> the official documentation. I'm also not familiar with the console,
>>>> unless you're referring to a dom0 terminal. Any guidance would be
>>>> wonderful. Thanks.
>>>>
>>>>
>>>>
istent --option permissive=true --option
> no-strict-reset=true sys-net dom0:00_1f.6
>
> So, it took me only about 55 hours of tearing my hair out to get Qubes
> running on my computer. Admittedly, I'm not an IT professional, but I
> know a fair amount about linux systems, which
On Tue, September 11, 2018 7:10 pm, Guy Frank wrote:
> On Tuesday, September 11, 2018 at 1:44:13 PM UTC-5, Guy Frank wrote:
>
>> Was a bit premature thinking that my qubes installation was stable.
>> About half the time I start the system, it locks up and I am only able
>&g
On Tue, September 11, 2018 7:05 pm, mmeli via qubes-users wrote:
> Hi there,
>
>
> I have started using qubes 4.0 only recently and I ran into an issue I
> can't seem to find a solution for.
>
> I need to setup a PenTest Lab and I have already installed Kali and Win7
> wi
Stuart Perkins:
>
>
> On Sun, 16 Sep 2018 23:47:08 -0700 (PDT)
> Hugo Costa wrote:
>
>> Hey,
>>
>> I couldn't find the answer to this problem that has been annoying me for a
>> while. Basically, Qubes 4.0, fedora 28 and PVH qubes.
>> Problem is si
ptitv...@gmail.com:
> Thank you.
> After using Qubes for other things, I've seen that the time in dom0 was
> corrected automatically.
> So by going back to Fedora 26 in sys-net solved my problem.
> Maybe I should open an issue ticket.
>
> Nevertheless I will check it
is 4.4.14-11
> But if i execute ‘sudo qubes-dom0-update qubes-kernel-vm-support
> kernel-devel’ I get a different version (4.14.67-1) of kernel headers
> installed in dom0. How can I force the dom0 to install the kernel headers
> for version 4.4.14-11?
Have you ran just "sudo qube
qubesuserma...@gmail.com:
The most promising result is given by xenpm, however only info of 2 cores out
of 4 are listed.
I think xenpm is supposed to work the best. Qubes disables SMT for
security, so if you only have 2 real cores that's all you'll see.
--
You received this message because
jeppewr...@gmail.com:
Hi all,
I'm quite new to Qubes and Linux in general yet I have manged to run Qubes OS
as my main desktop for several weeks. At the moment I'm fiddling with
networking, more specifically I'm trying to get whonix-14 working, as Qubes
comes with an outdated version
to
get rid of the old volumes listed with lvs, my assumption being Qubes
will realize they are gone and handle the entries in /dev/qubes_dom0
appropriately. Haven't encountered this problem before.
3) Also lvremove.
1) Yes, VM's are shutdown before removing. I am double, tripple checking before
any
jeppewr...@gmail.com:
onsdag den 19. december 2018 kl. 06.05.57 UTC+1 skrev awokd:
jeppewr...@gmail.com:
Hi all,
I'm quite new to Qubes and Linux in general yet I have manged to run Qubes OS
as my main desktop for several weeks. At the moment I'm fiddling with
networking, more
at
https://www.qubes-os.org/doc/windows-vm/#qubes-40---windows-vm-installation
exactly? If so, where does it break? Do not attempt to pass anything
through until you've completed all the steps.
I got a Windows 7 HVM to work all the way to the desktop, but I did not install
QWT on it just yet
Claudio Chinicz:
Hi Folks,
I'm willing to use my Qubes notebook as my main notebook in a corporate
environment. One of the things I use daily is an external keyboard,
which cannot be hooked to my Linux Mint 19.1 Cinnamon 64 bits HVM
because qurexec is not present.
Anyone has done it before
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 web vi
> unattended anyway.
> In contrast your colleague sitting next to you at work can plug in a USB
> stick into your laptop and perform the thunderbolt attack whilst you're
> at lunch.
> Having someone physically take away your laptop or even dismantle it is
> a lot more suspici
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 web visit
https://groups.go
/EFI/qubes.
There is no such path, the closest I'm aware of is EFI/BOOT, which contains
BOOTX64.cfg, which I already modified with nouveau.modeset=0 on each option to
no avail. To my understanding this is the conf that should apply since this is
the EFI boot folder, so I don't think that setting
Hi,
I'd appreciate it if someone can help me debug an issue with the qubes
installer. I am not able to enable legacy booting on my bios, so I am only
booting the installation ISO using UEFI. My hardware is
https://www.gigabyte.com/Mini-PcBarebone/GB-BLCE-4105-rev-10#sp, and it is
running F1
the
package in a qube already internet connected, then qvm-copy it to the
template. That way you can avoid touching the Internet from your template.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
Mike Keehan wrote on 3/24/19 3:36 PM:
On Sun, 24 Mar 2019 02:07:10 -0400
Yushatak wrote:
Machine has no legacy mode.
On Sat, Mar 23, 2019, 11:32 PM Gaijin wrote:
On 2019-03-24 02:41, Yushatak wrote:
On Thursday, March 21, 2019 at 8:57:09 PM UTC-4, Yushatak wrote:
When I boot the Qubes
billol...@gmail.com wrote on 3/24/19 8:48 PM:
I am sure this is a silly issue, but I've been searching in the archives and
can't see the answer.
I have a laptop with 1 SSD and 1 SATA drive. I installed Qubes on the SSD, and
have a couple of data partitions on the SATA drive. I want to make
specifically enabled in the BIOS. However, the Qubes 4 installer
apparently can't see them. (I wonder if this is because I can only boot
the installation USB in Legacy mode and not AHCI mode)
I'm wondering if it would be OK to proceed with the install despite this
warning. Is there a way to check
1701 - 1800 of 4387 matches
Mail list logo
