That's odd. It doesn't work for me with templates that I have with non-default
names. That's why I was asking this question.
There's no instructions out there about which qubes packages need updating or
installing, nor are there instructions about how to update the Qubes
repositories.
This
I mainly ask the question because I already had templates that were up-to-date
in terms of software packages, so there's no real reason to be starting over
there.
It would be nicer to be able to update whatever they need for their Qubes
backend and keep the template going.
This is especially
This appears to have been fixed when I changed over the updateProxy value
(which I brought up in another thread). So everything here seems to work now.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop
That did it - thanks!
--
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
Hello,
I'm trying to get a fedora-25 template from Qubes 3.2 updated to Fedora 26 on
Qubes 4.0. This template has a variety of packages already installed and I
thought it would be easier to bring this forward to Fedora 26 rather than
trying to reinstall everything on the default fedora-26
Hello,
I recently migrated from Qubes 3.2 to 4.0 and it appears that the networking
for all the template VMs is shut off by default.
To update the default debian-9 template, I turned networking on and attached it
to sys-firewall. But when I run the template, it appears that I can't connect
Hello,
I'm having a variety of problems trying to get my templates to update. One of
these is that all my templates seem to want to update through sys-whonix. I
run on a lower memory laptop and while I have sys-whonix installed, I don't
want to run it every time I want to run updates.
The
Hi Yuraeitha,
Yes, I have looked to see if PCI reset could be changed. I have had no luck.
I am aware of the security implications of running things in sys-usb. For the
time being I accept the risks, though I will be looking a little closer at the
hardware of my next laptop!
--
You
Hi N,
I did not find a better solution. I run the radio peripheral from sys-usb
directly and moved any software for it to that VM.
Yuraeitha, my USB controller does not support PCI reset, so your ideas do not
help me. If sys-usb goes down the only way to get any USB functionality is to
On Monday, December 4, 2017 at 8:39:48 AM UTC-5, awokd wrote:
> Can't help with that specific issue but as a workaround you can assign one
> of your USB controllers directly to the AppVM. Look under "Finding the
> right USB controller" in here
> https://www.qubes-os.org/doc/assigning-devices/ .
Hello,
I am running Qubes 3.2, with a Fedora 25 sys-usb. I have a HackRF One SDR that
I am trying to attach to an appvm, with no luck.
When I run qvm-usb in dom0 to attach the USB device the command hangs and there
is the following in the appvm's dmesg output:
[ 490.254687] vhci_hcd
Hello,
I am running Qubes 3.2 on a Lenovo Yoga 720. The wireless hardware for this is
Qualcomm Atheros QCA6174. This card has given me a few headaches.
Anytime I go to shutdown sys-net (typically to restart it) I get the following
errors (in dom0) in /var/log/libvirt/libxl/libxl-driver.log:
12 matches
Mail list logo
