Re: [qubes-users] xentop's disk I/O
On Sun, Nov 6, 2022, 9:29 AM Ulrich Windl wrote: > Hi! > > Watching xentop, I have a question: > I know that the network operations aren't accounted in xentop when > running Qubes OS, but I'm wondering: > For domain-0 all of the disk I/O (VBD_RD, VBD_WR, VBD_RSECT, VBD_WSECT) > also seem to be zero, This is because dom0 does not use paravirtualized disk drivers. Specifically, no Xen block backend device in dom0 is connected to a block frontend device in dom0, since the latter does not exist. Instead, dom0 accesses disks directly like a bare-metal OS. If you want disk I/O statistics for dom0, you want to use something like iotop. and for sys-net-dm all the writes seem to be zero. > DM stands for "device model," a main role of which is to emulate the physical (i.e. non-virtualized) hardware for HVM guests that do not have the paravirtualized device drivers installed. If sys-net has all the necessary paravirtualized drivers (which almost always is the case), sys-net does not need the DM to access the disk. This is why sys-net-dm does not access the disk after boot. Is it because sys-net is a "HVM"? > No. You'll observe non-zero disk I/O numbers in the DM when you boot e.g. a Windows HVM without Xen paravirtualized disk drivers. > Regards, > Ulrich Windl > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAMnQwqVcyNL4n5v1apKxbFXML2dThJGXVC_70dMk1xQVa8ckHQ%40mail.gmail.com.
[qubes-users] xentop's disk I/O
Hi! Watching xentop, I have a question: I know that the network operations aren't accounted in xentop when running Qubes OS, but I'm wondering: For domain-0 all of the disk I/O (VBD_RD, VBD_WR, VBD_RSECT, VBD_WSECT) also seem to be zero, and for sys-net-dm all the writes seem to be zero. Is it because sys-net is a "HVM"? Regards, Ulrich Windl -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2ac2c5f7-cff2-968d-9456-59dcbb45515f%40rz.uni-regensburg.de.
Re: [EXT] Re: [qubes-users] Re: Task bar disappeared?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Sun, Nov 06, 2022 at 12:52:19AM +0100, Ulrich Windl wrote: > On 10/28/22 19:52, 'Stuart Perkins' via qubes-users wrote: > > > > On Fri, 28 Oct 2022 09:55:18 -0700 (PDT) > > Scat wrote: > > > > > Update: > > > - I typed: xfce4-panel into the Dom0 terminal > > > - I received errors in the Dom0 terminal and as mentioned the Task bar > > > appeared > > > > > > It didn't survive a reboot of my computer. I typed: xfce4-panel into Dom0 > > > it appeared... > > > > > ... > > I had a similar problem with the desktop wallpaper under Qubes 4.0. It > > went away after doing something similar. > > For a working journaled filesystem I'd expect that only items that were > changed while the power failed would disappear (when the incomplete > transaction is undone). Looks like some bug. > Maybe your disks use local caching or some other volatile write-back cache > (known to fail with journaled filesystems)? It will only fail if one of the following is true: 1. The filesystem does not properly issue FLUSH and/or FUA commands. 2. The disk does not properly implement these commands. 3. Qubes OS is not properly issuing fsync(). - -- Sincerely, Demi Marie Obenour (she/her/hers) Invisible Things Lab -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEdodNnxM2uiJZBxxxsoi1X/+cIsEFAmNm+pAACgkQsoi1X/+c IsHAoQ//b3yv3bhZwqgCrsE684oxOj3fMVU7FS2JX8xU0eBje1+1JATF9++uSVy0 V5/HA3K1oxv7k7CzHmjfEZfMF1ylw8wYFexUGHxs6RR6QdvhH851QZlc7XBBgRoL 1+M4S8zBiSdGg0YdI6O4BBlgkhOlL6nZO9GGlQ+iUafduHX8oFOLGFoPFBcz0N1h +wRVNFklWX5sr7CxVfN+++LDrJdDrHON3pSgRHesCRyKOxobiAjoZLfrLCdTyGAV 5jyfpfW5klfne2wL3LQMEv7eP6aYrc94sYigQeb4b0MgcJS6KbGIEKwsqOxisTnx nXjfnEKHH8y4zVZFmNvp9p8aQFqyQ+qQHF+Fyu6yCvdPS+whT+kTlBSaq0wC4VaT jlsNbHB3EleVMoO0IbQZcnmP+JFDcrCHZrvI15AknHo8FcqkxMcAHt1ENyibD324 D+WLXApYxX7u1dHmjUAzMl04qS5pVdw2+yPDQVvPe09lIUeyPH5Xsd+gT0fNlEuq xGR5F8UxqaP5OWHpq+zlSO63fwy/nxKp6CX6Z9hLdYjqUdTeeDMWK2UplN/457Qd qOM4nvTBkuo5RWnl4WikjxX/BRBnjAoHcun/e7XWvn6Jq9ydFDRESK6ozbgoGFO/ QVdweJiIk39KY+7ieTozaytAOY+vzeGcSEJObT9czrQBmNgoBGw= =8YcW -END PGP SIGNATURE- -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/Y2b6kTePur0StEzo%40itl-email.
Re: [EXT] Re: [qubes-users] Re: Task bar disappeared?
On 10/28/22 19:52, 'Stuart Perkins' via qubes-users wrote: On Fri, 28 Oct 2022 09:55:18 -0700 (PDT) Scat wrote: Update: - I typed: xfce4-panel into the Dom0 terminal - I received errors in the Dom0 terminal and as mentioned the Task bar appeared It didn't survive a reboot of my computer. I typed: xfce4-panel into Dom0 it appeared... ... I had a similar problem with the desktop wallpaper under Qubes 4.0. It went away after doing something similar. For a working journaled filesystem I'd expect that only items that were changed while the power failed would disappear (when the incomplete transaction is undone). Looks like some bug. Maybe your disks use local caching or some other volatile write-back cache (known to fail with journaled filesystems)? Regards, Ulrich Stuart -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/71596238-68a4-292d-6294-6071b689d7d8%40rz.uni-regensburg.de.
[qubes-users] HCL - XPS 17 9720
---layout: 'hcl' type: 'notebook' hvm: 'yes' iommu: 'yes' slat: 'yes' tpm: 'unknown' remap: 'yes' brand: | Dell Inc. model: | XPS 17 9720 bios: | 1.4.0 cpu: | 12th Gen Intel(R) Core(TM) i9-12900HK cpu-short: | i9-12900HK chipset: | Intel Corporation Device [8086:4641] (rev 02) chipset-short: | FIXME gpu: | Intel Corporation Device [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev a1) (prog-if 00 [VGA controller]) gpu-short: | Intel Iris Xe GeForce RTX 3060 Mobile network: | Intel Corporation Device 51f0 (rev 01) memory: | 65220 scsi: | usb: | 5 versions: - works: 'yes' qubes: | R4.1 xen: | 4.14.5 kernel: | 6.0.2-2 remark: | FIXME credit: | FIXAUTHOR link: | FIXLINK --- Graphics Issues With Solutions: Install using disabled graphics, while following: https://www.qubes-os.org/doc/installation-troubleshooting/#not-asking-for-vnc-because-we-dont-have-a-network--x-startup-failed-aborting-installation--pane-is-dead-error-during-installation Video with the integrated graphics work on the latest Linux kernel supported by R4.1. On Kernel version 5.16 there were issues with the i915 drivers (of course), but those went away with 5.18 if I remember correctly. These features are still working on 6.0.2-2.fc32. I had an issue where I was having artifact from my Intel GPU after installation. I found the fix from here: https://github.com/QubesOS/qubes-issues/issues/7507#issuecomment-1153081021 The following is a slimmed down version of what needed to be in the config. /etc/X11/xorg.conf.d/99-intel.conf > Section "OutputClass" > Identifier "Intel" > MatchDriver "i915" > Driver "intel" > EndSection PCI(e) Pass-Through Solutions: PCI(e) pass-through had to be enabled by disabling the raid option so that VMD works as per https://github.com/QubesOS/qubes-issues/issues/6932#issuecomment-1084468446 I have not tested PCI(e) yet, but I plan to soon and write a guide for gaming potentially. Graphics Issues W/O Solutions: The resolution seems to be stuck as 4k with this config. I have tried i3, KDE, and of course I stuck with Xfce due to the support. Probs a side effect of what I did to the XOrg conf. I haven't looked into it that much. If you care about high dpi issues check out the arch Linux wiki on Xfce High-DPI: https://wiki.archlinux.org/title/HiDPI#Xfce Mouse Issues W/O Solution: There may be an issue with the mouse, however I can not quite tell to be honest if it is my physical hardware or software limitations. Lastly, there seems to be an issue with the speakers not working, however, I don't use them. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f526cwM_6iFaPKL45wgNMkukfnA2d33jhceRe9_Ma3hbzmgIIiKk64pX2w_eq0vxoutiugeKR3oemQBuffbMgz7LgkslQpnIIq-vB91x4o0%3D%40protonmail.com. publickey - FileMagic@protonmail.com - 0xC318E816.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
