I'm trying to update the kernel in the Debian Template of Qubes OS, following the official documentations, but it seems I'm missing something or doing something wrong. I'm using gcc 6.3.0.
**Qubes Docs:**
Installing kernel in Debian VM In Debian based VM, you need to install qubes-kernel-vm-support package. This package include required additional kernel module and initramfs addition required to start Qubes VM (for details see template implementation). Additionally you need some GRUB tools to create it’s configuration. Note: you don’t need actual grub bootloader as it is provided by dom0. But having one also shouldn’t harm. sudo apt-get update sudo apt-get install qubes-kernel-vm-support grub2-common Then install whatever kernel you want. If you are using distribution kernel package (linux-image-amd64 package), initramfs and kernel module should be handled automatically. If not, or you are building kernel manually, do this on using dkms and initramfs-tools: sudo dkms autoinstall -k # replace this with actual kernel version sudo update-initramfs -u When kernel is installed, you need to create GRUB configuration. You may want to adjust some settings in /etc/default/grub, for example lower GRUB_TIMEOUT to speed up VM startup. Then you need to generate actual configuration: In Fedora it can be done using update-grub2 tool: sudo mkdir /boot/grub sudo update-grub2 Then shutdown the VM. From now you can set pvgrub2 as VM kernel and it will start kernel configured within VM.
**Debian Docs:**
Don't be afraid to try compiling the kernel. It's fun and profitable. To compile a kernel the Debian way, you need some packages: fakeroot, kernel-package, linux-source-version. Hereafter, we'll assume you have free rein over your machine and will extract your kernel source to somewhere in your home directory. Make sure you are in the directory to where you want to unpack the kernel sources, extract them using tar xf /usr/src/linux-source-version.tar.xz and change to the directory linux-source-version that will have been created. Now, you can configure your kernel. Run make xconfig if X11 is installed, configured and being run; run make menuconfig otherwise (you'll need libncurses5-dev installed). Take the time to read the online help and choose carefully. When in doubt, it is typically better to include the device driver (the software which manages hardware peripherals, such as Ethernet cards, SCSI controllers, and so on) you are unsure about. Be careful: other options, not related to a specific hardware, should be left at the default value if you do not understand them. Do not forget to select “Kernel module loader” in “Loadable module support” (it is not selected by default). If not included, your Debian installation will experience problems. Clean the source tree and reset the kernel-package parameters: make-kpkg clean Now, compile the kernel: fakeroot make-kpkg --initrd Once the compilation is complete, you can install your custom kernel like any package. As root, do dpkg -i ../linux-image-version-subarchitecture.deb. For instance, the System.map will be properly installed and /boot/config-3.16 will be installed, containing your current configuration set. Your new kernel package is also clever enough to automatically update your boot loader to use the new kernel. If you have created a modules package, you'll need to install that package as well.
**The Debian Way Output:** ... ... ... This is kernel package version 13.014+nmu1. install -p -d -o root -g root -m 755 /usr/src/linux-source-4.8/debian/linux-image-4.8.15-rt10-11.pvops.qubes.x86_64/DEBIAN sed -e 's/=V/4.8.15-rt10-11.pvops.qubes.x86_64/g' -e 's/=IB//g' \ -e 's/=ST/linux/g' -e 's/=R//g' \ -e 's/=KPV/13.014+nmu1/g' \ -e 's/=K/vmlinuz/g' \ -e 's/=I/YES/g' -e 's,=D,/boot,g' \ -e 's@=A@amd64@g' \ -e 's@=B@x86_64@g' \ ... dpkg-gencontrol: error: illegal package name 'linux-image-4.8.15-rt10-11.pvops.qubes.x86_64': character '_' not allowed debian/ruleset/targets/image.mk:230: recipe for target 'debian/stamp/binary/linux-image-4.8.15-rt10-11.pvops.qubes.x86_64' failed make: *** [debian/stamp/binary/linux-image-4.8.15-rt10-11.pvops.qubes.x86_64] Error 255
**Manual compiling:**
I've downloaded linux-source-4.8 from Debian and I've extracted it in /usr/src. Then: make defconf make menuconf # custom settings make Same error as above: dpkg-gencontrol: error: illegal package name 'linux-image-4.8.15-rt10-11.pvops.qubes.x86_64': character '_' not allowed
I think this can be solved easily, but if I can compile the kernel manually, then how should I procede?
make install and make modules_install are required or I have to use dkms autoinstall directly? This isn't specified...

