Hey all,
Over the last week I've noticed my laptops CPU keeps peaking @ 80-85
every now and then, even when I'm not doing any resource intensive
tasks.
I run 11-12 VMs @ a time which barely scratches the 34GB RAM on a P51
Thinkpad with a i7 7820HQ running in a standard temperature room
'npdflr' via qubes-users:
Hello all,
As stated in the link:
https://wiki.xen.org/wiki/Xen_PCI_Passthrough#How_can_I_check_if_PCI_device_supports_FLR_.28Function_Level_Reset.29_.3F
"For checking if PCI device supports FLR (Function Level Reset) one has to Run "lspci -vv" (in
dom0) and check if
Jon deps:
and sounds like no tutorial on non PS2, non laptop computers for USB
keyboards .
https://www.qubes-os.org/doc/usb-qubes
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails
qtpie:
I just did a fresh install of Qubes 4.0.1 to move to a larger ssd, and
then restored all qubes vms, except for sys-usb, sys-net and
sys-firewall. Before I was also running 4.0.1, that was upgraded from
3.1 via 3.2
I note that the startup time of both dom0 and vms is significantly
lower,
On Tuesday, March 12, 2019 at 7:57:15 AM UTC+1, dcabr...@gmail.com wrote:
> After updating Fedora and dom0 yesterday, today my laptop entered into a boot
> loop, stopping some seconds right after the initramfs line and re-booting
>
> Hardware: Lenovo X1 Carbon 6th Gen
> Booting with UEFI, dual
I just did a fresh install of Qubes 4.0.1 to move to a larger ssd, and
then restored all qubes vms, except for sys-usb, sys-net and
sys-firewall. Before I was also running 4.0.1, that was upgraded from
3.1 via 3.2
I note that the startup time of both dom0 and vms is significantly
lower, and the
Hello all,
As stated in the link:
https://wiki.xen.org/wiki/Xen_PCI_Passthrough#How_can_I_check_if_PCI_device_supports_FLR_.28Function_Level_Reset.29_.3F
"For checking if PCI device supports FLR (Function Level Reset) one has to Run
"lspci -vv" (in dom0) and check if the device has "FLReset+" in
Hello guys. Iam currently use thinkpad x220 for Qubes.
i7 ips 16gb ram 1tb ssd coreboot.
But it only good for PVH templates.
I just install i3wm and use debian-10 and fedora-30 as a builder templates to
build anything i want from scratch, for example, firmwares.
Thanks to Unman. because i
On 6/17/19 11:38 AM, brendan.h...@gmail.com wrote:
Chris - thanks for jumping on this. :)
On Monday, June 17, 2019 at 11:16:05 AM UTC-4, Chris Laprise wrote:
I would fully expect lvremove to issue discards, if lvm is configured
for it. Did you try changing /etc/lvm/lvm.conf so that
On Monday, June 17, 2019 at 11:32:50 AM UTC-4, Chris Laprise wrote:
> FWIW, if there were any issues with data not being discarded, it would
> be with the (size) mismatch between what ext4 considers a discarded
> block and what the thin + lvm layers consider a discardable block or chunk.
Yes,
Chris - thanks for jumping on this. :)
On Monday, June 17, 2019 at 11:16:05 AM UTC-4, Chris Laprise wrote:
> I would fully expect lvremove to issue discards, if lvm is configured
> for it. Did you try changing /etc/lvm/lvm.conf so that "issue_discards =
> 1" ?
I've got that set (also in dom0 &
FWIW, if there were any issues with data not being discarded, it would
be with the (size) mismatch between what ext4 considers a discarded
block and what the thin + lvm layers consider a discardable block or chunk.
If I wanted to solve this issue relatively quickly, I'd first consider
moving
On 6/17/19 10:28 AM, brendan.h...@gmail.com wrote:
There is a tool in dom0 called "thin_trim" which is part of the
"device-mapper-persistent-data" package. It issues discards to the unallocated space of a
dm-thin device that is not in use. This gets a bit trickier if it is an lvm2 device, as
> Do you have already newer kernel version installed? If so, dnf is picky
> and refuse to operate on older packages in most cases... But also
> shouldn't download old package when newer is already there, unless
> you've explicitly requested it to do so.
>
> But you don't have newer kernel (like
There is a tool in dom0 called "thin_trim" which is part of the
"device-mapper-persistent-data" package. It issues discards to the unallocated
space of a dm-thin device that is not in use. This gets a bit trickier if it is
an lvm2 device, as there's another management layer above the dm-thin
scurge1tl:
> Nice one. Where should I normally put the #!/bin/bash scripts in dom0?
> Is it ok to use /usr/bin or is it better to leave it for
> package-managed executables and have an another /bin?
> Thank you.
I put dom0 user scripts in ~. The #!/bin/bash at the top is a directive
for what
16 matches
Mail list logo
