Periodically all graphics-heavy apps (Firefox, ...) in all VMs seem to
slow down simultaneously. Rebooting fixes the situation. Running `sudo
journalctl -f` in dom0 doesn't show anything unusual. What would you
suggest as a next step towards locating the problem?
--
You received this message
On Thu, Dec 26, 2019 at 11:47:37AM +, 'awokd' via qubes-users wrote:
There's a brief discussion at https://www.qubes-os.org/doc/networking/,
but there may be more detailed notes in the source code for Qubes' VM
networking components. Qubes uses Xen's networking, so that might be the
best
On Thursday, December 26, 2019 at 5:31:50 AM UTC-8, awokd wrote:
> What happens if you use an options line like the following?
>
> options=console=vga loglvl=all efi=no-rs
>
```
(XEN) Platform timer is 23.999MHz HPET
(XEN) [...]
(XEN) CPU0: No irq handler for vector 40 (IRC -2147483648, LAPIC)
On Thu, Dec 26, 2019 at 11:47:37AM +, 'awokd' via qubes-users wrote:
tetrahedra via qubes-users:
I haven't been able to find any documentation for what network
interfaces sys-net is expected to expose internally. If I want to create
my own sys-net from scratch, how does Xen/Qubes send
I'm following https://wiki.ubuntu.com/DebuggingKernelSuspend to debug a
kernel suspend bug on my computer. Since there's no nvme available during
suspend, I must rely on the motherboard clock for logging.
The problem is that when I use the clock for logging, it loses its clock
time and then
I'm following https://wiki.ubuntu.com/DebuggingKernelSuspend to debug
kernel suspend problems. However, on dom0 there's no pm-suspend command.
How can I install SECURELY this command or how to substitute for another
one?
This is the command:
sudo sh -c "sync && echo 1 > /sys/power/pm_trace
Thank you very much for your answers, my replies in bold below.
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Thursday, December 26, 2019 2:03 PM, 'awokd' via qubes-users
qubes-users@googlegroups.com wrote:
> 'Chökie Gyaltsen' via qubes-users:
>
> > On Thursday,
awokd:
Il giorno giovedì 26 dicembre 2019 14:21:38 UTC+1, awokd ha scritto:
>
> Robert M:
> > Claudia,
> >
> > Sorry for the late reply. Here are my answers:
> >
> >- Yes, i modified the BOOTx63.cgf file in ANACONDA.
>
> What were your modifications? Per
>
>
On Thu, Dec 26, 2019 at 03:01:26PM +, lik...@gmx.de wrote:
> dpkg: error processing archive
> /var/cache/apt/archives/kali-themes_2020.1.0_all.deb (--unpac
> k):
> trying to overwrite '/etc/xdg/Trolltech.conf', which is also in package
> qubes-gui-agent 4.0
feels crude but
Hi!
I get the following error while upgrading a kali template which was working for
at least 1 year:
dpkg: error processing archive
/var/cache/apt/archives/kali-themes_2020.1.0_all.deb (--unpac
k):
trying to overwrite '/etc/xdg/Trolltech.conf', which is also in package
qubes-gui-agent 4.0
December 23, 2019 6:09 PM, "hut7no' via qubes-users"
wrote:
I have a setup like this:
AppVM -> FirewallVM -> NetVM -> internet
and want to be able to use UPnP for the AppVM.
Do any of you know how you would set this up in Qubes?
-- You received this message because you are subscribed to the
'Chökie Gyaltsen' via qubes-users:
> On Thursday, December 26, 2019 12:24 PM, 'awokd' via qubes-users
> qubes-users@googlegroups.com wrote:
>> In which log
>> are you seeing the above error?
>
> This message is from journalctl -ax and persisted after installation at
> everyboot until today
Thank you for the answers,Below i reply in bold.
Happy new year everyone!
‐‐‐ Original Message ‐‐‐
On Thursday, December 26, 2019 12:24 PM, 'awokd' via qubes-users
qubes-users@googlegroups.com wrote:
> > > > Dec 15 20:52:30 dom0 systemd-modules-load[195]: Failed to find module
> > > >
Aaron Janse:
> At this point, I got the black screen described in issue #5165 (3).
> Following
> the advice there, I updated my options line to the following:
> ```
> options=console=vga efi=attr=uc noapic x2apic=off loglvl=all efi=no-rs
> iommu=no-igfx dom0_mem=min:1024M dom0_mem=max:4096M
Spleen Productions:
>
>
> I have a HVM with a bootloader .ISO loaded in the VM.
> I would like to swap the cdrom and point it to another .ISO located in an
> AppVM.
> I cannot detach the device since i get an empty response from qubesd(see
> journalctl in dom0 for details).
> Is there any way
Robert M:
> Claudia,
>
> Sorry for the late reply. Here are my answers:
>
>- Yes, i modified the BOOTx63.cgf file in ANACONDA.
What were your modifications? Per
https://www.qubes-os.org/doc/uefi-troubleshooting/#installation-freezes-before-displaying-installer
? Try also
rickey:
> Good evening Everyone,
> I have installed previously Qubes 3.2.1 on a Dell's Optiplex 3010, Small
> form factor desktop pc, and I was able to use it.
> When I tried to install the Qubes versions mentioned above on the same
> hardware, it is showing the message into the attached
Claudia:
TLDR; check bottom of https://community.amd.com/thread/241650, looks
like there was a recently released related updated. Not sure if
applicable to your situation.
> This caused a very sneaky problem on my machine. My USB controllers are in
> the same group as my
> GPU, sound card, and
'Chökie Gyaltsen' via qubes-users:
> Thank you, i removed the alpha_support and with that the gtk errors i was
> having vanished along with the tainted kernel messages.
> Also noticed improvement of the speed of the graphics. Things appear to move
> smoother and faster screen. Does that make
Thanks, I'll check them out.
On Thu, Dec 26, 2019, 1:05 PM awokd wrote:
> Ondřej Šulák:
> > Hello everyone,
> >
> > I'm pretty new to QubesOS, and I have just start experimenting. I have
> > installed Qubes 3.2.1 (because of incompabilities with my HW), upgraded
> > Debian Template to Debian 10
Ondřej Šulák:
> Hello everyone,
>
> I'm pretty new to QubesOS, and I have just start experimenting. I have
> installed Qubes 3.2.1 (because of incompabilities with my HW), upgraded
> Debian Template to Debian 10 and also sys-whonix Service VM to Debian 10.
>
> When I try to run apt update in
Ray Joseph:
> I opened sys-usb settings and found the controller listed in the settings
> pane (on the right). The control button/bar at the bottom entitled
> "Configure strict reset for PCI devices". I clicked on the controller in
> the ‘selected’ window, then clicked the strict reset
tetrahedra via qubes-users:
> I haven't been able to find any documentation for what network
> interfaces sys-net is expected to expose internally. If I want to create
> my own sys-net from scratch, how does Xen/Qubes send network traffic to
> sys-net, to be sent onwards to my NIC?
>
There's a
Eva Star:
> Hello,
> To enable swap trim need to add "discard=once".
> The string at /etc/fstab will be like this?
> "*default,discard=once,x-systemd-device*"
> After editing fstab need to run something?
> Thanks
>
Yes, to the line:
/dev/mapper/qubes_dom0-swap swap swap
brendan.h...@gmail.com:
> If fedora were still running init, I'm pretty sure I could find the right
> place to do this, but with systemd, I am quite discombobulated.
Perhaps that is the "do one thing, and do it well" systemd strives for.
> 1. Where/how do I insert a thin_trim of the qubes_00
B. Kent:
>
>- Created the USB installer disk and then tried to modify the
>BOOTX64.cfg file (with VI), USB filesystem is Read Only
> - I've read that I need to mount the Qubes ISO on my laptop, edit
> BOOTX64.cfg from the ISO and then save that file...then create a new
>
26 matches
Mail list logo