**UPDATE:** Installing directly the Debian package linux-image-amd64 make the console disappeared and the VM work unproperly, I tried to reboot it, but I could use it only by attaching to the serial console.
I noticed the dpkg crashed during installation, so I ran dpkg --configure -a and it finished the installation, but it showed a warning message that told with that initramfs, the machine would have never booted, in fact I updated GRUB and rebooted, but initramfs couldn't mount root.

I'd like to test Qubes OS using the Live USB Option. I used Rufus in order to create a bootable USB, changing the image from ISO to DD after opening the iso image. Then I changed the Boot priority to Legacy First. Nothing happened. Qubes OS fails to start the live session. What should I do? (I use Ubuntu 16.04.1) Help much appreciated. Thank you.

To startup vm called "sys-net" in Qubes on my laptop need to write "1" in file echo -n "1" > /sys/bus/pci/devices/0000\:04\:00.0/remove also 0000:04:00.0 and 0000:04:00.1 are conflicts and need to be removed first after every startup laptop. then network start and work fine. there is some input for information $ lspci | grep -i eth 04:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev12) $ find /sys -name *04:00.0 /sys/bus/pci/devices/0000:04:00.0 /sys/bus/pci/drivers/rtsx_pci/0000:04:00.0 /sys/devices/pci0000:00/0000:00:1d.3/0000:04:00.0 $ find /sys -name *04:00.1 /sys/bus/pci/devices/0000:04:00.1 /sys/bus/pci/drivers/pciback/0000:04:00.1 /sys/devices/pci0000:00/0000:001d.3/0000:04:00.1 How can I convert it to systemd script to run it at start-up? It works only temporarily. After reboot the network device is there again.

Is it possible to install the Ubuntu Software Applications, such as LibreOffice and others in Qubes OS? Thanks.

After burning Qubes iso on a USB stick using dd I boot it in UEFI mode and I got a problem with the following symptom : If I select Verify source and install Qubes the process freezes after the test passes. If I select Install Qubes I got this : Ignoring BGRT : invalid status 0 (expected 1) mce : unable to init device /dev/mcelog (rc:-16) /etc/vconsole.cong line 1: 1=: command not found /etc/vconsole.cong line 1: 1=: command not found sd 4:0:0:0:[sdb] no caching mode page found sd 4:0:0:0:[sdb] assuming drive cache : write through mount: /dev/sdb is write protected, mounting read-only And then the booting process freezes completely and I can only reboot with ctrl+alt+del. I have to add that the Qubes graphical logo blinks very briefly before it comes back to the command line and freezes. Any idea on what is happening ? Is there a way to activate a verbose mode so there is more detail on the failure reason ?

I tried Qubes OS and found out that it is too heavy and complicated for me. So I tried to install Debian from a flashed USB. However, the installer gives the following error: the logical volume vm-sys-net-private on qubes_dom0 could not be deleted I have a Bodhi Linux installer on another flashed USB and that gives the same error. Asking about this on the Qubes OS forum resulted in an answer suggesting the use of "dd if=/dev/zero of=/dev/sda bs=1M or something" I've been reading abouf the dd command and it seems to be a legit way of wiping out contents of a hard drive. lsblk gives the following output:

user@personal:~$ lsblk
NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
xvda    202:0    1    20G  0 disk
├─xvda1 202:1    1   200M  0 part
├─xvda2 202:2    1     2M  0 part
└─xvda3 202:3    1  19.8G  0 part /
xvdb    202:16   1     2G  0 disk /var/spool/cron
                                  /usr/local
                                  /home
                                  /rw
xvdc    202:32   1    10G  0 disk
├─xvdc1 202:33   1     1G  0 part [SWAP]
└─xvdc3 202:35   1     9G  0 part
xvdd    202:48   1 510.7M  1 disk

How should I wirte the dd command in order to succeed with the installer? If I wipe out everything, does the computer boot from the USB?

I have bought a fanless PC, and it is really important for me to have some form of power management for this PC, because currently I don't under Qubes, and the result is that if I do something that puts a lot of load on the CPU like playing a full-screen video in Firefox, the CPU overheats and the system (firmware?) automatically goes into emergency power-saving mode, which involves making the CPU go really slow. I have transferred responsibility to the Linux kernel for power management by adding cpufreq=dom0-kernel to the Xen command line. This doesn't help. I have then tried to switch from the intel pstate driver (which doesn't work with my Rocket Lake CPU, an Intel® Core™ i7-11700) to the acpi-cpufreq driver by adding intel_pstate=disable. This also doesn't help - sudo cpupower frequency-info shows "no or unknown cpufreq driver is active on this CPU". I then installed the latest version of thermald on my dom0 domain, but thermald is not able to find any temperature sensors:

[WARN]Thermal DTS: No coretemp sysfs found

I have ran sudo sensors-detect, but that didn't help. I have then ran modprobe processor_thermal_rapl and modprobe processor_thermal_device and restarted thermald, but it still showed the same errors. My motherboard is an Asus TUF GAMING B560M-PLUS WIFI. Please help me to enable some form of thermal throttling / frequency governor on this PC, other than the firmware's emergency thermal throttling.

I have a LUKS encrypted logical volume which is spread across two physical drives. I use the Qubes OS. The first drive is fine. I did a whoopsie with the partition table of the second drive. But the data on that drive seems to be OK. testdisk can find the windows partition and a little LUKS partition which I had. I managed to look into both and they are good. I *think*, and ChatGPT backs me up (clutching at straws), that there is a single LUKS header for the whole logical volume. I still have that LUKS header, which is on the first drive. On the second drive, in the place where the second part of the encrypted logical volume should start, I have data which looks like encrypted data. I know the UUID of the second part of the logical volume. I know the location of the data. I know the size. (I'm getting all this from dracut in the boot partition of the first drive. How can I recreate my needed partition? I can use testdisk to re-create the other partition (which is Windows, and which shows up in testdisk). But I didn't do it yet. I just backed up the data and the raw data with dd. Can I just use parted to create the partition on the spot where I have the data eg: sudo parted /dev/sdc mkpart logical 40000000s 42000000s Then set the UUID to be the one I need re-created tune2fs -U "4bac4411-201a-2a4d-ab0e-2e4a306a5bb2" /dev/sdb1 What is the problem with that? Hopefully this is only writing the partition table, not overwriting my data. Do I need to think about something more, like do I need to delete the partitions that are there already (which are crap set up by the process that went astray and got me here)

I have now tried about 20 times to install Qubes (on a Windows 11) system, and no matter what I try I keep hitting a brick wall incredibly early in the process. I can't even get to the Qubes installer proper, which I understand has a pretty logo and everything and is supposed to show up just to even really *start* the partitioning and installation process. Instead I just get a **blank screen** almost immediately! - If I choose the normal installation option from the GRUB2 menu, I get a blank screen immediately (though sometimes with an underscore cursor at top left). - If I choose the troubleshooting/verbose installation option from the GRUB2 menu, I see a few pages of output text, then the text all disappears (in a strange top-to-bottom wipe effect) **IMPORTANT LATE EDIT (WHOOPS!): The last line seen is "(XEN) Xen is relinquishing VGA console."** Either way I can't accomplish anything at that point other than powering off the computer (and once again contemplating giving up on Qubes). In a few of the 10 or so instances during which I was using a USB flash drive with a drive access light, that light continued to flash, but I've let it run for a good 15 minutes before and nothing else happened. My most basic attempt at installing Qubes was setting up a 128-GB USB flash drive with **Qubes-R4.1.1-x86_64.iso** using Rufus, with the GPT and UEFI options, in ISO/hybrid mode. Here are the many and varied workarounds I remember trying so far, based on everything I've been able to find online on this issue: - Setting up USB flash drive using Rufus in **DD mode** instead of ISO mode - Using a **different USB flash drive** (in case there was something wrong with the first drive) - Setting up USB flash drive using **Easy2Boot**, and dropping the ISO into that - Setting up USB flash drive using Easy2Boot, using the **Easy2Boot MPI_FAT32 file conversion utility** to convert the ISO (to DD mode? I don't remember now. It was one of the earlier attempts), then dropping the *converted* file into the Easy2Boot drive - Setting up a USB flash drive using **Ventoy**, and putting Qubes-R4.1.1-x86_64.iso on that - **Trying another Linux distro ISO, on the same drive as the Qubes ISO** (on that Ventoy (multi-boot) drive) and verifying the other distro launched with no problems - In BIOS, verifying **Secure Boot disabled** (this was the default setting) - In BIOS, **trying to switch from UEFI to MBR/legacy or CSM mode** (but not seeing that either of those other modes is possible with my BIOS). (I did read a little on flashing in a new BIOS, but I really don't feel like going down that road unless I *know* it will work and I know it is the *only* way to make this work) - Some **other BIOS settings changes** I don't remember the details of at this point - Using **Qubes-4.1.20221231-*kernel-latest*-x86_64.iso** (from https://qubes.notset.fr/iso/) (since fairly new hardware might only work with a fairly new kernel) - Using a third USB flash drive, this time an **8-GB drive** (since I heard in some cases the maximum drive size the system can read could be 8 GB) (and on that drive trying all four (non-multiboot) set-up combinations (Rufus ISO/hybrid mode and DD mode, basic ISO and latest kernel ISO)) - **At the blank screen, pressing every possible combination of modifier key and F-key** ([F1], [Shift]+[F1], [Ctrl]+[F1], [Alt]+[F1], [Shift]+[Ctrl]+[F1], [Shift]+[Alt]+[F1], [Ctrl]+[Alt]+[F1], [Shift]+[Ctrl]+[Alt]+{Fi], [F2}, ...), since I heard you can sometimes get some kind of CLI prompt that way Please help. This is crazymaking. At this point I've loaded my Ventoy drive up with *many* other Linux distribution ISOs, and maybe the only reason I'm still giving Qubes a chance is because I haven't settled on a second choice of distro yet! I did come across *yet another tactic*, which was changing some configuration variable values, either in the ISO or live during the install. I haven't tried that, though, because (for the ISO editing route) I don't know how to edit an .iso file, and (for the live variable setting route) I don't know how to interrupt things (even in the 10 luxurious seconds I would have in verbose mode before the screen goes blank) and live-edit those variables and resume things. (Note: I'm using the 'Linux' tag here because I don't know if this is an issue with just the Qubes distribution or with other distros as well, even though I have had success with one other distro.)

I've installed Qubes OS and try to install KDE with sudo qubes-dom0-update @kde-desktop-qubes as docs suggest, but it failed at the first try. I then ran into google and found that I've should use sudo dnf install apper breeze-icon-theme colord-kde dolphin kcm_systemd kde-runtime kde-settings-pulseaudio kde-style-breeze kdelibs kdeplasma-addons kdialog khelpcenter khotkeys kinfocenter kmenuedit kmix konsole5 kscreen ksysguard kwin phonon-qt5-backend-gstreamer plasma-breeze plasma-desktop plasma-desktop-doc plasma-pa plasma-user-manager plasma-workspace polkit-kde qt5-qdbusviewer sddm sddm-breeze sddm-kcm sni-qt I tried that and it installed some 300MB successfully just to find out that I've should use something else(below) instead and the previous method of installing lots of packages with dnf on dom0 is a big mistake. sudo qubes-dom0-update kde-settings-qubes So I did run this command and it successfully finished, but I don't get any visual changes. Do I need to do something else? What exactly the way to install latest qubes with kde please? Update: I'm currently re-installing qubes, because I'm getting some very odd behavior of the system(not shutting/restarting properly etc).

I'm trying to install Qubes OS on my computer. I have just deleted the Ubuntu Partition in order to install it, but there's a problem with the storage configuration, and I need to find a suitable stage1 device. There's nothing I can do... What should I be doing in such a case?

Qubes Devices does not see the camera, only the microphone. If I type lsusb the camera is visible: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 Root Hub Bus 003 Device 003: ID 1358:c123 Realtek Bluetooth Radio Bus 003 Device 002: ID 27c6:5110 Shenzhen Goodix Technology Co, Ltd. Goodix fingerprint device Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 Root Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 Root Hub Bus 001 Device 003: ID 0408:1040 Quanta Computer, Inc. ov9734_techfront_camera Bus 001 Device 002: ID 3151:3020 YICHIP wireless device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 Root Hub How to configure the camera please help. The camera is not on the list, If I type qvm-pci BACKEND:DEVID DESCRIPTION IS USED dom0:00_00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Root Complex dom0:00_00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 IOMMU dom0:00_01.0 Host Bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (models 00h-1fh) PCIe Dummy Host Bridge dom0:00_01.3 PCIe Bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] dom0:00_01.7 PCI Bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 PCIe GPP Bridge [6:0] dom0:00_08.0 Host Bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (models 00h-1fh) PCIe Dummy Host Bridge dom0:00_08.1 PCI Bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Internal Bridge PCIe GPP 0 to Bus A dom0:00_14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller dom0:00_14.3 ISA Bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge dom0:00_18.0 Host Bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: function 0 dom0:00_18.1 Host Bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 1 dom0:00_18.2 Host Bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 2 dom0:00_18.3 Host Bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 3 dom0:00_18.4 Host Bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 4 dom0:00_18.5 Host Bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 5 dom0:00_18.6 Host Bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 6 dom0:00_18.7 Host Bridge: Advanced Micro Devices, Inc. [AMD] Raven/Raven2 Device 24: Function 7 dom0:01_00.0 Non-Volatile Memory Controller: Sandisk Corp WD Black SN750 / PC SN730 NVMe SSD dom0:02_00.0 Network controller: Realtek Semiconductor Co. RTL8822CE 802.11ac PCIe Wireless Network Adapter sys-net dom0:03_00.0 VGA-compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso dom0:03_00.1 Audio Device: Advanced Micro Devices, Inc. [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio Controller dom0:03_00.2 Encryption Controller: Advanced Micro Devices, Inc. [AMD] 17h Family Platform Security Processor (Model 10h-1fh) dom0:03_00.3 USB Controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 dom0:03_00.4 USB Controller: Advanced Micro Devices, Inc. [AMD] Raven USB 3.1 dom0:03_00.5 Multimedia Controller: Advanced Micro Devices, Inc. [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor dom0:03_00.6 Audio Device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) HD Audio Controller In the manual for the documentation you left it said so. Also when entering qvm-usb: [ivan@dom0 ~]$ qvm-usb BACKEND:DEVID DESCRIPTION USED BY [ivan@dom0 ~]$

Is it worth installing VirtualBox with a Linux based distributed OS like Kali or Qubes if your hardware does not support iommu? Is there any benefit in regards to security if isolation is limited?

I already installed qubes it's booting to gui but i can't start any domain i keep getting this error. i have amd 5600x with amd-v enabled. i think it got something to do with csm being enabled which i believe will disable some virtualization feature but if i disable csm i can't boot into qube or reinstall the os this happens in second phase of installtion (after first reboot configuration) sudo cat /var/log/libvirt/libxl/libxl-driver.log

Primary OS is Qubes, secondary OS is Windows 10. I have a disk sda with full disk encryption (LUKS). But now I don't see my ext4 partitions on that disk and there only is one NTFS partition with a size of 50 MbL ... ... │ │ └─qubes_dom0-vm--sys--firewall--private 253:87 0 2G 0 lvm │ └─qubes_dom0-swap 253:5 0 7.3G 0 lvm [SWAP] └─sdb1 8:17 0 500M 0 part /boot/efi loop0 7:0 0 1G 0 loop sda 8:0 0 5.5T 0 disk └─sda1 8:1 0 50M 0 part What should I do and are there any solutions for this situation?

I am trying to install Qubes OS via an iso image on a USB stick. Version R4.0.4. I checked the release signing key and the hash value of the iso image. But the graphical installer keeps showing me a Debian11 logo, and says Debian11 everywhere. The official Qubes installation tutorial has photos in it indicating that it should say Qubes R.4.0.4 instead: https://www.qubes-os.org/doc/installation-guide/ While this is not strictly a technical problem, I wonder why this happens, and if it's safe to proceed with the installation. Edit @KnutLarsen: That's very weird. Mine looked just like this: And also after installation, it looks like a plain Debian11. Could it be that creating the installation stick with "Startup Disk Creator" is a problem?

Chromium, which I installed using snap, started hanging on startup. snap list hangs. snap changes hangs. snap version hangs. All the troubleshooting steps here result in either a hang, or an error, or no change in the situation. This is in a Fedora 32 VM on Qubes OS. The VM also hangs on shutdown, and has to be killed. A look at the console shows that it is hanging due to snap.

In Qubes OS, processes are running in multiple VMs, so just running top on a VM won't necessarily tell me anything useful, if that VM isn't using the CPU very much. How can I find out which process(es) is/are consuming the CPU and causing my fan to spin at a high speed, regardless of which VM they happen to be running on?

I currently run Arch Linux and I am considering moving to Qubes OS. I am spoiled by Arch's rolling release upgrade feature. I don't think Qubes OS supports rolling release. After I install Qubes OS, are future upgrades to new releases of the OS easy? Or do they involve a full rebuild of my system?

I have tried various ways to reconnect to my Bluetooth headphones in my Fedora VM after restarting my computer, but they all seem to either take a long time, or not work reliably. I have tried restarting pulseaudio, turning the Bluetooth adaptor off and on again, and turning the headphones off and on again. It's worth noting that I am also pairing the same Bluetooth headphones with my Android phone. I then tried suspending the PC instead of shutting it down, but unfortunately after resume all of the USB devices, including the internal Bluetooth adaptor, are disconnected from the VM by Qubes OS, so then I face the same problem.